The answer more than likely resides in the last few posts here. It could be the issue I and others have faced as well. Please read.
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
- Thread starter ripee
- Start date
try flashing the stock rom using odin and then reflashing twrp using odin as well then reflashing LOS using twrp, that works for me
An option is to try and flash the correct modem for the country/provider. This will not affect Recovery or anything else.
For this get the firmware zip from
Download Samsung Galaxy Note Edge SCL24 firmware
Download the latest Samsung firmware for Galaxy Note Edge with model code SCL24. Check out our free download or super fast premium options.
On the other hand, it can be something else, possibly ROM-related.
Search string: tblte SM-N915FYI've read everything and still don't know. Can I install this ROM on my good old SM-N915FY or it is only for N915F. Can someone answer YES or NO?
Thanks in advance and sorry for the stupid question.
In general, it is tblte, but with some ROMs it is known to have issues... See this:
https://forum.xda-developers.com/t/...1-tblte-trlte-trlteduos.4067663/post-84388089
If you trace the above discussion - it wasn't resolved after a significant effort.
Last edited:
Hi everyone,
I haven't updated LineageOS since august, so I am planning on doing it now, hoping that Bluetooth mic volume on external headset will be fixed and as well as GPS lock (which takes 5 minutes currently).
At the same time, I'd like to fix my SD card mount point that is currently /storage/3839-3131 to /sdcard....can you point me how to do this ?
Thanks
I haven't updated LineageOS since august, so I am planning on doing it now, hoping that Bluetooth mic volume on external headset will be fixed and as well as GPS lock (which takes 5 minutes currently).
At the same time, I'd like to fix my SD card mount point that is currently /storage/3839-3131 to /sdcard....can you point me how to do this ?
Thanks
bmwdroid
Senior Member
- Mar 8, 2014
- 1,456
- 1
- 626
Is anyone else getting a no service on a 910T from T-Mobile ? I have made no changes and my service went away. I moved my sim to my backup 910t and still no service. I thought the sim may be bad and moved it to an old S4 and it works. I'm scratching my head. Any thoughts?
Yes! My no service with Tello started on Sunday Jan. 30, 2022. I keep seeing "no SIM card - no Service" even had Tello send new SIM thinking my SIM failed. I've gone back to stock ROM until I find a fix. Using Samsung Note 4 Lineage OS Android 11.
I did some more testing for Ripee. Both my lineage 18 S4 and S5 work with my T-Mobile sim card. Apparently this issue has been corrected in the official Lineage releases. It may have something to do with T-Mobile and other carriers moving to voice over data in their networks. Ripee, I hope you can fix this for our trusty note 4s. I will daily drive with my S5. I have 2 910T Note 4s if you want me to test. Thanks for keeping our Note 4s running.
I dusted off and tested the 915T with a T-Mobile SIM and it refuses to connect to the network. A quick search led me to a list of unsupported devices on T-Mobile's network. As of January 2021, the the edge and 18 others were kicked off. The 910T is supported but the AT&T and Verizon 910 are not. It may or may not pertain to the VoLTE requirement as they update the network.
Interestingly, the 915T support pages on T-Mobile's site state that the device is VoLTE capable.
After a soft brick during a TWRP update (the download was incomplete - my fault for not verifying checksum), I flashed the original 6.0.1 ROM and I now have a notification for a new baseband. Its a security update - N915TUVU2DTI1 - dated Nov 1 2020. I paused the download as I'm not keeping the current ROM, but I'm curious as to whats changed and whether it would make a difference.
BTW, the 910T also has a similar update listed (same date).
This custom ROM is amazing . Thank you for your hard work. Please solve this problem I cannot connect to data connection on my SIM. I'm using T-Mobile note 4 N910T and rom version 21/11/2021 .
I am also experiencing this issue as well, started Wed 2-09-2022. The device was working on the network and suddenly stopped and has been unable to connect to the network since. The device seems to recognize that a sim card is in but shows no service and does not allow you to view any properties of the mobile network. Using rom from 07292021
@ripee :
It would be nice to hear from you in this thread, because the newest three custom roms in your Google drive do not have functioning mobile data. Since long time I am working with your LOS 18.1 from 07.11.2021 (N910F), where almost everything is ok for me. But I want to ask you, if you still think of updating LOS 18.1 ?
Greetings from Germany
It would be nice to hear from you in this thread, because the newest three custom roms in your Google drive do not have functioning mobile data. Since long time I am working with your LOS 18.1 from 07.11.2021 (N910F), where almost everything is ok for me. But I want to ask you, if you still think of updating LOS 18.1 ?
Greetings from Germany
i
l love this rom and your hard work just i am looking forward to see if you can fix that issue for t-mobile users. network is working fine for me calls , sms all good but not connecting to mobile data service@ripee :
It would be nice to hear from you in this thread, because the newest three custom roms in your Google drive do not have functioning mobile data. Since long time I am working with your LOS 18.1 from 07.11.2021 (N910F), where almost everything is ok for me. But I want to ask you, if you still think of updating LOS 18.1 ?
Greetings from Germany
I never made any of those Lineage roms what so ever. I'm just a Android custom rom tester. I never every built a rom before.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
21If anyone is interested here is the new build
1
Imo nobody can tell you as it wouldn't work.
Use Odin for that.
Remember that everything will be gone.1Ok 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 ? -
65
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 QUESTIONSQ: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
(Please read them BEFORE posting anything in the thread!)
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.
[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!FULL WIPE (with external microsd card)
How to flash LineageOS and Open GApps
FULL WIPE (without external microsd card with NO Home PC access)
FULL WIPE (without external microsd card with Home PC access)
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 Installation1. 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-1516Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.16Changelog
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.11Changelog
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.
