[ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 - 20200928

lee.wp14 · Mar 6, 2020

Code:

/*
 * Your (probably expired) warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

LineageOS 16.0 for Samsung Note N7000
Beware, you are about to enter a dangerous zone!

ABOUT
This is an unofficial Pie build for the Galaxy Note (N7000) based on LineageOS 16.0.
Read the sections below carefully to understand the status of this ROM and how to prepare your device for installation.

CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.

INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration:

- Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
~~- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip~~
* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.

The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card (only in Android 7).
This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.

2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired, or boot_magisk.img if you need Magisk support.
8. Prepare a coffee or tea and sit back on your couch. Reboot system.
9. Remember to install Magisk Manager if you need Magisk support.

DOWNLOAD
Google Drive

XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy Note GT-N7000

Contributors
lee.wp14
Source Code: https://github.com/hikuii

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.1-1 (Emulated Storage Compatible)
Based On: LineageOS

Version Information
Status: Stable
Current Stable Version: 20200928
Current Beta Version: 20200417

Created 2019-05-05
Last Updated 2020-09-29

lee.wp14 · Sep 29, 2020

LineageOS 16.0

LATEST BUILD
lineage-16.0-20200928-UNOFFICIAL-n7000
kernel-90af5fc754cd991d0139ed9835e49dd594287704 (hikuii597)
magisk-v20.4

NOT WORKING/UNTESTED
- GPS/AGPS: untested
- DRM: untested
- IPv6: no connectivity

BUILD-SPECIFIC NOTES
- CPU Hotplug is disabled, please monitor battery usage.
- PowerHAL has been removed to provide flexibility in adjusting CPU governor.

INSTALLATION NOTES
- When prompted in TWRP, do not install TWRP Updater app as it will cause softbrick.
- To pass SafetyNet, you must use boot_magisk.img and toggle MagiskHide on every boot.

lee.wp14 · Sep 29, 2020

CHANGELOG

20200928
- general: upstream updates, ASB 2020-09
- frameworks/base: upstream updates
- kernel: revert lineage-17.1 changes, enabled swap (thanks to @goodwu for notifying)

minors 20200809
- device: revert lineage-17.1 configuration changes
- device/kernel: enable zram at 384MB with dual stream compression
- kernel: revert lineage-17.1 binder changes

OLD CHANGELOG

Zolo2000 · Jul 29, 2011 21 5 0

Hello,
We will have Android Pie on N7000 !!!!
Great and thank you !!!
I will buy a new battery for my Note I think.

D@rekills4 · May 14, 2019 at 4:27 PM

Oh my god!
Got my N7000 out of the closet and charging it right now! Gonna flash this right away!

Thank you, @lee.wp14

D@rekills4 · May 15, 2019 at 1:48 PM

@lee.wp14, it works! It actually works great!

I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.

I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?

lee.wp14 · May 15, 2019 at 5:30 PM

[email protected] said:
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?

Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.

D@rekills4 · May 16, 2019 at 4:11 PM

lee.wp14 said:
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.

I see, thank you for this information.
I will try repartitioning in the next build.

Right now, the ROM is working great!

01000010 · May 22, 2019 at 1:09 PM

GREAT! I am eager to try it as soon the RIL works! (still using this ancient phone as a backup)

lee.wp14 · May 22, 2019

Release 20190522

CHANGELOG
20190522
- Removed unused LTE network option in Settings
- Fixed GPS and RIL functionality
- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)
- New cursor icon for stylus (thanks to ComicoTeam)
- Added xt_hl support in kernel

Notes:
- Be patient when the phone is booting up, if you have a sim lock, wait a while before entering the PIN because telephony stuffs might still be loading. You will get SIM unlock failed error if the telephony stuffs are not loaded finish yet. We are using a 2018/2019 Android on a 2011 phone, be patient

- GPS is tested OK personally by me prior to this release. If you can't get a fix or detect any satellites, make sure your GPS antenna connection is ok.
- Due to upstream changes, we are currently using Autosleep driver to let the phone enter a suspend state (doze). A shorter standby time should be expected.
- Builds are not SafetyNet OK and also not pre-rooted. If you want root, you may flash the addonsu package from LineageOS's website.
- Builds have signature spoofing enabled by default (thanks to rINanDO), you may take advantage of this to replace GAPPS with MicroG.
- This build is tested OK with GAPPS (pico ARM 9.0), please expect a longer boot time if GAPPS is installed.
- I'm not sure why, but earlier before this after I made some changes in the sources, the USB dialog won't show in Notifications panel anymore. To change USB operating mode, go to Settings > Connected Devices > USB

John Moore · May 25, 2019 2 1 0

Quote:
1. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.
2. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)
Unquote

That means I need to flash TWRP twice from stock recovery?

lee.wp14 · May 26, 2019 at 5:04 AM

John Moore said:
That means I need to flash TWRP twice from stock recovery?

Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:

> If you are from stock ROM

1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".

> If you are from Custom ROM

1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.

John Moore · May 25, 2019 2 1 0

lee.wp14 said:
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:

> If you are from stock ROM

1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".

> If you are from Custom ROM

1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.

Thanks very much, Lee.

Zin Bo · Aug 14, 2018 5 3 0

I Can't boot to twrp 3.1.0 EMU Migtation

I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp

Stuck and reboot again in logo
Please help me

lee.wp14 · May 30, 2019 at 4:40 AM

Zin Bo said:
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp

Stuck and reboot again in logo
Please help me

Can you reconfirm the situation and possibly list out your procedures?

Zin Bo · Aug 14, 2018 5 3 0

lee.wp14 said:
Can you reconfirm the situation and possibly list out your procedures?

First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery

Then flash twrp 3.1.0-isorec.zip and reboot into recovery

And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)

So i start doing step-2( that you tell for n7000 pie rom installation )

I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)

So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.

Can't go to Twrp

Thank for your reply.

lee.wp14 · May 30, 2019 at 10:08 AM

Zin Bo said:
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery

Then flash twrp 3.1.0-isorec.zip and reboot into recovery

And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)

So i start doing step-2( that you tell for n7000 pie rom installation )

I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)

So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.

Can't go to Twrp

Thank for your reply.

Can you flash back to stock to make sure everything is still OK and repeat the procedures again and stop before the step of flashing the twrp emu isorec.
Instead, extract the boot.img from the rom zip and copy to phone (you can do it using TWRP usb mtp) or sdcard, inside TWRP choose inage flash mode, and flash the boot.img to Boot partition.
Next restart to TWRP again. If you can go into twrp then you may try flashing the twrp emu isorec. See if it works this time.

dclou · May 30, 2019 at 11:45 AM

Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^

lee.wp14 · May 30, 2019 at 12:44 PM

dclou said:
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^

Galaxys2/n7000 won't support magisk as our kernel 3.0.101 does not support namespace, which is required for magisk to operate.

01000010 · May 31, 2019 at 7:23 AM

Is this ROM Treble based?

[ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 - 20200928

Senior Member

Senior Member

Attachments

Senior Member

Member

Elite Member

Elite Member

Senior Member

Elite Member

Senior Member

Senior Member

New member

Senior Member

New member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member