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

[Wattsensi]

This (not so) little phone is a miracle. I bought it back when it was released, I still have it, it still works like a charm, and with this ROM it's actually quite fast too. Thank you (and the other developers who work on this phone) for keeping this phone alive so many years after its release. It's been my go-to backup phone for years, it's practically built to last forever!

My N7000 was stolen when I was 14...I still miss it, it had CyanogenMod 10.1 and the AMOLED display and back texture were lovely, oh, and the S-Pen too. Curse the lowlifes who did that! This device showed me the pleasure of having a well supported, powerful (back then) and unique device after experiencing the hell of having an obscure Huawei Y210 stuck forever on Gingerbread, back then Huawei = absolute crap. If I remember correctly it had a single boot image for both kernel and recovery and it required repartitioning for newer ROMs...if we only had something like Project Treble back then!

btw, how does this millenia old device perform with newer ROMs? Is it still usable as a low end browsing machine? I find it impressive that this 2011 phone has Lollipop ROMs let alone Pie.

 

[argood]

My N7000 was stolen when I was 14...I still miss it, it had CyanogenMod 10.1 and the AMOLED display and back texture were lovely, oh, and the S-Pen too. Curse the lowlifes who did that! This device showed me the pleasure of having a well supported, powerful (back then) and unique device after experiencing the hell of having an obscure Huawei Y210 stuck forever on Gingerbread, back then Huawei = absolute crap. If I remember correctly it had a single boot image for both kernel and recovery and it required repartitioning for newer ROMs...if we only had something like Project Treble back then!

btw, how does this millenia old device perform with newer ROMs? Is it still usable as a low end browsing machine? I find it impressive that this 2011 phone has Lollipop ROMs let alone Pie.

It is sad to hear that and which color you have I have the white one which stains extremely easily and isn't grippy at all.
And this ROM makes the device much better in performance it can also support most of the latest apps in this ROM I was even able to play PUBG mobile lite with lowest graphics possibe and it was totally playable at a frame rate of around 3-27 fps.

 

[Wattsensi]

It is sad to hear that and which color you have I have the white one which stains extremely easily and isn't grippy at all.
And this ROM makes the device much better in performance it can also support most of the latest apps in this ROM I was even able to play PUBG mobile lite with lowest graphics possibe and it was totally playable at a frame rate of around 3-27 fps.

I had the black one with rugged back, it was so good

 

[waro470]

Hi, Lee, hi everyone!

I'd like to try this fantastic ROM, but the URL for the repit file has expired. Now, I've found something similar on Google, but it's for the Galaxy SII (i9100) and I don't know whether or not that one'll work.

Could I have a working link towards for that repit file? Thanks in advance.

[UPDATE] Link got fixed! Thank you, Lee! You rock!

 

[lee.wp14]

Hello folks!
Here is another minor kernel update. I reverted all the binder changes that were brought over to our lineage-16.0 kernel during merging of the lineage-17.1 branch from rinando i9100. It seems that some changes from lineage-17.1 brings over the RIL crashing issue to lineage-16.0 which is not to be expected. I was unable to identify any suspicious changes except for these binder changes. RIL has been crashing frequently on my side since my June 2020 build, even worse it crashed 3 times yesterday and I missed my intern placement interview call. Although very busy but I went ahead and come up with this kernel update, hoping that RIL won't crash anymore as it shouldn't crash on lineage-16.0.

Should RIL crash (shows No Service) and you are in a rush, do not reboot your phone. Instead, try to toggle on and off and on the mobile data, then turn off and on the airplane mode. Just try to play around with the mobile data and airplane mode. This will save you from a reboot.

Thanks and have a nice day!

 

[argood]

Hello folks!
Here is another minor kernel update. I reverted all the binder changes that were brought over to our lineage-16.0 kernel during merging of the lineage-17.1 branch from rinando i9100. It seems that some changes from lineage-17.1 brings over the RIL crashing issue to lineage-16.0 which is not to be expected. I was unable to identify any suspicious changes except for these binder changes. RIL has been crashing frequently on my side since my June 2020 build, even worse it crashed 3 times yesterday and I missed my intern placement interview call. Although very busy but I went ahead and come up with this kernel update, hoping that RIL won't crash anymore as it shouldn't crash on lineage-16.0.

Should RIL crash (shows No Service) and you are in a rush, do not reboot your phone. Instead, try to toggle on and off and on the mobile data, then turn off and on the airplane mode. Just try to play around with the mobile data and airplane mode. This will save you from a reboot.

Thanks and have a nice day!

Hi Lee,
Why there is a magisk img file on all of your kernels zip is it something special.

---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------

Hi, Lee, hi everyone!

I'd like to try this fantastic ROM, but the URL for the repit file has expired. Now, I've found something similar on Google, but it's for the Galaxy SII (i9100) and I don't know whether or not that one'll work.

Could I have a working link towards for that repit file? Thanks in advance.

[UPDATE] Link got fixed! Thank you, Lee! You rock!

Did the rom install on your phone.

 

[oldcuriousbee]

I have 4.0.4 version on my phone can I install this?

Hi I am new . I have Samsung GT N7000 with Android version 4.0.4 , kernel 3.0.15-N7000XXLRI-CL811902 and build number IMM76D.XXLRI .Can i install this ROM if so pl tell me the procedure.

 

[User_99]

Ever read the first op?

 

[argood]

Hi I am new . I have Samsung GT N7000 with Android version 4.0.4 , kernel 3.0.15-N7000XXLRI-CL811902 and build number IMM76D.XXLRI .Can i install this ROM if so pl tell me the procedure.

I beg you not to install this rom from ics they have a emmc corruption bug which will destroy your / data partition and if that happens you will have only 2% chance of recovery so please upgrade to Android Jelly bean and install it from there. And here is the video tutorial from stock rom;- https://www.youtube.com/watch?v=jS_qbti_lg8&t=568s&ab_channel=ExploreGadgets

 

[waro470]

Hey, I've been using this ROM since yesterday, and so far so good!

I beg you not to install this rom from ics they have a emmc corruption bug which will destroy your / data partition and if that happens you will have only 2% chance of recovery so please upgrade to Android Jelly bean and install it from there. And here is the video tutorial from stock rom;- https://www.youtube.com/watch?v=jS_qbti_lg8&t=568s&ab_channel=ExploreGadgets

Wow, thanks for the heads up! Would that be the same reason why some Samsung phone would just die at some point, e.g. Samsung S3?

 

[argood]

Hey, I've been using this ROM since yesterday, and so far so good!




Wow, thanks for the heads up! Would that be the same reason why some Samsung phone would just die at some point, e.g. Samsung S3?

No the galaxy note 1 is not affected by this issue the /data corruption issue was a issue with the stock ics kernel of the galaxy note this happened when someone tried to erase the Emmc on a stock unsafe ics and the phone will hang there and after rebooting the /data partition was rendered unusable. And the galaxy note don't suffer from Sudden death Syndrome like the galaxy s3 and note 2.

 

[lee.wp14]

Hi Lee,
Why there is a magisk img file on all of your kernels zip is it something special.

That's for magisk support, as usual if you want to use magisk then you flash the boot_magisk.img for magisk support. Magisk support means the kernel is already magisk patched, you don't have to flash magisk anymore (and you can't too), you just install da Magisk Manager and you are good to go.

Hey, I've been using this ROM since yesterday, and so far so good!
Wow, thanks for the heads up! Would that be the same reason why some Samsung phone would just die at some point, e.g. Samsung S3?

Glad the rom works well for you!



So... a brief introduction here, regarding the emmc brickbug that we have here on i9100 and n7000.

There are some (maybe most) of the emmc chip which has faulty embedded firmware. The firmware on the chip is unable to process MMC_CAP_ERASE command properly which is being used by some update binaries and recoveries. After receiving MMC_CAP_ERASE command, the firmware is unfortunately unable to process it properly and will mess up the whole chip (not sure if we can call this as a destroy) and result in a broken emmc chip (semi-recoverable in some cases, by avoiding the bad/damaged blocks in partition table).
So there's no way to actually fix the firmware on the chip, but developers fix it on kernel side, initially bypassing the MMC_CAP_ERASE. However afterwards some other fixes are being introduced which allows bringing back MMC_CAP_ERASE that seems to be required for trim operation. Not pretty sure on this, just my findings when I dig thru the commits last time.

So, in overall, the emmc is not safe. But the kernel that we use protects the chip. Apart from this, we don't really have an issue with our models. Personally what I consider fatal is the Samsung Galaxy Note 4... that is a production stage issue, where all the emmc suffer from heating issues and die at a point, which means a totally dead phone. And the only way to fix is replace the emmc or motherboard entirely. You may lookup on this, there's even a court filling regarding this matter just years ago.

 

[waro470]

So... a brief introduction here, regarding the emmc brickbug that we have here on i9100 and n7000.

There are some (maybe most) of the emmc chip which has faulty embedded firmware. The firmware on the chip is unable to process MMC_CAP_ERASE command properly which is being used by some update binaries and recoveries. After receiving MMC_CAP_ERASE command, the firmware is unfortunately unable to process it properly and will mess up the whole chip (not sure if we can call this as a destroy) and result in a broken emmc chip (semi-recoverable in some cases, by avoiding the bad/damaged blocks in partition table).
So there's no way to actually fix the firmware on the chip, but developers fix it on kernel side, initially bypassing the MMC_CAP_ERASE. However afterwards some other fixes are being introduced which allows bringing back MMC_CAP_ERASE that seems to be required for trim operation. Not pretty sure on this, just my findings when I dig thru the commits last time.

So, in overall, the emmc is not safe. But the kernel that we use protects the chip. Apart from this, we don't really have an issue with our models. Personally what I consider fatal is the Samsung Galaxy Note 4... that is a production stage issue, where all the emmc suffer from heating issues and die at a point, which means a totally dead phone. And the only way to fix is replace the emmc or motherboard entirely. You may lookup on this, there's even a court filling regarding this matter just years ago.

Oh, that was very instructive. Now, I understand even how Samsung gained a reputation for making phones that slow down over time or just plain die.

 

[argood]

Oh, that was very instructive. Now, I understand even how Samsung gained a reputation for making phones that slow down over time or just plain die.

Which chip do you have i have the safe chip and i never bricked in wiping on unsafe kernels.
Here is more info on the emmc lockup issue ;- https://forum.xda-developers.com/showthread.php?t=1644364

 

[lee.wp14]

So.. for those who are following my updates in this thread, you may recall that I have a minor kernel update days ago that I intended to fix the RIL crashing issue.

Apparently, that is not working, and now I have identified the actual commit that causes the problem (which I have been looking for since initially but I overlooked it). I have my RIL running fine for more than 48 hours now with a new build (i seriously will jump sea if it still fails xD).

EDIT: RIP me but the RIL crashes right after 72 hours. I really need to take time to figure out the underlying problem.


So here is the fixing commit:
https://github.com/hikuii/android_k...mmit/68210a296115116ac11f9fcf31a967e687c9fe16
This commit is from lineage-17.1 and is only needed on lineage-17.1, as on los17 we need to hexedit our RIL blob for RIL to work.

So here I 'release' a new build, I'm sorry but I really have no time for a proper release update post.
This build has the following changes:
1. Reverted to old camera driver
2. Reverted to old audio configuration
3. enabled zram at about 384mb (half of total ram) with lz4 compression and dual compression stream (since we have a dual core)
4. obviously, chase off the RIL issue by reverting the related commit
5. Correct the google media codec path (using non-lowend configuration)

The files for this release are being placed in google drive. This is a clean release, however I plan to delete and rebuild when I have time after I finished my exam.
As usual, only tested booting and working with basics functionality. A clean release means a clean build (yes for compiling we also have something like a dirty build, just like how you dirty flash).

Thanks and have a nice day!

 

[argood]

Hi Lee
Greetings
I have found a Android 10 based rom on your Google drive named as "POSP" which I have given screens hots for why you didn't made a thread for that rom I recently installed it on my phone and it seems to be working. I think people might be more interested in the rom.

 

[joam280]

Hi Lee

Greetings

I have found a Android 10 based rom on your Google drive named as "POSP" which I have given screens hots for why you didn't made a thread for that rom I recently installed it on my phone and it seems to be working. I think people might be more interested in the rom.

I would be happy to try it, could you pass the direct download link?

Enviado desde mi GT-N7000 mediante Tapatalk

 

[argood]

I would be happy to try it, could you pass the direct download link?

Enviado desde mi GT-N7000 mediante Tapatalk

First open the Google drive link and go to n7000》potato and here is the rom file the steps are the same as the pie rom.
https://drive.google.com/file/d/10FMdv04yNEPgS4Hmx-Kgjf5Po4JNuKnQ/view?usp=drivesdk

 

[joam280]

First open the Google drive link and go to n7000》potato and here is the rom file the steps are the same as the pie rom.
https://drive.google.com/file/d/10FMdv04yNEPgS4Hmx-Kgjf5Po4JNuKnQ/view?usp=drivesdk

let's try it [emoji6]

Enviado desde mi SM-N910F mediante Tapatalk

 

[lee.wp14]

That's quite sometime already haha... I'm not really impressed with the graphical performance and also the RIL problem (and also I don't know how to fix the GPS but now should be able because rinando seems to fixed it on i9300), thus I decided not to publish it.
Furthermore, I can't build one shot with my laptop because in Android 10 you need at least 16GB to compile or else the build will fail halfway due to low memory. My laptop only has 8GB of RAM.
Android 9 build time: 2.5hours
Android 10 build time: 5-8 hours, every time have to fail at least 1-3 times only can build finish
So it's not really convenient for me to build Android 10, plus the performance is not so promising. I decided that Android 9 should be the most practical one to maintain.