Database Info

[TOOL][Forensic] Andriller - data acquisition from Android devices

Moderators: if this thread is in wrong place please forgive and move it to a location best suitable for this thread.
Self-introduction I come from law-enforcement digital forensics background aimed at data extractions from mobile devices.
I would like to introduce a tool that I created.
Andriller
http://andriller.com
Andriller is a Windows GUI forensic tool, that performs read-only, forensically sound, non-destructive acquisition from Android devices. The executable is run from a terminal or by executing directly; it produces results in the terminal window, and a report in a HTML format.
Usage:
Download Andriller from the download page and install. To use the software you need to obtain a license key (free trial available). Instructions on doing this will be provided on the page
Note: Android version 4.2.2+ requires to authorise the PC to accept RSA fingerprint. Please do so, and tick the box to remember for future.
Note: Devices with Superuser or SuperSU App require to authorise root access from an unlocked screen. Please grand permissions if requested.
Description:
Once andriller is executed, it will produce permilinary results in the terminal window; for rooted devices it will download and decode the content automatically. It will produce a new folder in the location where it was executed, where the main "REPORT.html" file can be opened in a web browser.
Supported data extraction:
Non-root devices (Android versions 2.x):
- Android device make and model
- IMEI, build version, OS version
- Wifi mac address
- Time and date check
- SIM card details (for a some Galaxy Sx devices only)
- Synchronised accounts
Non-rooted devices (via backup method, Android versions 4.x and above)
- Wi-Fi passwords (WPA-PSK/WEP)
- Call logs (Samsung) register
- Android browser saved passwords
- Android browser browsing history
- Google Chrome saved passwords
- Google Chrome browsing history
- Facebook* chat messages
- Facebook* user viewed photographs
- Facebook* user notifications
- WhatsApp* contacts list
- WhatsApp* chat messages
- Kik Messenger* chat messages
- BBM* chat messages (Blackberry Messenger)
- Viber* chat messages
Rooted devices (via root adbd or 'su' binary, any Android versions):
- Security lockscreen pattern gesture extraction (decoding online)
- Security lockscreen PIN code cracking (up to 8 digits long)
- Wi-Fi passwords (WPA-PSK/WEP)
- Synchronised accounts and profile picture
- Bluetooth mac address and name
- Phonebook contacts
- Call logs register
- Call logs (Samsung) register
- SMS messages
- Android browser saved passwords
- Android browser browsing history
- Google Chrome saved passwords
- Google Chrome browsing history
- Facebook* friends list
- Facebook* chat messages
- Facebook* user viewed photographs
- Facebook* user notifications
- WhatsApp* contacts list
- WhatsApp* chat messages
- Kik Messenger* chat messages
- BBM* chat messages (Blackberry Messenger)
- Viber* chat messages
* = if an Application is installed
Disclaimer:
Andriller comes with absolutely no warranty. Even though Andriller was written in a way to be a forensically sound read-only utility, I do not take any responsibility to any damage or harm caused to your computer systems or your Android devices, which may be believed to have been caused by executing Andriller. I also do not take any responsibility of any unsolicited, non-consensual or unlawful misuses of this utility. It is the end user's responsibility to believe an appropriate consent or a lawful excuse was obtained if the utility is used with an other's Android devices, and they are aware what the utility does.
Visit http://andriller.com to download the latest software

Andriller performing AB extraction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reporting in HTML
Android Decoders
Password Cracking

Update 14/10/2013
Version 1.0.0a
Python-based compiled executable for MS Windows uploaded.
http://andriller.com
Update 07/11/2013
Version 1.1.0a
Added support to the latest Facebook App.
Minor improvements to decoding method.
Updated 13/01/2013
Version 1.2.0a
Added support for:
- Lockscreen PIN cracking
- Wi-Fi passwords
- Android web browser
--- Saved passwords
--- Browsing history
- Google Chrome web browser
--- Saved passwords
--- Browsing history
- Synchronised accounts
- Kik Messenger
- BBM (Blackberry Messenger)
Improvements to downloading and decoding.
Minor bugs fixed.
Updated 03/02/2013
Version 1.3.0a
Added support for:
- Data extraction via backup method (android version 4.x), no need for root.
Updated 17/02/2013
Version 1.3.1a
Added support for:
- Android (default) E-mail client:
--- Account and passwords
--- E-mails support
Minor bugs fixed.
Updated 21/02/2013
Version 1.3.2a
Improved data handling.
Bugs fixed for PIN cracking.
Updated 01/04/2014
Version 2.0.0
Graphical User Interface (GUI) - for Windows XP/Vista/7/8
Lockscreen cracking for:
--- Pattern
--- PIN
--- Password (using a wordlist file)
Decoding of individual of databases
Also includes all features from previous versions of Andriller
Requires registration, free 7 days license
Updated 19/04/2014
Version 2.0.1
Transferred to andriller.com domain
- Minor bugs fixed
- Added support for decoding Grindr App messages & users (Apple iOS)
- Window size reduced to accommodate smaller resolutions
- Default font changed to Consolas
- License key filename is now stored as the unique id
Updated 29/04/2014
Version 2.0.2
- Installer; Andriller now comes as a Setup Installer for Windows
- Improved PIN and Password cracking speed of up to 48% faster than previously
- Minor bugs fixed
- Some descriptions clarified
Updated ??/05/2014
Version 2.0.3
- Decoders in menus were fixed for error handling
- Typing mistakes corrected (oops)
- Minor improvements all-round
Updated 14/05/2014
Version 2.0.4
- Added support for Viber Messages chat (Android)
- Fixed a bug in Email decoder, so the feature is working now
- Chrome web browser decoding works for any mobile/desktop operating system (Android, iOS, Windows, Unix, Mac)
- Fixed Facebook chat messages decoding for the latest App version
- Decoders; if [Output] if chosen, the decoded data will be saved there; else the decoded data will be displayed in a temporary directory
- Error handling improved within file browsing/saving, license key registration

seriously awesome dude
dude i am working on presentation on forensics ill surely give out your tool in the first place all the others congs :angel::angel::angel:

stealthroot said:
dude i am working on presentation on forensics ill surely give out your tool in the first place all the others congs :angel::angel::angel:
Click to expand...
Click to collapse
Thanks buddy, all the best luck with your presentation and forensics! :good:

Andriller is awesome, customer of yours since half a year, cannot recommend it enough.
This deserves a bump.^^

Hi.
Does your tool support retrieving (at least as a read-only) applications installed and their data from dead Android phones (particularly from those which are not rooted and stuck on boot and showing only logo)?
Do you know any other open-source solution for this?
Thank you.

john2014 said:
Hi.
Does your tool support retrieving (at least as a read-only) applications installed and their data from dead Android phones (particularly from those which are not rooted and stuck on boot and showing only logo)?
Do you know any other open-source solution for this?
Thank you.
Click to expand...
Click to collapse
What you are looking for does not exist (to my knowledge). There isn't a single tool to magically repair half-broken Android devices. It's handset make model dependant. This will require extensive manual interactions to repair boot loops, re-flashing individual partitions, etc. If not successful, the options left are JTAG or even chip-off.

den4uk said:
What you are looking for does not exist (to my knowledge). There isn't a single tool to magically repair half-broken Android devices. It's handset make model dependant. This will require extensive manual interactions to repair boot loops, re-flashing individual partitions, etc. If not successful, the options left are JTAG or even chip-off.
Click to expand...
Click to collapse
Thanks for your reply.
Actually, what I want primarily is not to repair the device itself, but to extract some apps installed with their data which are important.
If there is no a single solution, could you please tell what open source solutions can be used as a complex in this case and what sources would you advise to read (as a starting point and to have a general idea) in order to get a better understanding of possible solutions for this kind of problems?

Andriller is actually working!!!!
Thanks !

Thanks 4 this very useful tool!
At work i use UFED and XRY to aquire and analyse mobile datas...
...but this tool is definitly worth to use beside this two programs.... :good:
greets from austria
chris_forens!c

what is andriller reg. key

Can't extract/decode call logs
I'm able to extract the backup, but I'm not getting call logs for some reason. Is there a different way I should be using the decoder? I ran the adb extraction and got account info, phone MAC, build, wifi passwords and download history. After playing around a bit, I extracted the ab image using 'tools' then parsed the extracted folder which gave me chrome saved passwords and chrome history. I tried parsing .tar and .ab files extracted and didn't get anything useful. Using the call log decoder, i tried to access the com.android.calllogbackup file but theres only a manifest file there (no .db). Any advice on getting call/text logs? Will i need to root the phone? Its a Samsung Galaxy On5, on 6.0.1

[APP][4.0.3+] Facebook Patcher 100+ -Avoid using Messenger, send messages from FB app

PATCHED APK'S HERE - by @wolfballz
What to do if you don't want to use Messenger, rather to send messages from the Facebook app itself?
a) If you'd like to use the voip function, use 55.0.0.18.66 patched.
Do NOT use the unpatched app with Messenger 1.0 because it won't let you see your messages, instead it will ask you to update Facebook.
b) If you don't care about voip calls, but need Facebook's new features and a rich messaging interface like in Messenger, use either 85.0.0.0.18 patched or 78.0.0.16.67 patched (both for ARM only).
It also offers some extra features that the APK patched with 2.9 doesn't have:
● Version modified to 999 so the app won't ask you to update.
● Fixed crash when opening gallery from composer.
● No duplicate emoji buttons in composer.
● Bubble style delivery state icons like in Messenger.
● Blue title bar to fit FB's design (v85 only).
c) If you'd like to stay up-to-date, you can always patch the latest version using Facebook Patcher 100+. The latest version where message notifications work is 106.0.0.26.68. Note that you'll only see the mobile messaging site in the in-app browser on the latest versions!
● 106.0.0.26.68 patched for ARM devices (51.9 MB)
● 106.0.0.26.68 patched for x86 devices (54.8 MB)
FEATURES
● Send messages directly from the main Facebook app without the need to install Messenger.
● Send emojis and stickers.
[The following features aren't offered by Facebook Patcher 100+, just by FBPatcher 2.9 up to version 85.0.0.0.18]
● Use QuickCam to capture & send images and short videos instantly.
● Edit images and videos before sending them.
● Share images from conversations to Facebook.
● Send hot likes, audio clips, events and locations.
● See cool snow fall and floating hearts when sending the appropriate emojis.
● Play Messenger's basketball and soccer game (unfortunately, without score submission).
[The following features are only applicable to Facebook Patcher 100+]
● No matter what variant you download, the patched APK will be a 4.0.3+ one.
● Removes lots of junk from the APK and compresses it --> much smaller app size!
USAGE
0. Install the latest Java runtime if you don't have it yet.
1. Download a Facebook APK from apkmirror.
2. Download the patcher (from V100, use Facebook Patcher 100+), start it with double click and follow the instructions.
3. Uninstall the official Facebook app.
4. Copy the patched apk to your device, install and enjoy!
TROUBLESHOOTING
Can't start the patcher
Firstly, update to the latest Java -- the patcher requires version 1.8 at least. If you can't start it with double click on Windows, you should associate jar files with 'javaw.exe' (NOT 'java.exe' as it won't work). It's in the bin folder of your Java installation (typically 'Program Files\Java\jre*').
On Linux/Mac, you should use 'chmod +x' on the jar file before the first run to get execution permission. Google it if you're not familiar with that command.
Got an error while patching
● Most likely: Facebook changed something in the code, please wait for patcher update.
● Very unlikely: you don't have enough space (<100MB) for the patcher's temporary files.
● Very unlikely: APK file is corrupted, try to download it again.
If nothing helps, post a log or screenshot here.
Can't install patched APK
● You have the official Facebook app installed, you should uninstall it first.
● You have it preinstalled (flashed on 'system') -- you can only get rid of it with root, sorry, not my fault.
● You're trying to install a 4.0.3+ variant over a 5.0+ one and vice versa, uninstall the app first.
● You're trying to install a 5.0+ variant on a pre-Lollipop system, try patching & installing a 4.0.3+ variant.
Patched app quits on start
● If you've just updated to a patched alpha, you may have to clear app data before first start. Some alphas may get in an infinite loop on start if old app data is present. This is not the patcher's fault, the original app also has this issue.
● It's very likely that you've downloaded an APK built for an architecture that's different from your device's one. For example, you have an x86 device and installed an ARM APK that won't work. Since x86 mobile devices are rather rare, you could hardly find any x86 APK's. To obtain one for your device, you should install it from Google Play and save the APK with a backup application or Total Commander. Then you can pull it to your PC and patch it. Don't forget to uninstall the original app before trying to install the patched one!
KNOWN ISSUES
These issues are known and can't/won't be fixed.
● On some versions prior to 75.0.0.23.69 the app crashes when scrolling down 20 messages in thread list, this is not the patcher's fault, use a later version to avoid this bug (85.0.0.0.18 is recommended).
● Back and info buttons on title bar, GIF and Payment buttons don't do anything.
● On Android 6.0+, clicking the blue button in the Messenger permission request window causes a crash. Grant the permissions for the app from Settings/Apps.
● Your basketball and soccer score won't be submitted to the thread.
● From v107, message notifications don't work because Facebook messed up something - use v106 stable instead.
QUESTIONS & ANSWERS
Q: What does it do to the Facebook app?
A: FBPatcher is a desktop Java application that needs a Facebook APK file as input and will provide you a patched APK as output, with Messenger functionality. It only does minimalistic (but yet not trivial) modifications to some classes and the manifest, new code isn't inserted into the app -- the Messenger window with all of its resources and code is in the original APK, this patcher just makes it accessible.
Q: Will the patched app be updated via Play Store?
A: No, you should always download, patch and install the latest version manually to be up-to-date.
Q: Is there any way to make VoIP calls working?
A: From V56, no. Use 55.0.0.18.66 if you need free calls.
DESCRIPTION
Operations performed by the patcher
● Extracts manifest and dex files.
● Finds patchable classes in the dex files by searching for patterns that identify those classes.
● Disassembles dex files that contain patchable code, automatically modifies the classes and reassembles the files.
● Patches the manifest to remove FB specific permissions and modify the Messenger window's theme.
● [100+ only] Reduces app size by removing unused files.
● Updates the APK with the patched files and signs it.
List of patched stuff
● AndroidManifest.xml -- modifies ThreadViewActivity's theme and removes FB specific permissions to allow other FB apps to be installed, also adds CreateThreadActivity again.
● ForceMessenger -- enables in-app messaging.
[The following classes don't exist from a specific version / aren't touched by Facebook Patcher 100+]
● MessengerMSiteUriIntentBuilder -- creates entry points for Messenger code instead of mobile messaging site, also enables some features.
● DiodeMessengerActivity -- replaces the 'Install Messenger' Fragment with Messenger thread list.
● ThreadListFragment -- defines an on-click event for thread list items (ThreadViewActivity will be opened with the selected thread / mobile site will show up when tapping message request).
● FacebookActivityDelegate(Impl) -- crash fix for ThreadViewActivity.
● MuteThreadWarningNotification -- crash fix for ThreadViewActivity.
● BballView(.3) -- crash fix for basketball game.
● SoccerFeedbackEmojisView -- crash fix for soccer game.
● MessagesVideoConfigModule -- Enables gallery video sending/transcoding.
● InboxFilterManager.NoSaveStateBehavior -- was missing, added again
● TwoLineComposerView -- remove Payment button action
● ThreadListContextMenuHelper -- remove 'Mute thread' option
Included third party libs
● XZ for Java by Tukaani
● smali/baksmali by JesusFreke
● SignApk (part of AOSP)
Click to see licenses.
Licensing of XZ for Java
All the files in this package have been written by Lasse Collin and/or Igor Pavlov. All these files have been put into the public domain. You can do whatever you want with these files.
This software is provided "as is", without any warranty.
Licensing of smali/baksmali
[The "BSD licence"]
Copyright (c) 2010 Ben Gruver (JesusFreke)
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Licensing of SignApk
Copyright (C) 2007 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.
FOR ADVANCED USERS ONLY -- If you place a file called 'fbpatcher.dev' next to the FBP100+ jar file, containing the following text: 'I want my intern settings menu!', internal settings will be enabled in the Facebook app.
Free of Facebook code.
WHAT'S NEW
Version 2.9, 07-21-2016
● Support for latest versions (web view messaging only)
Version 2.8, 07-06-2016
● Fixed crashing new message option (mobile site fallback)
● Patchability check (does not proceed if Messenger code is missing)
Version 2.7, 06-25-2016
● Support for message requests
Version 2.6, 06-17-2016
● Fixed new message option for 83.0.0.0.39
Version 2.5, 06-16-2016
● OS native look and feel with support for high DPI displays
● Sticker search feature
● Fixed new soccer game
● Removed crashing options (mute thread & payment)
Version 2.4, 06-08-2016
● Same as 2.3 but has a GUI
● Reduced size (425KB)
Version 2.3, 06-04-2016
● Support for latest versions (tested up to 81.0.0.0.49 alpha)
● Reduced size thanks to proguard
Version 2.2, 06-01-2016
● Support for latest versions (tested up to 81.0.0.0.20 alpha)
● Removed aapt without losing backwards compatibility
Version 2.1, 05-30-2016
● Support for latest versions (tested up to 80.0.0.0.44 alpha)
● Much faster patching (dex files are assembled in memory)
Version 2.0, 05-26-2016
● 'New message' function: tap [<-] button on title bar in thread list
Version 1.9, 05-25-2016
● Support for latest versions (tested up to 80.0.0.0.18 alpha)
● Resource name obfuscation resistance
Version 1.8, 05-21-2016
● Bugfixes for latest stable and beta versions
Version 1.7, 05-21-2016
● Support for latest versions (tested up to 79.0.0.0.52 alpha)
Version 1.6, 05-20-2016
● Support for latest versions (tested up to 79.0.0.0.39 alpha)
● Basketball game re-fix
● Much faster and error-free patching
● APK verification
● Reduced size (removed apktool, wrote own manifest hacking routine)
● Improved cleanup method - requires less free space
Version 1.5, 05-07-2016
● Better logging and error handling
● Other Facebook apps can now be installed
● Backwards compatibility down to V59
Version 1.4, 05-04-2016
● Video sending from gallery
● Inline video playback
● Floating hearts
● Linux aapt permission fix
Version 1.3, 05-01-2016
● Easy starter batch file included for Windows users
● Reduced size
● No more separate 'tools' directory, everything is within 'fbpatcher.jar'
● More readable and structured command line output
● Error codes
Version 1.2, 04-30-2016
● Apktool/smali logging
● Safety cleanup on start
● Support for latest versions (tested up to 76.0.0.0.49 alpha)
● Messenger thread list instead of mobile site
● QuickCam video sending
● Basketball game fix
Version 1.1, 04-27-2016
● Support for latest versions (tested with 73.0.0.18.66 stable and 76.0.0.0.19 alpha)
If you like FBPatcher, you can support its development, or simply click Thanks or share this thread on social media sites.

Instructions
To keep all discussion on this thread I'm coping my reply here as well.
How do I do that?
2. Run the patcher: java -jar fbpatcher.jar <input_apk> <output_apk>
Click to expand...
Click to collapse
Here is step by step instructions i followed to get it work on windows ( i think linux users knows how to do this simple things )
this guide was written for earlier version of patcher, but @lorantm is providing much easier automated patcher version now (from v1.3+ ) so just follow OP's USAGE GUIDE
still you can go through my guide for some deeper details and reference it wouldn't hurt and you will learn some history of patcher !
1. you need JAVA installed in PC if not install it from here https://java.com/en/download/
2. Download official (Not patched ) apk of latest stable Facebook(for now v76 here ) or as per recommendation of OP according to patcher version.(USE V75+ TO AVOID THE THREAD LIST SCROLL DOWN BUG! )
3. download patcher by @lorantm from OP
4. extract patcher in fbpatcher folder (use extract to fbpatcher/ )
5. put donloaded FB version form 2nd point in this folder and rename it to fb.apk for ease.
6(new). hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains fb.apk & fbpatcher.. now No need to copy cmd.exe at that folder...this method will open your system inbuild cmd so skip directly to Point 9
8. now your folder should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. open cmd.exe and write java -jar fbpatcher.jar fb.apk fbpatched.apk (mind on spaces... see below pic for clarity )
10. wait for 5-10 min and let patcher do its job you will get fbpatched.apk as patched file.
Install & enjoy

Tomi_Ohl said:
Nice guide! Only one thing: I think it would be enough to hold Shift and right click on empty space, then select open command prompt here (in step 6).
@lorantm köszönöm szépen, nagyszerű!! (Thanks, it's awesome!)
Working fine with the suggested FB version on Xiaomi Mi3 with Marshmallow
Waiting for the version with that message icon, right now I can't access groups from app if there are no new messages.
Click to expand...
Click to collapse
that's nice suggestion ! actually i forgot about it while writing guide.

How do you patch the apk on a mac?

Smoking Monkey said:
How do you patch the apk on a mac?
Click to expand...
Click to collapse
I never had a Mac, but I think you should do it just like on Windows or Linux. Install Java, open a command line and run it from there.

So when using patched facebook app, when we click on msg icon, msg interface is loaded in mobile web mode inside the fb app itself. But i am using latest fb app, and latest facebook chat enabler , and it do the same thing. What's the benefit of patching ?
Sent from my MI 3W using XDA-Developers mobile app

a.broken.star said:
So when using patched facebook app, when we click on msg icon, msg interface is loaded in mobile web mode inside the fb app itself. But i am using latest fb app, and latest facebook chat enabler , and it do the same thing. What's the benefit of patching ?
Sent from my MI 3W using XDA-Developers mobile app
Click to expand...
Click to collapse
I replied in the other thread.

lorantm said:
I never had a Mac, but I think you should do it just like on Windows or Linux. Install Java, open a command line and run it from there.
Click to expand...
Click to collapse
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?

Smoking Monkey said:
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?
Click to expand...
Click to collapse
It's Terminal. Open it, navigate to the directory (with the cd command) where you have extracted the patcher and the official apk. Then run java -jar fbpatcher.jar FB72.apk FB72P.apk.

Smoking Monkey said:
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?
Click to expand...
Click to collapse
http://www.wikihow.com/Get-to-the-Command-Line-on-a-Mac
personally even i never used Mac so i don't know how to open it in any specific folder (like windows has Shift+right click in empty space of folder ) but you can try to navigate to your folder via cd/ commands ( try to google it )

For anyone doing this on a mac you open up terminal and type cd /
Then drag the fbpatcher folder into terminal and press enter.
Copy and paste java -jar fbpatcher.jar FB72.apk FB72P.apk then press enter again.

Work perfect thanks

I use the latest version Facebook*73.0.0.18.66 APK and it work perfect thanks
Sent from my LG-H631 using XDA-Developers mobile app

:crying::crying::crying::crying:
guys i have problem.. when i try cmd.exe i get error saying it isnt compatible with my windows..
i searched and to fix i do run command scf/scann something like that and after scan it found conflict but it didnt fix it. :crying:
am very bad at command prompt if i go to accessories and use the comand promt there it works , is there a way for me to do it from there or it must have the cmd.exe in folder.?
if not can osme upload it and share please.. or help fix why cmd says its not compatible.? windows tiny7.

raptorddd said:
:crying::crying::crying::crying:
guys i have problem.. when i try cmd.exe i get error saying it isnt compatible with my windows..
i searched and to fix i do run command scf/scann something like that and after scan it found conflict but it didnt fix it. :crying:
am very bad at command prompt if i go to accessories and use the comand promt there it works , is there a way for me to do it from there or it must have the cmd.exe in folder.?
if not can osme upload it and share please.. or help fix why cmd says its not compatible.? windows tiny7.
Click to expand...
Click to collapse
hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains FB.apk & fbpatcher..No need to copy cmd.exe at that folder...this method will open your system inbuild cmd

jineshpatel30 said:
hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains FB.apk & fbpatcher..No need to copy cmd.exe at that folder...this method will open your system inbuild cmd
Click to expand...
Click to collapse
thanks it worked :highfive:

Hi, I want to ask, there is no call function on this "messenger"?
and when are you going to release the one with working messenger button?
Thanks!!

Guys Plz Share ur Patched APK file I want to use on Android Lollipop

New version!
V1.1 is out! I successfully patched 73.0.0.18.66 and 76.0.0.0.19 alpha with it and they worked perfectly.
The new version of FBPatcher can be downloaded from the first post, I updated the link.
Explanation: a method in com.facebook.messaging.banner.MuteThreadWarningNotification had to be dummied to make it work.

motfis said:
Hi, I want to ask, there is no call function on this "messenger"?
and when are you going to release the one with working messenger button?
Thanks!!
Click to expand...
Click to collapse
You can't make calls. Facebook removed WebrtcIncallActivity from the manifest and its theme from the resources so even if the voip code is still in there, it's not possible. Also, native library fb-webrtc-jni that is needed to make calls was removed. Earlier I tried to add it from Messenger's apk and hack the code to be able to start a call. It was ringing out, but the conversation could not be started because the in-call UI theme was not present and the app crashed immediately.
I plan to add Messenger thread list feature at the weekend or next week but I already wrote that it will not work on all devices.

[TOOL] bindump - Dump binder service endpoint holders (owners) and users

Hello all,
(Note to mods: I'm too junior to post in Android Dev fora, so please someone move my post, I believe it's worthwhile as this is really useful)
I've updated my little known but highly useful 'bin dump' tool to work on Android 9 and later. This tool is like "service", able to list services, but not just In the normal namespace - also in the vndbinder (though that requires root).
The primary use of this tool is to list who's actually holding or using the service. There's a full explanation on how I accomplish this at the webpage - newandroidbook.com/tools/bindump.html (mods: please make this a link? I can't). This way you can see who's using "power", for example (i.e. holds wake locks) , or "SurfaceFlinger" (i.e. has activity views) or "activity" (i.e is an activity/service/broadcast receiver).
Unfortunately, the advanced use requires root, due to binder's debugfs entries being chowned and chmodded nowadays.
The tool DOES NOT use libbinder, and I effectively rewrote the whole thing in pure C with the low level ioctl()s. I support Android 9 and onwards (if you need insights to the parcel format, which changed three times in between these versions.. let me know). Should work everywhere - That said, I've seen idiosyncrasies in Samsung devices which I've accounted for. Feedback more than welcome.

I need a 32bit version , is source available?

Tool is not open source (too much secret sauce and re-implementation of libBinder from scratch) but I built a bdsm.armv7 binary and linked it from the download page
(direct: http://NewAndroidBook.com/tools/bdsm.armv7)

Thanks , will try that out

[ROM][UNOFFICIAL][s5neolte][SM-G903F][11.0.0_r49] LineageOS 18.1[28-Nov-2021]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
###########################################################
Note: This is the first time I am building a ROM. My initial plan was to build it just for personal use. But since it is stable, I decided to share it with whoever is interested. I am not sure how often I will be updating it. But, I will try to do it every month. I added LineageOS recovery even though I do not use it at all. It can be downloaded if desired.
What's working:
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
NFC
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
Vibration
Wifi Hotspot
Selinux enforcing
What's not working:
Nothing I am aware of.
Possible issue:
If phone does not connect to network, reset APN.
Go to settings->Mobile Network -> Advanced -> "Access point names" -> "3 dots" -> "Reset to default".
Flashing Instructions:
Copy Lineage zip to phone.
(Optional) Copy bit gapps to phone.
Boot TWRP
Backup things you want to keep.
Tap Install -> Select LineageOS zip (and optionally, gapps)
Swipe to flash
Reboot system now
First boot, especially with Gapps, may take a while.
Downloads:
LineageOS 18.1
Optional: Bit Gapps. This is the only gapps that has 32bit for android 11 AFAIK.
Optional: Lineageos recovery
Sources:
https://github.com/LineageOS
s5neolte lineage-18.1 branches
Fincer branch : android_device_samsung_s5neolte_lineageOS
XDADevDB Information
[ROM][UNOFFICIAL][s5neolte][SM-G903F][11] LineageOS 18.1, ROM for the Samsung Galaxy S5 Neo
Contributors
The authors and maintainers of s5neolte gerrit branch PixelBoot, Stricted, danwood76, Borduni, Fincer
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2021-06-16
Last Updated 2021-11-28

Changelogs
13-Sep-2021
- September security update
- Update Lineage sources.
11.08.2021
- August security update.
08.07.2021
- July security update
- Update Lineage sources.
- NFC fix applied. Thanks @Fincer
17.06.2021
- Added "Night Light" to display settings.
16.06.2021
- Initial release

Reserved

For now i cant test it cause i had to put back the latest stable official rom from Samsung on this spare phone, but, good work, keep it up. I'll try it for sure soon or later.
Maybe you could even try to reach out / join forces with Stricted and the others if that could simplify all of you guys' work on the roms. Idk, just saying.

Android 11!?!?! I was surprised that the S5 Neo got Android 10 and thought there was now way it would get Android 11, but I guess I was wrong. I wish I could test the rom, but the display on my S5 Neo is completely dead. RIP.

NFC without function, and the ROM feels a bit laggy, Pico GApps installed. Anyways, nice giveaway.

0LDST4R said:
NFC without function, and the ROM feels a bit laggy, Pico GApps installed. Anyways, nice giveaway.
Click to expand...
Click to collapse
NFC issue might be caused by the final 2 commits in the device tree.
s5neolte: build nfc hal from source · LineageOS/[email protected]
Change-Id: Ief7ef8f2a597b1a978ea4b0ec4e41391cec03a99
github.com
s5neolte: remove nfc manifest entry · LineageOS/[email protected]
* its a vintf manifest fragment now Change-Id: Ie81a0a3d7eb690fccb6987f16250d1c57cb1e8cd
github.com
The new NFC HAL doesn't allow updating the firmware. It fails on the A3 and A5.

JMek said:
For now i cant test it cause i had to put back the latest stable official rom from Samsung on this spare phone, but, good work, keep it up. I'll try it for sure soon or later.
Maybe you could even try to reach out / join forces with Stricted and the others if that could simplify all of you guys' work on the roms. Idk, just saying.
Click to expand...
Click to collapse
We have already completed the 11 bringup. This thread is really just a build of that work.
Regards,
Danny

I have got NFC working (s5neolte/Lineage OS 18.1), see my GitHub repository for details. After all, minor tweaks applied to current NFC [email protected] file and SELinux policy seem to be enough.

Fincer said:
I have got NFC working (s5neolte/Lineage OS 18.1), see my GitHub repository for details. After all, minor tweaks applied to current NFC [email protected] file and SELinux policy seem to be enough.
Click to expand...
Click to collapse
Thanks. I built a new version with NFC working. I see there is a commit in that branch that should enable call recording. I can't find the option in my phone though. It is maybe due to regional restrictions.

lallolu said:
Thanks. I built a new version with NFC working. I see there is a commit in that branch that should enable call recording. I can't find the option in my phone though. It is maybe due to regional restrictions.
Click to expand...
Click to collapse
Glad to hear . Call recording option should activate/be visible only during phone calls. Have you tested that?

Fincer said:
Glad to hear . Call recording option should activate/be visible only during phone calls. Have you tested that?
Click to expand...
Click to collapse
Yes, I tested it by initiating and later receiving a call. But recording option did not show up in either case.

lallolu said:
Yes, I tested it by initiating and later receiving a call. But recording option did not show up in either case.
Click to expand...
Click to collapse
Yeah, you are right. There are two relevant Dialer source java files which seem to dictate whether to show or hide the record option. The source code can obviously be patched.
packages/apps/Dialer/java/com/android/incallui/call/CallRecorder.java
- function canRecordInCurrentCountry() (lines 97-109) returns a boolean value
packages/apps/Dialer/java/com/android/incallui/CallButtonPresenter.java
- boolean variable showCallRecordOption, line 565, which gets its value from canRecordInCurrentCountry() function
- I assume showCallRecordOption dictates whether to show or hide recording button
I think one can simply replace lines 565-566 in CallButtonPresenter.java:
Java:
final boolean showCallRecordOption = recorder.canRecordInCurrentCountry()
&& !isVideo && call.getState() == DialerCallState.ACTIVE;
with
Java:
final boolean showCallRecordOption = !isVideo && call.getState() == DialerCallState.ACTIVE;

Bikeboy200 said:
Android 11!?!?! I was surprised that the S5 Neo got Android 10 and thought there was now way it would get Android 11, but I guess I was wrong. I wish I could test the rom, but the display on my S5 Neo is completely dead. RIP.
Click to expand...
Click to collapse
I was also surprised, I thought 10 would be the absolute max for the S5 Neo.

Fincer said:
I have got NFC working (s5neolte/Lineage OS 18.1), see my GitHub repository for details. After all, minor tweaks applied to current NFC [email protected] file and SELinux policy seem to be enough.
Click to expand...
Click to collapse
I have had a quick look over your changes.
The NFC sepolicy stuff doesn't look right to me (it may work but there is probably a simpler/correct way to fix it). I am guessing that an NFC file was incorrectly labelled, what were the original denials you were getting? I could probably fix our SEPolicy properly. It may be that Jan was in permissive when he made the original commits (I have usually taken care of the SEPolicy stuff).
The "patch_tcpsockettracker-crash.patch" fudges round a kernel bug which I should really get round to fixing, I think it is only a few picks (I might take a look at it tomorrow).
BTW running "device/samsung/universal7580-common/extract-files.sh" on an S5NEO stock firmware will probably break stuff, we use the A510F nougat as the source of the common files (our kernel is also based on the A510F). Running the extract scripts from the latest LOS version should work fine but it is actually better to simply use themuppets repo as that has our 18.1 changes already.
As you gathered the call recording feature is disabled in a lot of countries due to legality. For example it is illegal in Germany, Sweden, and lots of other countries.
Also if you fix anything you can always push your changes to gerrit and we can review/merge
Kind regards,
Danny

danwood76 said:
I have had a quick look over your changes.
The NFC sepolicy stuff doesn't look right to me (it may work but there is probably a simpler/correct way to fix it). I am guessing that an NFC file was incorrectly labelled, what were the original denials you were getting? I could probably fix our SEPolicy properly. It may be that Jan was in permissive when he made the original commits (I have usually taken care of the SEPolicy stuff).
The "patch_tcpsockettracker-crash.patch" fudges round a kernel bug which I should really get round to fixing, I think it is only a few picks (I might take a look at it tomorrow).
BTW running "device/samsung/universal7580-common/extract-files.sh" on an S5NEO stock firmware will probably break stuff, we use the A510F nougat as the source of the common files (our kernel is also based on the A510F). Running the extract scripts from the latest LOS version should work fine but it is actually better to simply use themuppets repo as that has our 18.1 changes already.
As you gathered the call recording feature is disabled in a lot of countries due to legality. For example it is illegal in Germany, Sweden, and lots of other countries.
Also if you fix anything you can always push your changes to gerrit and we can review/merge
Kind regards,
Danny
Click to expand...
Click to collapse
To me, looking at @Fincer's commits adding the SELinux rules, they seem like they've just been copied right out of a different device tree.
I'm using the new open source Samsung NFC HAL on my own LineageOS 17.1 builds. To address the SELinux denials that I got with it, I labelled its service in the sepolicy in my commit here: https://github.com/TALUAtGitHub/and...mmit/914f6ec44657732de3562fd1b259d3ad1b8fcf95 ...and so, your guess that a file, which happens to be the NFC HAL service, is incorrectly labelled is correct. Labelling it with the correct label is absolutely all that's necessary.
Speaking of NFC, I've got an issue with my S5 Neo where NFC only works with another phone that I've tested it with. It doesn't work with any of the NFC tags/cards that I've tested, and this issue exists with both the new open source NFC HAL and the old NFC HAL. I don't know if that issue exists on the stock firmware as I never tested NFC on it. Has anyone got similar issues?
On the topic of call recording, to enable it (for whichever regions it's set to be allowed in, of course), all that would be required is this change: https://github.com/TALUAtGitHub/and...mmit/11448569ef5d1358bae1e6abbfce9d37200f6887 I haven't tested it myself yet. Changes outside of device-specific trees, as have been shared for it, should always be avoided if at all possible.

So much technical stuff in this last posts. Very interesting for me to read all these things, and even more interesting how many people are active in development with this device. I'm just only the " typical enduser " with a fraction of all your knowledge, but i'm very happy to benefit from that.
Greetz, respect, and thanks.
_-_-_-_-_
0LDST4R
-_-_-_-_-

Thanks for commenting!
I am pretty sure there's room for fixes in my SEPolicy. What comes to NFC, I haven't copied all SEPolicy rules from "other device trees", although there are some rules used from other device tree sources (I know, rules should be evaluated, simply haven't had time for that). In most NFC rules, however, I simply allowed capabilities which did not cause any avc denials in my logs. I am pretty sure my SEPolicy might be too loose and should be more restrictive, and I am grateful if anyone like to improve it. I don't have list of original denials, but the current NFC SEPolicy rule set is mostly based on those.
Running '"device/samsung/universal7580-common/extract-files.sh" has not caused any issues on my S5 Neo, well, so far.
The patch file for TCP socket tracker crashing was one I found once I analyzed my logcat output and was seeing constant messages of the tracker process crashing. I don't like unnecessary crashes.
My personal opinion for call recording is that anyone who uses patches or workarounds to enable the feature takes legal and personal responsibility of doing so, as well.

TALUAtXDA said:
To me, looking at @Fincer's commits adding the SELinux rules, they seem like they've just been copied right out of a different device tree.
I'm using the new open source Samsung NFC HAL on my own LineageOS 17.1 builds. To address the SELinux denials that I got with it, I labeled it in the sepolicy in my commit here: https://github.com/TALUAtGitHub/and...mmit/7e1325429647c7420e02d106bfdd0477b44888e4 I also have this related commit: https://github.com/TALUAtGitHub/and...mmit/fe5d4e253c5310523e66c4ff2c84424d5beee424 That's absolutely all that's necessary.
Speaking of NFC, I've got an issue with my S5 Neo where NFC only works with another phone that I've tested it with. It doesn't work with any of the NFC tags/cards that I've tested, and this issue exists with both the new open source NFC HAL and the old NFC HAL. I don't know if that issue exists on the stock firmware as I never tested NFC on it. Has anyone got similar issues?
As for call recording, to enable it, all that would be required is this change: https://github.com/TALUAtGitHub/and...mmit/95dfe486a5cca4b5fe3c9721d927de4aca772e7f I haven't tested it myself yet. Whether or not the call recording option becomes available with it would depend on if call recording is marked as being illegal in your country. Changes outside of device-specific trees should always be avoided if at all possible.
Click to expand...
Click to collapse
That sepolicy change looks correct. Are you happy for me to cherry-pick your patch and upload to gerrit? (Or you could do that yourself?)
The moving config to vendor patch isn't quite right for us, I will do a correct version with your authorship if you are happy? (also upload to gerrit). We like to keep the config file names the same as on stock.
To test the NFC I use the android CTS verifier. You can emulate payments and all NFC functions using that.
I will also cherry-pick your call recording overlay patch, not really sure how that got dropped as I remember we had that a few years ago.
Thanks for your input.
Kind regards,
Danny

danwood76 said:
That sepolicy change looks correct. Are you happy for me to cherry-pick your patch and upload to gerrit? (Or you could do that yourself?)
Click to expand...
Click to collapse
Alright. Yes, you can upload it to gerrit. I don't know how to upload patches to gerrit yet, so it would be better for you to do it.
danwood76 said:
The moving config to vendor patch isn't quite right for us, I will do a correct version with your authorship if you are happy? (also upload to gerrit). We like to keep the config file names the same as on stock.
Click to expand...
Click to collapse
I've edited that commit through a rebase myself, and removed the change of the filename: https://github.com/TALUAtGitHub/and...mmit/c98d51d42c92af13bcfb8cb5157fcde077d9bdad
danwood76 said:
To test the NFC I use the android CTS verifier. You can emulate payments and all NFC functions using that.
Click to expand...
Click to collapse
I see. I think the CTS tests for NFC would pass. I just have the issue that I've described on my specific S5 Neo with both the new and old NFC HAL, and it looks like no one else has any similar issues. I think something might just be wrong with the NFC coil in the battery that I'm currently using, which really needs to be replaced, anyway.
danwood76 said:
I will also cherry-pick your call recording overlay patch, not really sure how that got dropped as I remember we had that a few years ago.
Click to expand...
Click to collapse
Okay. By the way, I've also edited that commit through a rebase to remove the call_recording_audio_source overlay, so that the default audio source, 1, is used. With audio source 4 which was set to be used through that overlay, call recording fails, with the following log messages from logcat:
Code:
[...]
07-15 09:48:02.103 3564 6980 E APM::AudioPolicyEngine: getDeviceForInputSource() no default device defined
07-15 09:48:02.103 3564 6980 W APM_AudioPolicyManager: getInputForAttr() could not find device for source 4
07-15 09:48:02.103 3564 6980 E AudioFlinger: createRecord() getInputForAttr return error -22
07-15 09:48:02.103 3594 5636 E IAudioFlinger: createRecord returned error -22
07-15 09:48:02.103 3594 5636 E AudioRecord: createRecord_l(0): AudioFlinger could not create record track, status: -22
07-15 09:48:02.104 3594 5636 E StagefrightRecorder: audio source is not initialized
07-15 09:48:02.104 6728 6746 E MediaRecorder: start failed: -2147483648
07-15 09:48:02.145 6728 6746 W CallRecorderService: Could not start recording
[...]
With audio source 1, it works fine.
danwood76 said:
Thanks for your input.
Kind regards,
Danny
Click to expand...
Click to collapse
You're welcome.

[ROM][Note 10/10+][A12] iodéOS = LineageOS 19.1 + MicroG + adblocker [04/04/2023]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
iodéOS is a privacy-focused operating system powered by LineageOS and based on the Android mobile platform. iodéOS aims at protecting the user's privacy with a built-in adblocker and by freeing the smartphone from snitches.
The objectives in the conception of this ROM are threefold:
To keep the stability and security level of LineageOS, by minimizing the modifications made to the system. Apart the system modifications required by the adblocker, we mainly only added a few useful options commonly found in other custom ROMs, made some cosmetic changes, modified a few default settings to prevent data leaks to Google servers.
To ease a quick adoption of this ROM by new users. We especially target users that are concerned by the protection of their privacy, but are not reluctant to still use inquisitive apps like Google ones. We thus included MicroG as well as a coherent set of default apps, and simplified the initial setup of the system. Particularly, an initialization of MicroG has been made with GCM notifications allowed by default, a privacy-friendly network location provider (DéjàVu) pre-selected, as well as Nominatim Geocoder.
To provide a new and powerful way of blocking ads, malwares, data leaks of all kinds to many intrusive servers. We are developing an analyzer, tightly integrated into the system, that captures all DNS requests and network traffic, as well as a user interface (the iodé app). Compared to some other well-known adblockers, this has the advantages of:
Avoiding to lock the VPN for that use. You can even use another adblocker that uses VPN technology alongside our blocker.
Being independent of the kind of DNS server used by the system or set by an independent app: classical DNS on UDP port 53 or any other one, DNS over TLS (DoT), DNS over HTTPS (DoH), ..., as we capture the DNS requests before they are transmitted to the system function that emits the DNS request. What we do not support, is DoH when it is natively built into applications, i.e. when an app communicates directly with a DoH server, without asking name resolution to the system. It would require to decrypt HTTPS packets between such an app and the DoH server, which may create a big security hole.
Precisely mapping DNS requests and network packets to the Android apps that emitted (or received) them.
Deciding which apps have a filtered network usage (by default, all apps), and which ones can communicate with blacklisted servers.
Since its first versions, we added many features to the iodé blocker: several levels of protection, fine-grained control over the hosts that should be blocked or authorized, displaying statistics on a map to see the quantity of data exchanged to which countries, clearing statistics... We are actively developing the blocker, and new functionalities will be regularly added.
Features
Changes in LineageOS to prevent data leaks:
Default DNS server: Google's DNS replaced by Quad9's 'unblocked' servers in all parts of the system.
A-GPS: patches to avoid leaking personnal information like IMSI to supl server.
Captive portal login: connectivitycheck.gstatic.com replaced by captiveportal.kuketz.de for connectivity check.
Dialer: Google default option replaced by OpenStreetMap for phone number lookup.
Pre-installed apps:
We included many useful default apps, but our choice cannot suit everyone; so we added the possibility to remove them. It can be done at the end of the phone setup, or at any time by going to Parameters -> Apps & Notifications -> Preinstalled apps.
MicroG core apps: GmsCore, GsfProxy, FakeStore.
NLP backends for MicroG : DejaVuNLPBackend (default), MozillaNLPBackend, AppleNLPBackend, RadioCellsNLPBackend, Nominatim Geocoder.
App stores : FDroid (with F-Droid Privileged Extension) and Aurora Store.
Browser: our own fork of Firefox (with Qwant as default search engine, many other ones added, telemetry disabled, parts of telemetry code removed) instead of Lineage’s default browser Jelly.
SMS: QKSMS instead of Lineage's default SMS app.
Email: p≡p (Pretty Easy Privacy).
Camera: our own fork of Open Camera, with a few tweaks.
Maps/navigation: Magic Earth GPS & Navigation (the only one free but not open source).
Keyboard: OpenBoard instead of AOSP keyboard.
PDF: Pdf Viewer Plus.
Personnal notes: Carnet.
{Ad/Malware/Data leak}-blocker: iodé.
News: to keep users informed about our developments, as well as a FAQ.
Meteo: Geometric Weather.
Pre-included FDroid repository:
The apps that we tweak or develop (microG services, the browser based on Firefox, the News app, Open Camera ...) are available through a repository that we included in FDroid (check the "Apps for iodéOS" category). For this purpose and to avoid name conflicts of some apps, we also had to make a few changes in FDroid.
Useful options from other custom ROMs:
Smart charging (disables charging when a given level is reached, to protect battery health).
Fingerprint vibration toggle.
Swipe down to clear all in recent apps (Android 10 only).
Installation Instructions
To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.
Supported devices
Fairphone FP3/FP3+
Fairphone FP4
Google Pixel 3
Google Pixel 4
Google Pixel 5
Google Pixel 6
Google Pixel 6a
OnePlus 9
OnePlus 9 Pro
Samsung Galaxy A5/A7 2017 (a5j17lte/a7j17lte)
Samsung Galaxy S9/S9+ (starlte/star2lte)
Samsung Galaxy Note 9 (crownlte)
Samsung S10e/S10/S10+ (beyond{0,1,2}lte)
Samsung Note 10 (d1)
Samsung Note 10+ (d2s)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ1 (poplar)
Sony Xperia XZ2 (akari)
Sony Xperia XZ3 (akatsuki)
Xiaomi Mi9 (cepheus)
Teracube 2e
Xiaomi Mi 10T 5G / Mi 10T Pro 5G
Xiaomi Mi 10 Lite 5G
Sources
iodéOS: https://gitlab.com/iode/os
LineageOS: https://github.com/lineageos
device tree:
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_d1
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_d2s
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_exynos9820-common
kernel: https://github.com/LineageOS/android_kernel_samsung_exynos9820
Bug Reporting
You can post a message in this thread or (preferred) open an issue here.
Credits
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit their Wiki for more details.
This ROM would be nothing without the tremendous work made on MicroG, and all the other open source apps that we included. We are very grateful to their authors.
Contributors
Direct contributors: @iodeOS, @vince31fr
Indirect contributors (too numerous to list): All the people that contributed to the device tree, to LineageOS, and to the included open source apps.
Sponsoring
You can help in the development of this ROM by paying us a coffee here: https://paypal.me/iodeOS.
Screenshots

Downloads : iodéOS
04/04/2023 (build 20230401) for Note 10 (d1) and Note 10+ (d2s):
Blocker: improved use of blocking lists (sub-domains blocking)
FDroid: fixes an issue on apps update
LineageOS synchronized with March security patch included
All apps updated
07/02/2023 (build 20230131) for Note 10 (d1) and Note 10+ (d2s):
Blocker:
Improved blocking settings. You can now choose 'Standard' blocking (ads, trackers, malwares, etc) or 'Reinforced' blocking (same objective but more extensive), and then select additional categories.
The 'Porn' category has been extended to a wider 'Sensitive content' one, that also includes fake news, gambling, drugs, piracy, torrent..., with mainly child protection in mind.
The 'Extreme' category has been removed, as it is now part of the reinforced blocking.
Improved blocking lists. We merge several acknowledged and up-to-date sources, and have diversified our sources to produce more complete lists. The standard list has however been reduced a bit, to avoid as much as possible interference with apps expected behavior.
Added a new network location provider: Local NLP Backend. It is an improved version of the DéjàVu NLP backend which was already available in iodéOS. Like DéjàVu, it builds a local database connecting localizations learned from other NLP backends and apps using GPS, and mobile antennas/Wifi; but also has an active mode (not preselected) that can trigger GPS requests. To configure it: Settings -> System -> microG -> Location modules
LineageOS synchronized with January security patch included
All apps updated
New devices support: Pixel 3, 6, 6a
20/12/2022 (build 20221218) for Note 10 (d1) and Note 10+ (d2s):
Fixes smart charging issue
16/12/2022 (build 20221215) for Note 10 (d1) and Note 10+ (d2s):
Blocker: added multiple selection in settings / domain customization. Long-press on a domain, select several domains or all, apply actions (block all, authorize all...)
PdfViewerPlus: improved security by updating core libraries
Network settings: added a switch to disable connectivity check (and thus captive portal detection)
LineageOS synchronized with December security patch included
All apps updated
New devices support: Pixel 4 & 5, OnePlus 9 & 9 Pro
24/11/2022 (build 20221121) for Note 10 (d1) and Note 10+ (d2s):
Improvements in the blocker user interface (iodé app)
LineageOS synced with September security patch included
All apps updated
17/10/2022 (build 20221014) for Note 10 (d1) and Note 10+ (d2s):
Blocker:
Network blockings following their type (Wifi, mobile data, VPN) added
Default blockings definition for new apps
Personnalized recipients management improved
iodé's app access restrictions by password added
Search filters added in report and map
Display theme selection
Automatic and 'real-time' refresh of the whole app
Performance and fluidity improvements of the app
LineageOS synced with September security patch included
All apps updated
27/07/2022 (build 20220726) for Note 10 (d1) and Note 10+ (d2s):
SafetyNet certification activated: allows many apps, notably banking ones, to fully work
Setup wizard: the push notifications configuration page now also activates SafetyNet (fine-grained control in Settings->System->microG)
OpenCamera: the 'Use alternative flash method' in photo settings is no more necessary and can be disabled, allowing flash optimization
News app: German translations
LineageOS synced with July security patch included
All apps updated
21/07/2022 (build 20220530) for Note 10 (d1) and Note 10+ (d2s):
Upgrade to Android 12 / Lineage 19.1
Setup Wizard: new page to configure push notifications through microG
Lockscreen settings: switch added to disable fingerprint unlock when screen is off
Improved German translations
Bug fixes and improvements
LineageOS synced with May security patch included
All apps updated
03/02/2022 (build 20220407/08) for Note 10 (d1) and Note 10+ (d2s):
News app reworked
Setup Wizard: new iodé introduction
iodé blocker: pull to refresh replaced by automatic refresh in report tab
Teracube 2e 2022 batch released, video playback in browser and video recording fixed
Music app : playlist crash fixed
Open Camera : crash when tapping thumbnail of a newly recorded video fixed, photos and videos now editable
LineageOS synced with March security patch
All apps updated
03/02/2022 (build 20220126) for Note 10 (d1) and Note 10+ (d2s):
New iodé blocker map feature
Build mode changed to 'user' (i.e. release) mode): more apps work out-of-the-box and more secure device, but more restrictive recovery
Camera app changed to Open Camera
Wireguard kernel module included
Dark bootanimation
January security patch
Preinstalled apps updated
Beware: Play store Magisk module broken
18/11/2021 (build 20211108) for Note 10 (d1) and Note 10+ (d2s):
LineageOS updated (November security patch)
Preinstalled apps updated
Iodé blocker: hosts can now be customized, either globally or by app
05/09/2021 (build 20210905) for Note 10 (d1) and Note 10+ (d2s):
LineageOS updated (August security patch)
Preinstalled apps updated
Backup app included: Seedvault
microG now uninstallable: Settings -> Apps & notifications -> Preinstalled apps
New default accent color (clear blue from iodé logo)
13/08/2021 (build 20210811) for Note 10 (d1) and Note 10+ (d2s): first publicly available builds.
Downloads : add-ons
phonesky-magiskV2.zip : Magisk module for NanoDroid patched Play Store, for those who really need to get access to their paid apps that don't work with microG. This module can be generally be deactivated when you have installed and ran once the paid apps.
NB : you may have to wait a couple of hours after activating the module for being able to install paid apps.

Why is there no N9750 (d2q)? Which god can develop a d2q ROM? d2q heart pain.

And the d2x? Note 10+5g model?

Do you root this like lineage? By flashing a patched boot image?

Morutimeru said:
Do you root this like lineage? By flashing a patched boot image?
Click to expand...
Click to collapse
Yes, you can use magisk for instance.

biggary said:
And the d2x? Note 10+5g model?
Click to expand...
Click to collapse
We will maybe build for d2x. Stay tuned!

vince31fr said:
Yes, you can use magisk for instance.
Click to expand...
Click to collapse
Just flashed the ROM and rooted, had a hard time with twrp bootlooping after flashing. Its working phenomenal with Lineage Recovery. Thanks Dev, this ROM is awesome.

Great idea and work. Thanks for making this rom. I'll test asap.

Sorry if this has already been asked but from what I can see with all roms if you flash them you lose 5g and the ability to use WiFi calling and calling over 4g/volte? This is because of Samsung baking it into their framework?

+++ New Update : 10/09/2021 +++
Available as OTA (see OP)​

During the "patching system image unconditionally..." I keep getting "E:Error in /sideload/package.zip (status 1) in recovery output when I use Lineage recovery 18.1 (most recent) or the IODE recovery to perform the adb sideload command. Most recently after a clean install of the latest samsung firmware for the note 10+.
I checked zip file(s) integrity using 7 zip. It reports no errors. I also used both the iode 2.1 from 0811 and 0905 earlier with the iode 0905 recovery.
Any suggestions?

*** New Update : 18/11/2021 ***
Available as OTA (see OP)​

vince31fr said:
*** New Update : 18/11/2021 ***
Available as OTA (see OP)​
Click to expand...
Click to collapse
Still no D2X version???

am on the way to get a 10+ and will try this OS. Looks good!
After reading the installing instructions tho I am a bit unsure whether it is done in windows or linux. I've only worked in windows and with twrp so far...
Can anyone bring some clarity?
Besides, i am wondering few things:
- do both sims work?
- does the phone recognize full 512GB microSD? Or god forbide, 1TB?

If we already have lineageOS running, can we just boot into lineage recovery and sideload IODE'. Or does anyone mind providing some instructions on how to do this?
Thanks for any help. I'm learning all this and it takes me awhile to figure it all out.

Hello,
New here and fairly new to the whole rooting/booting/ROM thing. Although I have loaded cyanogen on a phone years ago. Some tech/coding experience.
I would like to use Iode on a Note 10. NOT Note 10+, just Note 10
Earlier in the thread I see d1, d2q and d2x
Which specifically do each of these apply to? I am thinking that
d1 = Note 10 but with Exynos chipset
d2q = Note 10+
d2x = Note 10+ 5G
Do I have these right?
What is the codename of the snapdragon Note 10 (N970U) ?
I would like to use Iode on the snapdragon Note 10. Is this possible?
Do I have to have the Exynos chipset - and if so, will that chipset give me pain when using with US GSM cell network?
Thank you!!! Much appreciated!

*** New Update : 03/02/2022 ***
Available as OTA (see OP)​
Beware: Play Store Magisk module broken

Good job keep it on very good rom battery is awesom

i don't understand what recovery shall I have to install? Adb it's ok, Oem unlocked, but I think I have download the original recovery...