Database Info

[Android Security Update] 2020-01

I have a couple of Nokia 7.2 phones for me and the family. Google's security patch for January 2020 (aka 2020-01) is starting to trickle down to them.
Those on a custom ROM reliant on patched monthly boot image should not update until they are completely aware of the ramifications regarding Magisk/Root-enabled access.
Screenshot attached.

Writing from my Nokia 7.2 (Stock + Magisk) I can confirm that the patch won't install if you're rooted (I assume the modified boot is the culprit, not sure though). Gives some safety to those of us who haven't disabled the "update on reboot" setting.

Just received the latest update. 1.5Gb. Still on Android Pie tho (build 00WW_1_400)

kzamri said:
Just received the latest update. 1.5Gb. Still on Android Pie tho (build 00WW_1_400)
Click to expand...
Click to collapse
Yep. My bootloader is unlocked. Just waiting for 10 before I apply Magisk again.
I mainly just want to apply Energized to block the annoying ads.
Wish Nokia would hurry up and release the 10 update. ?
Sent from my Nokia 7.2 using XDA Labs

Riccorbypro said:
Writing from my Nokia 7.2 (Stock + Magisk) I can confirm that the patch won't install if you're rooted (I assume the modified boot is the culprit, not sure though). Gives some safety to those of us who haven't disabled the "update on reboot" setting.
Click to expand...
Click to collapse
Can confirm the same thing. I imagine the next cycle will be a patched January boot image. I'm not familiar enough with Magisk to break it down like that.

February security patch is online.

Is there any way to root j3 2017 (J330F)? (Android 9.0 patch 09.2020 update)

I need to install android 8.0. I have Android 9.0 (patch 09.2020 update). I can only install android 9 (install Odin). Is Android 8 installation blocked? Is there any way to root j3 2017? (Android 9.0 patch 09.2020 update).

Hey there. Samsung doesn't allow downgrading to lower versions. If you try doing it through Odin, you may end up bricking your device. Or if you do end up getting it installed, some things in the OS like camera, sensors, etc. may not work. Hence, it isn't recommended to downgrade.
For rooting, you can take a look at the thread below to check if your model number is listed and try.
https://forum.xda-developers.com/t/...axy-j3-2017-sm-j330f-j330fn-j330g-ds.3709056/ .

Blu Vivo XL4 Rooting and Custom Rom Questions

I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.

Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
Vivo doesn't allow bootloader to be unlocked

That's nonsense, I can enable OEM unlocking in the developer settings, ain't that what's required?

Austinredstoner said:
Vivo doesn't allow bootloader to be unlocked
Click to expand...
Click to collapse
It's not Vivo company! That's a BLU company.
Jewel724 said:
I want to root this phone, mainly to turn off dm-verity because it keeps popping up even after a factory reset and this may be my only good option, but what custom rom should I use for this? I tried looking around and couldn't find any recommended ones. Blu Vivo XL4 android version 8.1.0 and the roms I looked at (Corvus OS, AOSPExtended) did not list my device for the downloads at all. Any suggestions or help for rooting this thing? First proper rootable phone I have gotten and I'm not sure the best process for this.
Click to expand...
Click to collapse
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.

DragonPitbull said:
It's not Vivo company! That's a BLU company.
You need a special steps for work. Not a exclusive file to your phone because GSI (actual custom rom for any device with Android 8.1 and next android version) need some files to fix booting that in your device. But the happy notice is about actual GSI files not need very files for fix or maybe nothing.
Try install AOSP from phhusson Android 9 and Android 10 repository to know. Other great GSI is crDroid by eremitein or other GSI files by him. Need testing.
Click to expand...
Click to collapse
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.

Jewel724 said:
I'm on.. what's it called, Oreo? Android 8. Not sure if that's going to cause any trouble for roms.
Click to expand...
Click to collapse
Yes! Android 8 from very OEMs/companies not have Treble/GSI compatibility.
Only Android 8.1 has that.
Update: Install this app https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en-US in the phone and know what architecture your phone/firmware has. That will show you which type of GSI file you can test.

Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.

Jewel724 said:
Listing what that app says..
Required Image: Needs an image file named system-arm64-aonly.img.xz
Treble and VNDK: Supports legacy version of Treble, using VNDK version 27.0
System as Root: Does not support, use an a-only OS.
ARM-64 archetecture.
Seamless Upgrades not supported.
Does not use Dynamic Partitions.
Unless I missed anything, is this what was needed? Also I am on 8.1.0 for android version, I didn't know if that was just Oreo or if 8.1 had it's own name.
Click to expand...
Click to collapse
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.

DragonPitbull said:
In the first update Android 7.1 [Nougat] to 8.0 and after upgrade to 8.1 [Oreo]. Normal.
All informations good to know what GSI you should test.
Now you can install with fastboot or Custom Recovery [TWRP]. So if has is better and fast.
If not so can using fastboot commands.
Obviusly need bootloader unlocked!
You can read and find more threads but this is good: https://forum.xda-developers.com/t/guide-blu-vivo-xl4-vivo-xi-vivo-xi.3877294/
The only part I should warn you about is the loss of IMEI. So soon as you can do backup from your phone the files NVRAM; NDATA; NVCFG with SPFT or other way like fastboot you won't have wasted time and hassles.
Click to expand...
Click to collapse
I'll give it a shot. In terms of performing a backup, I would assume that' typical "copy all files on phone to desktop folder just in case"

I should've mentioned, I don't have an SD card in my device, just a SIM card. I don't think I can use TWRP, which is going to complicate matters.

Hello I have a Blu Vivo XL4 android 8.1.0 Oreo, I'm trying to install a custom rom, I looked everywhere not a single rom is made for Blu phones.
bootloader unlocked
according to treble info:
System-arm64-aonly.img.xz
Your device supports the legacy version of project treble using VNDK version 27.0
Use an A-ONLY operating system
ARM64
Seamless upgrades are not supported
NO dynamic partitions
HELP
thanks

Can we root Pixel 3 with android 12

Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12

Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.

Thanks for help
Can u tell me is there any twrp for android 12

Not that I know of, at least it doesn't work on my rooted P3 running Android 11

Hmm so how we install custom roms

rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary

I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.

Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.

Build error : Lenovo P11 kernel

Hello, I had bought a tablet from Lenovo previousely, being Lenovo P11 which has Sm6115 qualcomm.
They did release the kernel source but for an old version of the oem firmware. As a result, it is missing drivers for newer variant of machines (They have different panels and touchscreens on newer variants) and as a result the touch screen does not work for the machine I own (Wifi variant)
Luckliy the "5G" variant of the tablet has SD765 in it but has the same touch panel (Novatek NT36523) so I tried to copy that driver to my device's kernel and I'm unable to fix this error while compiling.
This is the repo for my kernel (Yes, I did not restore git history yet because I'm lazy) : https://github.com/HexagonWin/m11_row_kernel_temp
And this is the error message : https://pastebin.com/90XAsb2X
This is 5g variant kernel : https://download.lenovo.com/consumer/mobiles/tb-j607z_opensource_tb-j607z_s130035_210706_row.tar.gz
The weird thing is that the 5g variant kernel builds properly with that same touch panel driver included in defconfig. The defconfig I'm using for my kernel tree right now is "arch/arm64/configs/m11_defconfig". Could somebody please see what is causing the issue? I'm not able to understand.. Thanks. (Including -fPIC in root makefile's KBUILD_CFLAGS didn't help.)

Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.

adazem009 said:
Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.
Click to expand...
Click to collapse
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel

LegendOcta said:
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel
Click to expand...
Click to collapse
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...

adazem009 said:
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...
Click to expand...
Click to collapse
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..

LegendOcta said:
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..
Click to expand...
Click to collapse
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.

adazem009 said:
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.
Click to expand...
Click to collapse
Then, even if we make the oss kernel working most people won't be able to benefit from it as most people already have android 11 running.
Maybe we might go with the mainline route instead, I remember hearing that people got the mainline kernel booting on sm6115, was on a oneplus device probably..

Any news?