yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zenon9:
Hello guys,

I have possibility to buy pixel 4a in very low price the reason is that a friend of mine block this device.

He doesn't remember his email and can't get access to this device.

Since I know it wasn't stolen I thought to get it and unlock.

Is it possible to do it ? Will this device let me go with fastboot? And new recovery, rom ...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] floydster1708:
Without oem unlocking enabled and the boot loader unlocked I don't think you'll be able to do much without that email and password. I could be wrong but this is my understanding.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vivaeltopo:
What does the email address have to do with accessing the device?! And you should be able to reset the device from the recovery (power+down after boot), shouldnt you?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zenon9:
That's what I thought, I wanted to make sure.

Thank you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] floydster1708:
Not without an unlocked bootloader. It's basically to protect the device from someone stealing it and doing a factory reset. If you factory reset a phone and the bootloader is locked you have to have the original email and password to get into it. That's how all my devices have been. Maybe not on some devices not sure.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] floydster1708:
Deleted
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
Thanks for this! I thought I had to spoof it to pass safetynet to use google pay, but just using that safetynet fix was enough thanks man!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sx1fix:
Is it save to install EdXposed on top of Magisk with this ROM?

@PeterCxy: Very nice ROM - well done. I really appreciate the work. Many many thanks!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
Updated to 20210207 with fresh 2021-02-05 security patches. Also removed warnings about GAPPS because they should be working now.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eater99999:
The good: battery life is hugely improved over stock 11. Now with light use I can go 48 hours between charges.

But: I can't send or receive MMS on Sprint, at all. Tech support says all my picture messages are queued up on their server but the phone is not accepting them.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
Unfortunately I am not able to debug MMS support due to my local carriers. I can try to compare what's different from other Pixel device trees, but it would be really hard for me to determine exactly why it doesn't work.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eater99999:
Trying to install this on a friend's device and when booting after sideloading it keeps saying the device is corrupt. I tried half a dozen times, both v20210207 and v20210118, and finally just flashed the latest OTA, which worked fine.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eater99999:
Is there a way to copy MMS/APN settings over from the stock rom, if they are configured there?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
Just edit / add APNs in settings I guess?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eater99999:
@razorloves helped me figure it out, with a lot of trial and error. Putting this here for anyone else having Sprint MMS APN problems. I had to disable the SprintDM app that was auto-assigning the wrong APN info, and then manually put in the correct info.

adb root
adb shell pm disable-user --user 0 com.android.sdm.plugins.sprintdm
adb shell content query --uri content://telephony/carriers/preferapn

Then take the number after _id from the output of that query, and fill it in for the XXXXs below:

adb shell content update --uri content://telephony/carriers --where "_id=XXXX" --bind mmsport:s:80
adb shell content update --uri content://telephony/carriers --where "_id=XXXX" --bind mmsc:s:"http\\://mms.sprintpcs.com"
adb shell content update --uri content://telephony/carriers --where "_id=XXXX" --bind mmsproxy:s:oap7.sprintpcs.com
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Mindthegapps 11 are up

Codefire - Listing of gapps

Edit. Sorry I jumped the gun. I assumed they'd work but nope. Stick to razorloves or opengapps testing
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Moto_Fan:
MindTheGapps Updated to Android 11 : http://downloads.codefi.re/jdcteam/...MindTheGapps-11.0.0-arm64-20210212_144546.zip
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Do these work now?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Moto_Fan:
Date on the file is 2/12 did u tryon or before this date?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Yeah, the ones before wouldn't flash. Something about reserved partitions weren't jiving with mtg.

I tried these updated ones with my old 2xl and work fine
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
I guess I just reserved too little space for your GAPPS package to work. I'll probably expand the reserved space later.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
Updated to 20210222
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
Thanks for all your work! I am hesitating to switch from stock 11 for several reasons. One is whether we will be able to update from this build to an official one without wiping/reinstalling. Another is whether the build is completely stable and usable as a daily driver. Also, I am wondering about battery life and latency as compared to stock. I have found that on certain devices, Lineage was actually worse! Also, how are the opengapps working for people??

Summary of questions:

1. Stability?

2. Battery?

3. Is official coming soon and "guaranteed"?

4. Can we seemlessly upgrade to official 18.1?

5. Opengapps or other gapps working well?

Thanks to everyone for any input!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
1 & 2: I've been daily driving this for quite a while and I don't think it's less stable than stock, and I don't think I've observed any more battery drain than stock. Of course this could be due to the fact that I don't install the full GAPPS and instead use microG.

3: I am going to merge all my code into the LineageOS repository by the end of this week if no objections (I am already a maintainer of the official LineageOS repositories for Pixel 4a) and I will be submitting wiki entries & CI config for LineageOS 18.1 builds. I am not sure when LineageOS 18.1 will ship, but I expect it to ship with Pixel 4a builds, or in the worst case Pixel 4a builds will be up shortly after LineageOS 18.1 is shipped.

4: No, you will not be able to. This ROM is signed with my own keys, and I have no access (nor should I have access) to the official LineageOS signing keys. It will not be compatible with official builds for this reason.

5: As I don't use GAPPS myself, I'm not sure, but people in this thread have been successfully using GAPPS with this build for some time now. We at LineageOS have fixed the earlier issue causing GAPPS to break on new Pixel devices.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vivaeltopo:
1. & 2. no problems for the last two months with this ROM.

5. OpenGapps works fine for me.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EggZenBeanz:
This is amazing news! Excellent work on this device, it's been a joy to use from day one. Loving the microG patches also. Will you still continue to post patched unofficial builds here? I would be very interested to keep running them
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
Thanks so much for the thorough responses! I suppose that dirty flashing official over your build would be possible but not recommended?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] wireroot:
Isn't this question the same as question 4 which has already been answered, or am I missing something?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
It's not possible at all and you will find your device bootlooping if you dirty flash the potential official builds.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
I probably will because I use the microG patch myself.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mr_davis_12:
Hello, is it possible to install that rom with TWRP ?

If not, what version of fastboot do you use ?

Do i need to root my phone before installing the rom ?

Thx
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
I haven't tested the ROM at all with TWRP. You need to unlock, not root, the phone.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mr_davis_12:
Thx !

I unlock my phone and sideload lineageos.

I reboot into the new recovery.

I want so sideload Magisk-v21.4 and NikGapp but he said : "signature verification failed".

I can force the installation anyway, do i need to force it ?

Thx
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
It is expected because the recovery cannot recognize keys from third-party packages. You can just ignore the error and install anyway (i already said this in the post btw)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mr_davis_12:
Thx for your answer.

Everything works pretty well now !

I'm trying to pass SafetyNet but i don't know how.

I just try to go back in recovery mode and sideload the fix from https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

But that didn't work.

Any idea ?

Thx

Edit :

I find the answer, just need to download the file and install it with the module menu from Magisk!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] GuiLG:
Hey there,

I don't have this device (yet) but I was already wondering if this ROM has the same photo quality as stock ? I'm asking because on my current Samsung A3 (2017), flashing custom ROMs based on LineageOS yields degraded camera quality due to some proprietary drivers or something (I don't really know what I'm talking about to be honest).

Cheers
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
You can extract stock Google Camera from stock ROM and use that on LineageOS.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] grognaz:
i wanted to install this rom but im running into an issue when i try to do a factory reset from recovery. i get a lot of these messages: E:can't send spi message - Try Again

and it seems that is some kind of theft protection that has been added.

how do you get around this?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Ignore it.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
You don't need to worry about these messages.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] grognaz:
Is there some special patch to get viper working on this rom? I cant get it to work with the usual addons
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zombierockstar:
This is killer! Great job!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] darashikoh:
@grognaz its working for me. Install busybox and Audio Modification Library from Magisk repo to get it working.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] grognaz:
@darashikoh Are you using the canary version of magisk or the stable release?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] darashikoh:
The canary one.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
March 05 security patches are here.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] grognaz:
Anyone knows if its somehow possible to create color calibration profiles that can be switches with a widget or in some other easy way?

I find the screen needs to be darker and more red during night since the default night light is barely doing anything compared to my previous nexus 5x and at the moment im manually switching tye color calibration in the evening and in the morning and would like to simplify this process.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mr_davis_12:
Hi,

Magisk said that I pass SafetyNet.

But I can't use my bank app because that said my phone is root.

Any solution ?

Thx
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
just go into the magisk app and click the shield button at the bottom, and then tap magisk hide. Find the banking app and check the box to hide root access from the app. May need to clear the cache and/or data on the banking app
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mr_davis_12:
That's perfect.

Thank you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ptn107:
Installed and working with magisk (canary 220005) and nikgapps basic. Google camera installed and has the same picture quality as stock. Very happy. Thanks for all your hard work!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] roxy1712:
Just upgraded my Exynos Samsung S7 (stock ROM debloated since there's no Lineage for that model) to a Pixel 4a. My expressions when booting and using my new 4a looked something like this: 😦😲😒 with all the Google crap and reminders I couldn't turn off.

Installed your version and so far, so good. Am using Magisk 22.0 and the Jan 30 test version of OpenGApps. Only thing I've seen so far (and not a dealbreaker) is that my phone number isn't showing up on the SIM status screen or "Device phone number" in Google settings.

Really appreciate the hard work! 👍
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] roxy1712:
Okay, micro sized bug report - I suspect it's LIneageOS in general as there's a few old bug reports from 16/17 that show similar problems. The status bar starts to get a little weird when you add icons or details. For example... I moved the clock to the right of the battery and started losing system icons that previously showed up when it was on the left side.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] grognaz:
i think this is not lineage but default behavior now if there are to many icons they will not all show. Instead you see that little dot that i think should indicate that you have more icons that are not visible. Probably a workaround for the notches that have been introduced which reduce icon real estate.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] roxy1712:
Could be - I ended up moving the clock back to the left side and it's all good. You can change it to show more icons via GravityBox, but haven't tested it.

Here's another bug. If I make a call with mobile data disabled, it will not work if I turn it on during the call. The "x" will disappear from the signal strength icon, but there's no H+ icon next to it and no networks appear if you turn off the "Automatically select network" toggle.

Same thing will happen if I start a call with mobile data and then turn it off after the call starts. The mobile data will only work once the call is finished.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
This is not a bug but a feature introduced by Google since Android 9 (I believe). Extra icons are collapsed into a single dot when there is not enough space.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
Mobile data do not coexist with calls unless you have VoLTE support from your carrier.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] roxy1712:
Mine should, the voice call is done over LTE and the data drops to 3G/HSPDA. It still works when I start a call with data enabled (e.g., can surf the web at 3G speed while connected to a call), but will not connect if I'm already on the call and enable mobile data whilst talking.

I could also see if I can set Tasker to auto turn on data when a call comes through in case I need to use data (suddenly reminded of that old commercial where it was a big deal for iPhones to that 😆), but yeah... not sure why it won't work.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Fung-i:
Thanks for this! Unpacked and installed first thing, seems to work so far. But how do I get the google/pixel camera app?

Edit: Oh, and what's the latest on TWRP? Is it not recommended to install TWRP with LOS?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
https://www.celsoazevedo.com/files/android/google-camera/

or

https://www.apkmirror.com/apk/google-inc/camera/camera-8-2-204-362396359-12-release/#downloads

or

extract it from stock
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
@PeterCxy Are the official builds ok to flash today?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ptn107:
I flashed it. It's fine.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Fung-i:
In previous versions of Lineage(/android?) there was an option to long press the back button to force close an app in the developer section, but I can't find it in this version. Was it removed? If so, are there any good options to bring that functionality back? Thanks.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
this is a topic a little beyond this build or even just the pixel or lineage, but tasker would be the best in my opinion. At the same time I have the impression that pressing the back button multiple times in a row will force close or bring up the unresponsive dialog
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eng.stk:
It's up! https://download.lineageos.org/sunfish

Congrats on the official rollout @PeterCxy all good so far :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Since it's now official will the updater work with gapps surviving?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
It should work but I'm not sure if current Android 11 gapps have working addon.d scripts.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] a170xda:
Thanks for the "lineage-18.1-20210410".

Great work....
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
There is still no TWRP for Android 11 for the Pixel 4a or higher
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] betacrypt:
Great job with this rom. Working beautifully so far and your installation instructions were spot on. Thank you!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Finn1sher:
I'm pretty sure you van change the white balance of the live display modes in the display settings. It's been like that in past versions of lineage. But if that doesn't work for you, smartpack kernel manager has an option for it (and tons of other goodies!)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] betacrypt:
I've had some issues getting MicroG permissions fully working with this rom, specifically around allowing background location and sms permissions, also a persistent error notification with some apps that Google Play Services is not installed.

Basically you need to install MicroG from Magisk, disable it, manually install MicroG to properly allow permissions, then renable the Magisk module.

Here's what I did to resolve this in more detail:

Root your phone with the latest Magisk.

In Magisk, flash MicroG Revived and reboot.

Open MicroG and enable as many permissions as possible. (Background location and SMS might not be allowed right now)

Make a note of the MicroG version installed.

In Magisk, disable the MicroG module (do not uninstall) and reboot.

From your web browser, go to https://microg.org/download.html and only download the same version of Services Core that was installed from the Magisk module.

After downloading, install MicroG Services Core. You should be able to allow background location and SMS permissions now.

Open Magisk, and re-enable the MicroG Revived module.

Reboot your system. MicroG should be installed and working correctly.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] anthony.d:
Thanks, that was helpful.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] kzrussian:
What is the difference between this rom and the LineageOS for microG (lineage.microg.org)?
[Security Discussion] dedetok:
Please help me to remove com.android.sc (known as Android/Syringe.AD System Application) on Evercoss Genpro X Pro S50 MT6735. This Trojan exisit in the officeal firmware http://evercoss.com/img/software/EVERCOSS_S50_7_0_021_P1_180314_OE_CPB.zip

I use mtk-su to gain access to remove this trojan.

EVERCOSS_S50:/ $ cd /data/local/tmp

EVERCOSS_S50:/data/local/tmp $ ./mtk-su -v

armv7l machine

param1: 0x1000, param2: 0x8040, type: 4

Building symbol table

kallsyms_addresses pa 0x40bc2460

kallsyms_num_syms 54191, addr_count 54191

kallsyms_names pa 0x40bf7330, size 646794

kallsyms_markers pa 0x40c951c0

kallsyms_token_table pa 0x40c95510

kallsyms_token_index pa 0x40c95890

Patching credentials

Parsing current_is_single_threaded

c0362760: MOVW R0, #0x8d50

c0362764: MOVT R0, #0xc102

Possible list_head tasks at offset 0x290

comm swapper/0 at offset 0x400

Found own task_struct at node 1

cred VA: 0xc667e500

init_task VA: 0xc1028d50

Parsing avc_denied

c0aeca70: MOVW R12, #0x1278

c0aeca74: MOVT R12, #0xc113

selinux_enforcing VA: 0xc1131278

Setting selinux_enforcing

Selinux is already permissive

starting /system/bin/sh

UID: 0 cap: 3fffffffff selinux: permissive

EVERCOSS_S50:/data/local/tmp # pm list package com.android.sc

package:com.android.screenrecord

package:com.android.sc -> bloatware Android/Trojan.Syringe.AD (System Application)

EVERCOSS_S50:/data/local/tmp # pm uninstall com.android.sc

Failure [DELETE_FAILED_INTERNAL_ERROR]

EVERCOSS_S50:/data/local/tmp # pm uninstall -k --user 0 com.android.sc

Success

It still exists when I query list package

EVERCOSS_S50:/data/local/tmp # pm list package com.android.sc

package:com.android.screenrecord

package:com.android.sc -> bloatware Android/Trojan.Syringe.AD (System Application)

After I reboot the device, com.android.sc will installed its self.

Any suggestion?

Thank you

Sincerey, Dedetok
[Security Discussion] CXZa:
It use this to achieve its permanency.

GitHub - DroidPluginTeam/DroidPlugin: A plugin framework on android,Run any third-party apk without installation, modification or repackage

A plugin framework on android,Run any third-party apk without installation, modification or repackage - DroidPluginTeam/DroidPlugin

github.com

Sure, it does look suspicious, but is it a trojan?

Does it show ads? Or do some other weird stuff?

System apps do not uninstall. Just remove its folder to do it, i.e. "/system/priv-app/SystemClean". This might cause boot problems though. Depends...

What you could do is install a firewall at least to disable it receiving data from qiku.com or whatever...
[Security Discussion] dedetok:
I used Malware Bytes to scan my device, and it's reported as Syringe.AD. in apk decompile "com.android.com", it has has url string: http:// api <dot> os <dot> qiku <dot> com. I decompile the APK using JavaDecompiler online, and can be download from https://garasiku.my.id/android_malware_source/com.android.sc-1.3.3-1033_source_from_JADX.zip. But I have no skill to read the code.

"application inspector" by uniquesoft report unknown applications was installed, they are:

1. "App Settings" source code by JavaDecompiler online (APK Decompile) , and can be download from https://garasiku.my.id/android_malware_source/com.app.settings.amtapp-2.66-266_source_from_JADX.zip

2. "com.viysr.wkcx" source code by JavaDecompiler online (APK Decompile) , and can be download from https://garasiku.my.id/android_malware_source/com.viysr.wkcx-1.0-1_source_from_JADX.zip
[Security Discussion] CXZa:
I just looked the system.img file through the hex editor, so not that deep. It looked like it or some other app might try to hook some of the browsers. Then that firewall could be useless. Block at least https://api.os.qiku.com and https://api-en.os.qiku.com if you can. Although that qiku firm seems to be okay...

Odd that the stock firmware would contain a trojan...

But if so, it has planted there on purpose...

It's maybe included in some other stocks too...

English Community-Lenovo Community

https://community.umidigi.com/forum.php?mod=redirect&goto=findpost&ptid=16559&pid=92962