open_gapps-arm64-9.0-nano-20200123.zip can not boot into system on my xiaomi mi5(omni 9)
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
Hi,
I just tried installing the 1/16 Android 10 Pico BETA GApps to my HTC One M9 running LineageOS 17.1, and I get an incompatible error. I'm using a test version of TWRP from @Captain_Throwback that I'm told "no longer sets ANDROID_ROOT to /system_root" and that's likely the problem? I'm attaching the recovery log from TWRP for reference. Is there any way for me to install the zip?
TWP
I just tried installing the 1/16 Android 10 Pico BETA GApps to my HTC One M9 running LineageOS 17.1, and I get an incompatible error. I'm using a test version of TWRP from @Captain_Throwback that I'm told "no longer sets ANDROID_ROOT to /system_root" and that's likely the problem? I'm attaching the recovery log from TWRP for reference. Is there any way for me to install the zip?
TWP
Hi. Yes, indeed, that is a problem for us. It's unfortunate that folks at TWRP decided to change this behavior again (I believe it's the third time they do this), and since we relied on this variable, it seems that we can't anymore.
We've discussed this change already with @osm0sis (since our mounting scripts are based on his solution for the AnyKernel 3) and if that change will be accepted and merged, we'll adapt the scripts accordingly.
For now the only solution for you will be to use an older version of the recovery.
Sent from my OnePlus7Pro using XDA Labs
curiousrom
Recognized Contributor
Boot Fail - Open GApps Android 9.0 Builds 2020-01-22 & 23
What are the exact names of the LineageOS & Open GApps files that you flashed & failed to boot please?
Guys, how did you flash Open GApps? By sideloading or copying to the device & flashing from there with a Recovery?
Do any of you still have the open_gapps_debug_logs.tar.gz from the failed install?
@Nezorflame - 2 other LineageOS users reported failed to boot with Open GApps Android 9.0 builds 2020-01-22 & 23 here in the LineageOS subreddit.
There are very few commits in https://github.com/opengapps/opengapps/commits/master made on Jan 21, 2020.
Could the fail to boot problem be related to @ipdev's Copy logs to sdcard/ when using sideload commit?
***
What are the exact names of the LineageOS & Open GApps files that you flashed & failed to boot please?
Guys, how did you flash Open GApps? By sideloading or copying to the device & flashing from there with a Recovery?
Do any of you still have the open_gapps_debug_logs.tar.gz from the failed install?
@Nezorflame - 2 other LineageOS users reported failed to boot with Open GApps Android 9.0 builds 2020-01-22 & 23 here in the LineageOS subreddit.
There are very few commits in https://github.com/opengapps/opengapps/commits/master made on Jan 21, 2020.
Could the fail to boot problem be related to @ipdev's Copy logs to sdcard/ when using sideload commit?
***
Guys, how did you flash Open GApps? By sideloading or copying to the device & flashing from there with a Recovery?
YES!
Do any of you still have the open_gapps_debug_logs.tar.gz from the failed install?
no,How can i do to catch logs?
Last edited:
curiousrom
Recognized Contributor
Where to Find the Open GApps Installation Logs
From Pull request - Copy logs to sdcard/ when using sideload #794:
So starting with build 2020-01-22 or newer, if you sideload the logs should be in the internal sdcard or /data/media/0/.
If you copy or move the open_gapps...zip to the device & flash from there using the recovery the Open GApps installation log will be created in the same directory as the open_gapps...zip.
***
@Nezorflame - Why not simplify for users & the Wiki and always save the logs to /data/media/0/?
***
From Pull request - Copy logs to sdcard/ when using sideload #794:
So starting with build 2020-01-22 or newer, if you sideload the logs should be in the internal sdcard or /data/media/0/.
If you copy or move the open_gapps...zip to the device & flash from there using the recovery the Open GApps installation log will be created in the same directory as the open_gapps...zip.
***
@Nezorflame - Why not simplify for users & the Wiki and always save the logs to /data/media/0/?
***
Last edited:
I have had users reporting that if they choose to install the TWRP app (prompted before reboot to system) that they get a boot loop when installing opengapps.
Are you buy any chance doing that?
My advice is, you don't need the TWRP app so don't install it.
I flashed by copying open_gapps-arm64-9.0-nano-20200123.zip to the device then flashing from TWRP (which I've been doing since the first release of official Lineage for the Mi A1 without issue). Unfortunately I don't have a log as it's my daily driver and I needed to get it back up.
Just to clarify, OpenGapps appeared to flash without issue at all - it was when booting I had the issue: the Lineage boot animation would just loop and loop for a few minutes before it rebooted back into Lineage recovery (each flash overwrites TWRP and I wait until a successful first boot before reflashing it) saying there was a problem with my device and I needed to factory reset. This was with lineage-16.0-20200122-nightly-tissot-signed. The same thing happened with official Lineage builds from 17th, 18th, 20th and 21st as well (initially I thought it was a Lineage issue so I tried rolling back for a few versions before coming here and realising others seemed to be having issues with Gapps).
Once I used an older version of OpenGapps (open_gapps-arm64-9.0-nano-20200117) instead, it was fine.
Could you post a logcat while the device is booting. It's a permission issue once again...
The bootloop some of you are seeing seems to be an issue with recent Opengapps when one has the TWRP app installed - see opengapps forum: https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/page648
I don't really think that is an issue because few of my users of Lineage 16.0 builds with both OrangeFox and unofficial TWRP had bootloop issues. I guarantee that is once again a permission issue which hasn't been solved for a week. If someone can please flash the latest build and upload a logcat so we can fix it for future builds it would be great.
EDIT:
@Nezorflame can we get some info on this one?
Last edited:
I was trying to flash my OnePlus One with LineageOS 16.0(lineage-16.0-20200123-nightly-bacon-signed) and it seems the prebuilt opengapps(20200124) prevent the OS from ever booting. It gets stuck in the boot animation for 10 minutes then reboots into TWRP again (v3.3.1-0).
Everything is clean, freshly unlocked bootloader, wipe/format everything, clean sideload of both together as instructed by lineage. No TWRP app or anything else allowed. Tried micro and nano.
Everything is clean, freshly unlocked bootloader, wipe/format everything, clean sideload of both together as instructed by lineage. No TWRP app or anything else allowed. Tried micro and nano.
Please post logcat. Known issue but no logs from anyone.
Easiest way is to flash Lineage, boot, enable ADB from system and then flash opengapps and collect logcat from PC.
On January 18, I installed a bacon device with TWRP 3.1.1 (app not installed), reboot to recovery and then installed lineage 16 and nano gapps, both built on January 17 via TWRP, and everything worked fine.
Last edited:
Ooof.... I kinda lied a bit. Not my phone, a friend's phone (even if I have the same one - I flashed mine a few months ago). Came over for a root-party. Except its now getting late over here and I have to go home. So I can't collect logs.
Btw, do you mean go against the instructions which specify to flash lineage and gapps before booting lineage first? As in flash lineage, boot, enable adb, flash gapps?
How do I post a logcat? I am using a Samsung Galaxy Tab S2 T810. LinageOS 16. I'll do anything I can to help as I am not in dire need of my device to work at this time.
Just adding my 2 cents...
I got gapps installed by using an older version on my Oneplus 3T. I was installing via TWRP and did NOT let TWRP try to install its app afterwards. I simply flashed the ROM, flashed the old gapps, and finally was able to get into the OS.
I was using:
lineage-16.0-20200123-nightly-oneplus3-signed.zip
open_gapps-arm64-9.0-pico-20200117.zip
I got gapps installed by using an older version on my Oneplus 3T. I was installing via TWRP and did NOT let TWRP try to install its app afterwards. I simply flashed the ROM, flashed the old gapps, and finally was able to get into the OS.
I was using:
lineage-16.0-20200123-nightly-oneplus3-signed.zip
open_gapps-arm64-9.0-pico-20200117.zip
Easiest way is to do the following
1. Download and extract platform tools from Google's platform tools
2. Go to the folder where platform tools (adb.exe) is extracted, hold shift and select Open PowerShell here or Open Command Prompt here whichever available
3. Flash Lineage 16.0 without OpenGapps and let it boot
4. Enable Developer Settings (by pressing build number 5 times) and enable ADB
5. Connect your phone to PC and type adb devices. Make sure the device is recognized.
6. Reboot to twrp or whichever recovery you use, flash OpenGapps and reboot the phone
7. Once it gets stuck on bootloop in the command window you opened in step 2, type adb logcat -d > logcat.txt
8. Upload the file here
---------- Post added at 00:51 ---------- Previous post was at 00:43 ----------
Apparently from 20200117 onward there is an issue. One log would mean a lot for me and the OpenGapps team since I have no access to my device currently to check
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.4
MindTheGApps has Android 14 builds. I'm using it on an A14 LineageOS gsi ROM right now. The only problem with MTG, is that it isnt customizable. The zips are take it or leave it, you're installing all the components in the zip, or not at all. There is only 1 version (all the zips are the same, excluding hardware/Android version-specific details) which is essentially 1 size fits all. But most other GApps providers have customization in that you can choose which parts you do/don't want. But MTG is also very minimal, it just includes the core GApps components and little to no bloat. So it's not a big deal to me. I don't need all the extra stuff, just Play Services/Play Store/calendar and contacts syncing, not much else.
MTG for Android 14:
2
What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there. -
837Questions? Use Q&A!
Please read the FAQ before reporting any bugs or errors!
If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without a logcat, your post will be ignored by the developers!
Not because we are evil, but because the same questions keep popping up over and over again and too often we get a "X doesn't work, plz fix" without any clue what is happening. We don't have telepathic connection to your device and all the time unnecessarily wasted on this can't be spend on development of Open GApps itself.
The Latest builds of Open GApps for Android can easily be downloaded from the:
- Open GApps App
- FAQ @ GitHub
- Package comparison @ GitHub
- Advanced Features and Options @ GitHub
- Development Repository @ GitHub
I work on this project for FREE and putting in a lot of hours into it. While not mandatory, donations encourage me to continue to further pursue this project and I'd deeply appreciate them, if you feel generous.
Donate to The Open GApps Project
Are you a ROM developer and want to hotlink to the latest Open GApps package? Then check this wiki entry for details.
Please don't publicly mirror the prebuilt packages without explicit consent of @MastahF, to ensure that users will always be directed to the very latest version and the source code of the project.
About The Open GApps Project
Open GApps is a Google Apps package completely developed by writing buildscripts which allow for the automated creation of new up-to-date packages automatically.
The development process is completely open-source (GPLv3) and the goal is to have multiple contributors involved, to secure and reinforce the sustainability of Open GApps development.
Builds are generated every (European) night automatically (if there are any changes) and uploaded to GitHub.
Official AROMA Open GApps package is developed in collaboration with long-time LP-AROMA-developer @raulx222 and has a dedicated XDA thread
For any questions about the AROMA installer development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.
Official Open GApps For Stock support is developed in collaboration with @Rapper_skull and has a dedicated XDA thread
For any questions about the GApps for Stock development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.
The x86 package branch of the package is focused on Zenfone support and is maintained by @deadman96385 of the famous Zenfone GApps packages and has its own topic for x86 related questions
For those that cook their own ROM, an AOSP-build mechanism for Open GApps has been developed by @blystad and can be found at GitHub, remember that you should not bundle any pre-packaged Google Apps with any ROMs you want to distribute further though.
To gather all the various APKs that are necessary for the packages our master of the APK Universe @MNBooZe has written a tool called APKCrawler that scrape these from the internet, e.g. from APKMirror, it can be found at GitHub too.
Characteristic of Open GApps:
Some highlights about the characteristics of the Open GApps packages:- All platforms and and all Android versions are supported
- DPI-optimized support for all Google packages (unlike other GApps)
- Frequently updated Google Apps: The pre-built OpenGApps.org packages are updated every (European) night (if there are any updated Google Apps available)
- Strong compression, allowing for relatively small downloads of even the most complete packages
- Automatic backup: It is not necessary to re-flash Google Apps when you flash a ROM update. Most ROMs support this (addon.d) function
- The installer checks your device’s capabilities, like the system partition size. It will notify you, before making any changes, if it finds any problems
- Several package variations, from a Google Super Package (includes all applications that ever shipped on a Google device), to a Stock package that equals the set of applications found on the most current and complete Nexus, to smaller, minimalist packages and an AROMA package that allows graphically selection of what to install
- A special ‘for Stock ROM’ installation mode that allows to update the Google Apps on Stock ROMs that conform to the original Google Nexus filesystem structure
- All package installations can be customized to your individual preferences using our Advanced Features and Options
The idea behind this project:
I believe a big source of the problem for many GApps packages to stay up-to-date (or not be forfeited) is the lack of time for developers to do labour-intensive repetive every time a new google-app apk is released.
That is why I have taken it upto myself to write some Linux shell scripts to automate the packaging and to share these efforts with the world with the goal to create a team to continue this package together under the name Open GApps.
This project should not be managed by a person, but by a team, so volunteers willing to help are more than welcome!
- Team management and projectleader: @[COLOR="blue"]MastahF[/COLOR]
- Writing of the scripts: @[COLOR="blue"]MastahF[/COLOR] & @[COLOR="blue"]Rapper_skull[/COLOR] or check the team on GitHub and many other contributors
- Updating GApp sources: @[COLOR="blue"]MNBooZe[/COLOR] & @[COLOR="blue"]DJAlik[/COLOR] & @[COLOR="blue"]bgiesing[/COLOR] & @[COLOR="blue"]mc1100[/COLOR] & @[COLOR="blue"]deadman96385[/COLOR] or check the team on GitHub
- AROMA installer: @[COLOR="blue"]raulx222[/COLOR] using LibAroma
- Custom compiled commandline tools: @[COLOR="blue"]YashdSaraf[/COLOR]
- Website: @[COLOR="blue"]raulx222[/COLOR] & @[COLOR="blue"]MastahF[/COLOR] & signalv hosted by GitHub and created with Material Design Lite and JQuery
- Artwork: @[COLOR="blue"]Yeti12[/COLOR]: Yeti-Designs website
- Documentation: @[COLOR="blue"]Trafalgar-Square[/COLOR] and @[COLOR="blue"]MastahF[/COLOR] and many other contributors.
Open GApps installer uses open source third-party tools, like busybox and xzdec, compiled by @YashdSaraf; See his busybox thread for more info.
Open GApps is originally based on the now discontinued PA GApps package of @TKruzze and @osm0sis36
I run arm/arm64 builds of pico, nano and stock for testing.
Once they are tested a bit and seem stable, I upload them to MediaFire.
MediaFire - Link
Android 12 builds are in the SDK31 folder.
The 20211218 builds include some permission updates.
---
Last week I ran SDK32 builds to test on LineageOS.
LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.
LineageOS Gerrit - Topic 12L - Link
Edit: I just checked and see they decided to bump up to 19.1 a few days ago.
Note:
Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.
The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0
The boot image was SDK31 on the 12L preview release.
The only way to determine if you are running 12 or 12L is by checking the SDK level.
SDK31 = Android 12
SDK32 = Android 12L
The initial 12L OpenGApps test builds were blind builds and untested.
I did not have a device/rom to test them on.
I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.
Since it is a tablet, it utilized the large screen layout of SDK32.
The 12L pico and nano builds seem to be safe.
The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.
Unless you are using a gapps config script to customize the install.
Android 12L (SDK32) test builds are currently on gDrive.
gDrive - Link
Everyone is welcome to give them a try.
Cheers all.
Edit:
See additional posts.
Post # 7,316
Post # 7,31925Tomorrow there will be 7.0 builds
Small update concerning Nougat: everything is almost in place, only HotWord Enrollment is not de-odexable yet.
So tomorrow there will be 7.0 builds, ready for when the first source and custom ROMs will drop.
Of course beta-quality because they cannot be tested yet, so be careful.
There are some minor changes, Google changed their keyboard stuff, so there will be no swypelibs possible anymore.
Google VR Services is backported to all Android versions (so all the way from 4.4 to 6.0) but ofc not yet known how well it will work.
Also there are some new 7.0 core apps for Google's Shared Android Services (com.google.android.ext.shared; com.google.android.ext.services)
Trusted Face's unlock has also some major changes, it seems the pittpatt suff is not necessary anymore for 7.0.
That's it for now25For those who hadn't spotted it yet: we can celebrate 1 year of Open GApps
http://opengapps.org/blog/post/2016/05/09/open-gapps-first-anniversary/23Sorry to drop in but needed to clean up some unnecessary posts that were burying more legitimate posts to the thread.
Going into someone's thread and demanding they make you something is not only just plain rude, it goes against everything XDA is about. Numerous people suggested a way for you to remove the gapps and you chose to ignore them. The dev isn't going to make an uninstaller just for you. You could also always use root explorer and remove the apps that way too. Anywho, there won't be an uninstaller made so no need to continue this conversation.
Thread Cleaned
New posts
-
-
General Android 15 Beta 1 AP31.240322.018 - "Vanilla Ice Cream" - Pixel 7 Pro [Cheetah]- Latest: roirraW "edor" ehT
