Related
It seems like ever since the market updated to google play i can't download any new apps on my phone (the force close and disappear as soon as i open them). Also, when i try to update existing apps they also force close and disappear but they end up coming back if i restart my phone. Also applications that i've had on my phone that i don't use any more I can't get rid of. I delete them and they come right back as well.
I've tried to restore my phone in tons of diffrent ways, regular factory reset, ruu, thought hboot, and htc sync. Factory reset and hboot just give me a red exclamation that i can't get around, the ruu someone told me to use didn't work i believe because the version of android i'm running and htc sync always tells me my phone isn't connected when clearly it is because i can open it up and explore it on my computer.
I'm at a loss, anyone have any ideas?
Time for a new phone?
Maybe consider rooting? I actually haven't seen a dinc with GB 2.3.4 that upgraded to google play, for some reason I've seen it stay with the market. My phone hasn't been in stock for a long time so I couldn't really say if that were true now but I know that google play was first released back in March and mid-april when I first rooted my Dinc, it was still on the android market. That being said, the dinc is far from trash if you are willing to root and flash a custom ROM to it.
I've seen this problem on ROMs when the version of gapps wasn't compatible with the ROM anymore because either the ROM was updated or gapps was updated and compatibility was lost. Usually in that situation I would recommend that person to do a fresh flash of their ROM with the newest google apps but in your case I would suggest flashing a custom ROM for the first time. if that is not an option you want to explore at this time, I believe that if you place this PB31IMG.zip on the root of your SD card (which must be formatted to FAT32) and then get into hboot it will reflash gb for you which might do the trick.
http://www.mediafire.com/?1ovb6959r9qyg6w
my DINC upgraded to google play when it was on stock. But really, stock sucks and has bugs. Upgrade to a real firmware listed here
Welcome To NegaLite Huawei-Rom NX 2!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES! Use At Your Own Risk!
This Also Voids Your Warranty!
ROM Chefs: Use Whatever You Like! No Thanks/Credit Needed! Happy Cooking!
Features:
Based On N7G75S - Wear 2.0
Stockish Kernel
Rooted - SuperSU
Busybox 1.27.0
Adb Debugging Pre-Enabled
Many System Apps Moved To /data For Easy Uninstall
Includes Root Essentials
Includes Custom Advanced Settings
Updated Gapps, Hangouts, Fit, Maps, Music
------------------------------------------------------------------------------------------------------------------------------
Downloads:
If You've Never Flashed This Before, You Need To Format Data Partition Via TWRP Advanced Wipe
If You Don't Have TWRP, Get It Here: TWRP 3.0.3 Themed
Just Do This:
1. Push Zip To /sdcard/ Via ADB (adb push rom-location/rom-name.zip /sdcard/)
2. Flash zip In Recovery(TWRP) Via Install
3. Done (Enjoy!)
Huawei-Rom-NX-2-v1.2.zip - 6/7/17
LG G Watch R Faces - LG_Watch-R-Faces_v1.zip
Like the Rom? Try My Custom Kernel!: Negalite HW+
Special Thanks To SuperThomasLab For Allowing Us To Include Root Essentials
You Can Always Find It Here : https://play.google.com/store/apps/d...rootessentials
Special Thanks To suleymanovemil8 For Allowing Advanced Settings To Be Open Source
You Can Always Find It Here: https://play.google.com/store/apps/d...vancedsettings
------------------------------------------------------------------------------------------------------------------------------
Changelog:
v1.0
Initial Release
v1.1
Faster First Boot
Increased Performance
v1.2
Updated to N7G75S
Reserved...
Yes!!!
Fantastic!
Agreed. Looking forward to this.
Pleqse make advanced watch settings work
Edit: it works but DND doesn't work? Is this a dp4 bug?
Thank you for a great ROM. Is there a way to add more face watch to this version? I downloaded several, but none of them appear in android wear. Thanks.
atn0716 said:
Thank you for a great ROM. Is there a way to add more face watch to this version? I downloaded several, but none of them appear in android wear. Thanks.
Click to expand...
Click to collapse
Open the Play Store on the watch and install them.
edit - You might read this to get up to speed on the MASSIVE changes from AW 1.5 to 2.0 Previews:
https://developer.android.com/wear/preview/support.html
Awesome way to start the New Year! Kudos
new bootloader or anything else needed? Or just wipe and flash away?
is root working for anyone else? tried getting into advanced settings and it says i don't have root? can i simply flash a supersu zip?
edit: root appears to work, it's advanced settings that isn't getting along
im assuming i need to go to official dev preview for bootloader first coming from your other rom @negamann303
edit- never mind it took like 15 mins to boot but i was at my office so no biggie lol
Smacksmack206 said:
im assuming i need to go to official dev preview for bootloader first coming from your other rom @negamann303
Click to expand...
Click to collapse
You shouldn't have to change bootloader as long as you use my kernels (modified stock included)
Sent from my SM-G935P using Tapatalk
I will have to wipe the watch. ok. Will Wear Manager install "old apps" as installing 1.x rom? Or will i have to config the watch from scratch?
If the last one, i wont test it before weekend Wont like to be a half week without my watch
SirTurbo said:
I will have to wipe the watch. ok. Will Wear Manager install "old apps" as installing 1.x rom? Or will i have to config the watch from scratch?
If the last one, i wont test it before weekend Wont like to be a half week without my watch
Click to expand...
Click to collapse
It's recommended that you do a full wipe if only coming from my 1.5 rom. Only because I have system apps in data. But the workaround would be deleting the system apps in data/apps in recovery prior to install
You could probably use root essentials to uninstall the system apps that are stored in the data partition
Sent from my SM-G935P using Tapatalk
well, i understand to wipe cache, system, data... dont like, but think need to do, better at a version upgrade as this.
but if i do the big wipe (maybe i flash tonight because i cant refuse to play^^) i am not sure if i need to install the apps which come from phone again by hand. Or the android wear manager installed on the phone will "complete" the installation at watch as when i did fresh installed earlier, from 1.5 to 1.5.
Maybe i will need the android wear manager for 2.x too and that one wont use the config of the older one.
Hmm, think i will give it a try, just made a backup. Hate that watches have only 4GB flash. when using, storing some zips to flash und doing a backup... the watch begins to whine about less space...
Interested in the next days - having no time to play with wear. last weekend installed an amazon fire tv box for a mate, rest of the week will be "full" too. f.e. friday i drive to a friend of mine, installing her sons new phone. and then taking the tablet from one of her friends. to play around with grub to get it back to life. and so on. And now you forced me to play with my wearable. a day should have 48 hours
im so happy this rom is perfect.
and even advanced settings works since the dev updated to the lasted api
SirTurbo said:
well, i understand to wipe cache, system, data... dont like, but think need to do, better at a version upgrade as this.
but if i do the big wipe (maybe i flash tonight because i cant refuse to play^^) i am not sure if i need to install the apps which come from phone again by hand. Or the android wear manager installed on the phone will "complete" the installation at watch as when i did fresh installed earlier, from 1.5 to 1.5.
Maybe i will need the android wear manager for 2.x too and that one wont use the config of the older one.
Hmm, think i will give it a try, just made a backup. Hate that watches have only 4GB flash. when using, storing some zips to flash und doing a backup... the watch begins to whine about less space...
Interested in the next days - having no time to play with wear. last weekend installed an amazon fire tv box for a mate, rest of the week will be "full" too. f.e. friday i drive to a friend of mine, installing her sons new phone. and then taking the tablet from one of her friends. to play around with grub to get it back to life. and so on. And now you forced me to play with my wearable. a day should have 48 hours
Click to expand...
Click to collapse
Actually, it doesn't sync like 1.5. You actually have to install them all via play Store on the watch. The good news is that there is a section on recently used apps, which includes your watch apps installed prior, also they install pretty quick.
Sent from my SM-G935P using Tapatalk
negamann303 said:
Actually, it doesn't sync like 1.5. You actually have to install them all via play Store on the watch. The good news is that there is a section on recently used apps, which includes your watch apps installed prior, also they install pretty quick.
Click to expand...
Click to collapse
Hmmm... interesting recently used apps sounds nice. but i think i will save my backup for a while
but first problem: When i try to copy my google account to watch, i get an error on phone.
And an interesting issue: I chose english language because i read that other languages might cause some malfunctions.
but after that, the messages come in german, the language at my phone. i am not able to say what will be later on, because actually i stuck on copying the google account.
Edit:
ok, maybe the phone cant copy the account to watch because watch hangs. watch is looking for updates and "nothing goes"...
only thing i notice is play music doesnt open upon seleting play on wear.
it goes back to watch face screen
-edit-
if it does what i mention originally then uninstall and reinstall from play store to get "play music" working
I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?
If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
If HMD will push Android 10 officially, you can install it under ADB sideload easily and link will be posted here.
Internal build version: A1N-5060-0-00WW-B01
It will be updated from: A1N-414K-0-00WW-B01, which is unreleased January 2020 Security Update.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than A1N-414J-0-00WW-B03, update to 414J before proceed. (Alternately, dial *#*#7837#*#* to check, proceed if displays 00WW_4_14J-B03)
FYI, 414J is December 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install A1N-414K-0-00WW-B01-414J-0-00WW-B03-update.zip with adb sideload under recovery.
3. Reboot to normal OS and recovery again - it's not over yet.
4. Install A1N-5060-0-00WW-B01-414K-0-00WW-B01-update.zip with adb sideload under recovery.
5. Reboot your phone.
That's it.
If Android 10 official update pushed publicly, link will be updated here.
Download link:
To prevent throttle error, I didn't upload them to Google Drive or other cloud storages. Sorry for inconvenience.
https://www.androidfilehost.com/?w=files&flid=303427
Just perfect for me ! ?
Thanks !
edit: but gcam doesn't work anymore, I tested several versions ...
How to revert to android 9, please ?
Can this work on TA 1004?
christophebeuvry said:
Just perfect for me !
Thanks !
edit: but gcam doesn't work anymore, I tested several versions ...
How to revert to android 9, please ?
Click to expand...
Click to collapse
Can you please list down what all works and what doesn't? The phone is kind of my daily driver.
gcam does not work
nokia camera also bug but works
some lags and restart of the interface
To subscribers:
New internal packages updated!
Existing 5060 users may apply to 5100 by installing these 4 packages:
A1N-5070-0-00WW-B01-5060-0-00WW-B01-update.zip
A1N-5080-0-00WW-B01-5070-0-00WW-B01-update.zip
A1N-5090-0-00WW-B01-5080-0-00WW-B01-update.zip
A1N-5100-0-00WW-B01-5090-0-00WW-B01-update.zip
New comers with A1N-414L-0-00WW-B01 installed (can be acknowledged by dialing *#*#227#*#* or *#*#7837#*#*) can apply this update directly:
A1N-5100-0-00WW-B01-414L-0-00WW-B01-update.zip
And for enthusiasts who're interested with A1N-5100 full dump and would like to port that to original Nokia 8, I will upload that later.
Any update on the stability of this build? I want to test it but I use this phone as my secondary.
Thank you, hikari_calyx. ?
hikari_calyx said:
To subscribers:
New internal packages updated!
Existing 5060 users may apply to 5100 by installing these 4 packages:
A1N-5070-0-00WW-B01-5060-0-00WW-B01-update.zip
A1N-5080-0-00WW-B01-5070-0-00WW-B01-update.zip
A1N-5090-0-00WW-B01-5080-0-00WW-B01-update.zip
A1N-5100-0-00WW-B01-5090-0-00WW-B01-update.zip
New comers with A1N-414L-0-00WW-B01 installed (can be acknowledged by dialing *#*#227#*#* or *#*#7837#*#*) can apply this update directly:
A1N-5100-0-00WW-B01-414L-0-00WW-B01-update.zip
And for enthusiasts who're interested with A1N-5100 full dump and would like to port that to original Nokia 8, I will upload that later.
Click to expand...
Click to collapse
Can it work in TA- 1004? I'm waitting android 10 in Nokia 8 Thank kiu so much
Hi, I installed Android 10 on my Nokia 8 sirocco and since then, impossible to make gcam work. I have tried many versions but the application closes directly. Gcam worked perfectly on android 9. Do you have any solutions? Thank you.
Hey is it possible to install this on Nokia 8(TA-1004)?
To experienced developers:
Here's the full partition dump of Android 10 for A1N.
https://www.androidfilehost.com/?fid=4349826312261769554
If you'd like to port this to Nokia 8 (NB1, TA1004/1012/1052), now it's your chance.
Note this cannot be flashed to Nokia 8 NB1 directly.
To subscriber of this topic:
Nokia 8 Sirocco just got Android 10 official update.
If you have installed A1N-5120-0-00WW-B01 build (dial *#*#7837#*#* and output might be 00WW_5_120-B01), then it's same to official build and enjoy it.
We're fetching full OTA link and update soon.
Ok,
Because I was tired of waiting for Nokia to send the OTA update to my phone, I did this manually on a device that was running the latest March security patch and Android 9 using ADB and the A1N-5120-0-00WW-B01-414M-0-00WW-B01-update.zip package.
Follow the below guide if you want to update your device as well:
- dial *#*#7837#*#* and check that software is 414m
- download adb and fastboot from Google official site ( https://dl.google.com/android/repository/platform-tools-latest-windows.zip )
- download the update ( https://androidfilehost.com/?fid=4349826312261750327 )
- reboot the phone in recovery mode and go to Apply update to ADB ( guide how to reboot to recovery: https://www.hardreset.info/devices/nokia/nokia-8-sirocco/recovery-mode/ )
- placed all the above files ( firmware and google adb abd fastboot ) in the same folder open a CMD window and use the following command: ADB sideload A1N-5120-0-00WW-B01-414M-0-00WW-B01-update.zip
- wait for the update to finish, select reboot system now and reboot the phone.
Voilla, you are running the latest Android.
Things noticed after the update:
- phone feels a little bit snappier
- interface is the same, minor icon changes bug generally is the same
- has android 10 gesture navigation which does not work with a third party launcher
To subscribers of this topic:
Here's the full OTA link of A1N-5120 build.
https://android.googleapis.com/pack.../69b78c6f6a866f314a3b50e7ac88cd10e94233e7.zip
Hi!
Can you tell me how I can flash the latest full OTA of A1N-5120 build? I'm already on this update, but my phone is fully buggy after the official OTA update. I make a factory reset with clearing cache and some other folders by boot menu and I think I was delete something important. Get me advise, please! Thanks!
rudeboy1988 said:
Hi!
Can you tell me how I can flash the latest full OTA of A1N-5120 build? I'm already on this update, but my phone is fully buggy after the official OTA update. I make a factory reset with clearing cache and some other folders by boot menu and I think I was delete something important. Get me advise, please! Thanks!
Click to expand...
Click to collapse
I also have some problems with the phone running the latest OTA and also want to flash the latest OTA from file because neither factory reset from Settings nor from Recovery menu didn't help.
I've downloaded the file from https://android.googleapis.com/packages/ota-api/nokia_a1nsprout_avenger00ww/69b78c6f6a866f314a3b50e7ac88cd10e94233e7.zip, then copied it to the root of my Sirocco and dialed *#*#874#*#* but that didn't work for me.
I read that the file should have correct name - may be that is the problem?
What is the correct name for file so that it could be accepted as an update by the phone already running the same OTA?
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.