{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-walleye
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#walleye
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_google_muskie, https://github.com/LineageOS/android_device_google_wahoo
- Kernel: https://github.com/LineageOS/android_kernel_google_wahoo
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_google_wahoo.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Thanks for DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.
zpunout said:
Thanks for DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.
Click to expand...
Click to collapse
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.
SkewedZeppelin said:
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.
Click to expand...
Click to collapse
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.
zpunout said:
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.
Click to expand...
Click to collapse
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.
SkewedZeppelin said:
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.
Click to expand...
Click to collapse
Thanks for the tip about using a hub. It solved my headaches in recovery with the sideload command. Now the official instructions work perfectly after flashing back to stock and then DivestOS.
An experimental 12.1 based build is up with near full feature parity.
I've tested it working quite well on my taimen, should be fine on walleye.
SkewedZeppelin said:
I've tested it working quite well on my taimen, should be fine on walleye.
Click to expand...
Click to collapse
The Google Pixel 2 (walleye) with divested-19.1-20220411-dos-walley Experimental has been successfully tested on April 15, 2022, and here documented. Meanwhile, I'm running build divested-19.1-20220613 with relocked bootloader.
any new update for walleye?
galibalmasanick said:
any new update for walleye?
Click to expand...
Click to collapse
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news
SkewedZeppelin said:
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news
Click to expand...
Click to collapse
Ok,Thank You
Hi.
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Thankyou.
altromass said:
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Click to expand...
Click to collapse
Nah, you can just flash over to DivestOS.
Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!
altromass said:
Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!
Click to expand...
Click to collapse
No you don't either of those steps.
Firmware is included on taimen/walleye.
Bootloader - DivestOS Mobile
divestos.org
You only need steps 1, 2, 3, 4, 5, 6, 7, 9, 11, 12, 13, 14, 15
I'd like to use this ROM but there's one tiny feature I need root for: the app Battery Charge Limit which modifies a single, specific system file. Is there any way around it?
It sounds like a neat ROM for a spare device used solely for crypto operations, but unfortunately not for banking apps based on SafetyNet (because SafetyNet won't work without Google services).
There is no way around that.
There is no proper solution for an integrated battery charge limit.
And root is not supported: https://divestos.org/index.php?page=faq#rootSupport
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications,
*/
About:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction:
This is the unofficial Lineage OS thread for the Motorola G7, codename river.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
ROM:
lineage-16.0-20191001-UNOFFICIAL-river.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy Partitions: (To setup slot_b)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
01. Download TWRP and the Firmware for your variant from the links above.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader Instructions here.
04. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE-1: This last step installs vendor.img to slot_b as well.
05. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
06. ## Take a backup of EFS, Persist1, Persist2 then store this on your computer in a safe place!! ##
07. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
08. While in TWRP choose Reboot > bootloader
09. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM, TWRP and GApps from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Flash ROM.zip + TWRP_Installer.zip
04. Reboot > Recovery
05. Install Gapps + Magisk (if you choose)
06. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Lineage OS 16.0, ROM for the Moto G7, ROM for the Moto G7
Contributors
SyberHexen, erfanoabdi, LineageOS Team
Source Code:
[url]https://github.com/LineageOS[/URL]
android_kernel_motorola_msm8953
android_device_motorola_river_prebuiltvendor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock Vendor.img
Version Information
Status: Testing
Created 2019-08-19
Last Updated 2019-10-01
BUGS
====
1. Mobile Data can be intermittent (potentially carrier specific)
2. LiveDisplay: Default mode causes screen inversion
- Please Switch under Settings > Display > LiveDisplay > Color Profile > To Hal_Native/Standard
Release Notes:
(09/17/2019)
Device:-
* Adoptable Storage Support
* Added support HBM support for all known panels
(fixes non boot with certain screen suppliers)
Kernel:-
* Upstream Kernel [4.9.112] --> [4.9.165]
(09/08/2019)
* Included Patch for Magisk Support
* Different IMS/Telephony Implementation
(which should allow calls on VoLTE)
* LiveDisplay Adjustments
Can you share .repo/local_manifests/roomservice.xml that you use to build the rom?
I'd like to build too.
Thanks.
Great work.
Irrelevant reply, mostly due to error in OP thread;
In the first paragraph of the About it says this LineageOS is for Android Oreo (8.0) while at the bottom it is claimed for Android Pie (9.0)
Will be installing soon for better feedback, but just thought you'd like to be aware of that.
Also, would this include the Security Patch of the most recent official release or is that something not to concern myself over with LineageOS releases?
zenful said:
Irrelevant reply, mostly due to error in OP thread;
In the first paragraph of the About it says this LineageOS is for Android Oreo (8.0) while at the bottom it is claimed for Android Pie (9.0)
Will be installing soon for better feedback, but just thought you'd like to be aware of that.
Also, would this include the Security Patch of the most recent official release or is that something not to concern myself over with LineageOS releases?
Click to expand...
Click to collapse
Gotta love xda thanks for letting me know that xda reverted all my corrections to the main post over night.
So it's android 9.0 built with latest sources
Does this work for the Amazon variant of the Moto g7?
Hi, I apologize if this isn't the best place to post this, but I get an error when following installation instructions. While flashing stock firmware to slot A, I run the command `fastboot flash partition gpt.bin` and get the following output:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
I tried googling for the error, but wasn't able to come up with a clear idea of what to do to fix it. If anyone can point me in the right direction, I'd really appreciate the help. Thanks a lot.
jleprincehoff said:
Does this work for the Amazon variant of the Moto g7?
Click to expand...
Click to collapse
Last i knew Amazon Devices couldnt not be Boot Loader Unlocked
Yes they can be unlocked my g7 power Amazon is unlocked
A lightning said:
Hi, I apologize if this isn't the best place to post this, but I get an error when following installation instructions. While flashing stock firmware to slot A, I run the command `fastboot flash partition gpt.bin` and get the following output:
I tried googling for the error, but wasn't able to come up with a clear idea of what to do to fix it. If anyone can point me in the right direction, I'd really appreciate the help. Thanks a lot.
Click to expand...
Click to collapse
Try updating adb drivers or using different version
Cam Work!!! I can Capture Images and Record Video
Google Gapps - OpenGapps ARM64 Work Fine!!!
Magisk Not Work But the addonsu arm64 for lineage os 16 work!!! :good:
SyberHexen said:
Try updating adb drivers or using different version
Click to expand...
Click to collapse
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
A lightning said:
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Post result of
Code:
fastboot --version
adb --version
ptn107 said:
Post result of
Code:
fastboot --version
adb --version
Click to expand...
Click to collapse
Code:
1% fastboot --version
fastboot version 29.0.2-ArchLinux
Installed as /usr/bin/fastboot
% adb --version
Android Debug Bridge version 1.0.41
Version 29.0.2-ArchLinux
Installed as /usr/bin/adb
In addition to my Linux distro's package, I also tried downloading platform-tools with Android sdkmanager and got the same errors,
I've used lineageos 14 in the past but it's been a while.
What advantages does lineageos 16 bring compared to Moto's pie?
ptn107 said:
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Click to expand...
Click to collapse
I'm on FI with the same model.
Have you tried using older fastboot drivers or a different USB-c /USB port?
I sent the OP a pm asking if they would like any help or if they are willing to link us github information so we can start building and improving this for the River device.
Waiting to hear something back
Hell-Razor said:
I sent the OP a pm asking if they would like any help or if they are willing to link us github information so we can start building and improving this for the River device.
Waiting to hear something back
Click to expand...
Click to collapse
https://github.com/SyberHexen Here is his work.
flintman said:
https://github.com/SyberHexen Here is his work.
Click to expand...
Click to collapse
Thats not a guarantee its all the work he has done. He may still be pulling from multiple gits in a script. I would much rather talk to the op and check before trying to jump through loops that could easily be there.
EDIT: I sound like a **** there, I dont mean to be. I am just not great at this stuff so it may be nice to get a little help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS for Nokia 7.2
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint
FM radio
Sound
vibration
Bugs ?
Let me know if you see anything else. Especially please mention the issue and attach the logcat.
Installation process
Click Here for Installation process
Credits
* LineageOS Team for rom source
* Nokia for kernel source
Download Rom
Download TWRP
Join Community Group
Android OS version: 13.0
Security patch level: 2023-01
Build author: Raghu varma
Kernel source code : android_kernel_nokia_LC-SDM660
Source code: https://github.com/LineageOS
Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!
Awesome..!
Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .
Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.
xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?
xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!
i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.
Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex
Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps
Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you
Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?
Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community
Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an UNOFFICIAL build.of LineageOS 18.0 based on Android 11 for the OnePlus 7T Pro 5G Mclaren. Some LOS specific features haven't been re-imported yet so, just be aware. I did NOT create this ROM, it is an Open Source project by the community for the community and has many many contributors , some from this very thread!. thanks to all who have contributed to CyanogenMod/LineageOS over the years.
Supported device: OnePlus 7T Pro 5G McLaren (hotdogg)
Click to expand...
Click to collapse
Code:
[B]IMPORTANT[/B]
* Builds are done when they are done, and not a second sooner. Please no build begging.
* Do NOT be rude.
* If you don't get a reply from me in a timely manner about your bug, sorry i do this in my spare time
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
Built from latest LineageOS/Android 11 source
Service
Text
Data
Call
VoLTE/WiFI Calling/IMS/5G]
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Video recording
NFC
Standalone 5G
??? You tell me
Unlock Warning:
By unlocking a OnePlus phone, you can loose permanent functionality in fingerprint scanner and OTAs for Stock ROMS if improper steps are taken.
Please see 2rd post for backup instructions BEFORE flashing this or ANY custom ROMs
Join our Telegram Chat for added support
PAY ATTENTION!! DIFFERENT THEN MOST DEVICES! CURRENTLY TWRP DOESNT SUPPORT OUR DEVICE SO FASTBOOT MUST BE USED INSTEAD! GAPPS IS ALSO INCLUDED IN THE BUILD DUE TO SAME LACK OF TWRP!
(if you are comfortable with fastboot just run the following commands from fastbootd, if you are unsure of the procedure please read on IT IS DIFFERENT THEN TWRP!
Code:
(boot to bootloader)
fastboot reboot fastboot
fastboot -w
fastboot update lineage-18.0-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Boot to bootloader
from terminal/command prompt: fastboot reboot fastboot
(Don't forget the above step! This will bring us into fastbootd mode. Regular bootloader/fastboot doesn't have access to all needed partitions for flashing. You will see 'partition not found' errors)
Note: In order to access fastbootd mode, we must have stock recovery flashed until TWRP is fixed
if you are coming from a different rom wipe userdata by typing fastboot -w
now type fastboot update filename.zip where filename is the name of the downloaded zip. (e.g, lineage-18.0-20200723-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip)
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Devs
@mjevange
@Omariscal1019
@OC'D
Me
Not expected by any means but always brings a smile to my face when I see it, If anyone wants to Paypal me a couple bucks my way it would really help cuver all the coffee and smokes i go through debugging stuff haha
Thanks and happy flashing!
[*] See Post 3
[*] See Post 3
XDA:DevDB Information
[ROM] LineageOS 18.0 | Android 11 [UNOFFICIAL], ROM for the OnePlus 7T Pro McLaren
Contributors
albinoman887
Source Code: http://github.com/Team-Hydra
ROM OS Version: Android 10
ROM Firmware Required: Must be on 10.0.39 Modem or higher
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-20
Last Updated 2020-11-20
Reserved
Unlock Warning:
- This matters only if you ever want to revert to OnePlus ROMs or a fully stock phone
- Choose a method below to get backups BEFORE unlocking to prevent this
- persist.img and reserve.img are most important, but get full dump/backup to be safe
- If you need help, join our Telegram Chat
Getting your phone into EDL mode
Code:
- While holding {Vol+} & {Vol-}, insert USB
- Your screen will remain blank, you will immediately be in EDL mode
- You will have 10 seconds to interact with EDL mode, or the phone will restart into Charging mode
- If an EDL mode interaction fails, you will need to first reboot into fastboot by holding {Vol+} & {Vol-} & {Power} for 10 seconds
MSM Readback (Windows Only)
Download Tool
Grab any MSM Tool version
Obtain Backup
- Launch tool
- Select Target 'TMO'
- Press F8 (password is 'oneplus')
- Select Partitions & Hit OK
(persist.img and reserve.img are very important, but can't hurt to have a copy of everything, use Ctrl-A to select all)
- Put phone in EDL mode (SEE NOTE)
- Enumerate device
- Click Readback & Wait
EDL Tool Backup (Linux Only)
Obtain the tool
Use GIT:
Code:
~$ git clone [email protected]:bkerler/edl.git
—or—
Download ZIP: https://github.com/bkerler/edl/archive/master.zip
Prep
Use the included README for required packages / setup
Pay attention to UDEV rules, python, and pip
Backup
In the edl folder:
- Create folder named dumps
- Put phone in EDL mode (SEE NOTE)
- Use edl.py:
Code:
~$ ./edl.py rl dumps/ --memory=ufs --genxml --skip=userdata
Reserved
Nov 20
* Fixed up all the small bugs from test build
* Standalone 5G (NR SA) support, requires being on 10.0.39 or newer modem. Also be aware the signal icon will show no bars when connected to NR SA, this is just a cosmetic bug.
* Updated audio configs to to match OOS 10.0.39
* Added audio volume policy , should fix the lower then normal volume when below 50%
* SELinux is currently set to "Permissive" until I work out all the sepolicy errors
Oct 14
* Initial internal test Release
[ROM]: lineage-18.0-20201120-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Gapps: TEMP INCLUDED WITH ROM IMG UNTIL ITS FLASHABLE VIA CUSTOM RECOVERY
[Download Archive]: All ROMs
https://github.com/LineageOS
https://github.com/Team-Hydra/android_device_oneplus_sm8150-common
https://github.com/Team-Hydra/android_device_oneplus_hotdogg
https://github.com/Team-Hydra/android_kernel_oneplus_sm8150
https://github.com/Team-Hydra/proprietary_vendor_oneplus
Does this have pocket mode? .... to answer my own question no. I would love to use this with the OnePlus settings and pocket mode from aiosp
Thank you for your continued support of this phone! Your work is highly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 12.0
1. If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)
2. I will try to provide monthly patch updates and fixes as needed, don't ask for ETAs... I usually aim for the 5th of each month or whenever Google releases their patches
3. If you are coming from a previous version, I highly recommend clean flashing, otherwise you will probably have issues
Bugs:
You tell me
You tell me? I worked hard to get everything working, I don't see any other issues, please report real issues, not feature requests from MIUI or other roms.
Getting fastbootd drivers working on windows:
1. Download these drivers and unzip
2. follow the instructions here to install the unsigned drivers
3. select the windows inf
Steps:
Please follow these steps closely!
For new installs:
1. Unlock bootloader
2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)
3. In bootloader enter: 'fastboot reboot fastboot'
4. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
5. enter 'fastboot reboot recovery'
6. select format userdata
7. then select reboot to system
To upgrade from previous versions:
1. Reboot to fastbootd (adb reboot fastboot from inside android or fastboot reboot fastboot from bootloader)
2. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
3. Reboot
There is now a toggle to add SuperSU on boot in Phh Settings > Misc:
Just enable it and reboot. (Keep in mind it breaks safteynet, if you need to use a banking app, disable it from settings and reboot)
Downloads:
Latest ROM
@phhusson for his work on GSI (donate to this man, he works on dozens of devices), he worked closely with me to get everything working!
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that!
Source: https://github.com/aosp-tissot
Phh source:Link
XDA:DevDB Information
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][11.0][AOSP+GAPPS][05/11/20], ROM for the Redmi Note 9 Pro
Contributors
sooti, phhusson
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2020-10-17
Created 2020-09-21
Last Updated 2020-11-05
Changelog:
9/7/22:
* July Google security patch
9/6/22:
* Fixed the fingerprint issue in 12.1 (12L) that prevented me from releasing the latest build
* June security patch (12L)
* Some performance tweaks
* Latest Phh patches
13/12/21:
* December patch
* Latest phh patches
* Fixed battery manager crash
24/11/21:
* Fixed bt offload not working
* Fixed monet not working on other 9S versions
23/11/21:
* November security patch
* Added magisk support
* Added monet (theme based on wallpaper)
* Fixed some props not being written on boot
* Fixed some bt issues
12/10/21:
* Fixed CTS not passing (safteynet)
* Added old behavior of power button
11/10/21:
First Beta
* Android 12 Aosp base
* Optimized dalvik vm for better performance in apps
* Updated Gapps wizard and core apps to A12 base
Please report issues
RESERVED...
A job well done, thank you for keeping Curtana alive!
Any issues with your install?
Nice, thanks for the hard work, miatoll rock
New build is on the way, should fix safteynet not passing and return the old behavior of the power button
EDIT: New build is up
Changes:
* Fixed CTS not passing (safteynet), please clear google play services data if you already flashed the old build, if you enable supersu from settings then it will break again so keep in mind, its only for unrooted
* Returned the power button to the old behavior
sooti said:
New build is on the way, should fix safteynet not passing and return the old behavior of the power button
EDIT: New build is up
Changes:
* Fixed CTS not passing (safteynet), please clear google play services data if you already flashed the old build, if you enable supersu from settings then it will break again so keep in mind, its only for unrooted
* Returned the power button to the old behavior
Click to expand...
Click to collapse
Is it possible to implement a setting to have 2 behaviours of the power button as on stock? Press to unlock, or touch to unlock? Press is really preferable as it prevents accidental unlocks when carrying the phone around with the screen off.
Thanks for your hard work.
I Will install the ROM when I get back from Holiday.
Still 3 weeks
Can anyone post some screenshots??
foneiamone said:
Can anyone post some screenshots??
Click to expand...
Click to collapse
It seems there is a problem with screenshot shortcut. I took these using google assistant.
Hello. Is there call recording?
And can i upgrade from android 11? Should i wipe the phone?
mib383 said:
Hello. Is there call recording?
Click to expand...
Click to collapse
Not that I know of.
mib383 said:
And can i upgrade from android 11? Should i wipe the phone?
Click to expand...
Click to collapse
I'm not sure but i think you can upgrade from Android 11. Although i would recommend wiping the phone and doing a clean install.
Thank's for the great work. Audio bluetooth not work, the app phone work ok but show a message when os opened. Android auto don't work, when connect original USB cable, the car detect Android auto but the screen is black. With other curtana MIUI work fine.
Great work!!
I have installed it. But my magisk is broken now as i understand. Can i bring it ti life? Or i should delete it?
rezzocapo said:
Thank's for the great work. Audio bluetooth not work, the app phone work ok but show a message when os opened. Android auto don't work, when connect original USB cable, the car detect Android auto but the screen is black. With other curtana MIUI work fine.
Great work!!
Click to expand...
Click to collapse
Bluetooth works fine here, what device are you using? and what firmware is your vendor?
mib383 said:
I have installed it. But my magisk is broken now as i understand. Can i bring it ti life? Or i should delete it?
Click to expand...
Click to collapse
Off topic, magisk isnt supported by me...
sooti said:
Bluetooth works fine here, what device are you using? and what firmware is your vendor?
Click to expand...
Click to collapse
I'm using curtana 9S. I don't know firmware vendor version. How to get It or flash it?
LineageOS 20.0 unofficial build for enchilada & fajita
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source: LineageOS 20 (android-13.0.0_r20)
Buildtype: User
Kernel: 4.9.336
SELinux: Enforcing
Recovery: TWRP 3.7.0, Thanks to @Siddk for your hard work!!!
Root: Download the most recent Magisk canary .apk
Either install with "adb install app-release.apk" or download directly on your device and install with the file manager (Files). Download the most recent boot.img for your device, from the corresponding recovery folder.
Copy boot.img to sdcard, patch boot.img with Magisk. Flash modified boot.img with fastboot flash boot magisk_patched-*****_*****.img
In order to keep root across updates, see instructions here.
Included Gapps: MindTheGapps
Gcam: Included, by BSG. Don't forget to install Google Photos.
Note: You have to change one setting in gcam in order for it to work properly.
Google Camera -> Settings -> Configuration of modes -> Hardware level -> Select "Full".
Passes SafetyNet
Rooted? Install this safetnet fix (Displax v2.3.1-MOD_2.1)
All credit goes to the LineageOS team
Sources:
Kernel
ROM
Pixel goodies
Looking to expand our LineageOS 20 family! Send me a device (new or old) and I will port LineageOS 20 to it!
Are you happy with my work? Feel free to donate
Installation: Standard LineageOS installation method
Spoiler: Installation procedure (coming from 20221012 or earlier version of this rom):
Disable Screen lock (Settings -> Security -> Screen lock -> none)
Reboot to bootloader
Fastboot.exe boot TWRP-3.7.0_12 (enchilada version download link, fajita version download link)
In TWRP select advanced -> ADB sideload -> Swipe to start sideload
adb.exe sideload flashmeintwrp.zip
In TWRP select advanced -> ADB sideload -> Swipe to start sideload
adb.exe sideload lineage-20.0-LATESTVERSION-UNOFFICIAL-YOURDEVICE
Reboot to system
Spoiler: Installation procedure (coming from any other rom):
Disable Screen lock (Settings -> Security -> Screen lock -> none)
Reboot to bootloader
Fastboot.exe boot TWRP-3.7.0_12 (enchilada version download link, fajita version download link)
In TWRP select advanced -> ADB sideload -> Swipe to start sideload
adb.exe sideload copy-partitions-20220613-signed.zip (download here)
Reboot to bootloader
Fastboot.exe boot TWRP-3.7.0_12
In TWRP select advanced -> ADB sideload -> Swipe to start sideload
adb.exe sideload lineage-20.0-LATESTVERSION-UNOFFICIAL-YOURDEVICE
Reboot to system
Download links:
Enchilada version
Fajita version
Kindly report issues in this thread and post logcat output
Changelog LineageOS 20
20230112: 2023-01-05 security update,
Android r20 sources, re-implemented fingerprint swipe function, latest upstream from LOS & AOSP, minor adjustments to cutout/notch
20221213: Android 13.0.0_r16 sources, Updated kernel (4.9.335), 20221205 security update
20221121: OS built with Clang 16, updated gcam, power optimization, NFC & fingerprint tweaks
20221109: Android 13.0.0_r13 source, Security patch 20221105, fixed call recording not working in certain regions, minor kernel tweaks, NFC tweaks
20221107: Major updates to the fajita kernel, expect ∼30-60% longer endurance, updated gcam
20221106: Major updates to the enchilada kernel, expect ∼30-60% longer endurance, updated gcam
20221103: Google Camera included in build, Dialer/phone app can now record calls in any part of the world.
20221101: Unlimited Google Photos, new and improved SafetyNet-fix, Pixel spoofing.
Clear the cache for Google Play services and storage for Google Play Store.Settings -> Apps -> Show system (top right corner) -> search for playThen reboot your device. After this Pixel spoofing is working for all gapps, and device will be certified.20221016: You can now update via adb sideload in LineageOS recovery (no need for TWRP)
20221012: SafetyNet fixes. Most (all?) banking apps should work now
20221009: Fixed a major performance issue in the Fajita build
20221006: Buildtype userdebug -> user
Upcoming features: Pixel goodies (unlimited storage for photos, Google Camera and more), Linux 5.15 kernel, OTA updates, Nethunter kernel, build for fajita, SafetyNet
OTA Update instructions
Spoiler: Update instructions
1. Go to Settings -> System -> Updater
2. Reboot when prompted (you will loose root as boot.img is updated)
3. (optional) Flash Magisk-patched boot.img from fastboot to regain root
Safe to dirty flash over Lineageos 19.1, IF you completely uninstall Magisk before you do so.
Procedure:
Spoiler: dirty flash upgrade
1. Uninstall Magisk (complete uninstall) from Lineage 19.1, including all modules. 2. Flash LineageOS 20.0 unofficial from recovery 3. Reboot to system: adb install Magisk-v25.3.apk OR flash provided Magisk-v25.3.apk.zip from recovery. 4. Profit
Spoiler: Screen shots
Nice thanks for sharing it is there any telegram group from you?
Not yet. Might start one if there's enough interest.
How does this differ from the existing LineageOS 20?
Yeedatoy said:
How does this differ from the existing LineageOS 20?
Click to expand...
Click to collapse
No difference at all.
AFAIK there's no official or nightly release for enchilada (or any device for that matter, yet).
Kitch2400 said:
Kernel: 4.9.227
Download here!
Removed download links for now, to unstable. New build coming shortly.
Click to expand...
Click to collapse
Greetings. Just a friendly FYI. Please include your kernel source in your OP as per our rules for maintaining GPL Compliancy, and, is your DL link now correct?
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50
Badger50 said:
Greetings. Just a friendly FYI. Please include your kernel source in your OP as per our rules for maintaining GPL Compliancy, and, is your DL link now correct?
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50
Click to expand...
Click to collapse
Thanks for the reminder! Thread updated accordingly.
The link is correct, but I removed the rom from SF, too unstable.
No more random reboots! However now the device reboots constantly after unplugging USB/charging cable... Kinda reminds me of the first buggy tethered jailbreaks for iOS
Sorry for the delay, new build is cooking now.
Should be available for download shortly!
New build uploaded. BT, wifi, NFC, camera works perfectly. Gapps seems very unhappy and causes instability, any input is welcome.
Kitch2400 said:
New build uploaded. BT, wifi, NFC, camera works perfectly. Gapps seems very unhappy and causes instability, any input is welcome.
Click to expand...
Click to collapse
Which gapps did you use? I might try with a different gapps package over the weekend.
Thanks for this!
Might have figured it out. Will post an updated version.
Click to expand...
Click to collapse
umangtayal said:
Which gapps did you use? I might try with a different gapps package over the weekend.
Click to expand...
Click to collapse
I've tested quite a few.
MindTheGapps-13.0.0-arm64-20220917_172319.zip (my own build): boot loop
[RECOVERY]LiteGapps nano: boot loop
[RECOVERY]LiteGapps core: boot loop
NikGapps core: crash -> reboot after unlock
NikGapps full: insufficient space warning. boot loop
NikGapps basic: crash -> reboot after usb unplug
NikGapps omni: boot loop
NikGapps go: crash -> reboot after usb unplug.
MindTheGapps-13.0.0-arm64-20220903_143559: initial setup, OK, crash -> reboot after usb unplug
[MAGISK]LiteGapps_Nano: boot loop
[RECOVERY]LiteGapps_arm64_13.0_v2.6_official + LiteGappsFix.zip: boot loop
[RECOVERY]LiteGapps_arm64_13.0_v2.7_official: crash -> reboot after usb unplug
[RECOVERY]LiteGapps++_LTS_v2.5_official: LOG: not supported?
[RECOVERY]LiteGapps++_v2.5_official: LOG: not supported?
[MAGISK]LiteGapps++_LTS_v2.5_official.zip: not supported?
[MAGISK]LiteGapps++_v2.5_official: not supported?
[MAGISK]LiteGapps++_MicroG_v2.5_official: not supported?
[AUTO]LiteGapps++_LTS_v2.5_official: not supported?
[MAGISK]LiteGapps_arm64_13.0_v2.7_official: crash -> reboot after usb unplug
it restarts, when you install the gapps, and without gaps it works normally, but it is still unstable.
Kitch2400 said:
I've tested quite a few.
MindTheGapps-13.0.0-arm64-20220917_172319.zip (my own build): boot loop
[RECOVERY]LiteGapps nano: boot loop
[RECOVERY]LiteGapps core: boot loop
NikGapps core: crash -> reboot after unlock
NikGapps full: insufficient space warning. boot loop
NikGapps basic: crash -> reboot after usb unplug
NikGapps omni: boot loop
NikGapps go: crash -> reboot after usb unplug.
MindTheGapps-13.0.0-arm64-20220903_143559: initial setup, OK, crash -> reboot after usb unplug
[MAGISK]LiteGapps_Nano: boot loop
[RECOVERY]LiteGapps_arm64_13.0_v2.6_official + LiteGappsFix.zip: boot loop
[RECOVERY]LiteGapps_arm64_13.0_v2.7_official: crash -> reboot after usb unplug
[RECOVERY]LiteGapps++_LTS_v2.5_official: LOG: not supported?
[RECOVERY]LiteGapps++_v2.5_official: LOG: not supported?
[MAGISK]LiteGapps++_LTS_v2.5_official.zip: not supported?
[MAGISK]LiteGapps++_v2.5_official: not supported?
[MAGISK]LiteGapps++_MicroG_v2.5_official: not supported?
[AUTO]LiteGapps++_LTS_v2.5_official: not supported?
[MAGISK]LiteGapps_arm64_13.0_v2.7_official: crash -> reboot after usb unplug
Click to expand...
Click to collapse
damn! xD
DrangelTec said:
it restarts, when you install the gapps, and without gaps it works normally, but it is still unstable.
Click to expand...
Click to collapse
I'm aware. Think I fixed it now, new build cooking atm. Fingers crossed.
Kitch2400 said:
I'm aware. Think I fixed it now, new build cooking atm. Fingers crossed.
Click to expand...
Click to collapse
Eagerly following!
Fix for reboot after gapps found!
Will post flashable .zip here ASAP, or possibly include in build. More info to come.
Ok so I'm struggling with creating a flashable .zip that resolves the instability related to gapps, but I haven't given up!
New build with gapps-fix is cooking now, and I'm still experimenting with the .zip. Will upload whichever is done first.