Database Info

How to Install Gapps on LOS roms

Ive been trying every way I can think of to install an LOS rom with Gapps. It seems everytime I try to install gapps it gives me a play store or services crash. That or i cannot boot into the Rom. I was curious if anyone had a specific package of gapps that always worked, or if there is a firmware of OOS you needed to be on to be able to use custom roms. Im just a bit stuck because I have been able to use Havoc in the past, but now I cannot even get that to boot (using the procedure that is in every thread).

itsdan313 said:
Ive been trying every way I can think of to install an LOS rom with Gapps. It seems everytime I try to install gapps it gives me a play store or services crash. That or i cannot boot into the Rom. I was curious if anyone had a specific package of gapps that always worked, or if there is a firmware of OOS you needed to be on to be able to use custom roms. Im just a bit stuck because I have been able to use Havoc in the past, but now I cannot even get that to boot (using the procedure that is in every thread).
Click to expand...
Click to collapse
Wipe
Flash rom
Flash twrp
Reboot into twrp (important.....)
Flash gapps (Pico should be the largest)
Flash magisk if you are using it.
If it won't boot still.....
Wipe
Flash rom
Flash twrp
Reboot to twrp(its still important..)
Flash rom
Flash twrp
Reboot to twrp (yes.. 2nd time..)
Flash gapps (Pico still recommended
Flash magisk if u want root
Reboot and all should be fine..
If 1st doesn't work, then something has happened to a/b partition, should get fixed by 2nd

now it boots but hangs at "checking for updates"

itsdan313 said:
now it boots but hangs at "checking for updates"
Click to expand...
Click to collapse
gapps issue most likley OR magisk... what version did you download? could have gotten a corrupted zip
try this first: Flash magisk uninstaller, see if it boots.
if it works, proceed with the setup. after that, reboot to recovery and flash latest magisk (17.1 i believe is latest) see if it works.
https://opengapps.org/
ARM64, 8.1, pico
2 September 2018
Size: 109.04 MiB
if it still giving u issues then dont flash magisk. flash magisk after initial setup.

Has anyone successfully used Magisk to patch boot.img w build number PPR2.181005.003?

It just crashes for me every time I give it the boot.img from the walleye-ppr2.181005.003-factory-8613da61.zip (latest build of Android 9). I've tried the Canary build of Magisk and that didn't help.

I'm using it with magisk 17.2, no problems

Could you possibly post the patched boot.img?

... why not just flash the installer from twrp?

i have the same issue. not working for me too. crashes on bootup after flashing the patched boot.
---------- Post added at 11:54 PM ---------- Previous post was at 11:24 PM ----------
I tried the flash installed w/twrp and that failed as well.
Here's the patched boot image from magisk manager https://drive.google.com/file/d/1oCdvZehqikFy6STZIFe5efPFVskmRZGT/view?usp=sharing

Got it to work with the Nov security update. (PQ1A.181105.017.A1)
Downloaded the lasted beta and uninstaller from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
fastboot'ed into TWRP.
Ran the uninstaller zip
ran the magisk 17.3 zip
booted up fine afterwards.

Were you able to actually obtain root access? I was able to install 17.3 but the root access prompt never comes up.

I am also facing the same issue with Nov build , 17.1 , 17.2 , 17.3 none of them are working so far

yup. have root access

I"m running into the same issue. I have tried 17.3 both stable and beta without being able to successfully root. It appears the patched img is being built correctly, but no joy on rooting.. Any suggestions on this?

I just want to note that for me this turned out to be how I was selecting the boot.img to patch. I was finding the file in Root Explorer -- apparently if you back out and use the native file picker it works fine.

Wiped and back to stock recovery... Sigh.

Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.

yogra1921 said:
Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.
Click to expand...
Click to collapse
I had the same thing happen to me. I missed the part where I flash TWRP right after the OTA. That probably triggered the factory reset

So instead of rebooting, I should do a "fastboot boot IMAGE" and then install the bluspark twrp zip from inside that one? I guess I can boot up to TWRP and install Magisk as well after this while I'm at it?

Are you flashing from twrp?
If so,flash ROM zip
Flash twrp zip
Reboot to twrp
Flash magisk
Done.
If ur doing it from Android
Install ROM,when it asks you to reboot, DON'T
go to magisk app
Go to modules
Search for a/b twrp (you should only find one module)
Install it ,don't reboot
Go to main magisk screen
Press install,install, install to inactive slot (after OTA) after it's done you can REBOOT.
The module keeps your twrp
Flashing magisk to inactive slot will root the update you just installed

I was installing the OTA normally, without TWRP. It worked just fine last time.

You shouldn't install any OTA if you are rooted.
Only full roms.
yogra1921 said:
I was installing the OTA normally, without TWRP. It worked just fine last time.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

I understand. But it doesn't change the fact that it worked like a charm last time. I just assumed there might be a general way.

RASTAVIPER said:
You shouldn't install any OTA if you are rooted.
Only full roms.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
On OOS it knows if you are rooted and will download full ROM,so it's fine if you install a/b twrp magisk module after (keeps twrp) and then install magisk to inactive slot .
What happened here is he probably forgot to install twrp and magisk probably got to the wrong slot, hence the wipe

Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?

yogra1921 said:
Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?
Click to expand...
Click to collapse
no.... you do what i wrote like 3 posts up.. DO NOT REBOOT!!
After every single rom flash, TWRP, from android or fastboot or whatever way you install any rom TWRP will be replaced, aswell as boot.img (magisk is there)
OTA
DONT REBOOOOOOTT!!!
go to magisk, search for A/B twrp module, install it
DONT REBOOT
Go to main screen of magisk
install, install, install to inactive slot.
done..
your way will wipe TWRP.
From twrp:
Flash rom zip
flash twrp
reboot to twrp
flash magisk
done

Oh yeah. I completely forgot about that the TWRP retention script exists. Perfect. This is exactly what I did last time. Thanks!

Losing TWRP and Magisk after update

I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?

Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk

So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.

Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.

MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.

I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot

Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K

I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running

Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?

Root broken after forced update on t-mobile.

So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!

Honestly not sure how you got the update with twrp installed it always failed for me. Had to restore original boot.img to install.
But the update relocks the bootloader ... At least it did for me so hopefully you still have your unlock bin. Just unlock the bootloader and root as usual.
Unfortunately unlocking wipes.
If your bootloader didn't relock just root per the guide

nujackk said:
If your bootloader didn't relock just root per the guide
Click to expand...
Click to collapse
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
StrawHatZakk said:
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
Click to expand...
Click to collapse
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
StrawHatZakk said:
Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp.
Click to expand...
Click to collapse
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.

StrawHatZakk said:
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Click to expand...
Click to collapse
Just reflash twrp/magisk with powershell
Go to settings developer mode turn off auto install updates.

redpoint73 said:
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
Click to expand...
Click to collapse
I took my sweet time trying it but wanted to get root back as I just moved and won't have internet for a while. Everything seemingly went fine, got TWRP going then after installing Magisk it would just hang at the t-mobile screen indefinitely. Attempted to do a restore with TWRP and must have hit a leftover restore from the previous android version now the only thing it does is boot to the fast boot section. Might make a new topic but I'm searching everywhere for a fix, can't seem to get this MSM tool thing to recognize it... thinking I might just be boned. If you know of any fixes let me know lol.