I didn't have to reinstall efs modem or EMIE I had to use magik to patch boot image and my mobile network worked after that. I don't know if this will help you.
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
- Thread starter ripee
- Start date
Thank you very much.
It now starts.
I haven't been able to pinpoint what was wrong with it, but after a lot of work, it started
Thank you very much for your advice.
I managed to get it to boot on 910V.
Are you able to use a SIM here?
I live in Japan, but it doesn't seem to recognize the SIM of a Japanese cell phone.
I see posts here that say the SIM doesn't work, but is there a version of the day when the SIM works?
I managed to get it to boot on 910V.
Are you able to use a SIM here?
I live in Japan, but it doesn't seem to recognize the SIM of a Japanese cell phone.
I see posts here that say the SIM doesn't work, but is there a version of the day when the SIM works?
I had to use Magisk to patch boot image and my mobile network worked after that. I don't know if this will help you.
私の910Vは、内部ストレージ用に同じROMを認識できます。
note3にその症状がありましたが、再度インストールすると問題が解決しました。
手順の違いなのか、データが残っているのかわかりません。手順のわずかな違いなのか、内部にデータが残っているのかわかりません...
Translation by GT: My 910V can recognize the same ROM for internal storage.
I had that symptomat on note3, but installing it again fixed the problem.
I don't know if the procedure is different or if the data remains. I don't know if it's a slight difference in the procedure or if there's data left inside ...
Last edited by a moderator:
どうもありがとうございます。
パッチを適用しますか？
<m（__）m>で検索してみます。
Translation by GT:
thank you very much.
Do you want to apply the patch?
Try searching with <m (__) m>.
Last edited by a moderator:
Hello all,
I am new here and hope not to step on anyone's toes. I am also having the issue with missing IMEI after flashing lineage-18.1-20210725-UNOFFICIAL-trlte (on SM-N910W8 here). I am sorry to say I am not capable of providing logs (yet) but my issue sounds similar to @Notoki 's, except mine simply never works (IMEI = null).
I re-flashed stock firmware and the phone works fine. Tried again with 18.1-20210725 and again it didn't work. Went back to stock and it works fine again. So it seems the IMEI and/or EFS is not getting corrupted.
I don't really care if I have the latest lineage, so does anyone know which is the most recent version that doesn't have this issue?
I am new here and hope not to step on anyone's toes. I am also having the issue with missing IMEI after flashing lineage-18.1-20210725-UNOFFICIAL-trlte (on SM-N910W8 here). I am sorry to say I am not capable of providing logs (yet) but my issue sounds similar to @Notoki 's, except mine simply never works (IMEI = null).
I re-flashed stock firmware and the phone works fine. Tried again with 18.1-20210725 and again it didn't work. Went back to stock and it works fine again. So it seems the IMEI and/or EFS is not getting corrupted.
I don't really care if I have the latest lineage, so does anyone know which is the most recent version that doesn't have this issue?
Last edited:
I just tried lineage-16.0-20210413-UNOFFICIAL-trlte and no luck. Exact same issue.
Update: Tried again after a fresh full wipe. No luck. Then re-flashed stock rom and now it is stuck at flashing SAMSUNG.
This phone will be tossed in the trash, I guess. This experience has been very different than my Lineage install on S5 Neo, which works perfectly.
No tears shed...
Update: Tried again after a fresh full wipe. No luck. Then re-flashed stock rom and now it is stuck at flashing SAMSUNG.
This phone will be tossed in the trash, I guess. This experience has been very different than my Lineage install on S5 Neo, which works perfectly.
No tears shed...
Last edited:
Try the the 06/30 build I have had good success with this build
https://drive.google.com/file/d/11AqJJET7iZNRTL76tL_Bb92k2KLHL4oD/view?usp=sharing this is from ripees drive
you might have to flash boot image with magisk make sure you are running latest version of twrp 3.52
Thanks for the link. I'll give it a shot. I don't know how to "flash boot image with magisk" though...
I do have the latest twrp (flashed via heimdall on Linux) and I am using adb command-line in Linux to sideload the ROMs.
Update: It'll be a bit before I can attempt it
"Sorry, you can't view or download this file at this time.
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator."
Thanks. Ugh. Actively de-googling I am. That's one of the main points of Lineage for me (no Gapps here - BTW this is so appropriately named).
Perhaps I will use my old account for the purpose of DLing that ROM.
Wow! The 6/30 build works! Thanks very much @timandolly !!
Now I will try to figure out how to do an app + data backup from my S5 Neo and restore it to the Note 4. I had given up on the Note 4 and spent several hours getting all my apps downloaded and set up on the Neo. I'd really rather not have to do it all over again on the Note.
During the initial boot/setup, Lineage asks if you want to restore apps/data from a backup. My question is, what app am I supposed to use to create the backup on the "old" phone (S5 Neo)?
Or, is there a way to do it with heimdall and/or twrp via Linux/USB?
UPDATE: Never mind, I found "Migrate".
Now I will try to figure out how to do an app + data backup from my S5 Neo and restore it to the Note 4. I had given up on the Note 4 and spent several hours getting all my apps downloaded and set up on the Neo. I'd really rather not have to do it all over again on the Note.
During the initial boot/setup, Lineage asks if you want to restore apps/data from a backup. My question is, what app am I supposed to use to create the backup on the "old" phone (S5 Neo)?
Or, is there a way to do it with heimdall and/or twrp via Linux/USB?
UPDATE: Never mind, I found "Migrate".
Last edited:
I seem to have lost root access after successfully installing the rom. I tried to reinstall supersu through twrp but still I can't seem to get my root back. Hope someone has any suggestions. otherwise rom is working great.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
download magisk apk file
rename it to magisk zip, using a file manager
keep both files in your sd card
apk and zip
boot in twrp
flash rom, flash gapps(if you are using Gapps)
flash magisk zip
boot up
after setting up rom, find magisk apk and install it
it will ask for additional setup and reboot
there you go, you are rooted
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
76
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-1519Join 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.
