Related
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.
Does this have the Wifi fix in it? or has Google not published that yet?
Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm
Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?
ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3
Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.
Great work, thanks. Flashed about an hour ago, flawless so far!
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?
Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.
ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?
kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.
Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.
Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
I can flash back to stock via the SkipSoft Unified Android Toolkit, but not matter how far back I go, the only 3rd party ROM that will not get stuck on a never-ending bootscreen after install is CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte. Not even the CM nightlies that came immediately before or after would work once this was installed.
I would like to try something newer if there is a stable Lollipop, Marshmallow, or Nougat ROM you would recommend. I don't use as a phone anymore, so I don't even need cellular data to work.
Thank you very much to anyone that even takes a look at this.
More info...
Model Number
1HZGY
Android version
4.4.4
Baseband version
L710VPUDOH1
Kernel version
3.4.104-cyanogenmod-g3652409
[email protected] #1
Mon Aug 31 16:36:33 OCT 2015
Build number
cm_d2lte-userdebug 4.4.4 KTU84Q bdfbe2c9c2
test-keys
SELinux status
Enforcing
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
madbat99 said:
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
Click to expand...
Click to collapse
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
pravus87 said:
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
Click to expand...
Click to collapse
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
madbat99 said:
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
Click to expand...
Click to collapse
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
pravus87 said:
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
Click to expand...
Click to collapse
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
madbat99 said:
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
Click to expand...
Click to collapse
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
pravus87 said:
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
Click to expand...
Click to collapse
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
madbat99 said:
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
Click to expand...
Click to collapse
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
pravus87 said:
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
Click to expand...
Click to collapse
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
madbat99 said:
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
Click to expand...
Click to collapse
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
pravus87 said:
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
Click to expand...
Click to collapse
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
madbat99 said:
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
Click to expand...
Click to collapse
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
pravus87 said:
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
Click to expand...
Click to collapse
Happy to help
madbat99 said:
Happy to help
Click to expand...
Click to collapse
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
pravus87 said:
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
Click to expand...
Click to collapse
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
madbat99 said:
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
Click to expand...
Click to collapse
I did not try Lineage or Vanir again like I did Commotio and CarbonROM to verify the md5s. I will try them and some older builds of each.
I sincerely appreciate the offer. I would certainly be willing to download a large backup if you would be willing to take the time to clean install and upload. Let me try the remaining steps you listed first, though. Don't want you to have to spend time doing all that if we can get it working another way.
Thanks again. Will keep you posted!
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
pravus87 said:
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
Click to expand...
Click to collapse
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
madbat99 said:
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
Click to expand...
Click to collapse
Thank you. No rush - whenever you have time.
I don't get it either. I waited a long time to post about it because I assumed there was something simple I was overlooking that I would eventually figure out. Not sure this will work if nothing else has, but I can't wait to give it a shot.
My XT1795 is on stock 8.1 with unlocked BL, TWRP and magisk (I haven't installed any modules though). I am facing this weird issue since an year, the WiFi randomly keeps disconnecting and reconnecting automatically every 10 to 15 mins. I am sure that it has nothing to do with my WiFi router as I face the same issue when I am connected to mobile hotspots or any public or private network. I tried resetting the wifi and network settings, restored the device quite a few times, and also reflashed the stock rom but the problem still exists. The most recently that I reflashed the stock rom was a month ago, i didn't face any issue for the first 15 days but now it's back again.
Can someone please help me?
Try using a different kernel. But make sure that stock 8.1 is supported
Some random said:
Try using a different kernel. But make sure that stock 8.1 is supported
Click to expand...
Click to collapse
Yeah but I don't understand the reason behind this problem..
rizwan.mahai said:
Yeah but I don't understand the reason behind this problem..
Click to expand...
Click to collapse
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Some random said:
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Click to expand...
Click to collapse
View attachment alogcat.2020-03-30-11-09-20+0530.txt
Please have a look at the logcat, this morning while generating this log the wifi network ([email protected]) disconnected and reconnected atleast 3 times. Even after the reconnection, most of times I am not able to access the internet, I have enable airplane mode, then enable the wifi again or reboot the device. I am sure there is no problem with my router because, I face the same issue when ever I connect to any network be it a mobile hotspot or railway public network.
@lohanbarth @vaserbanix @kalyansundhar
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Some random said:
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
rizwan.mahai said:
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
Click to expand...
Click to collapse
The problem is still there on Lineage 15.1.
Lineage 15.1 Logcat
Some random said:
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
The wifi drops are more severe on lineage 15.1. Most of the times there's no internet access even while wifi is connected. Please have a look at the new logcat file.
View attachment logcat_lineage.04-01-2020_10-57-24.rar
I am being forced now to roll back to the stock rom from twrp backup.
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Some random said:
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Click to expand...
Click to collapse
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
rizwan.mahai said:
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
Click to expand...
Click to collapse
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Some random said:
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Click to expand...
Click to collapse
What is GSI ?
rizwan.mahai said:
What is GSI ?
Click to expand...
Click to collapse
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Some random said:
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Click to expand...
Click to collapse
Please try to run this command in terminal emulator, while wifi is on.
Code:
su
killall wpa_supplicant
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
rizwan.mahai said:
Please try to run this command in terminal emulator, while wifi is on.
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
Click to expand...
Click to collapse
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Some random said:
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Click to expand...
Click to collapse
Thanks. I'll give it a try.
rizwan.mahai said:
Thanks. I'll give it a try.
Click to expand...
Click to collapse
If the launcher for example is lagging, try adding this line
Sys.use.fifo_ui=1
Into build.prop and rebooting, maybe that makes it better
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.