Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.
I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
- Camera not working
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps (Opengapps pico)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1D0Od55prO_Q_e8RY6QkZ-DjO36Qb188X (Pick Grouper)
Credits to:
Unlegacy Team
Initial Release:
May Security Patch
Can't download the ROM 404 error
JT1510365 said:
Can't download the ROM 404 error
Click to expand...
Click to collapse
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!
KiD3991 said:
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!
Click to expand...
Click to collapse
Which kernel you use?
TureX said:
Which kernel you use?
Click to expand...
Click to collapse
It's stock thus far, but I am testing out other things.
So I assume F2FS can't work, right?
New update:
Direct Link: https://drive.google.com/open?id=1ObhbiIgSwxIS3fDfb2AREEx_6syQSpi_
Consider this pre-June patch build. And no F2FS doesnt work @Stylez Ray. I am too noob to implement it. (For now)
Guys, I apologize but this month's upload will be slightly delayed due to my work and studies having major setbacks. Again, I apologize.
New update:
Direct Link: https://drive.google.com/open?id=1LkbL1TEupSYUY2zA_L_NklEP-j9xWDUP
Changes are minimal in this build other than using a better build machine lol
Thank's good job !!!
All works fine magisk v19.3, dax_axon7_v1.6.1.zip
I return on Andisa rom 7.1.2 freeze and lags horrible
This is really awesome, no more random system freezes like in the first official UA builds. Thanks a lot, it really makes this ancient device useful again ?
@KiD3991 hello, maybe you would like to join Unlegacy team as Tegra 3 developer?
Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory
New build up, sorry I was really unavailable.
I tried fixing a couple of things, see if it helps, do tell me though, mention me and I will show up.
Direct link: https://drive.google.com/open?id=1g4eu0ulizZ8ZO44hRjMUnIyEYIyWQL9t
Changelog:
Minor bug fixes
July Security Patch
curioct said:
Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory
Click to expand...
Click to collapse
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.
KiD3991 said:
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.
Click to expand...
Click to collapse
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.
curioct said:
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.
Click to expand...
Click to collapse
OMG SAME! I was trying with the Kali too on my other device. It was kinda confusing no doubt
This rom is working great, thanks. Please can anyone help me with how to install browser on this rom, as the USB is not working.
did u tried to activate the debug mode , in dev settings? if that doesn't work .. you have to switch the drivers by yourself, in windows ( devices manager ) from ADB Bootloader to Storage Device .. for your Nexus 7
[Land][Ubuntu Touch][Experimental]
Changes :
Initial build for land
Fix call
Fix dualsim
Fix wlan and BT
Kernel:Added anbox support, alarm,apparmor for it
By tea
Special thanks:
rupashkek
UbportComunity
Support Groups @utland on telegram
Notes: Mount data in recovery.And make sure ur data partition not encrypted
Download links:
https://drive.google.com/file/d/1-Afwg-Qxfq7362VPN4z2Uy_K5vptepiU/view?usp=drivesdk
Source Device tree and kernel:
https://github.com/Ubports-Land
Yoooho
Thank you so much ?
Thank you so much. Will please provide small detail how to flash it on phone.
I dont understand, " Mount data in recovery"
masoomyf said:
Thank you so much. Will please provide small detail how to flash it on phone.
I dont understand, " Mount data in recovery"
Click to expand...
Click to collapse
Mount data before flash it
Very interesting... based on UBport ?
It doesn't boot.I follow every step as said.
Noru29 said:
Very interesting... based on UBport ?
Click to expand...
Click to collapse
If the system does not boot, return to TWRP and delete dalvik and cache and restart again.
Subho166 said:
It doesn't boot.I follow every step as said.
Click to expand...
Click to collapse
It's wrong sentence.. It will boot. But you are not able to boot
Then how to boot it?
tried. a new experience. Too bad there is no more variety of mobile environments, tired of aosp.
Subho166 said:
Then how to boot it?
Click to expand...
Click to collapse
Like installing every rom.. How could I know what is your issue.. You just said it doesn't boot
I followed the installation instructions. Wiped all partitions including data. Format data to remove encryption.
Checked in TWRP mount, data partition was already mounted.
So, I proceeded to flash the provided zip. It installed successfully.
Clear and dalvik/cache and reboot system.
It is now stuck on the MI logo since the last 5 minutes, not sure if it is booting or not. Any help?
Does anyone know how to add more WiFi and Bluetooth connections, I can only use the connection in the initial configuration
atomickaushal said:
I followed the installation instructions. Wiped all partitions including data. Format data to remove encryption.
Checked in TWRP mount, data partition was already mounted.
So, I proceeded to flash the provided zip. It installed successfully.
Clear and dalvik/cache and reboot system.
It is now stuck on the MI logo since the last 5 minutes, not sure if it is booting or not. Any help?
Click to expand...
Click to collapse
Try restart for 2 or more time
Working fine except VoLTE
Sorry, I didn't reply earlier.
It worked within an hour of my last post when I restarted it twice. Same thing happened on the following restart too, wouldn't boot up, would only start after every 2 unsuccessful attempts.
Anyways, the ROM is great and works perfectly fine. Data with Jio was working.
SMS and calling wouldn't work on Jio VoLTE.
WiFi, all apps, Headphone Jack, torch, Bluetooth, Camera, all worked fine.
Couldn't find a way to install android apps. Read many articles and official of anbox but just couldn't make it work. For one, since I don't have a data cable, I couldn't test adb with Ubuntu touch, since adb over network was missing.
Another thing that didn't work was adding a Gsuite/google account. The google login screen opens, but the keyboard wouldn't come out even when focusing on the text field in the web view.
I ended up typing out my credentials in the notes app and then copy pasting them in the screen.
Google refused to go ahead claiming that this was not a recognized browser!
If the VoLTE is fixed, I would use this as my daily driver! (Since I use my phone purely for work - calling, text, notes)
So, now I am back to lineageos for microg.
Thanks for wonderful work OP and devs and looking forward to an update soon. Request you to pleade get VoLTE working so that I can start contributing too.
Some screenshots
Screenshots for other users
I saw you use LOS4microg, did you try microg on this Rom too ?
Noru29 said:
I saw you use LOS4microg, did you try microg on this Rom too ?
Click to expand...
Click to collapse
MicroG cannot work on a non-android ROM. Ubuntu touch is based on the ubuntu gnu/linux software distribution and it comes with it's own SDK and notification engine.
May I ask for what purpose do you need microg?
I used microg cause I don't want google on my phone but I need my GPS and apps working.
Update pushed
Changes :
-bring Ubuntu library
-fix anbox issue on kernel
-fix anbox installer issue
-and something forgot
Download link:
https://drive.google.com/uc?id=1moH0JEAQnQd7YypTqg9sz_hfJaVDED-b&export=download
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem
re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?
rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]
installation error
https://download.lineageos.org/hltetmo
Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?
Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.
loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.
rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)
rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc