• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL][12][OTA][Material You][Signature Spoofing][Open Source][Encryption] LineageOS 19.0 for Galaxy Note10/Note10+/Note10+ 5G Exynos

Search This thread

Lotharioss

Member
Oct 20, 2010
30
2
Around the UK
I usually install it with twrp.
1. twrp flash
2. full erase, write yes
3. change the "data" partition

twrp / wipe / wipe advanced / select data - repair or change file / change file / ext4

4. restart recovery mode
5. flash rom, gapps, magisk optional if you want
6. reboot :)
hopefully, it will start normally, but twrp will be replaced by lineage recovery, and if you want to update the rom in future updates you should update it with lineage recovery, because if you flash twrp again, after booting this rom, it will cause errors in twrp.


The same occurs when flashing twrp. Can't boot to recovery.
 

Linux4

Senior Member
I usually install it with twrp.
1. twrp flash
2. full erase, write yes
3. change the "data" partition

twrp / wipe / wipe advanced / select data - repair or change file / change file / ext4

4. restart recovery mode
5. flash rom, gapps, magisk optional if you want
6. reboot :)
hopefully, it will start normally, but twrp will be replaced by lineage recovery, and if you want to update the rom in future updates you should update it with lineage recovery, because if you flash twrp again, after booting this rom, it will cause errors in twrp.

TWRP is NOT supported and WILL cause issues.
That issue is more likely related to firmware version, which one are you currently on @Lotharioss ?
 
  • Like
Reactions: Lotharioss

djshotty

Senior Member
Oct 7, 2008
1,065
530
East Maitland, NSW, Australia
Thank you for your hard work to build and share this ROM with us.

Are you planning to build a new ROM and bootloader unlock method for SM-N976B (Exynos 9825) devices if the user has already gone ahead and installed the Android 12 firmware update via the 'over-the-air' method? I'm growing quite tired of waiting for the update to become available in my market, and considering I've had to tolerate not having root access to my AUD$2000 flagship for the two years I've owned it from new, I'll happily install your ROM if the jerks at Samsung Australia don't get busy soon.
 
  • Like
Reactions: akaSk8krew

Linux4

Senior Member
Thank you for your hard work to build and share this ROM with us.

Are you planning to build a new ROM and bootloader unlock method for SM-N976B (Exynos 9825) devices if the user has already gone ahead and installed the Android 12 firmware update via the 'over-the-air' method? I'm growing quite tired of waiting for the update to become available in my market, and considering I've had to tolerate not having root access to my AUD$2000 flagship for the two years I've owned it from new, I'll happily install your ROM if the jerks at Samsung Australia don't get busy soon.

OEM unlocking is exactly the same on A12 firmware as on A11
Also as of today's build this ROM should work just fine on A12 firmware
 
  • Like
Reactions: akaSk8krew

Linux4

Senior Member
Thank you kindly for your fast reply. Now I'm wondering whether the stock A12 is worth waiting for, or should I jump to your ROM today?

I'm the dev so of course the answer I'd give you is yes (imo new versions of oneui just get worse and for me it's already worth it just for getting rid of samsung's proprietary crap and bloat), so would be great if someone else could give an opinion on it too.
 

djshotty

Senior Member
Oct 7, 2008
1,065
530
East Maitland, NSW, Australia
I'm the dev so of course the answer I'd give you is yes (imo new versions of oneui just get worse and for me it's already worth it just for getting rid of samsung's proprietary crap and bloat), so would be great if someone else could give an opinion on it too.
I'll give Samsung Australia until the end of this week (15th Jan) and if they haven't pushed out the stock A12 I'll grab your ROM and throw it on. How close to vanilla is your ROM, by the way? The only thing I'll need fully working - beyond the usuals like Bluetooth calls/audio, G'apps, GPS etc. - is the security permissions required by my internet banking app. so I can make point of sale payments with NFC.
 

Linux4

Senior Member
I'll give Samsung Australia until the end of this week (15th Jan) and if they haven't pushed out the stock A12 I'll grab your ROM and throw it on. How close to vanilla is your ROM, by the way? The only thing I'll need fully working - beyond the usuals like Bluetooth calls/audio, G'apps, GPS etc. - is the security permissions required by my internet banking app. so I can make point of sale payments with NFC.

Can't guarantee you that your banking app will work - likely it will require passing safetynet - you could join the telegram group linked in the OP tho and ask others about their experience with banking apps (maybe someone even got the same as you)
The other things you mentioned will work for sure.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    2
    2
    Thank you kindly for your fast reply. Now I'm wondering whether the stock A12 is worth waiting for, or should I jump to your ROM today?

    I'm the dev so of course the answer I'd give you is yes (imo new versions of oneui just get worse and for me it's already worth it just for getting rid of samsung's proprietary crap and bloat), so would be great if someone else could give an opinion on it too.
    2
    I'll give Samsung Australia until the end of this week (15th Jan) and if they haven't pushed out the stock A12 I'll grab your ROM and throw it on. How close to vanilla is your ROM, by the way? The only thing I'll need fully working - beyond the usuals like Bluetooth calls/audio, G'apps, GPS etc. - is the security permissions required by my internet banking app. so I can make point of sale payments with NFC.

    Can't guarantee you that your banking app will work - likely it will require passing safetynet - you could join the telegram group linked in the OP tho and ask others about their experience with banking apps (maybe someone even got the same as you)
    The other things you mentioned will work for sure.
    1
    Great to See the progress!

    3 questions:
    - Does MicroG work with this Version?
    - Is the comic-like voice recording gone from Video recording in LOS 18?
    - Is it somehow possible to use TWRP or another recovery?

    THX, tempe

    1. Yes
    2. *My* ROM never had that
    3. No.
  • 10
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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 here

    Downloads:

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • DO NOT Report bugs if you're using TWRP
    • 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: LineageOS Gerrit
    Kernel source: https://github.com/Linux4/android_kernel_samsung_exynos9820
    4
    Requirements:
    • Any Q or R based firmware installed on your device.

    Pre-Install Instructions

    Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.

    1. Connect the device to a Wi-Fi network.
    2. Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
      • From within the Developer options menu, enable OEM unlock.
    3. Power off the device, and boot it into download mode:
      • With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
      • Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
    4. Your device will reboot, you may now unplug the USB cable from your device.
    5. The device will demand you format userdata, please follow the onscreen instructions to do so.
    6. Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
    7. Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.

    Installing LineageOS for the first time
    1. Flash lineage recovery
      Only the provided lineage recovery will be supported,
      using TWRP might result in a possible data loss!!

      If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
      If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
    2. Boot lineage recovery
      IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
      If using Odin untick auto-reboot before flashing.
      After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
      immediately hold Volume Up and Power to boot recovery
      IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
      boot recovery via Volume Up, Bixby and Power.
    3. Factory reset using Factory reset -> Format data/factory reset
      Warning: Unlike TWRP this will also erase internal storage!
    4. Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
      Then run adb sideload <path to your lineage.zip> on your PC
      Optional:
    5. Sideload GApps and magisk by repeating above step
      with their zip/apk

    Magisk
    As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
    on every other device, no bootimage with magisk included or installing to recovery is needed!
    I also strongly recommend to use Lygisk instead,
    which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
    this will also fix OTAs getting stuck while having installed Magisk.
    2
    Features

    • SELinux enforcing
    • AES-256-XTS FBE encryption
    • Latest Linux 4.14.x kernel
    • All cameras are working
    • Ramdisk is working

    Known issues

    • VoLTE/VoWiFi
    • LineageOS specific features like livedisplay (for now)
    • You tell me
    2
    All sound systems are not working
    Who encountered this kind of problem

    Fixed builds are on the way and will be uploaded later today, sorry for this