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

[ROM][PORT][7.1.2][N950F/DS] LineageOS 14.1 & Resurrection Remix for Note8 (Exynos)

Search This thread

xperiaking247

Senior Member
Aug 5, 2014
150
16
Sarajevo
We seriously need to figure out how and who we should also to make the note 8 treble compatible.
If someone figures that out, the possibilities will be endless.

Missing LineageOS/AOSP ROMs too buddy - would have bought a different phone if I had had the choice back then.

Same here man, I wanted to buy a Pixel 2 XL or a Note 8. I made the biggest mistake in my life lol.
 
One other way for them to port treble is if they use a partition on sdcard as vendor ex. mmcblk0p2 (second partition of EXTERNAL sdcard). Before "mmcblk0" was the primary emmc chip, but now it's "sda".
Upside of this:
We could port treble without a chance of hard bricking the device by re-partitioning it
Downside of this:
The system might be EXTREMLY slow due to sdcard read/write speeds
I edited the kernel boot img to boot the entire system from sdcard, it was very slow. All partitions were cloned to an sdcard. Only thing you need to do to swap OS is to just flash the kernel. I needed 2 hours to complete the phone setup, it needs 20-30 seconds to unlock the lock screen, 5 minutes to open settings app. Now I had all partitions there, like /data /cache /system /efs and all others (21 in total), and an extremly slow 5 mb/s sd card.
I don't know how it would behave if it was just /vendor, because Note8 current vendor folder is ~250mb, and I don't know how often the OS would read it.
And of course another downside is if you eject the sdcard, the system would crash.
 

PivotMasterNM

Senior Member
Jan 19, 2013
278
231
Düsseldorf
One other way for them to port treble is if they use a partition on sdcard as vendor ex. mmcblk0p2 (second partition of EXTERNAL sdcard). Before "mmcblk0" was the primary emmc chip, but now it's "sda".
Upside of this:
We could port treble without a chance of hard bricking the device by re-partitioning it
Downside of this:
The system might be EXTREMLY slow due to sdcard read/write speeds
I edited the kernel boot img to boot the entire system from sdcard, it was very slow. All partitions were cloned to an sdcard. Only thing you need to do to swap OS is to just flash the kernel. I needed 2 hours to complete the phone setup, it needs 20-30 seconds to unlock the lock screen, 5 minutes to open settings app. Now I had all partitions there, like /data /cache /system /efs and all others (21 in total), and an extremly slow 5 mb/s sd card.
I don't know how it would behave if it was just /vendor, because Note8 current vendor folder is ~250mb, and I don't know how often the OS would read it.
And of course another downside is if you eject the sdcard, the system would crash.

great findings. so correct me if I'm wrong, but our main issue is repartitioning and not bricking the phone by doing that.

But: there is an option to repartition in Odin. So my question would be - if we have a NANDROID backup of EFS etc., and we do **** up at repartitioning the phone, couldn't we restore it by reflashing the stock software in Odin with repartitioning enabled and then flashing EFS etc?
 
great findings. so correct me if I'm wrong, but our main issue is repartitioning and not bricking the phone by doing that.

But: there is an option to repartition in Odin. So my question would be - if we have a NANDROID backup of EFS etc., and we do **** up at repartitioning the phone, couldn't we restore it by reflashing the stock software in Odin with repartitioning enabled and then flashing EFS etc?

It's true. Odin way is more safe, but the PIT file needs to be carefully crafted. On some cases, even official binaries HARD BRICKED the phone when re-partition was checked in odin. So yeah, it is an issue. I remember when I did nand erase all on J7 prime 32 gb and it became 16 gb. Flashing again fixed the issue, but there are countless stories of people hard bricking phones just because re-partition was ticked. You can't do anything at that point. There is a possibility of a recovery from such situation, but has not been confirmed. I've read that people recovered their devices by flashing 200mb of nand at start of the memory (of working donor device, has to be the same model as bricked) to sdcard and booting to download mode from that and Re-partitioning internal storage again with odin. I know SOME snapdragon devices can be recovered from a hard brick, but the issue is if exynos device gets bricked it won't be detected via odin, and won't power on (of course odin does not detect hard bricked snapdragon also, but snapdragon has special software for that situation).
As far as I know, there is no software to flash hard bricked exynos from computer (as of now), and the only CHANCE someone has is with sdcard.
There was an option in odin long time ago called "T Flash" and what it does is it creates a debrick sdcard from official firmware without you using someone else's device image. T Flash flashes bootloader to sdcard, and when you try to power on the phone with that sdcard, you'll be able to recover it.
So yes, possible if carefully done, very dangeorus if mistake is made (costs a new motherboard, or you taking your device to be JTAG-ed (very hard to find files for that these days)).
As for porting treble itself, android oreo is a full rebase of OS, regardless if it is project treble compatible or not. So that means that all the drivers had to be re-worked from ground up. Currently with our oreo update, if you somehow re-pitted your device to have 500mb vendor, and moved all files from /system/vendor to /vendor partition , it would work, right?
WRONG.
Those files inside /system/vendor have no idea that they are not in /system folder, and will of course try to load things from the folder in which vendor is. But since it is in a different partition it's a little problem?
That's where hex editing comes to play.
You can edit EVERY SINGLE FILE from vendor to load things from /system , and THEN move them to new partition. What now? Let's flash GSI and see if it works right?
WRONG AGAIN!
You need to create a kernel that supports treble, and loads /vendor as a partition, or else it would just be invisible to the system, and we would be at the start again.
Ok. We've got the kernel, the partition, all edited files, can we NOW boot a GSI?
SURE
If it doesn't boot then check logs and see where you messed up. If it boots, don't expect it to be "bugless" ROM like the S9. But that's what treble is right?
Yes, but there is a catch...
When a treble device software goes trought cretification, it NEEDS to be able to boot Google's android GSI with bare functionality working.
So, if it didn't need to go trough test, why would they bother fixing the drivers?
They would not.
So that's why it's hard to port treble.
And if there are any devs out there, I doubt they will start porting treble with android 8.0 on Note8.
It's better to wait for 9.0 and see what it has in stored.
Congrats to dev who figures it out and actually dedicates time to do so.
P.S. I don't think ANY samsung device got ported treble just yet (at least not publicly). There was a screenshot of dev porting treble to A5 2017 and booting GSI on it. I think that dev will also try to port treble to Note8, but I can't speak for others. It's purely his choice.
Regardless...those are difficulties about bringing treble unofficially to our Note8.
Most likely will see it after android 9.0 update. Would make more sence. Samsung is not gonna port it btw. And also today we got leaked firmware for snapdragon Note8, android 9.0.
Not much longer guys be patient, that's literally all we can do.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 35
    [ROM][PORT][7.1.2][N950F/DS] LineageOS 14.1 & Resurrection Remix for Note8 (Exynos)

    LineageOS 14.1 & Resurrection Remix Port for Note8!

    LineageOS-Cover.png


    First out of all, I'd like to thank @Fevax for making it possible as well as giving me permission to port it to Note8. I would also like to thank @farovitus for letting me use his awesome Notorious kernel! You can thank them by liking their posts and donating to them! :)



    What’s working
    Audio
    Bootanimation
    Brightness Level
    Bluetooth
    Microphone
    Wi-Fi
    LED
    All sensors except fingerprint reader
    SD Card
    S-Pen with hovering

    What’s not working
    RIL (calls, sms, microphone, data) - Doesn't work at all :(. But I'm trying to fix it too. Note: In Resurrection Remix, RIL works partially, IMEI and Baseband detection works, but other stuff is still broken
    NFC
    Camera
    Fingerprint reader
    Torch
    Wi-Fi Hotspot
    MTP - Trying to fix it.


    Guide:
    1. Download Lineage or Resurrection Remix from below.
    2. Download OpenGapps.
    3. Wipe system, data, cache, dalvik.
    4. Flash Lineage and then Gapps.
    5. Enjoy!


    Download:
    Resurrection Remix 5.8.5 Note8 (Exynos)
    LineageOS 14.1 Note8 (Exynos)
    OpenGapps - ARM64 - 7.1 - PICO
    Telegram Group for Note8 Ports.

    Credits:
    @Fevax for Lineage and permission to port it :) -- Donate to Fevax
    @farovitus for letting me use his awesome Notorious kernel! -- Donate to Farovitus
    @dylanneve1 for motivation and help with porting!
    @TimurAlaskara_TR for his YT video about the rom!


    YouTube Review:

    Source:
    S8 Lineage XDA Thread




    XDA:DevDB Information
    [PORT]LineageOS 14.1 for Note8 (Exynos), ROM for the Samsung Galaxy Note 8 (2017 Phone)

    Contributors
    ProtoDeVNan0
    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 4.x
    Based On: LineageOS

    Version Information
    Status: Alpha

    Created 2017-10-07
    Last Updated 2017-10-07
    14
    There's a new version of Lineage 14.1 which is almost fully stable and RIL and stuff works. But soon we should have a "more official" release with even more stuff that works. So soon I will post the update :).
    7
    treble for note 8? how?

    No treble for note8.
    There is a possibility that we will get treble with android 9.0 (most likely march), but in order to do that, they will have to replace /cache with /vendor , and have updates be installed in recovery mode from /data/ota .
    It's just too much work for the back-end stuff regular users are not gonna notice.
    So there is just a 0.1% chance that we will get treble.
    It would be cool if it happened but don't get your hopes up.
    It is so irritating that phones like J4 and J6 can have treble but the 2017 FLAGSHIP can't.
    Of course, they were shipped with oreo.
    But even /cache solution is a tricky one.
    /data partition is encrypted, so if they can't get the stock recovery to read it, then either no OTA updates, or no treble.
    And they can't make a new partition because our /data partition is at the end of GPT, in our case sda21, and we would have to format the /data to create /vendor.
    See where I'm going with this?
    If sda21 was system, and sda15 was data, they could just wipe, repartition, and install system files and vendor files. Only thing we need from samsung is treble kernel support and to slightly modify vendor files. Of course, treble COULD be ported over, but it would be buggy.
    We can port it because, here on XDA, we know how to backup and restore, so formatting /data doesn't do that much, but for someone who can barely make a call, it wouldn't do the job.
    And that's why samsung will most likely skip treble for 2017 flagships. Note8 was released september 2017, and they already knew about project treble, so they could have just left 500 mb of unpartitioned space, and there... I mean OnePlus did it with 5 and 5t
    It was most likely because it would be weird to have s8 that doesn't support treble, and to have a Note8 that does. At least from samsung point of view.
    As for Lineage OS, there will HARDLY be a bootable lineage 16, let alone a bugless masterpiece that is a GSI (or semi-GSI) just because more and more developers are leaving the Note8 development, even those who created modified samsung experience ROMs.
    So there is the situation with our Note8.
    Wrote this just to clear thing up once and for all, because there are people who don't fully get it and have to search the internet for hours and not find an answer.
    6
    Wow! Screenshots please!

    Sure. But I'm fixing bugs currently so I just have two.

    24c7hmq.jpg
    b4uera.jpg
    6
    Is this ROM still in development or is it abandoned?
    Like I said, nougat is done. I wait now until rr Oreo comes out. A Oreo los15.1 is already ready