Related
Google in the update from Android KitKat to Android Lollipop has introduced a new type of restriction that blocks the execution of non-PIE binary.
This block mainly forces the user to copy the binaries he wants to run in /system/bin, /system/xbin, or in /sbin.
This restriction stops executing some apps (also app no-root), this Magisk module disable this restriction.
Who needs this module ?:
This modulr can be useful if you run the following statement while you are running a binary:
Error: only available independent executables (PIE) are supported.
How does the module work ?:
The operation is really simple, I checked the commit of the aosp source to identify the changes made to linker.cc responsible for the PIE restriction and I removed the part of code that blocks the execution of non-PIE binaries then it was enough to compile the linker and create a Magisk module with modified binaries.
Compatibility:
Android 7.1.X (probably also 7.0 but has not been tested)
Architectures: all
Flash in Magisk Manager or TWRP, NEEDED MAGISK 13.1 OR NEWER
The source for now is not available, will be released on the following days (Monday at maximum)
Working on Samsung Galaxy S7 edge nougat 7.0
Spartacus500 said:
Working on Samsung Galaxy S7 edge nougat 7.0
Click to expand...
Click to collapse
Did you try to run a non-PIE binary?
No, I did not try, I just installed the module.
ErnyTech said:
Did you try to run a non-PIE binary?
Click to expand...
Click to collapse
Hi! Small understanding info on my language on net. Its security restrictions for PIE added,removed by Google in different versions of Android. But in newer buidls his add this check,and any modern OS too have it. In two words tell me why i need bypass this sec.system(e.g disable security)? For exploits?
sorry,Eng is not my native lang.
zentao78 said:
Hi! Small understanding info on my language on net. Its security restrictions for PIE added,removed by Google in different versions of Android. But in newer buidls his add this check,and any modern OS too have it. In two words tell me why i need bypass this sec.system(e.g disable security)? For exploits?
sorry,Eng is not my native lang.
Click to expand...
Click to collapse
Unfortunately in some roms there are, for example, the Oxygen OS and sometimes also the Lineage. The mod need for users who have to run a binary but its execution is blocked by PIE verification, probably most of the users do not need
Yes may be most of the users don't need but thanks for your efforts
If I use this Magisk module, I cannot take any photo with my camera. Disabling this module, everything is ok again.
I have got a HTC One M8 with LineageOS 14.1.
Herbie_2005 said:
If I use this Magisk module, I cannot take any photo with my camera. Disabling this module, everything is ok again.
I have got a HTC One M8 with LineageOS 14.1.
Click to expand...
Click to collapse
Uhm what rom?
LineageOS 14.1 (CM 14.1)
is it will work on latest LineageOS 14.1??
Edit :: Yes.! it works ...but can u please make a zip for supersu user??it will be really helpful.
Does this work on stock Android 8.0?
I cannot pass the "Starting apps" if i use this module
Darkaxis said:
I cannot pass the "Starting apps" if i use this module
Click to expand...
Click to collapse
What rom you're using?
I DONT TAKE ANY WARRANTY WHATSOEVER IN ANY DAMAGE THAT MAY RESULT IN FOLLOWING THIS GUIDE OR USING THE SOFTWARE, ROM IN QUESTION, IN ANY WAY, MAY IT BE AS INTENDED OR NOT. IF YOU HAVE ANY FEELING YOU COULD END UP SUING ME FOR RISKS *YOU ALONE* ACCEPTED TO TAKE, YOU SHOULD IMMEDIATELY STEP BACK AND LEAVE THIS POST, ALL THE OTHERS: BE CAREFUL. YOU WILL LOSE ALL OF THE DATA ON YOUR PHONE'S USERDATA, CACHE AND SYSTEM PARTITION AND THE PHONE WILL BE FACTORY RESET!
STOCK FIRMWARE INSTALLER: https://support.wikomobile.com/maj/Lenny5_OPE_V34.zip <-- if you brick your device.
Hey folks
This is just a brief explanation on how i built this ROM, a complete guide to building the rom may be published at a later point in time. For the Downloads, go to the Links section. The flashing guide will be focused on Lenny 5, but the image may work on other treble-enabled devices, too, so feel free to try and report if your device works with this build.
Build variant: arm-aonly-floss-su-userdebug
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Build description:
I have an old Wiko Lenny 5 around here and wanted to use it as a Kodi Remote etc. at home, but didn't want to use their stock ROM. Also i wanted some freedom in using my device, specifically a rooted device and microg implementation. After trying to build TWRP with no success and the Wiko Build information being massively outdated i then focused on Generic System Images, as Lenny 5 is Treble-enabled. Big thanks to @phhusson for the whole lot of effort he put into building AOSP GSI's (and also clues towards building LineageOS GSI's). After having AOSP9 installed on it for some time, i got bored and tried to compile LineageOS using the patch-and-build system provided on phhusson's github. That worked just great on AOSP9, but failed to build a bootable LOS16 in the first place. So after some recherche, i stumbled across @AndyYan's thread, containing some LineageOS GSI's prebuilt and ready to use. These worked great on my phone, but as stated above, i wanted to customize my LineageOS even further, so i manually patched my build-tree with AndyYan's Lineage-Treble-Patches by doing what this build script does, tested and it booted (i guess it's mainly related to the SELinux Policies not being correctly built for LOS with only phh's treble-patches). So far so good.
Additionally, i implemented the MicroG services by cloning these prebuilts on github to the respective folder in the build tree and before the build executed
Code:
export WITH_SU=true
to include LineageOS's root system in the build. I adapted the treble_arm_afS.mk device config to not use phh's su and the device/lineage/floss.mk file to include
FDroid
FDroidPrivilegedExtension (which is being built from treble sources)
MicroG services (use Play Store Apps)
FakeStore (use Play Store Apps)
MozillaNlpBackend (MicroG Network Location backend)
NominatimNlpBackend (MicroG Network Location backend)
OpenWeatherMapWeatherProvider (for LineageOS Weather Provider)
You are then free to use no Playstore at all or i.e. Yalp Store to download Play Store Apps.
After downloading the Image you may need to Unpack it via 7-zip or another tool.
Flash the device:
To install this custom ROM on the Wiko Lenny 5, in your stock ROM go to Settings->Developer Options->OEM unlock->Enable. Also, in the Developer Options, make sure, ADB Debugging is active and, on prompt, accept debugging connections from your computer.
On your computer, enter Command Prompt and issue the following commands:
Code:
adb reboot bootloader
*wait for device reboot*
fastboot oem unlock [COLOR="Red"]<-- this will factory reset the device!!![/COLOR]
*press vol up on the phone to allow unlocking the bootloader, and wait for the phone to return to fastboot mode*
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot flash system <path-to-the-downloaded-gsi>
*wait for each process to finish*
fastboot reboot
now, wait for the phone to reboot, it should, after some time, show you the usual LineageOS startup screen. Take your time to set up your phone. To make MicroG and FakeStore work properly, you will have to Go to Settings->Apps&Notifications->App-Permissions->Spoof package signature->Menu->Show System Apps and allow FakeStore to spoof Signature. Go to Settings->System->Advanced->MicroG Settings and add your Google account. Activate Device Registration. Then activate Google Cloud Messaging and Google SafetyNet, if you want to take advantage of those services. Inside the UnifiedNlp Settings choose MozillaNlp in the first, and NominatimNlp in the second setting.
Go back and choose "Self check", if required, if required, grant MicroG GmsCore the permission to spoof signature, this should make most of the boxes go "checked". If Phonesky shows errors about signature spoofing, this should normally be gone after a reboot of the phone (given you allowed FakeStore sig spoofing). Disable battery optimization and then reboot the phone.
Check back in MicroG Settings->Self check, if all the boxes have been checked. If not, most mandatory points are self-explanatory.
This Lineage ROM will not allow you to update to a newer version. I cannot guarantee continuous updates, but encourage you to try building LineageOS treble with the way explained above, yourselves. If enough interest is around, i will consider doing updated builds from time to time.
Update:
Today i compiled a recent source tree containing the 5th of October patches. I will try to keep up with updating the Image whenever security fixes are released. The download links below have been updated to the newest version. To update your phone without deleting the data on it (make sure you have adb debugging enabled), you can simply do
Code:
adb reboot bootloader
fastboot flash system <system-image.img>
fastboot reboot
and then give your phone some time to "update". it should boot normally without erasing your data.
Links:
ROM .7z [~430MB]
ROM .img (~1.1GB)
(version was compiled at 19th of October '19, containing the October 5th security fixes.)
Let me know if this works for you, too!
Cheers
ivelischt
*reserved for additions/build guide*
Nice work
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Hanthonious said:
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Click to expand...
Click to collapse
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
ivelischt said:
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
Click to expand...
Click to collapse
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Hanthonious said:
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Click to expand...
Click to collapse
Hi Hanthonious
ivelischt said:
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Click to expand...
Click to collapse
as the microG variant requires some "special sauce", namely the ability to spoof signature as well as other small fixes in the source code, my source tree is a bit different from the "vanilla/gapps" source tree. thus, to build variants not containing microg, you can simply sync the lineage source tree and apply the additional phh treble sources&patches. *edit: next to phh's patches, you will also need AndyYan's patches; you can find information about it in the OP. given, i write a guide (which i still intend to, but this takes some time), the patching step will be explained more clearly* basically, it's one step less than compiling it with microg. at the moment i cannot afford enough disk space to create another work tree, which is why i "can't promise" other build variants, until this issue is gone. which may be tomorrow or in a year. maybe you can find a gapps-version of treble-lineage 16 here in the xda boards. otherwise you will have to wait, or try to build it yourself. also, you might be interested in @AndyYan's lineage version, which is vanilla (no gapps or microg).
i would guess that the system image will not grow excessive just by including opengapps, but i may be wrong. i think that you'd possibly would have to choose a "non-complete" opengapps-package, to make it fit.
to quickly summarize what microg does is, that it spoofs its signature to make your phone think that you have the real Google Services Framework, Google Cloud Messaging, etc. services installed. this makes apps, which depend on these services, work even though you don't really "have" them. additionally, microg establishes an "essential" communication between itself and the real google services to allow you to use google services despite having all their bloatware.
to round this up, you have fakestore which spoofs existence of Google Play Store for those apps and games, which specifically check for GPS's existence (Phonesky app).
i think this should quite generally point out, what microg is for (an api which connects you to google, whilst only handing out information, which is crucial to keep a specific connection alive)
you can then use i.e. Aurora Store to download and update your preferred playstore apps. i tell you this specifically, as i hope that, using it right, microg might be able to give you a "fully stocked" phone experience, whilst keeping most of your data secure and your phone unbloated by google's app-hoard.
if you follow the instructions in the OP on how to fully enable microG, this might be a very handy solution for you, too, so maybe, you want to give it a chance.
to point out my issues with twrp (as far as i can tell using my little experience): twrp is device specific. which means, you need a vendor tree and you need to include it whilst building, so twrp can compile against it. now, treble is a way of excluding your device specific vendor tree from the build altogether (your system image basically doesnt contain the vendor files in a "folder" (/vendor), but in a seperate partition. this partition is "simply" beeing symlinked to from your system partition. this way you will never need to build vendor-specific sources but android builds against standardised "api's" which are being "serviced" by treble-enabled phone's vendor-files (lying at the vendor-partition). this makes building aosp and/or lineage, etc. easier as you can build one variant per architecture, which fits all treble enabled phones of that architecture (arm/64/binder32/64,a/ab,...). this is, very basically said, what is called a HAL (hardware abstraction layer) on a desktop computer.
but at the same time it's much more difficult to find vendor sources for those phones, as there is no more need at all for manufacturers to make these sources publich (as far as i understand it). as a matter of fact, you may not need these vendor sources for modern aosp (8.1+), which really is a grace!! but twrp doesn't seem to work when compiled against treble trees.
i even managed to compile a kernel which is mentioned at the wikogeek site for the lenny 5. i tried to include that kernel when compiling the recovery image but even that did not work out. as i am no experienced programmer (especially not in the high languages), i will not be the person to ask when it comes to finding out what bugs and how to circumvent it.
there is a little light at the end of the tunnel, though. as far as i understand it, treble-phones come with mostly generic kernels, which *could* make it easier to find a way to build a kernel/boot/recovery image in a similar fashion we build the gsi (generic system image) with. additionally, if there is some effort on it, i imagine, that it would be possible to generally modify twrp in a way so it's able to build against treble source trees with missing vendor source. this would enable twrp to run on virtually any phone which is treble enabled and there would be few to no need to port it for each device, specifically. maybe there would then be versions as in the treble gsi's (arm/64,a/b,...) as well as build variants for alternative display sizes etc.
but i wouldn't even know where to start...
i hope i was able to answer your questions. if you decide to stick with the variant in the OP, you should consider downloading and installing the most recent updated build.
best regards
Problems I found in the rom and if there is a way to solve them
Yo,
I wanted to point out the problems I found in the rom and if there is a way to solve
These are the problems I encountered:
1: *THE MOST IMPORTANT*
I can't pass the safetynet test, I researched a lot and I still couldn't solve
When I try to pass the safetynet test on magisk it gives "safetynet API Error"
When I try to do the test with the "SafetyNet Helper Sample" app it gives "SafetyNet request: success
Response validation: fail
Error Msg:
ApException [17]: API: SafetyNet .API is not
available on this device. Connection failed with:
ConnectionResult {statusCode = SERVICE_INVALID,
resolution = null, message = null}
And the "SafetyNet Test" app gives me "fail (Google Play services not available)"
I am aware of the new problem with the safetynet:
(sometimes people are still able to pass the test probably because it is still in maintenance or something)
https :// www . androidpolice . com /2020/03/11/safetynet-improvements-kill-magisk-hide
https :// twitter . com /topjohnwu/status/1237656703929180160
https :// twitter . com /topjohnwu/status/1238514375150850048
https :// twitter . com /topjohnwu/status/1237830555523149824
But even so I should be able to run the test even if it give both negative should run instead of showing those errors
2: The contacts I had on the SIM card and Google account do not appear in the contacts.
So I went on WhatsApp to save the ones I wanted to save, but after a few days and a few restarts the contacts are still saved, but on WhatsApp it shows that they are not saved even appearing in the contacts, to appear again saved on WhatsApp, I have to save them all again
3: Cant login in Clash Royale with google play games account, can i flash the rom and gapps to work or the microg and google play services will create some conflict, is there a way to unninstall microg completly and reflash the rom without microg and flash gapps?
4: Error when login in pokemon go: unable to authenticate, I researched it and it seems to be because the safetynet is negative but I can't even run the test (only after I became aware of the new safetynet problem) even with this new problem I would like to try to run the test to see if it passed since some people still are successfully passing the test
5: in the microg settings in self-check an option is not checked in the box "UnifiedNlp do not have location to test geocoder" I already researched to see if it solved something but I couldn't
edit: I solved it using the "Apple WI-FI" backend instead of the "Déjà Vu Location Service"
BUT NOW ITS GIVE ME AN UNCHECKED BOX
"Network-based location enabled:
you either disabled network-based location
(in system settings) or the system is not
supported"
6: some times in the time widget just appear "loading widget..."
and these are all the problems that I encountered, pls help me
solving these problems, thx!:good:
sorry for some mistakes i translated from portuguese to english with google translator and my knowledge of english
CooperTUGA, thanks for writing. And I want to apologize for letting you wait for so long. In fact, at the moment i do not actively develop this ROM (due to data loss on my virtual machine).
Anyways, i will try to address your issues as good as i can, though i must admit, none of these issues happened on my device.
ad 1: The only thing that comes to my mind is, that something went wrong when registering your device with the Android-ID. (see OP activation instructions). The SafetyNet-API itself should be working, atleast I had no similar issues (after Registering the device it takes some time - around 5 minutes - for Android to reflect the registered state).
But if someone happened to have this issue and knows another solution, you are welcome to tell!
ad 2: Does it help when you try to import the Files from the SIM card? As for Google contacts, it is - from my POV - stringent, that, if the SafetyNet API doesn't work properly, you will be unable to access Google Services (as Google Contacts) which would explain the missing Google Contacts.
ad 3: GApps and microG are two different things. GApps install a version (open-source fork, contains proprietary binaries) of the Official Google Apps, that is, they provide full functionality towards google services, provided you registered your device correctly.
microG is a pure Open Source fork of that, providing but the Framework with which Google Apps can be run. It does not provide Google Apps (like PlayStore etc.) by itself but merely allows them to run, given the configuration is right. This microG-ROM is not built to work with GoogleApps like PlayStore, but instead relies on the microG Services to get Apps, providing same or similar services, running (like Aurora Store etc.). To address your question, it is possible, to change the source code which was used to build this ROM, so it builds with Gapps or completely free of any such services, in fact it would mean to exclude certain patches, but such projects (Treble-enabled) are covered by others and because of above stated reasons i will not be able to provide such in near future.
Short but clear: No, there is no way to "uninstall" microG as it is built together with the ROM and the source used was especially prepared to use microG. But if configured right, you should be able to use your Google-Account in combination with Google-Services-Apps or Games despite using microG.
ad 4: See above. If everything's configured right, you should be able to play Pokemon GO, although i don't use any of these Apps (Clash Royale, Pokemon GO, WhatsApp). I never encountered any Problems along using Google Apps with this ROM.
ad 5: Well, the error says it all. I have Mozilla Location Service installed, which works like a charm. Maybe try this one? You can get it from FDroid, search for "MozillaNlpBackend" and see if it helps to sort this out? This works for me, after all.
ad6: as this is very unspecific, i cannot really tell what's the problem, but i would guess it has to do with the SafetyNet API not doing what it should or even the Location Backend not reporting position in time...
Did you clean your cache and data partitions while installing this ROM? I really am not sure what could create the behaviour you describe. Maybe there was a change in the SafetyNet/Device Certification process since this ROM-Build, maybe theres someone in those boards who could answer this, but i unfortunately can't...
I'm sorry that i cant give you more positive news, but hopefully it helps you in orienting what some common problems could be caused by.
Let me know about your success in trying to get the ROM working.
Best regards and greetings to portugal!
ivelischt
additionally: if you are interested in porting the Lineage Source for GSI/Lenny 5, you might be interested in this Thread: https://forum.xda-developers.com/android/help/how-to-root-wiko-lenny-5-t3819469
specifically, i wrote a guide there on how to build Android/Lineage Source for Treble devices. Maybe this helps you in getting your own build environment, enabling you to build to your disguise.
Images are not available anymore. Anyone here?
Hi guys,
I wanted to have a google-free phone, so I browsed the LineageOS download section and selected the zenfone 6, as it has headphone jack, sd card, no front facing camera, and it supported LineageOS 17.1
I bought a zenfone 6, and installed immediatly, keep in mind, last time I did this, I had a LG optimus Dual
Clear tutorial and learned there is a new "slot" system, cool.
Now, the phone runs ok, but I constantly have (multiple times a day) reboots, and it get stuck on the LineageOS logo for at least 40 minutes at a time, then it goes into recovery, and ask me if i want to try again to boot or wipe/restore "factory" default.
If I select try again, it will boot in an instant.
As it is, the phone is not reliable enough to use it, so i don't know what to do:
restore it to stock and sell it? Maybe, but I cannot download a stock image from asus support (blank page), and as far as I can tell there is no tool to "relock" the bootloader from asus, and i would rather not flash a random image found on google drive.
I tought of booting from slot B, but apparently the slot system is used during OTA updates, so I think I just deleted my previous OS by updating to a new lineageOS nigthly release.
Or is there something I'm missing about LineageOS? I remember when there were Stable releases, now I only see nigthly images, what am I not understanding?
I wish I could install debian on this thing.
Thanks everybody.
Bye
I am using havoc os
And even tried a11 bliss os
Their is no reboot no lag on 6z its great phone i think you have done something wrong and lineage os is no only the option bliss rom, aex, havoc all are great
You can join telegram group and ask for help their will help you their too..
Thanks, I'll try them :good:
@warsow
try AEX 8.0 [11.0.0_r8]
- https://forum.xda-developers.com/zenfone-6-2019/development/rom-aex-8-0-dmd79-t4183679
AEX ROMs have MicroG support.
Then, have a look at:
MicroG
- https://microg.org/
MicroG [XDA]
- https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
or if you want a LineageOS ROM with MicroG for the Zenfone 6 [I01WD]
- https://download.lineage.microg.org/I01WD/
metaxda said:
@warsow
try AEX 8.0 [11.0.0_r8]
- https://forum.xda-developers.com/zenfone-6-2019/development/rom-aex-8-0-dmd79-t4183679
AEX ROMs have MicroG support.
Then, have a look at:
MicroG
- https://microg.org/
MicroG [XDA]
- https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
or if you want a LineageOS ROM with MicroG for the Zenfone 6 [I01WD]
- https://download.lineage.microg.org/I01WD/
Click to expand...
Click to collapse
Hello,
I am preparing myself to install ROM without Google looking for something stable, i do not play any games.
I thought I will go ony with aps from fdroid to make sure that Google is not tracking me.
But since it is possible to make it wit microG I thought it can safe me in case I will miss some app.
But now I try to understand.
Not all mods support microG?
Do I need to do like in this instruction ?
And how can I know if it will work ? Maybe Google update some service and it will go over ?
Thank you
It is so much information ! The installations are not always easy.
I've created this thread to discuss LOS19. Hopefully, one of the maintainers will create a proper thread.
Downloads
Official: https://download.lineageos.org/sunfish
Installation
https://wiki.lineageos.org/devices/sunfish/install
Upgrading from 18.1
https://wiki.lineageos.org/devices/sunfish/upgrade
Updating
https://wiki.lineageos.org/devices/sunfish/update
If you find their work useful, don't forget to support all their work.
https://paypal.me/LineageOS
https://patreon.com/LineageOS
Visual Voicemail Error
I'd like to thank @razorloves for working on a fix to the VVM problem. Razorloves has already provided the work to the Android project. Let's hope all goes well. The work is greatly appreciated.
Razorloves created a new "Dialer.apk" for LOS19. The LOS18 version is already being shared in that thread.
I've attached "Dialer-19.1.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.
To try this fix....
Enable USB debugging in your phone.
Enable ADB root in your phone.
Use these adb commands....
'adb root'
'adb remount'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is from 2008
'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is now from 2022
reboot your phone.
Hopefully, the fix will make it through AOSP & onto the official LOS19 ROM soon.
Got notice that the VVM issue has been closed. The Dialer app will be fixed in next build.
So, if you're on LOS19, you can just wait for the June 2 build.
Big thanks to @razorloves for the work that made it happen
EDIT: Sorry! Deleted this post because my lack of knowledge made it appear like I was insultingly impatient. Many thanks to all the people who make LOS available for us dunces.
Sincere apologies to anyone whom I might have offended.
Since I switched from LOS18 to LOS19, I'm having a couple of issues.
This is NOT a complaint. I'm simply sharing to see if others are also experiencing these.
I updated per the LOS webpage instructions (ie. not a clean install). Phone has no custom-kernel,
no GApps, and no Magisk. Build is June 9th (latest).
1) Calendar notifications.
I'm not getting calendar notifications. This was working fine in LOS18. I'd get a notification at the defined time before an event. Sometimes, while I'm working on the Calendar, I get old notifications (as in events from days ago). Today, while testing, I got a "Calendar keeps stopping" popup.
My calendar data is offline. I deleted my calendar and created a new one. Nothing changed.
2) Charging.
When I plug into my PC, I get the sound acknowledgment from my phone. The Battery screen tells
me "Charging". However, it is not charging.
EDIT: As always, I'm a day late and a dollar short.
This is a known LOS19 issue (with USB) that was being processed. They have a fix in place that we should see next build (June 16th). Thanks (again) to the LOS team for their time/effort!
Is anyone else having the Calendar issue? If you're not, did you update to LOS19? Or, did you perform a "first time" install (wipe data & such)?
Thanks for your time.
@mangokm40 How is the battery life on LOS 19?
AkumDX said:
@mangokm40 How is the battery life on LOS 19?
Click to expand...
Click to collapse
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
mangokm40 said:
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
Click to expand...
Click to collapse
Oh okay ... Haven't used LOS 18 for few months now... Currently on 13 beta, battery isn't that great so thought of switching
4a LineageOS 19.1 Update 2022-06-16 - Security Bump
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-09 + lineage-19.1-20220609-recovery-sunfish to build 2022-06-16. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 12 minutes.
There are a bunch of changes as you can see here:
I tested the USB fix. It's not working for me. Thanks to user razorloves. I toggled the "Always allow USB connections" setting in "Settings->Privacy->Trust". My phone is now charging, even when locked.
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "June 5, 2022".
The Vendor security patch level (just below) is also "June 5, 2022".
The Build number at the bottom is now "SQ3A.220605.009.A1".
The Baseband updated to "g7150-00090-220406-B-8411773".
See Android Security Bulletin - June 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220616" and active slot 'a'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
lefteyecat said:
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
Click to expand...
Click to collapse
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
mangokm40 said:
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
Click to expand...
Click to collapse
Thanks,looks like i have to hold out on 18 for as long as i can.
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
Nope.
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
i use swiftbackup and nova launcher, its not as good as twrp ( still need log in verifications) but does restore all apps and screen positions , best and easiest solution i have found so far. Root reguired.
Is anyone running the latest version of LOS19 (lineage-19.1-20220623-nightly-sunfish-signed.zip) ?
I'm asking because there's this VVM issue open for a OnePlus7, running LOS18.
VVM is working for my 0616 build of LOS19, and the issue mentions it broke when they installed their device's 0619 build. Thus, I looked at the list of changes for our device here.
There are 5 changes to "android_packages_apps_Contacts".
There are also many changes to "android_vendor_lineage" that mention APN changes for various carriers.
I'm wondering if anyone is running the 0623 build & has VVM working.
Thanks.
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
mangokm40 said:
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
Click to expand...
Click to collapse
Thank you mangokm40 for all the infos, tips, tricks and hints you post! Really appreciate it!
4a LineageOS 19.1 Update 2022-07-14 - Security Bump, Calendar Update, Hidden Apps
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-16 + lineage-19.1-20220616-recovery-sunfish to build 2022-07-14. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 11 minutes.
There are a bunch of changes as you can see here.
The ones that I noticed are:
1) Security Bump - see details below.
2) Calendar Update - the update to version 1.0.30 didn't clear the search crash problem. The battery use is now forced to "Unrestricted", to allow all notifications to appear on time.
3) Hidden & Protected Apps - It remembered all my hidden apps from LOS18 & they were hidden without needing any new input from me. WooHoo!
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "July 5, 2022".
The Vendor security patch level (just below) is also "July 5, 2022".
The Build number at the bottom is now "SQ3A.220705.003.A1".
The Baseband remains as "g7150-00090-220406-B-8411773".
See Android Security Bulletin - July 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220714" and active slot 'b'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Hello, can someone help me with the following question?
* Does Google Pay / banking apps work good with this rom? I suppose that magisk is needed along with some safetynet fix?
Thanks!
I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.
P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.
The September update is now live.
Does banking app works?
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box
icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!
Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.
The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy
Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?
I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?
Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running
It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.
Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts
I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!
Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.
I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!