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

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
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 FROM STOCK
Follow these steps if you are coming from stock. You will need access to a PC.
1. Prepare Odin, Samsung USB Drivers, PhilZ CWM Odin Flashable, and your phone with a stable USB connection.
2. Install the Samsung USB Drivers and fire up Odin.
3. Select AP and choose the PhilZ CWM Odin Flashable package.
4. Proceed to flash. Once done, reboot your device into recovery.
5. You should be in CWM recovery now. Flash this zip to get TWRP IsoRec: 20210209-boot_n7000-twrp_i9100_3311.zip
6. Reboot recovery. You should now enter TWRP IsoRec recovery. Proceed to the installation steps below, except for step 2.

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:
* 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. Click to reboot system, BUT DO NOT SWIPE TO INSTALL TWRP APP or you will end up in a bootloop!
9. Remember to install Magisk Manager if you need Magisk support.

DOWNLOAD
Google Drive
 
Last edited:

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
LineageOS 16.0

LATEST BUILD
lineage-16.0-20210211-UNOFFICIAL-n7000
kernel-e604934cd028ba34c8a52d6898658a2e6053ad8e (hikuii597)
magisk-v21.4

NOT WORKING/UNTESTED
- GPS/AGPS: untested
- DRM: untested
- IPv6: no connectivity
- Bluetooth: in-call audio not working
- WiFi: extremely reluctant to auto-connect

BUILD-SPECIFIC NOTES
- 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.
 

Attachments

Last edited:

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
Changelog

20210211
- general: upstream updates, ASB 2021-02
- kernel: enable RPFILTER (fixes tethering)
- kernel: switch back to PegasusQ governor with hotplug enabled
- kernel: restore mali400 to stock configuration (166/266MHz)
OLD CHANGELOG


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

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


20200809
- general: upstream updates, ASB 2020-08-05

- frameworks/base: ColorFade fix for exynos mali​
- device-related: merge lineage-17.1 changes from @rINanDO

20200614
- general: upstream updates, ASB 2020-06-05

- device: merge lineage-17.1 changes​
- device: remove PowerHAL​
- hardware: default video buffer size to 1080p​
- kernel: mali400 reconfiguration, use 133Mhz, 160MHz, 266MHz.​
- kernel: lock mali to 160MHz during 1080p playback​
- kernel: disable CPU hotplug​
- kernel: use interactive CPU governor​
- kernel: use 500MHz as base CPU frequency​
- kernel: reconfigure thermal throttling, refer commit
- kernel: add TriangleAway support, refer commit
- kernel: remove a whole big bunch of logging that your grandpa never check on it​

20200417
- galaxys2-common: bring back PowerHAL

- kernel/galaxys2-common: added Lineage Trust USB Restrict support (untested)​
- kernel: cherry-picked Syncthing-Fork "NAT transversal" fix (credits to @TheNatureOne)​
- kernel: switch to autosuspend (full credits to @rINanDO and @ChronoMonochrome)​

20200407
- n7000: update GPS configuration

- n7000: update build fingerprint​
- n7000/kernel: add TriangleAway support​
- galaxys2-common: reconfigure wifi configuration​
- galaxys2-common: user configurable SWAP​
- galaxys2-common: actually fix in-call audio control​
- galaxys2-common: kernel modules to system​
- galaxys2-common: add Magisk build support (credits to @rINanDO)​
- galaxys2-common/kernel: bring over LOS 17.1 commits (credits to @rINanDO)​
- kernel: implement charge current control (credits to @TALUAtXDA)​
- kernel: prevent LCD lock busfreq​
- kernel: reconfigure ASV/DVFS for BUS/GPU​
- kernel: remove inbuilt recovery​
- kernel: bring back PegasusQ, adapted from Perseus-S3 (credits to @AndreiLux)​
- kernel: raised safefreq to 1.4GHz​
- kernel: bluetooth stack update (credits to @TALUAtXDA)​

20200205
- kernel: cherry-pick mali400-r3p2-rel4 (don't expect anything from this!)

- kernel: disable modules support, KSM, LZ4 ZRAM and many other unnecessary stuffs​
- kernel: added GCC optimization flags, build kernel with -Ofast​
- kernel: a whole lot bunch of changes which is too much to be listed here​
- kernel: default CPU governor to OnDemand​
- kernel: modify CPU frequency steps back to 6steps​
- kernel: modify GPU (mali400) to 2steps, 190MHz and 267MHz​
- kernel: increase lowest busfreq from 160MHz to 190MHz​
- kernel: increase display frequency from 57Hz to 59.94Hz​
- kernel: decrease video engine clock from 267MHz to 190MHz​
- kernel: decrease shared GPU memory from 512MB to 256MB, increase GPU low-level memory to 24MB​
- kernel: slightly-slightly tune throttling configs, first throttle to 1200MHz, second throttle to 1000MHz​
- kernel: bring back FB_BLANK​
- kernel: adjust CONFIG_HZ to 300​
- kernel: add/enable exFAT, NTFS support​
- galaxys2-common: remove PowerHAL​
- galaxys2-common: revert use low-end video codecs​
- galaxys2-common: update whole bunch of framework configs​
- galaxys2-common: disable wifi adapter debug​
- galaxys2-common: more platform specific gcc optimization flags​
- galaxys2-common: fix USB info configuration​
- galaxys2-common: build libsecril-client​
- galaxys2-common: decrease ZRAM to 128MB​
- galaxys2-common: enable AOD (Always-On Display)​
- galaxys2-common: actually make macloader works​
- galaxys2-common: modify healthd to blank screen first before power off or reboot attempt in offline charging mode​
- n7000: rework GPS configuration (don't expect anything from this!)​
- vendor/samsung: add prebuilt si4709 FM driver​
- general: upstream source updates, security patch 2020-02-05​

20191009
- kernel: panel brightness optimization from i9300

- kernel: adjust unified memory allocation size​
- kernel: disable logging​
- kernel: disable pegasusq core lock​
- kernel: switch to ZEN I/O scheduler​
- kernel: fix tuning table for Q1 (credits to rINanDO)​
- kernel: misc source updates from rINanDO, ChronoMonochrome, ComicoTeam​
- galaxys2-common: remove SamsungDoze​
- galaxys2-common: use low-end video codecs (credits to ChronoMonochrome)​
- galaxys2-common: make sure burn-in protection is enabled​
- galaxys2-common: wifi hotspot channel 1-11 instead of 1,6,11 only​
- galaxys2-common: platform specific gcc optimization flags​
- galaxys2-common: lower haptic feedback intensity​
- galaxys2-common: dual-speaker output implementation (back speaker + earpice speaker)​
- galaxys2-common: fix RIL PIN unlock (credits to rINanDO)​
- galaxys2-common: misc source updates from rINanDO​
- n7000: increase minimum adjustable brightness threshold​
- n7000: fake vendor security patch level​
- n7000: conditionally reset max17041 fuel gauge on boot​
- hardware/samsung: added missing OUI mapping [SEMCO - 50:cc:f8] (credits to J..J)​
- general: upstream source updates, security patch 2019-09-05​

20190522
- Removed 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​

20190505
- Initial build

- Exclude RIL and GPS blobs due to non-working RIL and GPS​


 
Last edited:

[email protected]

Senior Member
Nov 6, 2010
2,172
748
193
@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)?
 
  • Like
Reactions: lee.wp14

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
@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.
 
  • Like
Reactions: [email protected]

[email protected]

Senior Member
Nov 6, 2010
2,172
748
193
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!
 
  • Like
Reactions: lee.wp14

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
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
 
Last edited:
  • Like
Reactions: 01000010

John Moore

New member
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?
 
  • Like
Reactions: kartalim2551

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
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

New member
May 25, 2019
2
1
0
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

Member
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
 

Zin Bo

Member
Aug 14, 2018
5
3
0
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.
 
  • Like
Reactions: lee.wp14

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
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.
 
  • Like
Reactions: Zin Bo

lee.wp14

Senior Member
Sep 15, 2015
514
390
93
Penang
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.
 
  • Like
Reactions: jerryspring