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

[lee.wp14]

I couldn't download the file, i'm using laptop.
can you upload it to another site or other link?

---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------



I got for here, is it the same file???
https://forum.xda-developers.com/showpost.php?p=81945073&postcount=236

Minor changes but it doesn't affect anyway. Yes, you can use that one, it's identical.

 

[qaddory]

Minor changes but it doesn't affect anyway. Yes, you can use that one, it's identical.

i don't know what's wrong with my phone today, yesterday i was able to log in recovery mode in TWRP, but today i cant!! just looping!!
I used odin to install recovery PhilZ-cwm6-XXLT6-XSA-5.06.1.tar , now i can log in cwm recovery .
from cwm i installed recovery-twrp3.1.0-build2-isorec-n7000 ,
wrote that install done !! but when i reboot recovery it boot back to cwm again!!

can you please write the steps with files link from the beginning ! i have odin but cant install .img file from it(as step 2 in your thread)
I really don't care about my data any more ..I want install fresh ROM.

sorry if i waste your time, i will be very appreciated for your help.
I'm sure we can do it

Please

 

[vitaly-zdanevich]

Please record a video about this firmware, I am concerned about the performance.

 

[qaddory]

Minor changes but it doesn't affect anyway. Yes, you can use that one, it's identical.

I fixed it. i flashed stock ROM.
Can you write the steps of what to do from THE START??I mean from stock ROM, so your thread will be completed

 

[qaddory]

Can you place the logcat99 file in /system/etc/init.d? Then reboot, wait for about 5 minutes then reboot recovery and attach here the file /data/local/logcat.txt

I did the same pf your steps from a stock ROM, and ofcourse i got the same result!! LOOPING!!
Now i looking for for the Path /system/etc/init.d? to copy logcat99 file in, there is no such exact path!!
olny this path /system/etc/bin OR /system/etc/usr
i attached the file in /system/etc/ logcat99 but i don't get any logcat.txt in this path /data/local/ !!!

PLEASE DO REPLY !! I"M WAITING YOU 3 DAYS!! I LOST MY DATA FOR NOTHING!! AT LEAST I WANNA GET A NEW CUSTOM ROM !!

 

[lee.wp14]

@qaddory I'm sorry, if you are in a rush it's better for you to use other ROMs instead. I am extremely busy with my academics and didn't have free time for these kind of things anymore at the moment.
I don't know, you might or might not be a new n7000 user but here is what you need to do:
1. Flash everything back to stock.
2. Follow steps to flash Nightowl's Lineageos 14/15 with TWRP IsoRec support.
3. If you can get everything work with TWRP IsoRec at this stage then only you proceed with my instructions in first post.

There's no init.d folder because:
1. maybe you didn't mount /system yet
2. maybe you are on a ROM that didn't have init.d support, like stock ROM
logcat99 is a script and has to be placed in /system/etc/init.d

That's all. Bear in mind that all developers are doing everything on the forum voluntarily and we take no responsibilities at all, as per the disclaimer in the first post. It's up to you whether you take the risk or not, and it's up to me whether I assist you with your problem or not. Why I can't come up with a zero to hundred guide is because I need to test everything before writing a guide. I didn't have time for that. You have to know that all my development efforts are done in within my every semester break only. Just one month time. When semester starts, I have to stop all my development stuffs or my hobbies completely and focus on my studies.

If you are really in rush or you felt like unable to follow with my guide, I'm sorry, please use other ROMs instead. And also, I don't know what you mean by losing your data but I already have written that repartitioning is mandatory for installation and it will destroy your data.

 

[qaddory]

I DID IT

@qaddory I'm sorry, if you are in a rush it's better for you to use other ROMs instead. I am extremely busy with my academics and didn't have free time for these kind of things anymore at the moment.
I don't know, you might or might not be a new n7000 user but here is what you need to do:
1. Flash everything back to stock.
2. Follow steps to flash Nightowl's Lineageos 14/15 with TWRP IsoRec support.
3. If you can get everything work with TWRP IsoRec at this stage then only you proceed with my instructions in first post.

There's no init.d folder because:
1. maybe you didn't mount /system yet
2. maybe you are on a ROM that didn't have init.d support, like stock ROM
logcat99 is a script and has to be placed in /system/etc/init.d

That's all. Bear in mind that all developers are doing everything on the forum voluntarily and we take no responsibilities at all, as per the disclaimer in the first post. It's up to you whether you take the risk or not, and it's up to me whether I assist you with your problem or not. Why I can't come up with a zero to hundred guide is because I need to test everything before writing a guide. I didn't have time for that. You have to know that all my development efforts are done in within my every semester break only. Just one month time. When semester starts, I have to stop all my development stuffs or my hobbies completely and focus on my studies.

If you are really in rush or you felt like unable to follow with my guide, I'm sorry, please use other ROMs instead. And also, I don't know what you mean by losing your data but I already have written that repartitioning is mandatory for installation and it will destroy your data.

It's OK bro, i did it :good: i was just wanted your last reply to put me back on track.
Your build was AMAZING and works PERFECTLY !! Thank you so much :good:
sorry for inconvenience, Good luck in your studies :good::good::good:

 

[lee.wp14]

It's OK bro, i did it :good: i was just wanted your last reply to put me back on track.
Your build was AMAZING and works PERFECTLY !! Thank you so much :good:
sorry for inconvenience, Good luck in your studies :good::good::good:

Hey pal, I'm sorry for the long reply! Things has not been going smoothly lately, I have personal issues and also academic issues to deal with.

I'm glad things work out for you! And thank you so much, so far everything is ok for me. Have a nice day!

 

[argood]

Error while installing rom

Hey lee,
greetings
I always get error 7 while installing this rom in twrp isorec or cwm why it is saying error 7 when it is the galaxy note n7000
can you please help me .
it is the indian variant with baseband version N7000DDLS6
Sorry for my bad english
Regards

 

[lee.wp14]

Hey lee,
greetings
I always get error 7 while installing this rom in twrp isorec or cwm why it is saying error 7 when it is the galaxy note n7000
can you please help me .
it is the indian variant with baseband version N7000DDLS6
Sorry for my bad english
Regards

Follow these:

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


If you can make it until TWRP isorec then just follow the installation guide in first post from beginning. It should be fine then. The base requirement is you need to have a TWRP Isorec.

Error 7 is most probably due to device identification error. And as long as your device bootup shows GT-N7000 then everything should be compatible.

 

[lee.wp14]

Build 20200809

Greetings folks. Here is a new build. Nothing special other than a minor update.

CHANGELOG
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali
- device-related: merge lineage-17.1 changes from @rINanDO

This update mainly is to address the ColorFade issue that exists and crash your system when you set to non-lowram configuration, and also bring over the gralloc related fixes and other changes from lineage-17.1 branch that looks kinda interesting to me.
This is my first build after fomatting my laptop before school reopens, so hopefully it doesn't affect anything. I have tested with a dirtyflash.

 

[argood]

Thanks for the information but TWRP Isorec was not causing the problem but the problem was coming from a partition error also I didn't properly understand the third reparation script and just repartitioned in Odin as with the first and second script it failed with error 1 both when flashing with USB otg or a SD card.
To fix this I just copied the file to the emulated storage and flashed it and then the ROM installed successfully.
I'm writing it on that phone.
Thanks,
Regards.

 

[argood]

Greetings folks. Here is a new build. Nothing special other than a minor update.

CHANGELOG
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali
- device-related: merge lineage-17.1 changes from @rINanDO

This update mainly is to address the ColorFade issue that exists and crash your system when you set to non-lowram configuration, and also bring over the gralloc related fixes and other changes from lineage-17.1 branch that looks kinda interesting to me.
This is my first build after fomatting my laptop before school reopens, so hopefully it doesn't affect anything. I have tested with a dirtyflash.

 

[goodwu]

Greetings folks. Here is a new build. Nothing special other than a minor update.

CHANGELOG
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali
- device-related: merge lineage-17.1 changes from @rINanDO

This update mainly is to address the ColorFade issue that exists and crash your system when you set to non-lowram configuration, and also bring over the gralloc related fixes and other changes from lineage-17.1 branch that looks kinda interesting to me.
This is my first build after fomatting my laptop before school reopens, so hopefully it doesn't affect anything. I have tested with a dirtyflash.

Thanks for the update.
Magisk in boot_magisk.img doesn't work in this version. It's OK in the last version.

 

[lee.wp14]

Thanks for the update.
Magisk in boot_magisk.img doesn't work in this version. It's OK in the last version.

Ah... forget to double check magisk boot image. Will test now and get back to you.
EDIT: yes indeed it's not working. I will check on it and recompile the kernel again. Will notify when fixed.

 

[lee.wp14]

Hi folks, it's my mistake... mistake in procedure when creating the magisk patched bootimage. I did it when I just wakeup so is kinda blur during that time. Sorry folks xD


I also doubt how the magisk installation is successful although the steps are incorrect... nevertheless I have updated the boot_magisk.img
Magisk should work now. Sorry for the inconvenience! Thanks to @goodwu for pointing out.

 

[argood]

Ah... forget to double check magisk boot image. Will test now and get back to you.
EDIT: yes indeed it's not working. I will check on it and recompile the kernel again. Will notify when fixed.

Thanks for the update,
Can you make the always on display a bit darker and changing it's position after a certain period because I forgot to unplug my phone because of a personal issue and it actually burned the battery percentage on the screen very severely. Can you fix it in the next update.
Regards

Sent from my [device_name] using XDA-Developers Legacy app

 

[lee.wp14]

Thanks for the update,
Can you make the always on display a bit darker and changing it's position after a certain period because I forgot to unplug my phone because of a personal issue and it actually burned the battery percentage on the screen very severely. Can you fix it in the next update.
Regards

Sent from my [device_name] using XDA-Developers Legacy app

The AOD has been configured with minimum brightness (you can notice that on minimum brightness there's no brightness change when transitioning to AOD). Currently that's the minimum achievable brightness on our device.

And actually burn in protection has been enabled also (if you check on it, the battery percentage and clock is not completely at the center of screen, there's a bit of shifting). So.... it's weird if it still burns. Actually burn-in protection is enabled system wide, like the status bar also.

For everything of the AOD is stock android behavior (except for the fact that I explicitly enabled the AOD feature). I'm not sure if we can further adjust it... need to check whether the framework overlay supports adjusting the shifting size. Might be better if you temporarily turn off AOD and turn on the Clock screensaver while plugged in, if you don't really need AOD to see notifications but just to check the clock while charging. I will check on the AOD on next update.

 

[argood]

The AOD has been configured with minimum brightness (you can notice that on minimum brightness there's no brightness change when transitioning to AOD). Currently that's the minimum achievable brightness on our device.

And actually burn in protection has been enabled also (if you check on it, the battery percentage and clock is not completely at the center of screen, there's a bit of shifting). So.... it's weird if it still burns. Actually burn-in protection is enabled system wide, like the status bar also.

For everything of the AOD is stock android behavior (except for the fact that I explicitly enabled the AOD feature). I'm not sure if we can further adjust it... need to check whether the framework overlay supports adjusting the shifting size. Might be better if you temporarily turn off AOD and turn on the Clock screensaver while plugged in, if you don't really need AOD to see notifications but just to check the clock while charging. I will check on the AOD on next update.

Thanks for reply. As I think the burn in might have caused by the degraded of the display in the last 8 years I owned the phone and my whole display is burned up like crazy because of a eBook. Regardless, I will just turn off AOD.
Sorry if I wasted your time.

Sent from my GT-N7000 using XDA-Developers Legacy app

---------- Post added at 12:30 PM ---------- Previous post was at 11:55 AM ----------

The AOD has been configured with minimum brightness (you can notice that on minimum brightness there's no brightness change when transitioning to AOD). Currently that's the minimum achievable brightness on our device.

And actually burn in protection has been enabled also (if you check on it, the battery percentage and clock is not completely at the center of screen, there's a bit of shifting). So.... it's weird if it still burns. Actually burn-in protection is enabled system wide, like the status bar also.

For everything of the AOD is stock android behavior (except for the fact that I explicitly enabled the AOD feature). I'm not sure if we can further adjust it... need to check whether the framework overlay supports adjusting the shifting size. Might be better if you temporarily turn off AOD and turn on the Clock screensaver while plugged in, if you don't really need AOD to see notifications but just to check the clock while charging. I will check on the AOD on next update.

Hey Lee I have found a way to even lower the brightness. If you go to calibrate on screen colors option and then reduce RGB values to zero percentage for all colors then it will be perfect for an Always On display I hope it helps.

Sent from my GT-N7000 using XDA-Developers Legacy app

 

[lee.wp14]

Thanks for reply. As I think the burn in might have caused by the degraded of the display in the last 8 years I owned the phone and my whole display is burned up like crazy because of a eBook. Regardless, I will just turn off AOD.
Sorry if I wasted your time.

Sent from my GT-N7000 using XDA-Developers Legacy app

---------- Post added at 12:30 PM ---------- Previous post was at 11:55 AM ----------

Hey Lee I have found a way to even lower the brightness. If you go to calibrate on screen colors option and then reduce RGB values to zero percentage for all colors then it will be perfect for an Always On display I hope it helps.

Sent from my GT-N7000 using XDA-Developers Legacy app

Nah... don't say yourself like that! I will reply to questions when I'm able to. Just that maybe I don't have much time.

That's so brilliant of you xD! I recalled of doing that when using the phone in bed during midnight last time haha..
As our device doesn't really supports AOD (there's no support on the kernel level) so.... actually hmmm maybe we can do something thru samsungdoze which I have abandoned in my builds in favor of stock AOD... not sure... need to experiment.