[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]

Search This thread

louisJJ

Senior Member
Oct 3, 2010
207
4
@louisJJ that's really peculiar.
Can not recommend a lower TWRP version directly as I've never had that problem.
Was just an idea.

I've read about broken RAMs on trlte.
If it was mine I'ld start from scratch by flashing latest stock to make sure still working on stock.
ok thank you, can you tell me the quick steps to flash stock ? (never did this)
I guess I should download the stock rom and flash it via Heimdall.
 
Last edited:

louisJJ

Senior Member
Oct 3, 2010
207
4
Ok I used a tool as you mentionned to download the stock rom (I used samloader, very good for linux).

Here's the command

$ sudo ./heimdall flash \
--APNHLOS stock_rom/NON-HLOS.bin \
--MODEM stock_rom/modem.bin \
--SBL1 stock_rom/sbl1.mbn \
--DBI stock_rom/sdi.mbn \
--ABOOT stock_rom/aboot.mbn \
--RPM stock_rom/rpm.mbn \
--TZ stock_rom/tz.mbn \
--BOOT stock_rom/boot.img \
--HIDDEN stock_rom/hidden.img.ext4 \
--RECOVERY stock_rom/recovery.img \
--SYSTEM stock_rom/system.img.ext4 \
--CACHE stock_rom/cache.img.ext4 \
--USERDATA stock_rom/userdata.img.ext4

I didn' flash TRLTE_EUR_OPEN.pit, should I have ?

I didn't use -repartition option.

The phone boots, and the system seems to work, I gonna test it a bit.

So like this my phone is not rooted anymore right ?
If this stock rom works, what does it mean ? I can try and reflash LOS ?
 
Last edited:
  • Like
Reactions: bmwdroid
....except for
TRLTE_EUR_OPEN.pit
should I flash it too ?
Thanks
1st I would try without repartitioning.
If flashing doesn't work you can still try it.
I prefer Linux as well, but for flashing I use Odin on Windows as there are not that many files to cope with. ;)

Thx for giving the hint to samloader.
 
Last edited:

louisJJ

Senior Member
Oct 3, 2010
207
4
Yes samloader is very good.

Haha I understand ...so many files.

As you put it, I understand TRLTE_EUR_OPEN.pit is for repartitioning ?

So the stock rom seems to work but is really slow...and reboots from time to time. Is it a symptom of something ? Should I reflash with repartition option to be sure ?

I just tried this command :
$ sudo ./heimdall flash --repartition --resume \
--pit stock_rom/TRLTE_EUR_OPEN.pit \
--APNHLOS stock_rom/NON-HLOS.bin \
--MODEM stock_rom/modem.bin \
--SBL1 stock_rom/sbl1.mbn \
--DBI stock_rom/sdi.mbn \
--ABOOT stock_rom/aboot.mbn \
--RPM stock_rom/rpm.mbn \
--TZ stock_rom/tz.mbn \
--BOOT stock_rom/boot.img \
--HIDDEN stock_rom/hidden.img.ext4 \
--RECOVERY stock_rom/recovery.img \
--SYSTEM stock_rom/system.img.ext4 \
--CACHE stock_rom/cache.img.ext4 \
--USERDATA stock_rom/userdata.img.ext4

but I get an error at the beginning and it doesn't flash :

Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
Rebooting device...
Releasing device interface...


I retried without --repartition and I get this :
uploading SYSTEM
18%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

Can you help me here ? :)
 
Last edited:
Yes samloader is very good.

Haha I understand ...so many files.

As you put it, I understand TRLTE_EUR_OPEN.pit is for repartitioning ?

So the stock rom seems to work but is really slow...and reboots from time to time. Is it a symptom of something ? Should I reflash with repartition option to be sure ?
pit stands for "partition information table".

I've encountered flashing stock multiple times helped once on a different device with letting it in "Download mode" all the time.
If it keeps crashing there's obviously something wrong.
About speed I can't tell.
Mine was too long ago on stock so I can't compare.
 
  • Like
Reactions: louisJJ

louisJJ

Senior Member
Oct 3, 2010
207
4
pit stands for "partition information table".

I've encountered flashing stock multiple times helped once on a different device with letting it in "Download mode" all the time.
If it keeps crashing there's obviously something wrong.
About speed I can't tell.
Mine was too long ago on stock so I can't compare.
ok thanks for the clarification. I flashed multiple times now, and still rebooting erratically.

How come I don't succeed flashing with -repartition option
Is there a way to check if it's the phone's RAM failing ?
 
...
Is there a way to check if it's the phone's RAM failing ?
Once saw somewhere a pic where in download mode one additional row (in pic attached) showed emmc failure.
But Idk if not showing is a guarantee for a good RAM.
A professional may have tools for testing.
Seen this?
 

Attachments

  • dwnld.png
    dwnld.png
    59.9 KB · Views: 22

louisJJ

Senior Member
Oct 3, 2010
207
4
Once saw somewhere a pic where in download mode one additional row (in pic attached) showed emmc failure.
But Idk if not showing is a guarantee for a good RAM.
A professional may have tools for testing.
Seen this?
I don't see any eMMC failure in the lines in donwload mode. Thanks for the hint.

Do you have any idea why I can't seem to repartition while flashing ?
Maybe I should try and find a windows pc to flash the whole .tar with odin for once.
 

louisJJ

Senior Member
Oct 3, 2010
207
4
Anyone could provide a link to 18.1-20211107 please ? It seems this is the last build with working mobile data for N910F. Thanks a lot
 

louisJJ

Senior Member
Oct 3, 2010
207
4
Hi
i have the very same issue with mobile data on my friends N910F which i got today to flash with it LOS, stock firmware was on latest DBT-N910FXXU1DRI2.

I tried all the builds which are available for download:

18.1-20211121 no mobile data
18.1-20211117 no mobile data
18.1-20211116 no mobile data
17.1-20210414 hangs at LOS logo, never completes initial boot
16.0-20211117 mobile data OK

Gapps (obviously) don't make a difference, but tried with/without as well, no changes.

As per previous post, 18.1-20211107 might be a working build, I'd happily try that if someone could provide it for download.

@ripee, thank you very much for the great work! Let's keep fighting planned obsolescence!
This post says it all for us users of N910F.
I have the exact same feedback on those builds :
18.1-20211121 no mobile data
18.1-20211117 no mobile data
18.1-20211116 no mobile data
17.1-20210414 hangs at LOS logo, never completes initial boot

I just saw that 18.1-20211107 is back again in the google drive for TRLTEs.
Thanks @ripee.
Although, I just tried it with three different versions of twrp.
The first attempt : infinite boot.
The 2nd and 3rd.....unknown command [retry_update] while flashing

Can someone help find a way to repartition ? can't seem to work with odin nor heimdall.
 

louisJJ

Senior Member
Oct 3, 2010
207
4
This post says it all for us users of N910F.
I have the exact same feedback on those builds :
18.1-20211121 no mobile data
18.1-20211117 no mobile data
18.1-20211116 no mobile data
17.1-20210414 hangs at LOS logo, never completes initial boot

I just saw that 18.1-20211107 is back again in the google drive for TRLTEs.
Thanks @ripee.
Although, I just tried it with three different versions of twrp.
The first attempt : infinite boot.
The 2nd and 3rd.....unknown command [retry_update] while flashing

Can someone help find a way to repartition ? can't seem to work with odin nor heimdall.
Hi @ripee,
I just tried with a N190F that has never been rooted or flashed, and I get this :
18.1-20211121 no mobile data
18.1-20211117 no mobile data
18.1-20211116 no mobile data
The only one that gets mobile data is 18.1-20211107...
What would be very useful is that you give us a combination of version of
twrp + lineageOS 18.1 + openGapps + magisk that works.

I know you are busy, but right now, it's almost impossible to have a working LOS 18 on a N910F.

Thanks !
 

Top Liked Posts

  • There are no posts matching your filters.
  • 66
    image17.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    Code:
    * [B][U]Your warranty is now void.[/U][/B]
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your 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 us for messing up your device, we will laugh at you.


    FREQUENTLY ASKED QUESTIONS

    (Please read them BEFORE posting anything in the thread!)
    Q: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
    A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.5. Simply flash the linked below version 3.5 or higher, reboot back into recovery, and flash the rom zip again.

    Q:Will any of the variants receive official builds from LineageOS?
    A: In short, no. While official support would certainly add credibility to our work, there is absolutely no reason to believe that unofficial builds are any less secure or stable than official ones. Naturally all the bugs listed below would first need to be fixed, but still the process of submitting and maintaining official support is very time-consuming and not something I, for one, am unable to make such a commitment.
    Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.

    Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
    A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.

    If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
    1) You missed one of the Wipe steps in the flashing procedure.
    2) You are running an old bootloader or modem. Flash the most recent one listed for your variant under the links in the TWRP thread. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
    3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 6 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
    4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!

    Q. Flashing a build failed with the message "eMMC Write Fail".
    A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board. :p


    [Official] Note 4 Verizon Bootloader Unlock
    - ryanbg

    Open GApps

    ROMs
    - SM-N910F/G/P/R4/T/T3/V/W8: trlte
    - SM-N9100ZC/ZH/6W/9W: trlteduos
    - SM-N915F/G/P/R4/T/W8: tblte

    Magisk

    SPenCommand

    - It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.

    WipeTelephonyProviderData
    - hsbadr



    If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 18.1 variant, which corresponds to the model of your phone!


    How to flash LineageOS and Open GApps
    FULL WIPE (with external microsd card)
    1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with NO Home PC access)
    1. Move any files you want to keep to a safe folder - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    FULL WIPE (without external microsd card with Home PC access)
    1. Move any files you want to keep to your Home PC - ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Move your LineageOS Rom and GApps Package to the internal storage,
    4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
    5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    6. Swipe to Wipe at Bottom of Screen,
    7. Back to Main start screen,
    8. Wipe > Format Data,
    9. Type 'Yes' and press blue checkmark at the bottom-right corner,
    10. Go Back to Main Start Screen to Install Rom and GApps,
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!
    13. Once first boot is completed you can safely move your files back onto your Internal Storage.



    Important information about stock S Pen functionality!
    The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.

    Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.


    Problems known to happen after a Dirty Installation
    1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.

    * Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.

    * Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.


    Bugs
    - When the phone is powered off from Lineage and the battery is not removed, the battery charge will fall at an approximate rate of 2% per hour of time that the phone is powered off without the battery having been removed since it was powered off. This does not occcur when powering off from TWRP, having first powered up to TWRP or rebooted to TWRP from Lineage. It also does not occur if the battery is removed from the phone before being put back in, either after powering off from Lineage or being pulled out while Lineage is running. This bug has affected the apq8084 chipset since Oreo (as described by the S5 Plus community, which uses the same chipset). However, the S5 Plus had received official lineage-15.1 and 16.0 support despite being affected by this bug. Furthermore, we have deduced that it must be caused by one or more of the 652 commits that separate the Nougat and Oreo kernel branches. We will never have the time to go through each and every one of these commits to fix this bug outright, but we are always open to suggestions.
    - If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
    - The 2nd SIM slot does not work in any trlteduos variant.
    - VoLTE is not supported, and will not be supported for the foreseeable future.
    - You tell us!

    Changelog
    All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.

    Credits
    - Our resident Developer Emeritus fattire, Elektroschmock for his work on shamu (Nexus 6), and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the tblte, trlte, and trlteduos.

    Sources
    - LineageOS
    - apq8084

    XDA:DevDB Information
    LineageOS 18.1, ROM for the Samsung Galaxy Note 4

    Contributors
    ripee, Inkypen, logosA, ghostwheel, ananjaser1211, khalvat, tripLr
    ROM OS Version: Android 11
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: Stock Marshmallow for your variant.

    Version Information
    Status:
    Stable
    Current Stable Version: 11
    Stable Release Date: 2021-04-14

    Created 2020-03-16
    Last Updated 2021-04-15
    17
    Changelog

    Builds 0421 for all variants
    * Fingerprint sensor is fixed.
    * Increased microphone levels to improve video recording, courtesy of Telegram user AomineDaiki87.
    * Synced with LineageOS sources.
    16
    Join us on Telegram!

    LineageOS is part of the triplr_dev_users
    group, courtesy of tripLr.
    16
    Changelog

    Builds 0322 for all variants
    * trlte-common: Enable comp backpressure. This is supposed to improve the overall smoothness of the rom.
    * Synced with LineageOS sources.
    11
    Changelog

    Builds 0329 for all variants
    * Video playback in Chrome, YouTube, etc., is fixed by removing the widevine instance from the manifest.
    * Synced with LineageOS sources.