My tablet (Nexus 7, 2013 flo) just updated to Cyanogenmod 13 (snapshot, I was previously using the latest snapshot version of 12). it was an automatic update, where it let me know that there was snapshot version for download, then let me download it and install automatically.
When I re-started the tab my google apps were fussy so I realised I needed to update gapps. I downloaded (from opengapps) the pico version for Android 6.0 and flashed it (using twrp 2.8.7). After that I rebooted. Now as soon as I boot up, it pops up the notification "unfortunately setupwizard has stopped" and a variety of "Google play services/youtube/gmail/etc have stopped" notifications. As soon as I click OK the notification returns so I am unable to interact with the system at all.
What have I done wrong? How do I fix it? help please.
aequidens said:
flashed it (using twrp 2.8.7)
Click to expand...
Click to collapse
"Known broken TWRP versions: 2.8.7.0"
Perhaps it is also broken on N7?
k23m said:
"Known broken TWRP versions: 2.8.7.0"
Perhaps it is also broken on N7?
Click to expand...
Click to collapse
Maybe it was that. Impatience got the better of me and I ended up getting the latest TWRP, downloading CM13 from their site and reinstalling everything (I had hoped to avoid that because of reinstalling everything but I'm not good at waiting). Something in he mix worked anyway and it's all fine now. (Except Neko Atsume which does not store anywhere and has to start over LOL).
I have a problem with the latest update from lineageOS 10. I have downloaded the latest update lineage OS 10 by using OTA update and after I installed the update there was a problem with my file manager could not be opened. Always says "unfortunately the file manager has stopped". My devices samsung galaxy N7000. And i have successfully run android nougat with the help of custom rom lineage 14.1. But after I did this update then did the file manager problem no longer work. How to fix it? Please help me !!!
Sultan211, LineageOS 10 (10.0, not 10.1 and 10.2) is Android 4.1.2 Jelly Bean?, Correct?
Sent from my XT1254 using XDA Labs
Flash stock rom
If the File Manager is buggy with the latest update you downloaded, there is nothing much you can do except to wait for the next update and hope for it to be fixed. Alternatively, you can download a different file manager and use that in the interim until the next update where the FM might get fixed for your version of the OS. If you really, really, want to see what's causing the issue then you will need to use an utility such as CatLog and start monitoring for errors right before the error and stop monitoring after the error.. That will tell you what's causing the issue but won't fix it. You can post the log here if you know how to capture it.
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on crackling
Official Download link:
LineageOS Downloads
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
Open GApps (pico only)
Changelog:
Changes for crackling
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to LineageOS
reserved
reserved2
The "old" Lineage 17.1 thread got lost during some xda server maintenance. It's not really clear to me what happened.
It couldn't be brought back for several weeks now, so I decided to create a new thread.
I'd also like to inform you that I'll provide some test builds here. Before merging bigger changes I'd like to ensure the builds are okay (not just for me).
It would be nice if some of you could test a bit. Only caveat: You won't be able to switch between test builds/official builds easily as different signature keys are used and a factory reset is needed (alternatively flashing a migration file could save you from resetting the device (more info)). However, these test builds are thought for interested persons only
You'll find the first test build here.
Changes:
switch to userspace lmkd (more info here)
It would be interesting if you experience any differences in memory management (how many apps can be opened in background, how fast is app switching, when are apps closed...).
And of course if the system is usable at all.
Recovery
Can the lineage-recovery.img do nandroid backups now that twrp can't?
petexd said:
Can the lineage-recovery.img do nandroid backups now that twrp can't?
Click to expand...
Click to collapse
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
115ek said:
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
Click to expand...
Click to collapse
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
petexd said:
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
Click to expand...
Click to collapse
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
115ek said:
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
Click to expand...
Click to collapse
Thanks for the info. That's exactly what's happening but I have no idea how to apply that patch. I don't really want to install an unoffical rom: that's how I discovered twrp wasn't working properly, testing one of my builds then hoping to go back to your offical from restore.
Any way I'm happy to wait for your next issue.
Thanks for doing a great job.
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
libove said:
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
Click to expand...
Click to collapse
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Certification Status on 17.1
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Must sideload, not enough space to push and install from local, I feel silly...
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
115ek said:
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Click to expand...
Click to collapse
zappbrannigan62 said:
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Click to expand...
Click to collapse
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
didyou said:
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
Click to expand...
Click to collapse
Have you installed Gapps or MicroG on your system ?
Cerealekillers said:
Have you installed Gapps or MicroG on your system ?
Click to expand...
Click to collapse
Yes, installed pico GAPPS.
Works
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
I flashed the latest nightly + pico gapps using TWRP and
everything is working beautifully
Playstore reports the device to be certified
So thanks a lot!
libove said:
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
Click to expand...
Click to collapse
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
Can verify that my Play Store, on 17.1, reports my ridiculously modded Swift as certified without having to do anything to achieve that.
Sorry, I know I am a real dunderhead when it comes to these things and I apologise for such a basic question. But...
I have a Swift 2 X which is working on Oreo. If I replace this with LineageOS 17 do I have to do anything "fancy" to get Google Pay to work after I've installed LineageOS?
I've installed LineageOS on my Oppo R5 which doesn't have NFC so this can't use "Tap 'n' Pay" anyway. I've installed LineageOS on mine and my Wife's Nextbit Robin and Google Pay - "Tap 'n' Pay" - worked without doing anything more than install and go.
It's just that I do really like the facility of Google Pay and wouldn't want to lose that just for the sake of system wide dark mode.
Sorry again for being so dense as to not understand.
Hello,
I have a brand new device which has not officially been released yet. Therefore, there is no stock firmware image available or recovery image. Just wanted to get that out of the way. I could not remove a lot of the manufacturers bloatware because i could not root or port TWRP without a stock image or recovery image.
I stumbled onto Project Treble. I flashed phh treble and it worked. Well, I managed to get everything to work with some workarounds. The only thing I am having trouble with is when I install phh with gapps. After booting I get the "Your device is not Google certified" message repeatedly spammed.
The only workaround I have been able to get to work for the uncertified device message is to remove phh superuser. I have tried using the Google device registration page. It does not work for my device. I want to keep root so I can pull the recovery image and port TWRP for this device. Are there any other fixes that will work? In order to pick up in some of my games I think I need Google Play?
Thanks,
Rocky
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
LR7875 said:
What Gapps? you can try bitgapps, opengapps, etc...
If google play is impossible, you can download .apk android apps (Android PacKage, APK) from www.uptodown.com, www.apkmirror.com and www.apkpure.com, unless it is google play exclusive(probably payment content?)
Click to expand...
Click to collapse
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
bigroc2223 said:
Thanks for your reply. Yes, I need to recover paid content. There are games and programs that I have spent a decent amount on that I would like to have access too. I wish there was a phh gsi image with magisk root instead of phh root. From what I read you can disable it with Magisk.
I do not know a whole lot about root. I wonder if now that I am using phh gsi if it would be possible to install Magisk now? I could not install it before because the device does not have a system image available yet since it has not officially been released. Like I said I do not know much about root, could I just download a vanilla phh gsi image and patch that with magisk?
Click to expand...
Click to collapse
No no no, you need to patch boot.img for magisk, not system. Go to www.apkmirror.com (app repository), search and download 'magisk ' app(that is magisk manager), click and install the downloaded .apk file, allow install from browser, and after installing use the app to patch the boot.img(search Google), and flash patched boot.
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
bigroc2223 said:
I thought I bricked the phone but was able to recover. I am getting an error that I cannot seam to resolve. The phone screen will go black. It goes to a crash dump screen that says the fallowing.
Qualcomm Crash Dump Mode
modem subsystem failure reason
trm_rf_alloc.cpp:459:allocation
not found for RF Tech:2 Band:126
sub_capability 0.
After this happens and I reboot the device I have a hard time getting mobile data to work. It is definitely an error pertaining to the signal radio. I have no clue how to fix it. With this happening the device is pretty much unusable.
Click to expand...
Click to collapse
I am sorry to hear that.It is pretty much beyond what I can solve so I will try find similar threads.
Hello,
I regularly upgrade my LineageOS for mircoG via OTA. However, every time there is a new lineageOS version, there is also a new recovery file available online to download, having different sizes and checksums. So there seems to be changes. However, I didn't find any place online where I could see a changelog, or list of changes/fixes for the new recoveries (for my phone, which is a Samsung S5 Duos klteduos). Previously, I used LineageOS with GAPPS, and TWRP, and it was clear from the website which fixes/features a new TWRP version had.
When booting into recovery, my recovery for microG doesn't have a version number, but it just shows the date of the latest lineageOS for microG which I OTA updated.
Could somebody point me to the website which discusses recovery of microG changes, so I could see whether I should/need to upgrade regularly the recovery?
thanks!