How can I trust ROMs?


My device is a few years old (it's a Wiko Ridge 4g) and the last official update was Lollipop 5.0.2. This means I can't get security patches anymore, and the recent Meltdown and Spectre attacks made me think about how bad that is.

From what I have read if the manufacturer does not provide updates I have to get a custom ROM, downloaded from somewhere, or give up and get a new device. I am not opposed in principle to flashing a ROM but how can I trust the source (and the tools)?

Background: I am a software developer but know next to nothing about the whole mobile ecosystem.


"Trust" is a small world for a large field. You have to look at each variant individually:

Trust that the custom ROM does not brick your device or destroy smartphone components

The more people use a specific custom ROM, the more likely all serious problems are known and may be even already fixed. For that reason, I personally prefer LineageOS-based ROMs without any modifications (or the minimum to support the specific device).

Trust that the custom ROM does not contain malware

I assume that purposely infected ROMS are very unlikely. Most custom ROMS are created by experienced developers that are active for years. Publishing an infected ROM would result in a loss of reputation for such people. As a lot of users use their ROMs rooted, the chance is high that the infection would be detected. Therefore (as long as the developer account has not been hacked), infected ROMs are unlikely.

However, I would recommend to check the history of the author and only use popular ROMs from XDA-Developers or better those directly provided by Lineage OS.

Tust that there are no backdoors or similar

Custom ROMs contain a lot of compiled code. Especially the kernel and other sensitive software running with high privileges is usually compiled by the author. Even if the sources for the kernel used by the ROM are public (and is free of backdoors and so on), it is a common problem to prove that the source code is really the one used to build the kernel. Detecting something malicious in a kernel or a different compiled software is very problematic.

Again, you have to trust the author of the custom ROM...

Trust that the all security features work as intended

The main factor of security is that some actions are forbidden/denied for certain entities. The usual testing approach of custom ROMs is "it works for me". Therefore, I assume that most of the security features are not well-tested in custom ROMs. If something goes wrong in the build process, it may remain undetected for a long time.

One common problem for example is that custom ROMs are signed with AOSP private key (which is public). Therefore, it is easy for malware developers to sign an app with the system keys to gain special system permissions.


2D Engines   3D Engines   9-Patch   Action Bars   Activities   ADB   Advertisements   Analytics   Animations   ANR   AOP   API   APK   APT   Architecture   Audio   Autocomplete   Background Processing   Backward Compatibility   Badges   Bar Codes   Benchmarking   Bitmaps   Bluetooth   Blur Effects   Bread Crumbs   BRMS   Browser Extensions   Build Systems   Bundles   Buttons   Caching   Camera   Canvas   Cards   Carousels   Changelog   Checkboxes   Cloud Storages   Color Analysis   Color Pickers   Colors   Comet/Push   Compass Sensors   Conferences   Content Providers   Continuous Integration   Crash Reports   Credit Cards   Credits   CSV   Curl/Flip   Data Binding   Data Generators   Data Structures   Database   Database Browsers   Date &   Debugging   Decompilers   Deep Links   Dependency Injections   Design   Design Patterns   Dex   Dialogs   Distributed Computing   Distribution Platforms   Download Managers   Drawables   Emoji   Emulators   EPUB   Equalizers &   Event Buses   Exception Handling   Face Recognition   Feedback &   File System   File/Directory   Fingerprint   Floating Action   Fonts   Forms   Fragments   FRP   FSM   Functional Programming   Gamepads   Games   Geocaching   Gestures   GIF   Glow Pad   Gradle Plugins   Graphics   Grid Views   Highlighting   HTML   HTTP Mocking   Icons   IDE   IDE Plugins   Image Croppers   Image Loaders   Image Pickers   Image Processing   Image Views   Instrumentation   Intents   Job Schedulers   JSON   Keyboard   Kotlin   Layouts   Library Demos   List View   List Views   Localization   Location   Lock Patterns   Logcat   Logging   Mails   Maps   Markdown   Mathematics   Maven Plugins   MBaaS   Media   Menus   Messaging   MIME   Mobile Web   Native Image   Navigation   NDK   Networking   NFC   NoSQL   Number Pickers   OAuth   Object Mocking   OCR Engines   OpenGL   ORM   Other Pickers   Parallax List   Parcelables   Particle Systems   Password Inputs   PDF   Permissions   Physics Engines   Platforms   Plugin Frameworks   Preferences   Progress Indicators   ProGuard   Properties   Protocol Buffer   Pull To   Purchases   Push/Pull   QR Codes   Quick Return   Radio Buttons   Range Bars   Ratings   Recycler Views   Resources   REST   Ripple Effects   RSS   Screenshots   Scripting   Scroll Views   SDK   Search Inputs   Security   Sensors   Services   Showcase Views   Signatures   Sliding Panels   Snackbars   SOAP   Social Networks   Spannable   Spinners   Splash Screens   SSH   Static Analysis   Status Bars   Styling   SVG   System   Tags   Task Managers   TDD &   Template Engines   Testing   Testing Tools   Text Formatting   Text Views   Text Watchers   Text-to   Toasts   Toolkits For   Tools   Tooltips   Trainings   TV   Twitter   Updaters   USB   User Stories   Utils   Validation   Video   View Adapters   View Pagers   Views   Watch Face   Wearable Data   Wearables   Weather   Web Tools   Web Views   WebRTC   WebSockets   Wheel Widgets   Wi-Fi   Widgets   Windows   Wizards   XML   XMPP   YAML   ZIP Codes