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
Related
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?
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
vincetoxicum said:
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
Click to expand...
Click to collapse
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Normally working fine. Read carefully the manual from lineage.org and learning by doing. Read the changelogs, too. That's helpful and read so much ypu can about A/B partion and if then working, don't update over Updater for few days. There is a bug, which is in the next days be fixed. So, you must invest some time to understand all. Here it was not easy, too. Maybe 2 days to learn from mistakes. Then you get it working.
41rw4lk said:
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Click to expand...
Click to collapse
Thank you for your reply! So what exactly would you propose I do? Wipe with TWRP first, then return to Fastboot and flash los from there?
Before booting I'd like to install an open gapps package which must be done before booting los for the first time. Could I do that via Fastboo as well?
vincetoxicum said:
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
Click to expand...
Click to collapse
Just flash it through twrp like a normal rom I have never heard of anyone sideloading a custom rom. If you're using a carrier variant of the Moto Z2 Force that may give you some issues too.
Hybrid Theory said:
Just flash it through twrp like a normal rom I have never heard of anyone sideloading a custom rom. If you're using a carrier variant of the Moto Z2 Force that may give you some issues too.
Click to expand...
Click to collapse
The wiki says to sideload for a reason -- you can bungle up FBE encryption keys by storing stuff in TWRP on a device where FBE decruption in TWRP is attempted (nash).
vincetoxicum said:
Thank you for your reply! So what exactly would you propose I do? Wipe with TWRP first, then return to Fastboot and flash los from there?
Before booting I'd like to install an open gapps package which must be done before booting los for the first time. Could I do that via Fastboo as well?
Click to expand...
Click to collapse
Follow the wiki description - it's a TWRP bug that sideload only goes to 47% - though it has actually suceeded. It would turn red and say "Failed" if it failed.
41rw4lk said:
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Click to expand...
Click to collapse
See above - it didn't fail.
Because of the A/B partition, you can only install through a temporary twrp. If you try permanent twrp, you won’t be able to boot
Same problem with Lineage Recovery. Followed exactly the wiki but it stays the same 15.1 version.
I'm on T-Mobile and I ALWAYS had that problem, totally forgot about it at this point. Just ignore it, the rom is flashes successfully anyway
Dany XP said:
I'm on T-Mobile and I ALWAYS had that problem, totally forgot about it at this point. Just ignore it, the rom is flashes successfully anyway
Click to expand...
Click to collapse
Well, but after reboot the new rom is not flashed or active (might be in one of A/B but no switch of slots).
carlos22b said:
Well, but after reboot the new rom is not flashed or active (might be in one of A/B but no switch of slots).
Click to expand...
Click to collapse
You might be right but last time I fastboot flashed anything was some time ago. Maybe after flashing I had to manually switch slot? I don't remember. I'm in Lineage 16 and is working great
Dany XP said:
You might be right but last time I fastboot flashed anything was some time ago. Maybe after flashing I had to manually switch slot? I don't remember. I'm in Lineage 16 and is working great
Click to expand...
Click to collapse
Ok. How can I change the slot manually?
carlos22b said:
Ok. How can I change the slot manually?
Click to expand...
Click to collapse
Of course, there Is a fastboot command for that, very simple. Just google it
Changed it so slot b - now bootloop in both a and b
This A/B system is really no help for custom roms...
Now try to flash with temporary twrp.
Same here.
Device: sweet TWRP: 3.6.1 and 3.6.2
Bash:
adb sideload CARBON-CR-9.0-R-WEEKLY-sweet-20230501-0124.zip
serving: 'CARBON-CR-9.0-R-WEEKLY-sweet-20230501-0124.zip' (~47%)
adb: failed to read command: Success
ROM flashed, booted, and seem to work fine.
EDIT:
It is normal. Found this:
https://www.reddit.com/r/LineageOS/comments/af12lu/_/edvwaex
That's an ADB issue, nothing is wrong with the device, cable, PC or the installation process.
If I remember correctly (from a discussion long ago), Google's ROMs are transferred about 2.2 times across the sideload. To make the progress bar add up to 100%, they said "2.2 times the file size equals 100%". Our ZIPs are transferred just once, so the final progress is at about 47% with a success. The xfer seems to show the transferred data compared to the file size. Ours clocks in at x1.00 or x1.01, while Google's is about x2.something.
Click to expand...
Click to collapse
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
wahlmat said:
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
Click to expand...
Click to collapse
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
ireaper4592 said:
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
Click to expand...
Click to collapse
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
wahlmat said:
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
Click to expand...
Click to collapse
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
ireaper4592 said:
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
Click to expand...
Click to collapse
I actually can't seem to find it on their site.
wahlmat said:
I actually can't seem to find it on their site.
Click to expand...
Click to collapse
https://www.oneplus.com/uk/support/softwareupgrade
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.