Nikgapps Files

[Fernando Capelle]

second :
start the Pi3 with Emteria.OS, when it's start plug your usb.
open the usb via the upper side of you screen.
press a long time on the gapps.zip file and copy past to Download folder.
eject your usb.

third :
Use the Shutdown preinstalled app and go to RECOVERY.
in the recovery menu , use "install" an go to the download folder. select your gapps.zip file.
and clic on install from zip.
select reboot after install.
wait and

I wouldn't recommend installing anything but the pico package, as most of the apps have crazy memory requirements, which can be hardly satisfied by RPi3. In any case, after the installation the system will do some optimizations in the background. Sometimes it takes up to 30 or 60 minutes until everything is set (pico package).

I installed Emteria.os on my RPi3 successfully. As I wanted to install GApps, I followed the instructions above but, when I rebooted after installing from recovery menu, the RPi didn't make it past the Emteria loading screen. It's been stuck there for 20minutes or so now with just the animation running and activity light (small green LED) on the Pi flashing irregularly.

@Igor,
How to use gapps-config.txt?
It should be renamed to gapps-config?
I didn't install gapps yet since i upgraded to Emteria v0.5.5
Is it possible to exclude everything except Google Play services?

@roxette, this is exactly what the file does. It prevents people from installing tons of huge applications. There is nothing to do for you - in our tests the OpenGApps installer detects this file automatically and applies the configuration. Here is the documentation: -Features-and-Options

@Smitty, we have no clue why this is happening. As I have mentioned in another thread, emteria.OS and recovery are using the same kernel to boot. Any chance you can provide us your logs ( _Serial_Connection)?

I can confirm that I followed the OpenGApps installation instructions that Jonas gave and it worked. I did try downloading GApps through emteriaOS as Kalkov suggested but the download failed multiple times. Just as Kalkov mentions, there is a period after starting the play store for the first time that everything is VERY slow but after a period of about 5 min. after the first reboot.

I installed fine today using the gapps.sh from github and pico however playstore always crashes. Having said that it crashes on nearly every android image I tried. keeps going in circles saying it has stopped working.

Hi to all,
as for today the Recovery menu of the latest Emteria for RPI4 doesn't have the "Install" option anymore.
Please, can someone give me some advice on what to do to install GApps?
Thanks a lot!

I have successfully used ADB over "Ethernet" (although, it's really WiFi), but I am unable to sideload any zip files. I can do a normal adb install of an .apk, but to sideload you need to be in the recovery menu, when you enter that menu, you can no longer connect/talk to the Pi through ADB (I have tried Wifi, Direct USB connection and Ethernet cable)

In other words, we need someone outside of Emteria to lay this out. Is there a custom recovery available for Emteria that will get around these limitations? Or what version of Emteria should I install so I can actually do something with GApps?

There once was a time in the Android rooting scene where we couldn't rely on using a custom recovery for all of our modding needs. Manual file flashing was very popular in the early days of Android before custom recoveries started taking over. With the rise of TWRP, it seemed like there was almost no need for manual file flashers; however, they appear to be making a welcomed return in a big way.

Well-known custom kernel developer Francisco Franco brought the manual file flashing feature back when he updated his kernel app. You might be thinking, why is this big news? Well, the apps we previously relied on for manual file flashing, such a Flashify, had been abandoned for quite some time now. Phones have changed a lot over the years, especially when it comes to rooting and modding.

Many of the top root-friendly Android phones use the A/B partition layout now, which the older file flashing apps do not support. This makes the old apps completely useless for today's devices. I'll be sharing two newer apps you can use to get your manual file flashing game on without needing to have TWRP installed. They might occasionally end up being a lifesaver for you in some cases, too.

If you like to install custom kernels for modding your device, chances are you may have come across the ElementalX kernel. The developer behind EX Kernel Manager, flar2, is a very well-known developer in the rooting and modding scene. You can trust that his work is rock solid. Not only do you get a manual file flasher, but you get a complete package for all things related to custom kernels.

To get started flashing your files with EX Kernel Manager, you only need to do a few quick actions. Open the app to the main screen, tap the "Flash" button, navigate to the folder where your mod files are stored, then tap the file you want to install. You'll see the text box at the bottom fill in with the location of the selected file, then you can hit "Flash" to begin.

It will automatically flash the file within a few seconds from here. Let it finish installing, then you can hit the "Reboot" button when you're ready to complete the process. That's all there is to it. You now have a new method of installing TWRP mod files without having to boot into the custom recovery environment!

In the specific example above, where I flashed TWRP, you would avoid doing a reboot until you installed Magisk in the same manner. If you're installing TWRP using this method on an A/B partition device, you need to flash Magisk right after that since it was likely wiped from your system. This will allow you to stay rooted after the reboot, which is ultimately what you'd want to happen.

One of the other big-time custom kernel developers in the Android community, Franco, almost needs no introductions. His name is synonymous with the rooting and modding scene along with flar2. You can certainly trust the Franco Kernel Manager app as a reliable choice. Just like the EX Kernel Manager, you get a manual file flasher and a complete package for managing your custom kernel settings.

To get started flashing your files with Franco Kernel Manager, you only need to do a few quick actions. Open the app to the main screen, tap the menu icon in the lower right corner, then hit the "Flasher" option. Navigate to the folder where your mod files are stored, tap the file you want to install, then hit "Select." This can vary depending on which file manager you're using at the time.

Once you've selected the file, a new message will pop up, reminding you about Magisk. For the most part, you should hit "Just Flash" so you can be in charge of a manual reboot. It'll start flashing the file from here. Hit "Reboot" when you're ready. That's all there is to it. You now have a new method of installing TWRP mod files without having to boot into the custom recovery environment!

In this era of fully-featured custom recoveries, is there a real reason to flash files manually as we did once upon a time? You can never have too many choices, and whether you plan on using this feature a lot or very little, there are quite a few reasons you might want to consider keeping it in your arsenal of root-only apps.

The official Android 10 update is now available on a variety of devices since its launch in August of 2019. However, many still don't have TWRP support at this time. Android 10 changed a lot on the system partition, so it's taking longer than usual to get TWRP working correctly. This might throw some people for a loop since they have relied solely on custom recoveries for their modding needs.

Even Google's Pixel 4 phones are lacking TWRP support on Android 10 at this time, which is why these manual file flashers are more desirable than ever. If you're running Android 10 and your device doesn't have access to TWRP, then pick a manual file flasher and have fun! This is easily the next best choice as a reliable alternative for installing mods without overly complicating things.

One of the challenges we face by relying on a custom recovery, such as TWRP, is that we must wait until the development scene gets it working on each device. Sometimes it can take a while to happen on lesser-known devices, and occasionally official support may not even make it at all in some cases. That's when we begin to see unofficial support popping up to try and fill in the missing pieces.

Still, that's not a guarantee for every single device out there. In comes the manual file flasher, which works universally for pretty much all devices across the board. As such, you can also use the feature as a stop-gap until TWRP support comes to your device if you still prefer using a custom recovery. You pick whichever method works best for you and your modding needs.

If you still plan on using TWRP as your primary way of installing mods, the manual file flasher could supplement your needs in another way. On the devices with an A/B partition, whenever you flash a new system update, it will automatically overwrite your custom recovery with the stock version. If you had a custom kernel or Magisk previously installed, those would also be removed as well.

Let's say you installed a custom kernel and Magisk after a system update while in TWRP. However, you forgot to flash the permanent TWRP installer. You reboot your system and realize that you're unable to get back to TWRP again because the stock recovery took over. You could easily use a manual file flasher to install the permanent version of TWRP right there, no computer necessary. Nice!

c80f0f1006