Related
AOSP MASTER BRANCH FOR MANTA DEVICE
Hello everyone, you can download on XDA many good ROMS but each of them are based on "stable" android releases. That's why I chose to share something else.
I am offering a master branch build
Why use master branch ?
clang 3.8 | daily updates | java 1.8
instructions :
reboot to twrp recovery ( you can use mine if you want to use f2fs or having issues flashing my packages)
flasy my package
reset factory and IF YOU COME FROM ANOTHER DISTRIBUTION delete /sdcard/Android/data folder
flash gapps package ( I recommend opengapps)
reboot
I recommend people to factory reset time o time because of the master branch, it can be required to remove some bugs
What is not working/bugging for now
ROOT: latest supersu are patching the boot image and this doesn't work currently with my master branch releases. You need to use SuperSU v2.56
MXPlayer: for some reasons mxplayer doesn't find libcutils.so while it does exists. So for now, you gotta to use some alternatives: vlc, or what ever
Download link
Sources
How to use AdwAway
In oder to get AdAway working you need to do the following:
1/ Set a file at
Code:
su/su.d
with the following content
Code:
mount -o bind /su/etc/hosts /system/etc/hosts;
2/ Make an empty host file at
Code:
/su/etc/hosts
I think you can find a working flashable package doing this on the unoffical adaway thred
XDA:DevDB Information
AOSP Master Branch for Manta, ROM for the Google Nexus 10
Contributors
Khaon
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2016-04-22
Created 2016-01-27
Last Updated 2016-04-21
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
PainToad said:
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
Click to expand...
Click to collapse
This is not 100% PURE aosp.
The base is aosp master branch. I have included some several extra such :
bootanimation
long press recent switches to latest app
led
...
Well nothing much.
The only critical thing I have touched is android permission : I override user's permission for google play service for the location permission access: otherwise it crashes.
I have uploaded a new build.
Too much changes to display here the changelog.
If you want extra tracking you should head here
To me, the main change, is clang prebult updated!
OP updated, root is now working.
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
ace9988 said:
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
Click to expand...
Click to collapse
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Khaon said:
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Click to expand...
Click to collapse
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
HmHm it is kinda late for me ( european timezone) but I have no issues using app requesting SU rights. I will take a look however at it tmr.
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
what opengapps version did you isntall ?
I am using pico, and I have no issue flashing it.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
How is your supersu status ?
I have no issue with su.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
I was reported an issue when formating to f2fs rebooting to the rom would format the userdata partition.
I investigated the AOSP code source and some commit format the partition if it fails mounting. Ofc trying to mount a f2fs partition with ext4 is considered as a fail...
Flashing my standalone kernel permit to pass that issue : my stand alone kernel will transform ext4 entries to f2fs(and vice versa) depending on the actual underlying fs.
The current release I am using features fixes for this, however, something broke the libsensors, so I need to find out what.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
Ewww, it should work ! Any other informations ? such logs ?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
I am uploading a new build, I had issues for days with the builds.
Please tell me if you got bootloop on reboot. From what I saw bootloops do not longer exist.
I uploaded a new build.
It features master branch 02/21 with my latest kernel.
You just need latest opengapps for marshamallow and supersu 2.56.
Have fun.
All I see is one dated 2/5?
Sent from my Nexus 10 using XDA Free mobile app
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Der_Graf said:
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Click to expand...
Click to collapse
Grant play service the location permission and it will be fixed.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
I had this issue sometimes when installing the Rom and gapps in the same queue.. Installing the gapps seperatly afterwards worked then.. Try this out
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Der_Graf said:
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Click to expand...
Click to collapse
@Der_Graf
Hehe sorry for you this issue happens, the real culprit is Google. Since MM, the dev got to ask permission if not given. Google Play Frameworks/Service doesn't ask for this. So that's why you got FC. You should try after a Factory Rest- you need to that anyway when coming from another ROM- not installing Gapps in order to not have the first setup screen where you will get stuck because of the fc's spam.
Then Install gapps, and, since you will boot on the Home Screen, you should be able, with some pain, to get access to the app menu to get Location permission for Google Play Services.
Then, for any upgrade install, you won't have issues as the permission is already granted.
I know this sucks, but I tried to force give the permisison and it doesnt work :angry:
Ewwwww.
I wanted to share my latest build, as of the 25th feb, but NFC is broken and makes continuous FC'S, this appears also on my friend nexus 6's device, which is still supported by Google. So this is the bad news I've got to understand why this happens, well until Google fixes it or I find the culprit.
However, the good news is, that this friend, maintains more extra features then I do, so the next releases will feature more extra features
Hello
I am going to release unofficial builds of LineageOS 14.1 for Wileyfox Crackling. The builds will be updated every month after a new security patch level is reached.
The build I made can be flashed on top of Cyanogenmod 13 build (with wiping dalvik and cache). It should work without any problems; I do not experience any.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
If it makes problems, wipe data/dalvik/cache and install again.
Besides that the ROM has two extra features:
I patched signature spoofing support into the ROM. Now it is possible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and will not affect the ROM in any way. It has to be enabled in the according settings.
Also, there's an option available to record calls now. Please respect the privacy of others.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-02-01.html"]February[/URL] | 2017-02-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170227-UNOFFICIAL-crackling.zip
Download:
Code:
[B][SIZE="2"]Openload.co:[/SIZE][/B]
https://openload.co/f/DBKYItUGllA/lineage-14.1-20170227-UNOFFICIAL-crackling.zip
https://openload.co/f/grRwId0HJJE/lineage-14.1-20170227-UNOFFICIAL-crackling.zip.md5sum
Alternativ:
[B][SIZE="2"]Free.fr:[/SIZE][/B]
http://dl.free.fr/uqIBAf8dM
The kernel and device sources I used to build the ROM can be found here:
Code:
https://github.com/lineageos
thomson.aa said:
Hello
This is my first build of LineageOS for Wileyfox Crackling.
I flashed it on top of my Cyanogenmod 13 build (with only wiping dalvik and cache) and it so far works without any problems.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
This release has the root access option disabled because LineageOS disables root for apps by default. It has to be enabled before building the rom - I didn't know that so I will provide an updated rom with root access for apps available.
Besides that the rom has one extra feature:
I patched signature spoofing support into the rom. Now it is possbible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and has to be enabled in the according settings.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-01-01.html"]January[/URL] | 2017-01-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Download:
Code:
https://openload.co/f/WCt_JxGZ-UE/lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Click to expand...
Click to collapse
Sorry thomson.aa sorry i do not have english my google translation. Work is very nice thanks one has a mistake sim card people do not see a way to solve it? I wish you continued success.
Where is the source ? You can't post this without kernel source
I dirty flashed this over crDroid and it seems to be working pretty well. Thanks.
All my app's (not many at the moment) were working fine.
Playstore thinks it's 'no carrier Wileyfox Wileyfox Swift'... but I guess that's better than 'Wileyfox Pixel XL' (crDroid).
On initial booting the status bar wouldn't pull down but works ok after a reboot.
Buttons were a bit messed up which only gave me a back button even though the usual defaults were all set. After deleting them and re-adding them they worked fine. I'm guessing this may be due to dirty flashing. Shame the button customisation is just as basic as cm13 especially after using crDroid.
Using Kernal Auditor Mod I see that the cpu only scales down to 800mhz and the gpu scales up to 400mhz. I don't know much about this but won't this make it a little power hungry?
Going through the settings, I'm thinking that LOS14 isn't quite as complete as the cm13 I was using a few weeks ago. Although I guess this is to be expected at this stage. And I'm used to the more versatile crDroid now so I'll be restoring that in a mo.
This MicroG project sounds great. It seems a bit complex to get it working as I'd like but I definitely be having a go when I get my head around it.
All in all, Great job. Keep up the good work... please. I'm already waiting for the next release.
Oh, and er... Surely you could find a better file host???
I tried to build the Image myself by using your other Thread's How-To and after flashing i had no WIFI.
Now i flashed this build and WIFI is also not working.
[Edit]
I've collected some Logs - perhaps they'll help.
[Edit2]
Now i tried another '14.1-ROM' and i've the same problem....
During all my Tests the shown MAC-Address during the 'inital install' was weird: 02:00:00:00:00:00.
Before the 14.1 Lineage i had the latest CMmod 13 running without any Problems :/
Ok - solved it....
I encrypted my Device during CM13 and always entered my Key during Boot/TWRP and Formatting/Installation of 14.1.
Now i *really* formated all the Data (and the former encryption), rebooted to Recovery and sideloaded the Image+Gapps.
Now WIFI is working.
How do I enable signature spoofing ? I can't find any relevant setting.
M.A.K said:
How do I enable signature spoofing ? I can't find any relevant setting.
Click to expand...
Click to collapse
Settings -> Apps -> Gear symbol -> App permissions -> Spoof package signature
No... it's not there for me.
M.A.K said:
No... it's not there for me.
Click to expand...
Click to collapse
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
fred0r said:
Now i *really* formated all the Data (and the former encryption)
Click to expand...
Click to collapse
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
thomson.aa said:
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
Click to expand...
Click to collapse
Ah, yes... got it now, thanks.
jobedius said:
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
Click to expand...
Click to collapse
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
update to official build?
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Nope, its not
Mithodin said:
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Click to expand...
Click to collapse
Twrp shows error 7(the data is incompatible). You need to wipe data, cache partitions and the system partition. Then install the zip with arm64 android 7.1 g-apps.
Cheers:good:
fred0r said:
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
Click to expand...
Click to collapse
Aahhh, that makes sense if you know it! Thanks!
{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is not just another ROM - it is a mobile ecosystem (ROM + online services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds are all signed with a custom private key for best trust. This also means you have to factory reset when coming from another ROM!
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
You can LOCK YOUR BOOTLOADER - if you like
Build variants (UNOFFICIAL, CUSTOM)
UNOFFICIAL builds:
full OTA support
no other differences to pure /e/. It is just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)
CUSTOM builds:
2 variants: rooted (magisk) or unrooted
removed: the app "Apps" (see FAQ why)
added: F-Droid, F-Droid priv ext, F-Droid additional repos (disabled by default), AuroraStore, Lawnchair-latest (taken from their TG group), PhoneSky (google play store - patched for microG), Magisk app when choosen the rooted variant
patched with this safetynet patch (this will not bypass safetynet though)
fully patched for AVB / dm-verity support - means you can lock your bootloader! (all builds since 3rd of Sep 2021) - yes even the rooted variant can run on locked bootloader!
SHRP included (accepted by a locked bootloader) - means when you want to use a different recovery you have to flash / re-flash it after flashing / upgrading the ROM. Including this is needed to not brick devices running on locked bootloader.
.. read all the details about locking your bootloader in this post
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
none known (yet)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build (while I am testing with SHRP only)
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything!
Planning to lock your bootloader? Read this first
Installation
Planning to lock your bootloader?
Read on here
Detailed guide:
follow MSe1969's guide here
Quick guide (assuming you have TWRP/SHRP already):
Full clean install as described here (FAQ #2). DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (planning to lock your bootloader? Read this first)
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
MSe1969, wth.. you did an AWESOME job
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot (let me know if that's the case ofc) ..
Sources
/e/ : https://gitlab.e.foundation/e
my build manifest
MSe1969's stuff
Frequently Asked Questions (FAQ)
Q #0: For CUSTOM builds only: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If your issue is not solved with selinux permissive click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there a FAQ specific for /e/?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
App alternatives (to replace google variants): click
Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
See OP
Q #8: Will my banking app (or other root detecting app) work with this ROM?
The answer is .. well .. simple. it depends.
First of all the following technique works regardless of what ROM you are using or what device. It worked with my LG G4, OnePlus 6T and now OP7tpro so its a generic "maybe-solution"
Read on here:
I am using a german banking app which works even when root gets detected. It will prompt and say thats bad but I am still able to use it. The same was the case for the TAN generator app of the same bank but it fully stopped working one day after a (forced) app upgrade.
So I started to play around and found a solution which works for me since several years but there is no guarantee it will work for you or for how long it will work. The process and steps must be followed briefly and nothing more, nothing less must be done.
The following references a banking app but it applies to any app which rejects starting when root or a custom ROM has been detected:
you need root, i.e. Magisk. This ROM has a custom build which includes Magisk already.
uninstall the currently not working banking app(s)
install & setup a work-profile manager like Insular, Shelter, (if you do not care about google trackers: Island), or [fill-in-another] ,.....
configure Magisk that it hides itself (i.e. re-package Magisk with a random name) & reboot just to be sure. and yes that works on signed and locked ROMs, too
newer Magisk versions will clone themself into the island profile during the repackage process so open island then switch to the island tab and remove the magisk app there (so not from the "mainland"!)
install the banking app(s) - BUT DO NOT start it!
clone that app into your work-profile (i.e. open Insular/Shelter/Island/.. find the app, clone it there), repeat that step for any app needed
configure Magisk hide for this app(s) and ensure you select all options (some apps can be expanded in magisk hide, select all options then)
remove any icons of your app(s) from your launcher but DO NOT UNINSTALL them!! (never)
in your work-profile manager (Insular/Shelter/Island/...) find your app and create a quick start launcher (repeat that for any app needed)
now start your banking app quick link (again it HAS to be the one created by your work-profile manager). usually you can identify that you are using the right one bc it has a mini icon of your work-profile manager on top of the regular app icon
enjoy. if it does still detect root or a custom ROM you either have not followed the above steps briefly or you are out of luck.
Background:
You cannot uninstall the app(s) from android (ever) because otherwise Magisk hide will not work. so you always need to keep that app(s) but never starting it.
It can make sense to try another work-profile manager if the above way fails for you as the app devs using different techniques
Q #9: Will DRM protected content work? | Will this ROM satisfy Safetynet?
Likely not. Yes this ROM is signed, selinux is enforcing and you can lock your bootloader but these days this is not enough anymore. While there are some workarounds available these might stop at any time. So do not expect that this will work or work for a long time.
LOCK your bootloaderYes you read correctly: you can lock your bootloader again! Why is that so amazing? The most important thing: security. When your bootloader is locked no one can install or modify without you notice it. Let's say you loose your phone and your bootloader is unlocked. The person can boot into fastboot and flash a custom recovery of his choice and have full access to your data (if not having a pin set) but also can tamper e.g. your system partitions like installing malware. Yea for that the attacker needs physical access to your phone but there is malware around and this is REAL which uses bugs to install themselves even on your system partition. For this the attacker does NOT need physical access to your phone.
On a locked bootloader the device won't boot anymore as a modification like that will be detected.
Anyways.. yea one can say both attack variants are not THAT critical or affecting you as you are paying attention on what you do but .. there is a always a risk of undetectable malware like the good old drive-by downloads etc. so .. its all up to you if you want to have that extra barrier or not..
But before we begin
a HUUUUGE thanks to @WhitbyGreg !!!
All this here would not be possible without his great guide here ! Ofc I need to adapt it and integrate all this within my automation process but it would have been a LOT harder without his thread(s).
So if you love it having a locked bootloader now - give HIM some thanks clicks, donations, hugs.. as well
Checklist: is locking the bootloader something for me?If you answer anyone - even just 1 - of the following with YES - then KEEP AWAY FROM LOCKING your bootloader!
I want to remove (not just disable) system apps (often called bloatware)
I want to add / convert apps into system apps (e.g. Titanium Backup offers such an option)
For rooted variant: I want to update Magisk to the latest version
For rooted variant: I want to change init scripts, XMLs or anything else within system/, product/ etc partitions
For rooted variant: I want to use an ad-blocker which modifies the "hosts" file (system partition)
I want to install another recovery then the one coming with the ROM (SHRP)
I want to flash GApps (LOL! this is /e/ !! even on unlocked bootloader this won't work!)
I want to flash anything else in recovery which modifies: boot, recovery, system or any other partition then userdata
Do you have answered at least 1 of the above with YES ? Then do NOT lock your bootloader. It WILL brick your device if you try.
if you can live with the above - GO GO GO
Lock your bootloader - processDownloads
ROM without root: https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom_pkmd.bin
ROM with root: https://leech.binbash.rocks:8008/e-os/a10_rooted/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom-rooted_pkmd.bin
backup all your data. I am serious EVERYTHING. we need to FORMAT the userdata partition during the lock process and there is no way around. so use TB or Swiftbackup, Migrate or any other. Always a good idea to also having a TWRP/SHRP backup just for the case..
boot your current recovery
flash the ROM of your choice (with or without root)
reboot to the bootloader / fastboot
if you flashed the ROM with root: fastboot flash avb_custom_key hotdog_eos-q_custom-rooted_pkmd.bin
if you flashed the ROM without root: fastboot flash avb_custom_key hotdog_eos-q_custom_pkmd.bin
type: fastboot oem lock
approve locking the bootloader on the phone's screen
< take a deeeeeeep breath >
recovery (SHRP) will load automatically
choose wipe -> format(!) data (there is no way around)
boot android -> you will notice a new bootloader message warning you that you have a custom ROM installed - but it will load
congrats! you now running on a locked bootloader + /e/ OS!
for the rooted variant: start the Magisk app (requires internet), accept the install request and open the magisk app afterwards and let it reboot when asked
enjoooooy
Locked - now what?OEM unlock option
The above does not mention one additional step: disabling OEM unlock in developer options. For a reason. I mean you CAN uncheck that option now that all is running fine but you don't get any more security tbh.
The reason is if you keep it checked an attacker is able to unlock your device but it WILL format the encryption keys when done. that means no way to access your data anyways. If you want to avoid even that then feel free to uncheck OEM unlock in developer settings as well but then a brick will require low level recovery tools to bring your device back to life.
Magisk (rooted variant)
I recommend to disable automatic update checking within magisk settings - remember: when flashing a newer version of magisk it WILL brick your device. you have to wait for me updating it within the ROM.
Anything you do within Magisk can EASILY BRICK your device, installing a magisk module which tampers your system partition: BRICK. So really really check if a module touches anything mentioned in the above checklist topic. Using the magisk variant has HIGH potential of bricking your device.
You can use all standard root functions, magisk hide and even re-pack the magisk app though.
Bricked
Always keep an eye on the above "Checklist" topic! If you change/do something mentioned there you will brick your device with a snap of a finger.
Android does not boot anymore because you flashed a newer version of Magisk or changed something within the protected partitions:
boot recovery (power off, press power on and vol down the same time and keep it pressed until you see the shrp logo)
flash the current ROM version or a later release and reboot
recovery does not load bc you flashed another recovery:
wait for the next OTA and it get fixed automatically
or unlock the bootloader again (this will need to FORMAT the userdata partition)
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
L4WL13T said:
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
Click to expand...
Click to collapse
hard to say. there are some which might not work and/or apps you should avoid (as they contain trackers etc). There is a good list of alternatives in FAQ 4 above
steadfasterX said:
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything
Click to expand...
Click to collapse
Do TWRP backups even work on this device? Last I heard, it was broken.
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
ap81z said:
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
Click to expand...
Click to collapse
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
steadfasterX said:
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
Click to expand...
Click to collapse
ok, I'll be waiting!!!
forgot to mention it here (another reason why users should join my automation channel):
Gestures are supported since the latest version.
breaking news:
I was working on using this device as my DD again but I have very strict requirements:
/e/ OS must work (reason: privacy focus, google-free) [ DONE ]
encryption must work (reason: security, e.g. loosing or selling the phone) [ DONE ]
selinux must run in enforcing [ DONE ]
/e/ OS must be signed with own private key (reason: allowing secure OTA and local/recovery upgrades) [ DONE ]
SHRP must work (reason: a password on startup can be set - allowing to have rich recovery feature set but secured - when the bootloader is locked!) [ DONE ]
and here the fun began:
/e/ OS must run on locked bootloader [ DONE ]
SHRP must run on locked bootloader [ DONE ]
OTA must work on locked bootloader [ WIP ]
so overall I am pretty much where I want to be and can provide a privacy focused, secure, google-free and locked bootloader experience soon...
stay tuned
Ever wanted to lock your bootloader - not on STOCK but on a custom ROM?Most ppl don't know (or don't care) that almost all Oneplus devices offer such an option - if the ROM dev is willing to take the journey implementing it.
This is now possible when running my /e/ OS CUSTOM builds (read more in the OP about the diff between CUSTOM and UNOFFICIAL) and not just that my new CUSTOM builds coming either pre-rooted or not - whatever you wish more.
I have to say that this was something on my to-do list since I bought this device more then 1 year ago. After a lot of work in the past months I am finally where I am and can use it as my DD again. Something which makes me reeeeeeally happy lol
Dunno but maybe someone enjoys having a locked bootloader like I do
Read all the details and how it works: here
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Also I doesn't find any option to change 60hz/90hz ?
Thetimelost said:
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Click to expand...
Click to collapse
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Thetimelost said:
Also I doesn't find any option to change 60hz/90hz ?
Click to expand...
Click to collapse
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
steadfasterX said:
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
Click to expand...
Click to collapse
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Thetimelost said:
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Click to expand...
Click to collapse
Hm interesting mine is running at 90 hz all the time it seems. Weird bc /e/ is based on LOS so maybe its an option in a11 first?
When will we get Android 11?
andr052h said:
When will we get Android 11?
Click to expand...
Click to collapse
Why do you want to have it?
steadfasterX said:
Why do you want to have it?
Click to expand...
Click to collapse
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
andr052h said:
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
Click to expand...
Click to collapse
Well first of all I thought no one uses my ROM anyways so there was no need for me upgrading to a11. This ROM is rock stable and does what i need as a daily driver and gets monthly security patches. Many ppl just want to have a newer android version just bc there is one and not bc for a specific reason. That's why I'm asking.
I personaly prefer a good working ROM over having always the newest android version just because there is one
Other then that i may upgrade to a11 but not anytime soon. Main reason is that I am using this as my daily driver so it would be hard alsi dev on it..
Hey Guys,
Hope you're doing great
For the people who wanted privacy based roms like CalyxOS or GrapheneOS
you have to
1. install vanilla version from ArrowOS or LineageOS
2. Flash Magisk
3. Then in Magisk go to Modules tab, click top button 'Install from storage' install LSPosed-(...)-zygisk-release.zip (has to be zygisk version)
4. then install FakeGapps.apk like an regular app
5. Reboot
6. Popup will came out that ask you to add shortcut icon to desktop for LSPosed, just add it and open it
7. Go to Modules and enable FakeGApps
8. Go to Magisk and install microG_Installer_Revived.zip as a Module
9. Reboot
10. Open microG Service Core and ensure all boxes are selected. The most important is signature spoofing - this is what LSPosed and FakeGapps is for.
For working push notifications go to microG Service Core app and enable Google devices registration and Cloud Messaging.
For working location at least two apps will be needed - MozillaNlpBackend and NominatimNlpBackend. After installing they need to be enabled in microG Service Core app (Location modules). Sometimes MozillaNlpBackend refuse to be enabled, then you just have to go to it's permissions and select "Allow all the time" for location permission.
For working SafetyNet additional Magisk module may be needed.
SMS and Location in background didn't work for me, reinstalled the microG installer module and it worked
Few Alternative apps that you can use:
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing
How to unlock bootloader for Redmi K40s
try looking into this video also if you have created an new mi account you may have to wait for 1week for getting your bootloader unlocked using miunlocktool you can also download the tool from https://en.miui.com/unlock/download_en.html
Also sorry everyone I forgot the metion the alternative apps that you could have used,
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing
SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...
UniNick said:
SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...
Click to expand...
Click to collapse
Thx a lot for mentioning, note: nevest version of spark is an erofs build so for the who didn't wanted erofs version can download previous versions of it
You can use this guide in every rom just make sure it's an vanilla build and it's has signature spoofing
The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatch.
UniNick said:
The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatching
Click to expand...
Click to collapse
We'll I'll try to get more info about it, if I get any fix for it I'll update the guide
Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it
If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.
UniNick said:
If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.
Click to expand...
Click to collapse
I know, as the official release is not available I'm doing it
Vinc3nt.exe said:
Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it
Click to expand...
Click to collapse
Cant wait for LineageOS for Munch. take your time, King.
Hello Guys
Hope you guys are great
this is to inform you that unfortunately i couldn't build the microg version of lineageOS but i have successfully builded it's vanilla version and it's avaliable on xda
Hello to everyone!
Here is a new Grass kernel line, which work with Kernel SU on POCO M3 (probably all chime).
It provides systemless root access on a kernel level for chosen apps only. No root access visible in system - nothing to hide.
Installation:
If you have magisk - flash uninstall.zip in recovery; then flash stock boot.img from your ROM; last flash grass-kernel.zip.
Manager run from apk file.
If you want back magisk with it's modules, you can install it from magisk.apk, grant root access from KernelSU manager, than you can patch boot via direct install (recommended). After reboot you can add your favorite modules like usually in Magisk.
The kernels are in next post.
Don't forget to change extension (apk->zip)!
Update from 19.05:
So, kernels are here:
Change extension from .apk to .zip, flash it in recovery and enjoy!
[email protected] is the latest one.
Will upload here one more time kernel for juice/chime and latest KernelSU apk:
Latest version of Grass kernel:
Optimised very good and working with 0.6.0 app. ver.
Also latest zygisk for kernel SU:
Version 10999:
Do u mean magisk module can co exist along with kernelsu. I mean i want root with KernelSu+magisk modules
Exactly. Root from KSU, modules from Magisk.
tariqa said:
Exactly. Root from KSU, modules from Magisk.
Click to expand...
Click to collapse
I'm wondering about root detection... You have double root(KSU&MagiskSU)...
Which one controls the root actually ? KSU has the better prevention from root detection but MagiskSU hasn't. If MagiskSU controls the root, it seems not to be a good idea ...
Kris Chen said:
I'm wondering about root detection... You have double root(KSU&MagiskSU)...
Which one controls the root actually ? KSU has the better prevention from root detection but MagiskSU hasn't. If MagiskSU controls the root, it seems not to be a good idea ...
Click to expand...
Click to collapse
Root is controlled by KSU.
Hello
Is this kernel for miui or Aosp Roms ? Please specify , and also mention andriod version Supported by this Kernel