CM 12.1 GApps not installing - Galaxy Tab S Q&A, Help & Troubleshooting

As the title says: cm 12.1 gapps (arm) aren't installing even though there are no errors during flashing. I flashed the latest CM 12.1 nightly and, as far as I am aware, the latest official TWRP.
Any ideas?
EDIT: I found the "problem." Since the GApps are shown as 3 different versions (arm, arm64, and x86), I didn't realize that all 3 versions were in the same zip folder. I thought if you downloaded the arm version, then that's the one you got.

Related

[Q] Version of my find7

I felt like giving paranoid android a go, seeing as I've been using CM for years now and wondered how different the two are these days.
But I've been stumped in trying to flash it to my phone. I'm running one of the latest CM nightlies for the find7 (not the s variant) and that states it's for the find7, find7a and find7s. But neither version of the PA rom will flash due to my phone version being the find7a.
Is there any PA rom that I can flash that is based on lollipop?
mada360 said:
I felt like giving paranoid android a go, seeing as I've been using CM for years now and wondered how different the two are these days.
But I've been stumped in trying to flash it to my phone. I'm running one of the latest CM nightlies for the find7 (not the s variant) and that states it's for the find7, find7a and find7s. But neither version of the PA rom will flash due to my phone version being the find7a.
Is there any PA rom that I can flash that is based on lollipop?
Click to expand...
Click to collapse
Nearly every project supports both 7a and 7s with a single unified build. CM broke their crap by listening to jumoog too much (even Nameless realized that splitting builds was a bad idea...)
The problem you describe sounds like a broken recovery.
Entropy512 said:
Nearly every project supports both 7a and 7s with a single unified build. CM broke their crap by listening to jumoog too much (even Nameless realized that splitting builds was a bad idea...)
The problem you describe sounds like a broken recovery.
Click to expand...
Click to collapse
I've just updated to the latest twrp and downloaded the find7 QHD and UHD version of the PA rom and still no luck. The error says the rom is for the find7 and my device is the FIND7. I also just want to double check the 7a isn't the QHD version of the device?
Entropy512 said:
Nearly every project supports both 7a and 7s with a single unified build. CM broke their crap by listening to jumoog too much (even Nameless realized that splitting builds was a bad idea...)
The problem you describe sounds like a broken recovery.
Click to expand...
Click to collapse
mada360 said:
I've just updated to the latest twrp and downloaded the find7 QHD and UHD version of the PA rom and still no luck. The error says the rom is for the find7 and my device is the FIND7. I also just want to double check the 7a isn't the QHD version of the device?
Click to expand...
Click to collapse
Could be a broken update-binary file in the zip file. People had this issue with some other ROMs. Will check later.

Faq's about cm13 for redmi 1s by feifofum

What are the known bugs of r6 of cm 13 by feifofum. And regarding the bootloader and modem files(firmware_7.0.5.0.zip) do we have to flash it before installing cm 13 or after installing cm 13 with gapps.
1st fimware
2nd ROM
3rd Gapps
igarg2001 said:
What are the known bugs of r6 of cm 13 by feifofum. And regarding the bootloader and modem files(firmware_7.0.5.0.zip) do we have to flash it before installing cm 13 or after installing cm 13 with gapps.
Click to expand...
Click to collapse
you install the firmware just once and it should be good to go, 1st firmware, 2nd rom, 3rd gapps.
future clean installs only need the rom and gapps

[MI 5][Lineage OS] Status 7 error even after updating latest stock rom

I am facing status 7 error error on installing lineage os zip (latest nightlies) even when I am on latest MI stock. Tried many times no luck. Currently on MIUI version 8.2.2.0 which is latest. TWRP version 3.1.1.0

Lineage Os 19.1 gapps

I've installed latest Lineage Os 19.1 and Nickgapps, everything works great, but now i've noticed that i've installed gapps for 12 android, not 12.1. Should i delete gapps and install 12.1 version?
klucik47 said:
I've installed latest Lineage Os 19.1 and Nickgapps, everything works great, but now i've noticed that i've installed gapps for 12 android, not 12.1. Should i delete gapps and install 12.1 version?
Click to expand...
Click to collapse
For my S10 on Lineage 19.1 its put error when I flash it on TWRP

How to update LineageOS 18.1 to a higher nightly build?

Hi,
I have Lineage 18.1 with Magisk and GAPPS (pico) installed on a Oneplus 8T. Now I'd like to update to a newer Lineage 18.1 nightly build. The Lineage Updater doesn't offer this option (why not? Wouldn't it be a nice feature request? ) thus I assume I have to update to a higher nightly build of 18.1 by myself.
Am I right that the update procedure is the same as installing LineageOS 18.1 from recovery except that I shouldn't do neither a Factory Reset nor a Format data / factory reset? (to keep my apps)
As I have Magisk installed, I assume that I have to repeat patching the boot.img. Right?
I'm unsure about GAPPS. Do I need to sideload it again after having installed a newer nightly build of LineageOS 18.1 and before booting?
Many thanks for your support.
you are not getting updates for 18.1 because 19 is out. uograde instructions are on lineage website

Categories

Resources