My Play Store crashes when downloading an app. - One (M7) Q&A, Help & Troubleshooting

Hello people.
I am trying to install a Rom + working Google Play Store for 6 hours now and I have no luck.
I tried CM13, Dirty Unicorn and Slim. None worked.
GApps I tried: OpenGapps 6.0 Pico, Banks Dynamic, DU Gapps Black. All for 6.x.x
I am using TWRP 2.8.7.0 .
Now when I flash the GApps, the old Play Store is installed, which doesn't have Pokemon Go yet.
When I restart my phone, it updates(?) somehow and I can see Pokemon Go.
Now after this update, I am unable to install any App.
It is really frustrating for me.
Procedure I follow in TWRP:
1. Wipe Cache/System/Data
2. Choose the Rom + add more zips -> and than the GApps.
3. Wipe Dalvik
4. Reboot.
I would hope for help guys!

Downgraded to 5.1 (SkyDragon 8.0) and it works there. It is a Marshmallow problem as it happened on ViperOne 9.0.0 as well for me.

Related

[Q] cyanogenmod gapps won't install

Hello, last night I decided to install cyanogenmod 12 on my phone. I had it and the gapps package working, and I decided I wanted to install SuperSU. After I did so, the play store, and google play services were not working on my phone. I tried reflashing both cm12 and the gapps but they are still not working, and claims my device is unsupported. What should I do?
I will provide any additional details as needed.
Thank you.
CM 12 is already rooted so you don't need to flash SuperSU.
You can wipe your system etc. and flash the Rom & Gapps again.

CM13 GAPPS problem XT1068

Hi
after flashing the open gapps (open_gapps-arm-6.0-pico-20160723 or open_gapps-arm-6.0-aroma-20160723) I got this:
"Unfortunately, Setup Wizard has stopped"" application crashed message again and again
but after flashing CM13 again (maybe i forgot to wipe data) CM13 work good but with google now laucher :/
to flash I use TWRP (newest version)
Is there any possibility to have google play store but without google now on CM13?
EDIT: Never mind, after seeing this error wipe data + flash CM13 but without installing GAPPS i restoring option from previous device make it working with gapps (I don't know why gapps are installed but they are and they work so it's ok to me )

[SOLVED]Audio&playback Problem

Hi i need some fix with my device (Oneplus 3T).
My mic,Loudspeaker,earpice,hedphone jack not work since i upgrade from marshmallow to nougat(oos4.5.1). Also i got my screen flickering on recovery mode.
I was try to downgrade and still no luck with that. Then i try to upgrade to oos 5.0.6 i have problem Automatic Factory Reset when first setup again and again.
And now i back in oos 4.5.1 with the same problem.
Things i have done:
- Factory reset
- Flash with unbrick tools and try flash another oos version
- install custom rom (but getting error in oreo rom)
- Flash any fix
- Clean my loudspeaker,mic,jack
I attach some problem when i play some video on youtube. And some video with my problem device:
Problem with mic&etc:
.
Problem when upgrade:
Can anyone help me to out from that ****ty problems? I will appreciate your respons:good:
For OOS try following this guide:
https://downloads.oneplus.com/oneplus-3t/oneplus_3t_oxygenos_5.0.6/
Flashing the full ROM like this will be better than OTA from earlier versions. (Not sure if you've tried this method..?)
For Custom ROM:
Don't know what the error is you mentioned, but make sure you are using latest Official versions of TWRP and Firmware before flashing the ROM. And make sure you are using the right Gapps for the ROM. For any Oreo ROM that would be OpenGapps 8.1 ARM64 (I recommend Pico package)
Firmware:
https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
TWRP:
https://dl.twrp.me/oneplus3/twrp-3.2.3-0-oneplus3.img.html
ROM:
I recommend RR Oreo:
https://sourceforge.net/projects/re...O-v6.2.1-20181003-oneplus3-Final.zip/download
Opengapps:
https://opengapps.org/
Update/Install TWRP first.
Reboot Recovery
Format Partitions from Wipe/Advanced menu
Reboot Recovery
Copy zips from PC to Internal Storage
Install Firmware/ROM/Gapps (Queue zips and flash together)
Wipe Cache/Dalvik when prompted and Reboot phone
Setup phone.
Let us know if you run into any problems with anything.
Dirk said:
For OOS try following this guide:
https://downloads.oneplus.com/oneplus-3t/oneplus_3t_oxygenos_5.0.6/
Flashing the full ROM like this will be better than OTA from earlier versions. (Not sure if you've tried this method..?)
For Custom ROM:
Don't know what the error is you mentioned, but make sure you are using latest Official versions of TWRP and Firmware before flashing the ROM. And make sure you are using the right Gapps for the ROM. For any Oreo ROM that would be OpenGapps 8.1 ARM64 (I recommend Pico package)
Firmware:
https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
TWRP:
https://dl.twrp.me/oneplus3/twrp-3.2.3-0-oneplus3.img.html
ROM:
I recommend RR Oreo:
https://sourceforge.net/projects/re...O-v6.2.1-20181003-oneplus3-Final.zip/download
Opengapps:
https://opengapps.org/
Update/Install TWRP first.
Reboot Recovery
Format Partitions from Wipe/Advanced menu
Reboot Recovery
Copy zips from PC to Internal Storage
Install Firmware/ROM/Gapps (Queue zips and flash together)
Wipe Cache/Dalvik when prompted and Reboot phone
Setup phone.
Let us know if you run into any problems with anything.
Click to expand...
Click to collapse
Sure i have try this 5 times with different way, via adb sideload, ota, recovery but it not working for me.
I dont understand wich firmware to flash this RR. Because previously i had to try flash havoc os but get mdtp corrupted and my device cannot booting.
Problem has been fixed.
I tried to change the audio ic wich is the ic series: TFA9890A.
If anyone have same problem you can check this one to fix this.

Install TWRP, Root, LineageOS and Immensity Kernel from Stock?

Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?

[GUIDE] March 2021 AOSP 6.0.1 Marshmallow for Tab S

Hi everyone
I recently tried installing AOSP/CM ROMs on SM-T800. Lineage 14.1 (and all derivatives) have issue with Netflix - it will stop playing after 1-5 min with cryptic error. Youtube Vanced will crash or freeze from time to time.
Clearly bad ROMs.
So I found this https://forum.xda-developers.com/t/...t-5-2016-t700-t705-t800-t805.3219759/page-247
Cannot direct link - but it has 2 AOSP 6.0.1 downloads.
ROM itself works, but when I tried OpenGapps - weird freezes/errors started.
So here are steps to make it work:
Wipe data/system/cache, Flash AOSP 6.0.1 only in TWRP recovery, reboot, make sure it works.
Reboot into recovery, flash opengapps nano - I found some old ARM openGapps6nano from 2016 by googling. You can try newer, but not sure if it will work.
Reboot couple of times - you will see a lot of force closes.
Reboot into recovery and clean dalvik, data, cache. Keep system. Reboot.
Everything worked since for me - Netflix, Youtube Vanced, Amazon Prime Video.

Categories

Resources