GCam Port | Google Camera APK v9.2 (April 2024) › Forums › Samsung Device Forums › Galaxy NOTE 4 T-Mobile – trltetmo › Galaxy NOTE 4 T-Mobile LineageOS 14.1, Android Nougat 7.1 ROM
- This topic has 42 replies, 12 voices, and was last updated 7 years ago by Linux User.
- AuthorPosts
- February 20, 2017 at 4:30 PM #13352Linux UserParticipant
Like Yavor Said, maybe you should try to flash your radio. I remember having some trouble with radio when I flash some CM Rom. I dont remember if it’s was from 12 or 13 but the radio was not OK and i have to flash radio after the ROM prior to first reboot.
When I flash this ROM, I was on stock 6.0.1 with the latest radio on it.
If you don’t find your radio, it’s possible that it would be easier to re install stock ROM and after try to flash this than trying to flash from CM 12
February 20, 2017 at 9:39 PM #13359Linux UserParticipantAny GApps for Android v7.1 should work. When you go to the download page just pick 7.1. However, the phantom battery drain is really a problem if this is your daily driver phone. Not sure if it’s just me. I tried the Xposed Mobile Radio Data Fix but as others have noted on XDA, it only fixes the battery stats, not the battery life.
February 24, 2017 at 7:06 AM #13646Linux UserParticipantHi Everyone,
Sorry I didn’t weigh in earlier, but I don’t get as much time to do this stuff as I would like sometimes.
In order for this ROM to work (Or any 6.0 or 7.0 ROM for that matter) you have to be on the latest bootloader: 910W8VLU1COI4There are two ways to get it:
1. You do a google search for a .zip file that can be flashed with TWRP. I recommend you restore the backup of your previous ROM, install this, then flash LineageOS 14.1.2. Or, flash a stock android 6.0.1 ROM for this phone. That will give you the latest bootloader and modem firmware. Then root, install TWRP, and flash Lineage)S 14.1 per the instructions on this page. Note: If you already have the Marshmallow bootloader and Lineage still isn’t seeing your sim card, its possible that you inadvertently wiped your EFS while you were installing it. This method will also restore your EFS.
Hope this helps!
BFebruary 24, 2017 at 11:15 AM #13673Linux UserParticipantHi again….thank you Bruce, better late than never! What you suggest is exactly what I have been doing since my last post – I went online and found/flashed the Samsung Bell Marshmallow 6.0.1 firmware and then TWRP and SuperSu to re-root my phone. Everything is running great and I am thinking I will try Samsung Touchwhiz Marshmallow 6.0.1 for a bit before flashing the Lineage Nougat ROM. I will post back here if/when I do move up to Nougat, thanks again everyone for your contributions to this post.
February 24, 2017 at 9:50 PM #13723Linux UserParticipantBoth the Nougat GApps link point to the same location. It is just provided so that it will be handy for the user to click on that link and go to the GApps link without scrolling or searching here and there.
February 24, 2017 at 10:01 PM #13724Linux UserParticipantYou can search the latest FW in the following location: http://samsung-updates.com/device/?id=SM-N910W8
or from here: https://www.sammobile.com/firmwares/database/SM-N910W8/
February 27, 2017 at 12:52 AM #13950Linux UserParticipantSnapchat isn’t working, my phone is not rooted. The error says; “There was a problem connecting to the server. Please try again”
February 27, 2017 at 5:34 AM #13955Linux UserParticipantIts a common issue, some people talk it could be possible to hide your rooting with app like magisk etc. But for me it doesnt work. Other talk that if you could install snapchap on non rooted device and logging it would be possible after doing a titanium backup of your app you could re install on the rooted device, but i didnt try it for now
March 2, 2017 at 9:59 AM #14168Linux UserParticipantThe call noise reduction options seem to be missing. Anyway to force it? There’s also the issue with low sound, but easily fixed by editing mixer_paths.xml.
March 2, 2017 at 2:29 PM #14174Linux UserParticipantHi Long Pham, can you just explain what was the actual low sound issue and what did you edit on the mixer_paths.xml to fix this issue?
- AuthorPosts
- You must be logged in to reply to this topic.