Database Info

[Completed] How to remove Gapps from CM 12.1?

I have the wrong gapps installed and am trying to flash gapps 5.1
I can't flash and just update the apps because the binary is different.
What I am trying to flash ( Google Stock Package )
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
I want to keep everything on my device except the proprietary google apps
so if there is a way to back up everything via TWRP( Except Gapps) please let me know.
From there I would perform a full wipe and just restore and then flash gapps 5.1
Tk gapps debug log
.View attachment tk_gapps_debug_logs.tar.gz
Thanks
-CRad

Thread closed as user already founded the right place for his question.
http://forum.xda-developers.com/showpost.php?p=61915212&postcount=387

Installing CM11.M11 on Nexus 5

Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap

Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.

Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.

Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.

Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".​- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.​- fastboot flash recovery twrp.img​- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.

[GUIDE] Install custom ROM without computer

Hello everyone. I have come up with a lazy way to install custom ROM (such as Cyanogenmod) in *most* phone (I tried this on S3mini and Galaxy MEGA). Please note that this method moght not work on your phone and I am not responsible for bricking your phone.
Things you need:
-Your phone, fully charged
-Your precious time (About 30-60minutes)
-One click root app (I use Kingroot, download it with apk) (You may use other apps, of course)
-TWRP manager from playstore
-ZIP file of TWRP in latest version (V3?)
-ZIP file of the custom ROM matching the version of your device
-ZIP file of GApps matching the version of the custom ROM (Google for gapps and download it)
Steps:
1. Backup your personal information
Copy your personal information such as music, photo, documents out of your phone (e.g.: Cloud drive, USB, SD card). Safety first.
2. Root your phone
Download Kingroot and install the apk with package installer. Run the app and follow the instruction in the app to root.
3. Install TWRP manager
After rooting, install TWRP manager. In the app, install TWRP that match your device.
4. Create a backup for your phone
Boot your phone into recovery (Every phone have different method, so please google about this). In TWRP, press 'Backup' to create the backup.
5. Flash the latest version of TWRP
As the TWRP manager does not offer the latest version of TWRP, you have to flash the latest version by installing ZIP. The latest version of TWRP can install ROM with higher success rate.
To do this, press 'Install' in TWRP. Find the ZIP file of TWRP in latest version and install it.
6. Reboot your device to Recovery mode
7. Wipe your device
In TWRP, press 'Wipe'. Select Cache, Dalvik Cache, System and Data partition and wipe them.
8. Flash custom ROM
In TWRP, press 'Install'. Select the Custom ROM ZIP and install it.
9. Flash GApps
Most custom ROM does not have Google apps such as play stote, so you have to install it.
In TWRP, press 'Install'. Select the GApps ZIP and install it.
10. Wipe Cache and dalvik cache
In TWRP, press 'Wipe'. Select Cache and Dalvik Cache partition and wipe them.
11. Reboot your device
Now the ROM should be properly installed. First boot might take longer, so please wait patiently.
Shall you brick your phone, try to recover by using backup created in step 4.
PS: I am a newbie here and this is my first guide

While you have to wipe your device to flash the custom rom, it will wipe your data, including the actual Gapps and rom. This shows that your method won't work.

[GT-I9505] Flash Stock-Custom Roms & Useful Links

THIS THERAD WILL NO LONGER BE UPDATED. TAKE A LOOK ON MY UNIFIED GUIDES/COLLECTION​
CLEAN & DIRTY FLASH STOCK OR CUSTOM ROM
Note: These guides have mostly specific links for the S4 GT-I9505 Roms TWRP, Modems & Bootloaders but the steps are the same for all other S4 Models - You just need to find specific Roms,TWRP, Modems & Bootloaders for your device model. You can take a look at "Usefull Links" section below.
THIS IS A COMPLETE GUIDE FOR THE BEST CLEAN INSTALL OF A CUSTOM OR STOCK ROM FROM THE SCRATCH:
1*. Download a stock LOLLIPOP Rom from here or here (doesn't really matter which country you will choose, just be sure to download one of the latests firmwares-recommend is QK1 or PK2) and recommend is latest QK1Modem / QK1Bootloader or PK2Modem / PK2Bootloader. For the all others Modems/Bootloaders, you can find them here. Also Download a windows program Odin. Next, move all your personal data such pictures,music etc from your internal storage to your external sd card or to your pc.*
2*. If you are going to flash a Custom Rom, Download the Custom Rom you want (Recommened any JDC Roms of your preference), Pico or Nano Gapps (or Super Gapps if you have a custom gapps-confg file) be sure you have choosed Platform: ARM and the proper android version of the rom you are going to flash) [If the Rom you want to flash include Gapps, no need to download and flash any Gapps at all] and the latest Magisk for root. After you finished with downloads move your Custom Rom,Magisk,Gapps to one folder in ur external sdcard. *
3. Reboot to Download Mode(power button+vol.down+home button) and Flash TWRP 3.3.1-1 or JDC TWRP 3.3.1-0 via Odin. (You put the .tar file in AP)
4*. Reboot to TWRP Recovery (power button+vol.up+home button) go to Advanced-File Manager-external_sd and delete all folders on ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom Rom/Magisk/Gapps you want to flash. *
5. Now still on TWRP select Wipe-Format Data and type yes-then go back and press-Advanced Wipe-Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe.
6. Now Boot to Download Mode(power button+vol.down+home button) and Flash Stock LOLLIPOP Rom via Odin. (You put the file in AP section)
7*. When Stock Rom is Flashed go to Odin again,
Reboot your device to Download Mode, connect it to PC and put Modem(CP Section) Untick Auto Reboot in options, flash it and reboot your device to system by holding Power Button.
Then Reboot to Download Mode again, put the Bootloader(BL Section) and do the same steps as before.
Check what Modem and BL you have, if Modem and BL didn't changed do the same steps again.
If for some reason Odin fail to flash, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash to your C: drive.*
8. Now Reboot to Download Mode once again and Flash TWRP 3.3.1-1 or JDC TWRP 3.3.1-0 via Odin. (You put the .tar file in AP)
9. Reboot to TWRP(power button+vol.up+home button) and do the steps 4. and 5. Then flash your Custom Rom--->Magisk--->Pico or Nano Gapps (or Super Gapps if you have a custom gapps-confg file) (If Rom doesn't include).
10. Let the Rom boot and Install Magisk Manager manually if it's not preinstalled. Enjoy!
1*For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have PK2 Stock Rom then you need to have PK2 Modem/BL.
On Custom Roms doesn't matter. You can have any of the latest Modem/BL you want but recommend is QK1.
If you want to use KitKat Rom custom or Stock you should flash the proper KitKat Modem/Bootloader. It will not work if you have Lollipop.
2*Skip the step 2. if you are going to flash only Stock Rom.
4*Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
7*If you wanted only to flash stock Rom you done on step 7. If you have any problem with Force Close Apps etc go to Settings->Accounts->Backup and reset->Factory data reset.
***** You can follow the same steps for other variants too but you need to find and choose the proper Firmware-Rom/Modem-Bootloader/TWRP for your variant. *****
THIS IS A COMPLETE GUIDE FOR CLEAN INSTALL OF A CUSTOM ROM BUT NOT FROM THE SCRATCH:
1. Download the custom Rom you want (Recommened any JDC Roms of your preference), Magisk for root solution and Pico or Nano Gapps (or Super Gapps if you have a custom gapps-confg file)[If the Rom you want to flash include Gapps, no need to download and flash any Gapps at all], be sure you have choosed Platform: ARM and the proper android version of the rom you are going to flash. Then move all those files to one folder in ur sdcard.
2*.Reboot to Download Mode(power button+vol.down+home button) and Flash TWRP 3.3.1-1 or JDC TWRP 3.3.0-0 via Odin. (You put the .tar file in AP)*
3.Reboot to TWRP Recovery (power button+vol.up+home button), go to Advanced-File Manager-external_sd and delete all folders on ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom Rom/Magisk/Gapps you want to flash.
4. Now still on TWRP select Wipe-Format Data and type yes-then go back and press-Advanced Wipe-Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe.
5. Flash your Custom Rom--->Magisk--->Gapps.
6. Let the Rom boot and Install Magisk Manager manually if it's not preinstalled. Enjoy!
2*Skip the step 2 if you already have TWRP Recovery installed.
THIS IS A COMPLETE GUIDE FOR DIRTY INSTALL OVER YOUR CUSTOM ROM:
1. [Optional]Make a full nandroid backup., just in case something goes wrong. You can use TWRP to do that. (TWRP-->Backup-->Select everything)
2. Uninstall all Substratum overlays if you have any installed.
3. Remove previous root solution with Magisk Unistaller and optional UnSU to ensure all root remnants are gone. (TWRP-->Flash the unistaller.)
4. Reboot to TWRP and Wipe system, cache and art / dalvik.
5. Flash the Rom-->Magisk-->Gapps.
6. Reboot and Enjoy!
***** I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP . *****
USEFUL LINKS (USB DRIVER, TWRP, ODIN, PIT FILES, ROOT-MAGISK, FIRMWARES, MODEMS AND BOOTLOADERS)
SAMSUNG USB DRIVER
If you have a problem while plug-in the device to your PC and PC can't recognize it, you may miss the Samsung USB DRIVER. To fix follow these steps:
1. Download SAMSUNG USB DRIVER.
2. Unzip it and install it to your PC.
3. Connect your device and done! Now should be ok.
TWRP
Download the TWRP version for your specific model of your device HERE.
Installation Process:
1. Without any custom recovery installed on your device: Download the .tar file of the version you choosed.
Reboot to Download Mode(power button+vol.down+home button) and Flash the TWRP version you choosed via Odin. (You put the .tar file in AP)
Done!
2. With TWRP already installed to your device (UPDATE to latest version): Download the .img file of the version you choosed.
Reboot to TWRP(power button+vol.up+home button) and press Install--->Install Image--->Navigate to .img file you downloaded before---->Flash.
Done!
ODIN
You can download ODIN HERE
PIT FILES
GT-I9505: You can find the link HERE. Flash it in Odin at PIT tab.
ROOT - MAGISK
You can root your device via MAGISK. Just download the .zip from HERE and flash it in TWRP.
SAMSUNG FIRMWARES
You can find all Samsung Firmwares HERE or HERE.
Just search for your device model.
MODEMS & BOOTLOADERS COLLECTION
GT-I9505:
Latest Modem QK1Modem
Latest Bootloader QK1Bootloader
You can find most of the Modems & Bootloaders HERE. Just search for your device model.
Steps:
1. Open Odin
2. Reboot your device to Download Mode, connect it to PC and put Modem(CP Section) Untick Auto Reboot in options, flash it and reboot your device to system by holding Power Button.
3.Then Reboot to Download Mode again, put the Bootloader(BL Section) and do the same steps as before.
4. Done! Check what Modem and BL you have, if Modem and BL didn't changed do the same steps again.
If for some reason Odin failed to flash, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash to your C: drive.
Some explanation:
- For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock Rom then you need to have QK1 Modem/BL.
- On Custom Roms doesn't matter. You can have any of the latest Modem/BL you want but recommend is the latest QK1 for GT-I9505 or the latest for your variant.

Great Tutorial, thanks @Retrial!
I wanted to ask if you could add some additional hints, e.g. like you did in response to a question of @InTheY2K here:
https://forum.xda-developers.com/showpost.php?p=78100797&postcount=2175
Then I realized, you've already done so. Thanks again!
But I've got some additional questions:
In step 4 you describe how to clean external sd. In step 5 you advise to clean internal storage. But if you wipe internal storage, all personal data (e.g. downloaded files, music etc) is lost. Wouldn't it be sufficient to delete the same folders as on external sd card and leave the personal folders?
In step 6 you flash an actual lollipop rom, in step 7 modem and bootloader. I thought an actual stock rom comes with modem and bootloader, so that a separate flash of modem and bootloader would not be neccessary. Am I wrong?
As this is a guide for clean flash, one could not expect to find information about a dirty flash . But I think, this is the best place to at least leave a hint to a place where this information can be found. I remember @Buff99 has one for his roms. @Buff99, @Retrial - wouldn't it be a good idea to add this information directly or as a link to this description?
Additional question: When reading the post with my beloved i9505 and XDA Labs I can't see the colour difference in the asterisks, they all look the same. Perhaps you can replace them with additional ones (meaning *, **, ***) or list your remarks with the corresponding number from your main list (meaning 1), 2) etc.)

pocketrule said:
In step 4 you describe how to clean external sd. In step 5 you advise to clean internal storage. But if you wipe internal storage, all personal data (e.g. downloaded files, music etc) is lost. Wouldn't it be sufficient to delete the same folders as on external sd card and leave the personal folders?
We are doing the best clean install from the scratch so the internal storage must be wiped. You should move all your personal data in your sdcard before you wipe. I will add it as clue to the guide.
In step 6 you flash an actual lollipop rom, in step 7 modem and bootloader. I thought an actual stock rom comes with modem and bootloader, so that a separate flash of modem and bootloader would not be neccessary. Am I wrong?
That's not exactly true. If you have an old modem/bootloader and u flash for example PK2 firmware, you will not have same Modem/BL as ur firmware and then ur WiFi etc will not work. Flashing Stock Rom doesn't change them. You need to separate flash them.
As this is a guide for clean flash, one could not expect to find information about a dirty flash . But I think, this is the best place to at least leave a hint to a place where this information can be found. I remember @Buff99 has one for his roms. @Buff99, @Retrial - wouldn't it be a good idea to add this information directly or as a link to this description?
Hmm yeah this guide is for clean flash, but probably I will say something for dirty flash too.
Additional question: When reading the post with my beloved i9505 and XDA Labs I can't see the colour difference in the asterisks, they all look the same. Perhaps you can replace them with additional ones (meaning *, **, ***) or list your remarks with the corresponding number from your main list (meaning 1), 2) etc.)
Maybe the xda app has some issues. I've added numbers near asterisks, I guess it can help. Thanks for feedback.
Click to expand...
Click to collapse
Thanks mate, I've answered with green color under ur questions.

Up

Update:
Added recommendation for JDC Roms
Added JDC Roms Universe Link
Added JDC TWRP 3.3.0-0 Link
Updated Visual Color Titles for each guide
Updated some Links.
Updated some steps in the guide "clean install not from the scratch"

Update:
Added note that other S4 Models can follow the same steps.
Added Usefull Links Section with quick guides.
Visual changes on Titles

Update:
Added PIT Files section with links at "Usefull Links"
Minor general changes at steps.

Update:
Change the recommended Modem/ Bootloader to the latest QK1.
Added links for recommended Modem/Bootloader for GT-I9505 (latest QK1 links) at "Usefull Links" section.
Added steps with explanation how to flash Modems/Bootloaders at "Usefull Links" section.

Update:
Changed the steps of flashing Modem and Bootloader and added an additional tip.

Will this firmware work with T-Mobile Galaxy S4? (SGH-M919)?

varunkp said:
Will this firmware work with T-Mobile Galaxy S4? (SGH-M919)?
Click to expand...
Click to collapse
No, FQA1 should be the latest for your variant.
However, all the steps in my guide are the same for all variants. You just need to find the latest Firmware/Modem/Bootloader/TWRP for your variant.

Retrial said:
No, FQA1 should be the latest for your variant.
However, all the steps in my guide are the same for all variants. You just need to find the latest Firmware/Modem/Bootloader/TWRP for your variant.
Click to expand...
Click to collapse
Where can I find the latest FQA1 firmware other than SamMobile? The firmware from that website is only available for premium members.
EDIT: I couldn't find the FQA1 firmware in SamMobile. Where else can I find it?

varunkp said:
Where can I find the latest FQA1 firmware other than SamMobile? The firmware from that website is only available for premium members.
EDIT: I couldn't find the FQA1 firmware in SamMobile. Where else can I find it?
Click to expand...
Click to collapse
Try from here.

Retrial said:
Try from here.
Click to expand...
Click to collapse
Thanks. It's now downloading ?

Update:
Updated Firmware Links
Updated TWRP Links
Updated PIT File Link for GT-I9505
I am working to reform-rewrite from the scratch the guides these days. I will unified the guides with adding the latest "stuff", links for all variants, change some steps and more
EDIT: NEW UNIFIED THREAD HERE

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

Gapps installation problem - LineageOS 16 + Oneplus 7 Pro

I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks

Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps

oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...

cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work

liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....

cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.

liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.

Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.

cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?

Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.