Database Info

[RECOVERY][tulip] TWRP-3.2.3-x [UNOFFICIAL][20181214]

{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [tulip], Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Testing
Created 2018-12-14
Last Updated 2018-12-14

Reserved for changelog.

Thanks for this huge job

Is there a link the official/universal disable force encryption mod somewhere? Or are there different mods for different devices (cause of treble or something)?

Is there any possibility of having the phone encrypted and also be accessible (ability to decrypt) in TWRP? I mean is it a matter of development or is there a security measure preventing it?
Enddo said:
Is there a link the official/universal disable force encryption mod somewhere? Or are there different mods for different devices (cause of treble or something)?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

Super

Hi. I am yet to unlock the bootloader of my RN6 Pro. Once I do it I'll be getting rid of MIUI and install LOS.
In order to make the recovery work, do I have to decrypt the device? Also, to decrypt I have to flash TWRP from PC(ADB) then wipe /data from TWRP, right? TIA.

can i update this recovery on sayad1 twrp recovery from sayad1
https://forum.xda-developers.com/re...pment/unoficialtwrp-redmi-note-6-pro-t3863679
Sent from my Redmi Note 6 Pro using Tapatalk

the more important question is > any reasons to update the sayad1 twrp ?

can i flash this rom via sayad1 recovery ??
Sent from my Redmi Note 6 Pro using Tapatalk

if you know why then try and let us know if this one will be better than sayad1 twrp,
and make backup before
for flashing by fastboot you would need an img file ?

phonepete said:
if you know why then try and let us know if this one will be better than sayad1 twrp,
and make backup before
for flashing by fastboot you would need an img file ?
Click to expand...
Click to collapse
i want to flash lineage 15.1 with recovery best this one ya sayad1?
Sent from my Redmi Note 6 Pro using Tapatalk

Shivam Kumar Jha said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [tulip], Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Testing
Created 2018-12-14
Last Updated 2018-12-14
Click to expand...
Click to collapse
Thanks for your work.
Keep debugging... Regards,

Thanks for your work indeed @Shivam Kumar Jha !
I've read in the Github tha release 3.2.3-1 of twrp solved the decrypt issue for many devices. Can anyone try to build it for tulip?

Hi Shivam Kumar Jha,
Do you have any news about decryption that does not work?
Regards,

[ROM][STABLE][R7S/R7Sf][OFFICIAL][9.0] LineageOS 16.0 (Qualcomm)

{
"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 is a free, community built, aftermarket firmware distribution of Android 9.0 (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.
Devices supported by this package :
Officially: Oppo R7S ( R7Sf / R7Sfg / Snapdragon Model Only! )
What's working :
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
GPS
What's not working :
Instructions :
Official Instructions here in LOS Wiki.
Download the latest build and gapps arm64 for 9.0
Open GApps (choose the variant you want. Recommended nano package)
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds
ROM : https://download.lineageos.org/r7sf
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
Phone model (R7Sf, R7Sfg):
LOS version:
LOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
LOSSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
[MENTION]My wife[/MENTION]: For her patience
[MENTION]Uberlaggydarwin[/MENTION]: For you know what!
[MENTION]mikeioanna & maniac103[/MENTION]: For all their amazing work on the R7 series!
Unknown Oppo Dev: For providing the PS Kernel Source Code
LineageOS Team
Donations :
Please consider donations to support development.
mikeioannina: Donating via PayPal without him LineageOS 16.0 for the R7sf would not have been possible!
XDA:DevDB Information
LineageOS-16.0 for Oppo R7S (1080p), ROM for the Oppo R7S
Contributors
mikeioanna,maniac103,celoxocis
Source Code: https://github.com/LineageOS
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.10.108
ROM Firmware Required: Unlocked bootloader
Based On: LineageOS 16.0
Version Information
Status: R7Sf entered Official builds.
Created 2019-04-17
Last Updated 2019-04-17

*reserved*

Please make sure before upgrading to LineageOS 16.0 to read the Official Instructions here in LOS Wiki carefully!
Make sure before flashing you upgrade the TWRP version with the one provided in the instructions page due to changes to support hardware accelerated encryption on our R7S!
You will run into issues if you do not upgrade to the provided TWRP version!
I recommend a clean install due to above changes.

Followed the instruction exactly but wifi does not work (mac address 02:00:00, it can not find any AP...)
If someone has this issue like me, flash back to Spectrum then boot into it and connect to some AP, then flash LineageOS again, but do not wipe anything.

Does Pixel Launcher work for you?
It crashes on my phone. A workaround: https://www[.]reddit[.]com/r/LineageOS/comments/awjvnk/lineageos_16_stock_open_gapps_pixel_launcher/

Working well so far even though I updated using twrp 3.2.3
Only issues are, app permissions seem to show up when they want and bluetooth connection can be ropey depending on device. Have one receiver with no issues but my Sennheisers cant keep a connection from two feet. Will try re-pairing.
Thanks to you all. :highfive:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?

LordAlberto said:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?
Click to expand...
Click to collapse
Why not use Magisk?

trmdi said:
Why not use Magisk?
Click to expand...
Click to collapse
I do use magisk, I need to install this beforehand or magisk doesn't work.
When I first installed 16, I read that lineage removed the su binaries so there is no root out of the box.
Bit of a pain really.

When the screen is locked, you're still able to swipe down from the status bar to expand it to show buttons. Is there any way to disable expanding the status bar when the screen is locked?

Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?

Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/

Luuta said:
Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?
Click to expand...
Click to collapse
The recommended TWRP image is actually a lower version than the official image through the TWRP app, and that's why my recovery got screwed up. I'd flashed an earlier image onto a later one. The recommended one would probably be the one to use if you were switching to Lineage for the first time, maybe? Just to warn people not to be as careless as I am!
I spent half a day messing about with getting the tools again to perform a flash from my pc. Every time, I end up relying on "Minimal ADB & Fastboot" because I have no luck getting any other driver package to work. But this package really is the smallest pack to get it done and it makes it easy to use, thank goodness.
Thanks to the developers for continuing to work on the phone. I'm loving Android 9/Lineage 16. There isn't much of a visual change, which is great. Under the hood, it's more obvious, but it's definitely running much smoother than L15 already.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
trmdi said:
Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/
Click to expand...
Click to collapse
There will, of course, be changes, or it wouldn't be offered. Most changes are bug fixes or security updates, so you wouldn't necessarily notice any change.

Maybe the gestures are sensitive but every time I go out, the phone always opens my music player at destination. Have turned them off see if it happens again.
Never happened on 15.

Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...

LordAlberto said:
Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...
Click to expand...
Click to collapse
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...

Luuta said:
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...
Click to expand...
Click to collapse
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.

LordAlberto said:
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.
Click to expand...
Click to collapse
Ah, yes, it loses the pairing in our car, too. It's a small annoyance, can live with that!

is anyone success to install magisk on this rom ?

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
yes. I flashed it right after flashing the rom without any problem.

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
On page one of this thread I've linked the su code to get magisk to install.

[ROM][H830,H850][UNOFFICIAL] LineageOS4Microg 15.1 [8.1] - 2020 Build (by Bernie_nix)

{
"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:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), 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.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Why build Oreo Now? What about other variants of the G5?:
Oreo is very stable on the h830 and works great with microg. I'm using this build now. This is also a build I am interested in maintaining and comparing to a future Pie build with microg built-in. Unfortunately, Android 17/Q is not yet fully compatible with microg.
Working:
5ghz WiFi, camera, calling, bluetooth, great battery life. USB-C audio earbuds work great. Reported that NFC works.
You tell me.
Known issues:
Please test WiFi, NFC. IR blaster not working for me but I may need to find a suitable app; please test. FM radio reported not working.
Automatic updates not yet implemented but will be in next build.
You tell me.
Install Instructions (If coming from another rom):
Prerequisites: Coming from another rom with Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Wipe your device. Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these (if in twrp. if in ofox, wipe system but do not wipe system 10)
(3) Select Format Data Button. Type yes
(4) Select Install button. Choose rom zip. Swipe to confirm flash.
(5) Install Magisk if you choose.
(5) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(6) Reboot. Phone may or may not mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then boot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Upgrade Instructions (If coming from my previous build):
Prerequisites: Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Select Install button. Choose rom zip. Swipe to confirm flash.
(3) Wipe caches.
(4) Magisk should persist after reboot but if not, go back into twrp/ofox and flash it.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Tips for Use
1. Root can be enabled in this build (if not installing Magisk) by going to Developer Settings->Manage Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you ​4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. I've found Hypercam to take excellent pics with our cameras. Please download for the G5 here: https://gcambrasil.com.br/lg
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & Limits
This thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A; doing so allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
New Builds:
Mar. 5, 2020 Change log
1. Latest security update
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Mar. 5, 2020
H830 Download link: https://www.androidfilehost.com/?fid=4349826312261742170
H830 MD5: 8bd86770d84b94a5d999489c7f993db6
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261742710
H850 MD5: 6fe7febb5b4f994a1f32af18390a988c
Older Downloads:
Feb 29, 2020 Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Feb. 5, 2020
H830 Download link: https://androidfilehost.com/?fid=4349826312261734920
H830 MD5: 017e4f8352f670e1d409bbce34490178
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261735367
H850 MD5:fb428e8a245e06d66037a4254b519ebf
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_msm8996-common
Last Updated Mar. 11, 2020
Thanks to x86cpu's posts, Dark98, Electimon, Gabi and the countless others who helped me out!​

Will test the h850 build as soon as you release it! :good:

I would love this for the h840! Oreo and security patches sounds great.

ml11ML said:
Will test the h850 build as soon as you release it! :good:
Click to expand...
Click to collapse
Build posted. See link in first post.

LollipopLover said:
I would love this for the h840! Oreo and security patches sounds great.
Click to expand...
Click to collapse
I would love to build for the h840, unfortunately it seems harder to build for. Not seeing a whole lot of sources or development on that variant.

Thank you anyway. I'll always have hope.

Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?

ROMSG said:
Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?
Click to expand...
Click to collapse
Yes I will continue forward to make an los 16 microg build. As far building yourself, please read the first post. I will not answer any questions related to building in this current thread after my response below.
I'm going to put together some info on GitHub with required files and some instructions to build on Ubuntu. In a nutshell, you install docker on Ubuntu, install the microg docker container and then supply a manifest file for the docker to download sources, etc.
I don't provide support for building in my threads because it's off-topic and really adds quite a bit of support that is better provided in its own unique thread where many members can help. I would be happy to answer questions in a Q/A thread of its own, on GitHub or in a telegram group.
If anyone is reading this and knows of an active telegram group for the g5 please message me and I'd be happy to provide assistance there. Otherwise wait until I update on GitHub. I have my reasons but do happily share in the spirit of open source. A ROM release thread is not the place to do it.

Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.

ml11ML said:
Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.
Click to expand...
Click to collapse
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side

Bernie_nix said:
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side
Click to expand...
Click to collapse
I see. Anyway thank you for looking into the IR issue as I agree that it's a great feature and also the fm radio. I would not have any problems with it being a magisk module if it can't be added to the rom. And yes, the phone runs great with this rom so far. Very responsive and minimal battery drain even with my half dead battery that dies at 50%. It is definitely my new daily driver.

New build released to update to March 2020 security update. See 1st post for download links.

Bernie_nix said:
New build released to update to March 2020 security update. See 1st post for download links.
Click to expand...
Click to collapse
Installed on my h850 over the old build and wiped cache and it works. :good:

ml11ML said:
Installed on my h850 over the old build and wiped cache and it works. :good:
Click to expand...
Click to collapse
Great to hear. Thanks for your feedback!

Cnt install googleplay store.

mie_ayam said:
Cnt install googleplay store.
Click to expand...
Click to collapse
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.

this rom have low mic issue and low sound issue?

Zorcnecrophades said:
this rom have low mic issue and low sound issue?
Click to expand...
Click to collapse
I know that Los usually has lower sound. Haven't experienced the lower mic myself but I could be wrong. You could probably easily edit some mixer_path volumes if it is not to your liking.

Hi, real cool rom. thanx a lot. But: PicoTTS does not work. App shuts down in test. And Hdmi (or Slimport??) on an OTG does not work.
And the LG Camera Plus add-on-piece is not recognized
Is H850_v2.2-mk2000.zip compatible with this rom? or maybe H850_v0.3-BETA2-mk2000.zip?
(after Test) No its not, camera is not working with both kernels and Android says, thats the Vendor Image is not right, when i reboot. What ever that means
P.S. The rest is really stable after 2 days of testing.#
P.P.S. Changing BT Connections from one (Airpods Gen 2) to another (JBL Charge 2) while playing music reboots the phone.

Bernie_nix said:
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.
Click to expand...
Click to collapse
yes. because I am accustomed to downloading apps on Playstore. and some applications when we want to log in using a google account. can't log in using a google account that is included in the Google Microg app.
Thank this rom great . mybe this is litel bug.

[UMX U693CL Recovery/Rom/Root RELEASE]

{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U693CL
Recoveries
OrangeFox_10 Recovery
Roms
AssuranceRom Custom Stock- Android 9
OmniRom Custom GSI- Android 9
CrDroid Custom GSI- Android 11
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
3- Pip install Command: sudo apt install python3-pip
Rom Notes/Disclaimer/Warning
**Don't Deviate From The Install instructions Or The Rom Won't Install Correctly**
**The AIO ToolKit Unbrick Option Is Not Meant To Be Used As A Daily Rom**
** Flashing AssuranceRom Will Bypass FRP Locked Devices **
**Battery Stats Are Broken On GSI Roms**
**Only Use OrangeFox Until Further Notice: 11-15-2021**
-AssuranceRom Clean Flash Installation-
1- Move AssuranceRom To Device(External SD)
2- Boot Recovery
3- Wipe Cache, Dalvik Cache, Data
4- Install AssuranceRom
5- Enjoy!!
-Custom GSI Roms Flash Installation-
1- Move GSI Rom zip To Device(External SD)
2- Boot Recovery
3- Wipe Dalvik, Cache, Data
4- Install Custom GSI Rom zip
5- Boot Custom GSI Rom & Wait Until A-Team Notification
6- Boot Recovery With Normal Reboot and Hold Vol+
7- Enjoy!!
Contributors
Thanks To @deadman96385 for the Firehose Programmer
Thanks To Brenton Miller For The Substantial Donation For Continued Dev Work On This Device
Also Big Thanks To Brenton Miller for September 2021 Device Firmware Files
Big Thanks To The Folks Who Have Come To A-Team Telegram Group To Help Test
Device Downloads
UMX U693CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions​

-Updates-
6-17-2021: Setup for Official Release
6-19-2021: Initial Package Release, Bugs Expected, Recovery Tree still needs some work
6-27-2021: AIO ToolKit Release, removing Initial old release. ToolKit is unfinished and missing some recoveries but is working. I'll add the remaining recoveries and such as time permits
6-28-2021: ToolKit Update v0.06. Dumping options added to Dev Menu, Custom Stock/unbrick Images further tweaked, bugfixes, menu tweaks, etc...
7-3-2021: Added option to remove device encryption, custom stock/unbrick option now a menu, DarkStar Recovery added to recovery menu, disabled first boot setup screen, removed a couple more bloat apps
7-9-2021: AssuranceRom v0.07 recovery flashable zip released, AIO ToolKit v0.09 released, changelog and installation now included in toolkit, removed DarkStar and Batik Recovery(Too Old and Missing Needed Features), Added OrangeFox Recovery, Added PitchBlack Recovery, Android 9 GSI roms tested booting, Android 11 GSI roms tested booting
7-24-2021: AssuranceRom v0.08 Recovery Flashable zip Released, AIO ToolKit v0.10 Released, Changelog now included in the ToolKit Package
8-31-2021: Rude people associated with this device and I'm bailing, go find some other sucker willing to give up their free time, for free, only to be bashed.
9-16-2021: Re-Added Link for The Files, enjoy.
10-21-21: Fixed Main Thread Post, Planned updates are 2 more recovery builds, posting device tree source for all recoveries, update AssuranceRom based off newest OTA release, several planned updates for AIO ToolKit, investigate fixing Lockscreen bug when encryption is disabled, investigate fixing dialer not being set as default dialer on first boot(Magisk Script Not Kicking in Like it should)
10-22-2021: Added TWRP_10 Device Tree to Github & Updated Post Link, TWRP_10 Added to Device Downloads but not yet added into the ToolKit.
11-11-2021: Fixed MTP in Recovery, Fixed Decryption in Recovery, New version of AssuranceRom based off September 2021 Update, AssuranceRom Lockscreen bug fixed, AssuranceRom Dialer bug fixed, Device is now using default encryption since recovery has working decryption AIO ToolKit Updated to reflect new recovery builds, AIO ToolKit Updated to reflect updated unbrick files, several small tweaks to AIO ToolKit, TWRP_10 Updated in ToolKit, OrangeFox_10 Updated in ToolKit
11-12-2021: AIO ToolKit v0.14 Release- Broke Unbrick Option into 2 parts, ReadMe explains this more. Unbrick options will now auto reboot device after flashing, Added Option 9 for testing ADB Connectivity, AssuranceRom v0.10 Release, Re-Added Google Dialer into AssuranceRom(Now set to default dialer), Added AssuranceRom Installation Instructions to Main Thread Post
11-13-2021: AssuranceRom v0.11 Release, Post Boot Setup Script properly adds preset settings now for X-Plore, Preset settings for NovaLauncher, Added Custom Lockscreen wallpaper and wallpaper, Added a bunch more preset device settings to Post Boot Setup Script. Device will now auto reboot when Post Boot Setup Script is complete so that the changes and settings can be applied, Updated NovaLauncher, AIO ToolKit v0.15 Release, NovaLauncher Updated in unbrick System Image, Added Installation Warning on Main Thread Post
11-14-2021: Prep Main Thread for Custom GSI Releases, OmniRom_A9_Custom_GSI-UMX_U693CL-v0.01.zip Release, AIO ToolKit v0.16 Release(Unbrick Option 1 BugFix)
11-15-2021: AssuranceRom v0.12 Release(Consult ChangeLog), OmniRom v0.02 Release(Consult Changelog), AIO ToolKit v0.17 Release(Remove TWRP For Now)
12-5-2021: CrDroid Custom GSI v0.02 Release, Working Assurance Service and Volte OOTB, All GSI Roms will only require 1 install now , I will eventually spread that out to AssuranceRom as well in the future.
1-4-2022: AssuranceRom v0.13 Release, AIO ToolKit v0.19 Release, consult ChangeLogs for changes

I would love to beta test this if possible, and assume all risk that may come with it as my own problem.
Fcking suuuper excited to make this garbage phone just a little less stinky. Thanks for putting this all together!

lol I just noticed I am considered a new member... after 11 years on the site. Must be cause I lurk.

I am interested in an orange fox recovery. But at this point any will do. So, how does one get past the fastboot issue this phone has?

Striking gold once again I see, much thanks and kudos to you,can't wait for release

Thanks alot

I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?

tesell said:
I ****ed up and forgot to make a backup of data first. Anyone have the Assurance Wireless APK for activation backed up?
Click to expand...
Click to collapse
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine

timjames474 said:
Unless you're still on a Sprint sim,it shouldn't be needed. I'm on the new T-Mobile tower sim and did initial activation on a GSI just fine
Click to expand...
Click to collapse
sweet, yeah, i think i am on t-mobile, pretty stoked with it so far. unlimited tether data, and now that its rooted, my vpn works. thinking about cancelling my xfinity.

There a step by step guide?

OK got it worked out what rom you recommend for this device there along on the page lol

I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?

Minalia said:
I'd like a step-by-step guide too. It would save people a lot of trouble if they don't know this particular method of unlocking. Also, is there a way to unlock the assurance sim card for use on other devices?
Click to expand...
Click to collapse
Assurance locks the SIM to the IMEI network side,so short of commiting felonies no you can't. Good news is the UMX is sim unlocked out of the box,so you can go to any T-Mobile,AT&T or Sprint MNVO(May need to call ASW and tell them to cancel your service for Sprint ). SafeLink is a good choice for lifeline

An AIO ToolKit is about to be released for this device, I wrote it to handle everything from fresh untouched device to fixing a soft-bricked device. The initial release will be removed shortly and this new ToolKit is for Linux...

Thanks for all your work, assurance sent my grandfather a wiko phone, He received a call and from the phone call. the phone was bricked aswell as some chinese ransomware looking malware. Called assurance and their sending this malware infested UMX again, thanks to you though I can get off that malware infested os and onto stock android! Keep up the great work!

tx for this toolbox coming out!
i got this phone via assurance, and indeed, it not only installs many apps/websites with zero user control, but also apps with all chinese characters, and that was right out of the box. a month later i called assurance to stop my service with them, though i've kept this phone. they asked why i was stopping their service, and i just told her it was enough that i had daily apps/games/sites installed without my permission or control, but that some of them were in a chinese character set; this from a phone given to u.s. citizens applying for federal help during covid.
i now use safelink instead, which just gave me a sim for my pixel 3a, much simpler/safer than assurance.

This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
I followed the guide step by step but as I have attempted other root options in the past, I think it caused my phone to soft-brick due to those past attempts that I tried with only my own limited knowledge.
So this is my personal experience, only posting for others in the event that someone else has a similar or identical issue. The issue(s) I had were almost certainly not at the fault of the person who wrote this guide, just FYI. For many, their process has proved successful first-try, as you'll see within the comments.
Again, MY experience:
FIrstly, I had to do things differently. So I DID NOT flash anything to the boot partition. I SKIPPED THAT STEP. (Of course this is after my first try when I followed the post's instructions. After my first attempt I found myself in a soft-brick situation. Luckily, I have two of these devices so I was able to rescue the device using the working device's firmware and I only flashed recovery to begin with, and then booted into TWRP, pushed Magisk and installed it...error. Sideloaded Magisk, SUCCESS!
(Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've got you some Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. PitchBlack wouldn't show my files AT ALL so options were very limited with that recovery.
And other than that, this guide is awesome! I'm now rooted, and I've got LSposed and even changed my font with a magisk module, as well as the boot up screen haha.
Thank you so much to @PizzaG , for not only putting this together but for taking the time to share and help others.
(TAKEN FROM ORIGINAL POST-UNCHANGED): We really appreciate your effort and your sharing with us!!! You ARE AWESOME!

clintongsan said:
This is an awesome feat. I thank you so much! BUT I do need to explain a couple points from my experience doing this, just in the event that it maybe helps someone out.
FIrstly, DO NOT flash anything to the boot partition. SKIP THAT STEP. I did this and it bricked my phone. Luckily, I have two of these devices so I'm currently trying to use the other to pull the firmware off, partition by partition, in hopes I can restore the first one with it, without copying over device info....we'll see lol. But yeah, all you need to do if you want this awesome guide, created by these wonderful devs, to work, is just flash the recovery image...reboot into recovery. (You can hold power and volume up until you see the screen flicker/flash, then let go of power or both power and vol up (I don't think it matters) and wala! You've got into TWRP.
Now, either install Magisk off a microSD card OR just sideload it using adb sideload (path to magisk). I used the latest Magisk from their website. (Always use software from the creator's site/forum, even when you know you can get it here...just to ensure you're getting a safe and up to date version). Once you've sideloaded Magisk, you can choose to flash any of the recoveries...(I used OrangeFox and TWRP. OrangeFox is prettty cool, but I don't see backup/restore options like in TWRP. I'm sure it's there somewhere I probably just didn't look well enough.
And other than that, this guide is awesome! I'm now rooted, unlimited data (xposed framework modules) and completely dark-mode across the device (again, xposed modules). I even changed my font with a magisk module and the boot up screen haha.
Thank you so much to the guys/girls/team that put this together. We really appreciate your effort and your sharing with us!!! You ARE AWESOME!
Click to expand...
Click to collapse
you are false in giving people that "advice" if you were in the test Telegram group for this device, you would surely know that 3+ people have been testing the ToolKit without issue. I post the Telegram link for a reason. So if people have an issue with something, instead of badmouthing an option or feature, you come get live help to fix the real issue at hand, which is not flashing the boot image.

So I pushed root for this device and installed a batick recovery and bootloops, trying the unbrick restore.

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!