I recently installed LineageOS version 14.1-20170403-NIGHTLY-bacon on my oneplus one about two weeks ago. My phone gave me a notification saying there is a new nightly update.
If I download the new update will it automatically install?
I'm new to rooting and installing roms so it took me almost 6 hours to figure out the terminology and I don't want to do that again
Thanks guys take care!
Lineage OS supports OTA. Just download the ROM from the update app and then it will ask you if you want to install, it will run an Openrecovery script and all by itself update. Make sure you have twrp installed.
Settings>About>Lineage Updates
Related
Hey there, I am using OnePlus2 since october 2015 and it came with OxygenOS 2.0.1 installed. However, I have tried to check for updates several times, but, it always says that I have the latest version of firmware installed which is not. I have checked my root status and it is not rooted. So, why am I not getting the lates updates from time to time?
Is there any way to install the latest firmware manually? Definitely there is but as I have never rooted any mobile yet so I will be thankful if you can instruct me how to install it step by step. It is highly appreciated if you can provide the screenshots too.
If I wait a week to update Lineage OS 16.0 do I need to flash every update for that week starting from the oldest or can I only download the newest one and have it work?
Unless the developer states previous versions require installation first, just go for the latest. :good:
Good luck.
Hi there,
Sorry for the noob(ish) question but I've lost base some time ago and now I thought I might look into getting the phone updated if possible.
This is European 034 dual-SIM version, Oreo 1.30.401.2, unlocked bootloader, running Magisk now.
I did some research through the forums (spent whole evening on this) and only got confused. I'm not looking for spoonfeeding, just clear answer what should be my path if I want to get the Pie - is it worth on U12+ btw?
I'm familiar more or less with cli and adb, twrp are no news to me as well.
Many thanks
doc
first step, flash RUU Oreo on your device.This provedure erases everything, all files, twrp too.
Then search update from settings and install updates up to Pie.
So install,if you want,twrp magisk ecc...
When somebody will release Ruu Pie, we could skip previous procedure
I will update you about my last night. I have tried to update the phone but I've flashed the Exodus rom instead of Imagine.
Took me most of the night and morning to get it back up and running - the fix was to use force update script I found on 4pda. Im running rooted Pie now.
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.