Database Info

[Recovery][Unofficial] TWRP 3.0.2-C [r7plusf]

This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"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"
}
Full Source: Github.​Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.

...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.

Major Props ! Great job and you actually fulfilled a request of mine ! Thanks

I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?

midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.

It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks

Small update - read OP.

teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.

celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis

teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.

celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well

teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?

celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.

Is there any chance that this would be updated.?

kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.

x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........

celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?

kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.

[ROM][OFFICIAL][kirin][11] LineageOS 18.1

{
"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 :
https://wiki.lineageos.org/devices/kirin
Downloads :
https://download.lineageos.org/kirin
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 and /sys/fs/pstore/dmesg-ramoops-0. (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:

Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?

diyod said:
Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Click to expand...
Click to collapse
>Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Launcher customizations aren't brought up yet thus search bar is stuck there for time being.
>Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Power menu additions aren't brought up either.

LuK1337 said:
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.
What's not working :
WFD
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=318024
http://downloads.codefi.re/jdcteam/luk/lineage-18_0/kirin
https://sourceforge.net/projects/luk-lineageos/files/kirin/lineage-18.0
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 and /sys/fs/pstore/dmesg-ramoops-0. (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:
XDA:DevDB Information
[ROM][UNOFFICIAL][kirin][11] LineageOS 18.0, ROM for the Sony Xperia 10
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Based On: LineageOS
Version Information
Status: Testing
Created 2020-09-28
Last Updated 2020-09-28
Click to expand...
Click to collapse
Hello. Does the rom have signiture spoofing?

Gapps Not working
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.

dian1994 said:
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Did you actually reboot recovery between installing rom and gapps?

LuK1337 said:
Did you actually reboot recovery between installing rom and gapps?
Click to expand...
Click to collapse
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.

dian1994 said:
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.
Click to expand...
Click to collapse
You tried fastboot booting twrp and installing gapps there?

LuK1337 said:
You tried fastboot booting twrp and installing gapps there?
Click to expand...
Click to collapse
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.

dian1994 said:
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.
Click to expand...
Click to collapse
What fatal error are you getting on nikgapps?

LuK1337 said:
What fatal error are you getting on nikgapps?
Click to expand...
Click to collapse
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.

dian1994 said:
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.
Click to expand...
Click to collapse
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
Thanks I will give a try and let you know about the result.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
I just want to let you know that this version worked as expected. I have no explanation but probably I did something wrong with the slots. Thanks. I will keep you posted in case of a bug found. However Gapps required TWRP, Lineage recovery does not install gapps due Signing request error.

Bugs Report
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.

dian1994 said:
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.
Click to expand...
Click to collapse
1. Consider not being over 5 builds behind.

LuK1337 said:
1. Consider not being over 5 builds behind.
Click to expand...
Click to collapse
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?

dian1994 said:
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?
Click to expand...
Click to collapse
Go ahead and try.

LuK1337 said:
Go ahead and try.
Click to expand...
Click to collapse
Gotcha. Thanks.

has anyone had any luck getting magisk 21.1 to work with this rom and twrp yet?
im going round in circles trying to root after updating. i can install magisk from twrp, but i end up in a bootloop, then installing the bootloop fix from twrp wipes magisk and breaks root.
i know 21.1 is a beta and likely doesnt support sony phones yet, but someone might have a fix.
EDIT: I have root working now. Anyone having trouble, DONT install twrp to ramdisk. just leave the lineageOS recovery in place and use fastboot on a pc to boot twrp when you need it.
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.

born2bkilled said:
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.
Click to expand...
Click to collapse
Which package is it you use?
If I flash the Gapps, Lineage can't boot into system and asks for a factory reset.
I'm following the steps exactly as they're described.
Am I missing something?

Just installed it. Was some effort, coming from SailfishX.
Had to install Sony binaries first, then get the latest TWRP (old one gave me errors, the provided one in this post as well). After that installed NikGapps (Gapps or open Gapps do not work I think). Was up till 3am
Got some problems though:
Cannot enable wifi.
Does not detect cellular network at all?
GUI stopped working error at every boot (works after clicking at away).
Settings stopped responding when I click network.
Fingerprint does not seem to be working? Do I need a specifiek Gapps version for that?
Can you tell me what the camera mod does? I do not see any difference?
Thanks for the effort this far!
Edit: I seem to be missing the firmware alltogether. Any ideas how to fix this?

[ROM][OFFICIAL][sunfish] LineageOS 18.1

{
"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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com

PeterCxy said:
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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Using it now... ROM is stable, smooth and fast... as of now...
Initially, I couldn't call or text but after resetting the apn and switching it once to 2G and reverting back to 4G should fix that...( Jio users India).
Used nikgapps
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/30-Jan-2021/NikGapps-core-arm64-11-20210130-signed.zip/download

PeterCxy said:
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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
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/* (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.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Any way to use banking apps bro... (Like in descendent without magisk)

Raj Pandiyan said:
Any way to use banking apps bro... (Like in descendent without magisk)
Click to expand...
Click to collapse
I'm sorry but LineageOS does not provide any officially-supported way to bypass SafetyNet restrictions. Please look into third-party solutions for that.

I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.

Fung-i said:
I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.
Click to expand...
Click to collapse
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.

has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader

miko12312 said:
has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader
Click to expand...
Click to collapse
No problem here, flashed with mindthegapps.

any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?

PeterCxy said:
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.
Click to expand...
Click to collapse
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...

Does the "Show battery percentage in status bar" works for anyone?

HeartWood said:
Does the "Show battery percentage in status bar" works for anyone?
Click to expand...
Click to collapse
you should be able to configure the battery percentage using settings > system > status bar

wawap68 said:
any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?
Click to expand...
Click to collapse
It replaces many of LOS stock apps and stuff... So download omni variant, extract and edit nikgapps config file ( It is self understandable when you open and read it.. basically change variable from 1 to 0 which affect LOS framework and default apps like dialer etc...)... Again zip them and now sideload... It should work fine...

Got everything working passing safteynet

miko12312 said:
Got everything working passing safteynet
Click to expand...
Click to collapse
please tell us what method worked for you!

mma1162 said:
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...
Click to expand...
Click to collapse
fugured it out. It was the Magisk Fault. After reconfiguring BBS using ADB everything worked fine.
BTW the battery life is gorgeous comparing to stock ))

claviger-pc said:
please tell us what method worked for you
Click to expand...
Click to collapse
claviger-pc said:
please tell us what method worked for you!
Click to expand...
Click to collapse
1. extract the boot from LOS payload.bin
2. install Magisk 22 by patching the extracted boot image
3. hide the magisk from: google play store, play services, gpay, clear data for all these apps.
4. install magisk module safetynet-fix-v1.1.1.zip
5. reboot

Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?

droncheg said:
Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?
Click to expand...
Click to collapse
Advanced restart option is there.

Anyone coming off the unofficial build... tips? I nuked everything: went back to stock, flashed Lineage recovery, wiped/data reset, flashed zip, rebooted to recovery, then flashed MindTheGapps as OpenGapps won't install due to a version mismatch. Been stuck on the boot screen for eons.
Went back and repeated the process only to still be stuck on boot screen. Is there any log I can record/provide to figure out what's going on?

[ROM][11.0.0][Hima] crDroid 7.12 [Official] ViperFX ready, All M9s should be supported again [18.11.2021]

{
"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
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/Claymore1297/android_kernel_htc_msm8994
Download:
ROM crdroid.net
ViperFX Profile for Speaker
Unzip_me_not_flashabel
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
ViperFX is included and fully suporrted,
just disabel AudioFX or turn on legacy mode.
I dont recommand both together couse (loud bugs)
For those peopel who download over phone i suggest to turn Desktop Mode ON in Browser settings to be abel to Download directly.
Known issues:
Only FM not working, if found something
share log and we will see
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2021-05-11
Last Updated 2021-11-18

Thank you for the great work!
The gapp link is for android 10. Is it good to go on android 11?

Oh, yeah i replaced them. 10 from opengapps not work doe SDK. Nikgapps should work but remember when flash new rom also to flash Nikgapps again , in recovery it will say it will backup and install again but in the end it can lead to bootloop so after a New Build flash Nikgapps again or it will not start. i just looked at Opengapps they dont have 11 there. Or when you want to ungoogel go to /data/app and find vendig or venedig apk and delete it from Recovery in Advanced settings. So it should start without need to flash of Nikgapps

Does not boot for me, even on a clean flash, just reboots with a "TSENS reset" error
Edit : After flashing it like 10 times for whatever reason it booted up just fine, will use it some time and then give you my thoughts
Edit1: After trying to install gapps, the phone crashed on boot with the same error, like 5 reinstalls later, still doesnt work, maybe it could be because my phone is hot, i think TSENS means Temperature SENSor, ill let it cool off a bit.
Edit2: After cooling down the phone shows a different error "KP: EDAC cache: UE instance:cpu7 block L2 'A57 L2 Uncorrectable Error'
This was a very cool rom for the 30 minutes that it worked, i wish i could use it, hopefully you fix these issues.

I wiped everything, installed ROM, but always reboot after logo screen.
firmware 4.16.709.3
twrp 3.4.0.0

Seems very interesting, i tryed before upload and it worked fine by me , but i will now clean flash it and try by my self. I already have the newest build, build and will check these dont forget to thx Claymore to make this possibel

In this rom i have disabled some cores and set some Voltages to enlarge battery and normal performance.
Also i replaced the Camera app to OpenCamera couse this is just a better app for photos and sharpines, also 4k is supported in OpenCamera.

Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.

tombbb said:
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
Click to expand...
Click to collapse
What youre mean with no luck ?

Was it booting before Gapps ?
@tombbb

platinumthis said:
What youre mean with no luck ?
Click to expand...
Click to collapse
I mean the phone doesn't boot into system, keeping reboot.

platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
no, I tried only flash Rom, same reboot loop.

tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.

platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
yeah for me too, it did boot one time but after that it never booted again, with gapps or without.

pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Click to expand...
Click to collapse
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.

tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
tombbb said:
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
Click to expand...
Click to collapse
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!

pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
Click to expand...
Click to collapse
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.

pinckston said:
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
Click to expand...
Click to collapse
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...

tombbb said:
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
Click to expand...
Click to collapse
Did you tried to format /data and then install without gapps ? will this work ?

platinumthis said:
Did you tried to format /data and then install without gapps ? will this work ?
Click to expand...
Click to collapse
I always format data, wipe data,system,cache, install rom, gapp, magisk. But I will try again, maybe flash new build.
What I don't understand is why lineage ROM works?

[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!