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.
Related
Hi, the title says almost all... I can't get past the TWRP screen on both official TWRP and Bluespark one, only solution is flashing Magisk but i have to remove it in order to use some Apps that detect it, any advice...?
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
whizeguy said:
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
Click to expand...
Click to collapse
I need twrp so I can flash magisk if I need it.
And yes, tried to use latest versions of Magisk and, obviously, the Uninstaller, every time I run the Uninstaller it just boot back to twrp.
Anyway I've solved by dirty flashing Pie, now it's working, thanks
Will there be any incompatibility issues with magisk and xposed?
No problem with rooted device on updating, althought you will get unrooted once you update with OTA.
Also, there is no xposed for Pie.
Not yet faced any issues. After OTA update done don't reboot the device. just come to Magisk manager -> install -> select install after OTA option and reboot so that you won't lose root.
Ok, I will stay on oreo for now then. Does Pie run better than Oreo on stock?
Should've read this **** before updating to Pie.
Currently in a bootloop after going from oreo to Pie :'(
What is the latest version of Oreo I should be able to get to with Xposed on OP6?
I faced some issues. After updating to 9.0.2 TWRP and Magisc were gone. So had to reroot and reinstall TWRP via fastboot.
Yes.. this will ALWAYS happen. if you want to keep root when doing OTA you have to do this after install is done, but before reboot!
open magisk app
press downloads
search for TWRP A/B
Install that module ( :::::...:.:..:...::::O NOT REBOOT:::::...:.:..:...::::
Go to main screen of magisk again
press install
press install to inactive slot (after ota)
NOW you can reboot and all will be kept.
If you do it from TWRP (like i prefer, since its just faster)
Flash full rom
flash Twrp (blu_spark latest)
reboot to twrp
flash magisk (latest)
done.
flashing roms will ALWAYS override recovery and boot partition
If I understand you precisely, you say, that this is a question of OTa roms. I am not very keen for OTA. Would TWRP and Magisk stay when flashing a non-OTA rom? If yes, are there non-OTAs of OOS?
No what I ment was using the update function from within android.
You will ALWAYS override recovery and Magisk. Follow the steps above when you flash..
Always like this from twrp
Flash Rom
Flash Recovery
Reboot to twrp
Flash magisk
And u be good...
OK thanks. I did wrongly to accept the automatic update instead of downloading the zip and install it via TWRP.
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
xtartrackR said:
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
Click to expand...
Click to collapse
flash magisk uninstaller, then reinstall magisk v18 and add one module at a time to understand which one causes bootloop
It worked. Thank you!
Just a heads up next upgrade: disable all (except ROMs maybe) magisk mods, also disable substratum themes before updates. They can make your phone bootloop or system UI crash. Glad it works fine now
For me, flashing magisk uninstall and reinstalling v18 still didn't work. I had to install beta version 17.3 after flashing the uninstall, then I installed magisk manager when it successfully booted and finally updated to v18 through the manager. Not sure why v18 wouldn't work even after flashing magisk uninstall, but 17.3 worked.
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Sepero said:
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Click to expand...
Click to collapse
Have you tried magisk uninstaller and fresh start without any module? In my case one of my custom made module was causing problem because i didn't update it to latest template. Try one module at a time to find the culprit.
You need to disable all magisk modules before doing system update, otherwise it goes in auto shutdown and then you need to flash magisk uninstaller and then re-flash magisk
And remember to remove pin/password lock too
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Mord0rr said:
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Click to expand...
Click to collapse
Format DATA from TWRP then boot to system once and when it's ready you can reboot to twrp to install magisk if you want
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?
Hi to everyone. I have a european version of the op7 pro. The device produces an issue when using android auto, which I use daily (the bottom bar is rarely responsive to my touches whereas the rest of android auto works fine). So I wanted to try a custom ROM and see if the problem persists.
I tried multiple roms like havoc, aosip and lineage following the respective guides of installation, but regardless of the ROM, I always get stuck at the startup animation when I first try to reboot to system after installing twrp, magisk, gapps etc.
The only rom that seems to work is any version of OOS.
Any help would be greatly appreciated!
Exact what steps you do when installing a custom ROM?
U need to explain how you flash those OS; from my experience on OP6 -> flashing a third party rom need to update it' firmware to match the rom u try to flash, or else it cannot go into system definitely!
Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
What oos do I flash? Would you mind linking me to it?:good:
Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
Latest android 10 stable rom available for your phone.
pranacrockz said:
Use international version instead of European. This mostly solves the issue.
Also steps should be.
Flash oos
Flash twrp
Reboot recovery
Flash oos
Flash twrp
Reboot recovery
Format data
Flash rom
Flash twrp
Flash gapps (if required)
Flash magisk(if needed)
Flash dm verity (if needed)
Reboot system
Click to expand...
Click to collapse
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.
c3drik 67 said:
Latest android 10 stable rom available for your phone.
Click to expand...
Click to collapse
Is that the same as going back to stock with the MSM tool?
Like this one: https://androidfilehost.com/?fid=4349826312261732239
poulidis said:
Steps :
Unlock bootloader
Boot twrp
Flash twrp
Flash rom
Flash twrp
Reboot to recovery
Once again flash rom
Once again flash twrp
Flash magisk
Flash gapps
Click to expand...
Click to collapse
You must Format internal storage before booting into Custom ROM.
Also, when you flash a Custom Rom, when it's done flashing, reboot once more to recovery and then flash the rest like Gapps, Magisk, etc... (Keep in mind that some custom ROMs require once time boot before flashing Magisk).
Kama45 said:
What oos do I flash? Would you mind linking me to it?:good:
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
GöğüstekiDövme said:
I think this post is useful. But what is dm verity, where to find?
I flash the roms and manage to open them but sensors not working on any custom rom. I create a topic to help but nobody cared.
Click to expand...
Click to collapse
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?
pranacrockz said:
https://otafsg1.h2os.com/patch/amaz...P.26_OTA_026_all_2003222032_6893aca031668.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
Dm Verity is to keep the phone unencrypted. I don't use dm Verity but I never faced such problems.
Which rom u using?
Click to expand...
Click to collapse
Oos O2 Beta 11 now. Back when I try, it was oos beta 10. None of custom roms sensors were not working. Like Pixel exp, havoc, lineage
Sent from my OnePlus7Pro using XDA Labs
Never use beta. Always use stable
pranacrockz said:
Never use beta. Always use stable
Click to expand...
Click to collapse
I'll try one more time later. Thanks.