I've been running LineageOS on my Nexus 6P for a while now, with no problems. The first couple OTA updates worked fine. But starting with the Feb 27 update, I've been having problems.
The update appears to work, but my home screen is completely blank. Everything but the launcher seems to be working. I can hit the multitasking button and bring up apps, and those work ok.
I tried restoring a backup (with TWRP), and that completely killed the system (won't boot). I had to wipe, and then copy backup files back from my PC.
This happened with both the Feb 27 and the Mar 6 nightlies.
Has anyone else seen this? Am I doing something stupid?
Have you tryed , restoring just launcher data?
Sent from my Sprint Note 3 running Lineage 7.1.1 on T-Mobile. using XDA-Developers Legacy app
What is your launcher?
Enviado de meu Mi 5s Plus usando Tapatalk
I'm using LineageOS without google apps, so it's the default Lineage launcher (trebuchet).
Is there some way to reinstall just trebuchet?
I've seen a few comments here on xda-developers suggesting that the LineageOS OTA system isn't entirely reliable. I think I'll try flashing an update manually, rather than OTA, and see if that works better.
Following up to my own question, just in case anyone else runs into this...
I flashed the latest LineageOS update (manually flashed via TWRP, not OTA), and ran into exactly the same problem: my home screen is completely blank.
The trick was to remove LineageSetupWizard, as described here: https://forum.xda-developers.com/showpost.php?p=71123022&postcount=1269
I wish I knew WHY this works, but at least I have a working phone.
Related
Hi
Fresh install of 5.0.1 from google images, rooted and then a few weeks later flashed boot, boot loader and system from 5.0.2 and re rooted.
All of that went fine.
But I'm finding major stability problems. The tablet is hanging, crashing, losing the all icons on the home page including the bottom row.. Only choice I have is to force a reboot and it works for a day or two.
Its very slow and laggy.. Any ideas ?
On 4.4.4 it was fine, as soon as I upgraded the problems started. I've kept it up to date to see if that will help, but its not.
I am considering going back to 4.4.4 which is a shame as I do like the look of 5.
Help !?
Sent from my Nexus 7 using XDA Free mobile app
So its jut me then
Think I'll look for a alternative ROM
It's not the ROM. I did the same as you and it's running better than ever.
Did you try running fastboot format cache? Or I guess you can wipe it from recovery.
How did you root? I know chainfires regular non-auto zip works fine, don't know about any other methods.
Maybe an app you have is causing problems?
If none of the above apply try another full clean install from the latest image.
I flashed SuperSU via TWRP and wiped cache etc.
Think I'll backup what I needed a default it to start with.. Then see how it goes.
For what it's worth, I've used Apex Launcher on my Nexus 7 (2013) and Nova Prime on my Nexus 5 and haven't had any issues with redraws, lag, etc. Maybe it's the Google Now launcher.
On LineageOS 13, the latest official build of LineageOS for the Nexus 10, when I iinstall the Nova Google Companion for Nova Launcher, Google Play Services, Nova Launcher, and a number of other apps crash. When returning to the home screen, it freezes, then sends the app into a boot loop where after the LineageOS logo appears in it's entirety, my device tries to start LineageOS, but then crashes again and so the boot loop process continues. I have already reported this issue to the Nova Launcher Beta Google+ community and mentioned that Nova Google Companion ran fine on the stock 5.1.1 ROM. I've already tried reflashing LineageOS and GApps. Suggestions as to what I should do without flashing a different ROM?
Update: So as it turns out, ANY UI modifications (Launchers, TeslaUnread, Nova Google Companion/Action Launcher Google Plugin) will send the device into a bootloop. I suspect that the issue is with themes provider or GApps, since Google Play, Play Services, and Themes Provider are the first to crash.
I have a similar issue but I am unsure what program causes it.
The tablet was newly installed and installing my list of apps, one being Nova.
EDIT, information provided by op:
The August 5th nightly accepts Nova Launcher, but not TeslaUnread, Nova Google Companion, or Action Launcher
Hello, I have similar issue with my Nexus 10 on lineageos 13. I've reset from factory, reinstall all my apps except Nova and it works fine.
When I decide to reinstall Nova, my nexus immediatly boot in loop...
It arrive sudunly probably after an uptade of Nova...
Olivier.
Similar issue on Galaxy S3 running Cyanogenmod 13 (20161220 Snapshot).
Installing Nova Launcher causes the device to freeze and go into bootloop where it reboots after "optimising apps".
I've also tried installing Google Now launcher but " Home" option doesn't show up and there is no way to switch from Trebuchet to it.
Similar issue on S2 Plus CM13 after an update
Tested 2 weeks without Nova and nothing happened
Decided to give a shot again then bootloop happened again, luckily I had backup this time
I'm facing the same problem right now with my Redmi 4A. How did you solve it? Doing a factory reset?
I am currently facing a similar issue, but the culprit here for me is the facebook app, as soon as I install it from play store, it sends my samsung gt-i9082 (running cm13) into an instant bootloop, I tried deleting the facebook app's data from the twrp recovery's file manager.
but even then it kept on rebooting.
I had tested this even after a complete format of my device, including internal storage and external storage. even removing external storage, still as soon as the app was installed it went bootloop.
It's strange for me, cause it's the same rom and the same device, that was running the same app version before i format it to clean everything.
I would have doubt a data clash between my older files, but that was ruled out after a complete format. I have no clue why this is happening.
Edit: The only difference between my previous and the new installation is that I used deltagapps before and I am using opengapps now.
I will try with deltagapps again to see if it is sorted.
Edit 2: Well it did stopped the bootloop with the facebook app, but then again it started giving me the same issue with all the other random app I try to install(All those apps that previously were working on the same rom, same device).
Now the only suspect remains is the emmc of the device, maybe that is failing or got bad sector. strange that I haven't seen any issue on the device forum about this. Bad Luck, It reaches it's end.
The fix for this issue is available here (13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM 12
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
So of course since i am rooted i could not just simply download the update. I was part of the developers preview though and was running OPP3.
So i downloaded the Android O Factory image from google and installed it manually expecting to have everything wiped. After install though using fastboot flash of all the images, all my apps were still present.
Is this normal? Did it full y install correctly? I was expecting to have to reinstall all my apps and re-setup device. Or because i was on developer preview and part of the beta testing within google they spared me the act of wiping my device?
Same experience with N
I had the same experience with N preview. I went from rooted N preview back to stock N. I installed the N factoruy image and didn't have to reinstall everything. AFIK the only reason that the device would be wiped is if you rolled back to the previous version (ie unenrolled from beta). I haven't bothered to root since then and am on 8.0 build OPR6.17623.010 which came as an OTA today 8/22. The only thing that I have had an issue with is the Pixel Launcher never upgraded to the latest version. The installed launcher ver is 7.1.1-3705938. I can't find anything related to the Pixel C launcher version anywhere and Google support was useless... a 30 minute live chat where I asked "what is the current version of Pixel Launcher in 8.0" was ultimately answered with "you will need to reset your device". Yes, that's always the best course of action. What launcher version do you have?
johnbravado said:
So of course since i am rooted i could not just simply download the update. I was part of the developers preview though and was running OPP3.
So i downloaded the Android O Factory image from google and installed it manually expecting to have everything wiped. After install though using fastboot flash of all the images, all my apps were still present.
Is this normal? Did it full y install correctly? I was expecting to have to reinstall all my apps and re-setup device. Or because i was on developer preview and part of the beta testing within google they spared me the act of wiping my device?
Click to expand...
Click to collapse
i got the image OPR6.170623.010 . flashed via fastboot. pixel launcher 7.1.1-3705938. so the OTA did give the same launcher the factory .zip has
Hi everyone Would you be so kind to provide me OTA dp4 for Pixel c if you still have it since all links for DP are down. Kind regards.
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.
First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.