I recently tried to install a custom ROM on my Android device with the latest version of FlameGApps and ran into some problems (specifically, the device setup app kept crashing and looping on first startup of the device, never allowing me to get to the landing page).
Then I installed the previous version of FlameGApps onto my device (the one I was running before I installed a new version of LineageOS), and it works fine.
I'm just wondering: Is there any consequence to running an old version of FlameGApps? Does this make my device susceptable to security issues that have since been patched, or will all the GApps included in FlameGApps update themselves once the device is set up?
MachineMasher said:
I recently tried to install a custom ROM on my Android device with the latest version of FlameGApps and ran into some problems (specifically, the device setup app kept crashing and looping on first startup of the device, never allowing me to get to the landing page).
Then I installed the previous version of FlameGApps onto my device (the one I was running before I installed a new version of LineageOS), and it works fine.
I'm just wondering: Is there any consequence to running an old version of FlameGApps? Does this make my device susceptable to security issues that have since been patched, or will all the GApps included in FlameGApps update themselves once the device is set up?
Click to expand...
Click to collapse
It may not be a problem with the version that you're using, it might a problem with the size of the Gapps package. Have you tried installing a smaller Gapps package? Your system partition may not be big enough to fit your ROM and the Gapps package that you are using.
Thanks for the reply.
Actually, I'm not asking why the version of FlameGApps I was using had a problem (although your advice is helpful on that too!)
What I'm asking is whether there is any negative consequence to using an old version of GApps - does installing an old version of GApps permanently lock the various google apps to an older version, or will they self update from the play store after first bootup?
Related
Hi guys, I'm new here, I've searched forum similar posts but I couldn't find anything.
I rooted my Nuogat 7.0 device with the last versions of twrp recovery and SuperSu. (The device is unlocked and S-ON)
A couple days ago I decided ti flash LineageOS 14.1 ROM and the super Gapps package. At the beginning all' ok, but I noticed that the HTC sense interface was absent.
So I tried install the last versions of it but it gave me crash problems everytime I tried to interact with it (like when moving apps or installing themes). I Also noticed that the layout is smaller than the one I had before installing lineageOS(app icons are smaller, and apps layout too (this doesn't happen when I launch Google home Launcher)).
I've tried installing older versions found on apkmirror, but they all give me the same problems.
LineageOS ROM was the correct one for my phone and GApps pack was the correct one for my CPU. Please help I like too much Sense home
HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
bitboy85 said:
HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
Click to expand...
Click to collapse
For some reason all the official nightlies i have tried have this issue, some cant even make it past the setup screen. I guess something bad ended up in the sources.
Its not maintained anymore for our devices but one of the best CM12 builds in my experience was Mokee OS. You can run the builds for the Photon Q (xt897) just make sure its the old one- i recall having issues with the more recent builds.
Personally though i have moved on to the Nougat builds. I'm currently running the builds for the xt907 and they work fine with my xt926. The crDroid build seems to be the most stable - https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 The only requirements are you must be running the JBBL and the TWRP version for the XT907 (its linked in the ROMs thread instructions). You also need to format your data and cache partitions as F2FS.
Ever since I upgraded to android 10, I haven't been able to get OK Google to enable on any ROM (tried ArrowOS, AOSiP, Evolution X, AICP); in every ROM, switching on OK Google in Assistant settings just has it turn right back off after a few seconds, with a driving warning and "Something went wrong. Try again." at the bottom of the screen. I grabbed a logcat while running Evolution X, but I took a peek at logcat on other ROMs and the error is identical:
https://pastebin.com/Ryqz1iww
For the record, this is a Perseus global model on 11.0.3.0.QEEMIXM firmware that's had MIUI 11 then Xiaomi.EU's latest MIUI 11 stable on it prior to going to custom android 10 roms.
If any more info would be helpful toward solving this, let me know and I'll grab it.
EDIT: OK Google IS WORKING under Xiaomi.EU's latest MIUI 11 build, but still no dice on any custom ROM.
EDIT 2: If a ROM has gapps included, it works. If I have to flash opengapps, it doesn't.
EDIT 3: Solved! Just flash the latest firmware again after you flash everything else - you can get the firmware here.
I'm on the latest Xiaomi.EU weekly ROM and OK Google works just fine.
Official ROMs are the only things I CAN get it to work on. Vanilla MIUI 11 and Xiaomi.EU both work for this, so it's not just an issue with my Google account or something - but something is preventing OK Google from working on any of the custom ROMs, including the latest versions of the ROMs mentioned in my OP, even those that include GApps, so it's not like I'm using a bad GApps package. Literally all I do is wipe everything (incl. formatting data), flash the ROM, flash Magisk (which I also did on the MIUI ROMs it works with), reboot, connect to wifi, log in to google (I've tried declining to restore a backup), go straight to Assistant settings and it fails, same error as in that logcat in OP on every ROM it happens on.
Hey, I have the same issue on Evo X. Have you managed to work it out? Thanks
Same issue here on AOSIP. Interestingly, I have two identical devices (Mi Mix 3), running the same version of AOSIP, and on one it works fine, and the other does not!
In case it makes any difference, I am using a gsuite account.
Solved! Thanks to a tip from @Caccu, I now have it working. The secret was to flash the latest firmware over the ROM, even if you're already on the latest firmware. I'm not clear on why, but it works. If you need the latest firmware, you can get it from here. For reference I'm using V12.0.1.0.QEEMIXM on my global Perseus model.
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
bluviper said:
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
Click to expand...
Click to collapse
No no, just the firmware, not the whole MIUI package/ROM. The link I provided only has the firmware, with the rest of MIUI stripped out. The ROM is unaffected, the only change I notice after flashing it is that OK Google works now.
I have purchased a OnePlus 7 Pro from a friend of mine. He has already changed it from the T-Mobile to the International version via MSM. The current build number is 9.5.3.GM21AA and model number GM1915. I have currently installed TWRP 3.3.1-0 and rooted with Magisk 20.4. As I am new to OnePlus, I am confused as to go about updating the stock firmware, if I will lose root, updating to a custom rom. I have done this with other phones, Nexus 6P, 5X, Pixel 1 and Essential PH-1, but this seems different as I have a build number that is not necessarily meant for the T-Mobile version of this phone. I have read multiple guides and instructions throughout this forum, but don't seem to find the answers for my specific phone. Any help and direction would be very helpful.
If the phone has been updated to the international version then that's a REALLY old version, the latest version for International (Global) is 10.3.5, have you checked for an update via the phone already?
Update settings are in Settings > System > System Updates
If you want to upgrade manually, you can do that via Settings > System > System Updates > (Top Right) > Local Upgrade (Make sure the zip is in the main storage folder though or it won't be listed)
However, If you want to upgrade and keep root then you need to upgrade TWRP first, the latest is 3.4.0-0 from here : https://twrp.me/oneplus/oneplus7pro.html
Flash that first.
I've uploaded both the most recent versions onto my Android File Host :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
So....
Grab the international version (which is the full rom)
Download the latest TWRP and Magisk
Reboot to TWRP (3.4.0-0)
Flash the full rom build (do not reboot yet)
Flash TWRP 3.4.0-0 (before rebooting) then reboot back into recovery
Flash latest Magisk then clear cache (not data)
Reboot
Check the Magisk version with the app : https://github.com/topjohnwu/Magisk/releases
I would suggest choosing the beta release in the app as Magisk 21.0 is available and works fine (see attached)
If it shows that the phone is not rooted then just reboot back into TWRP and flash Magisk again and reboot.
-----------------
If you're going to install a custom rom then ensure you read the first posts in the thread first as the dev will usually advise pre-requisites (i.e. A specific stock rom version to have installed first, a specific version of TWRP to use, etc)
(Also, try to use paragraphs, makes your post a lot more legible)
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
njsges said:
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
Click to expand...
Click to collapse
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
djsubterrain said:
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
Click to expand...
Click to collapse
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
njsges said:
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
Click to expand...
Click to collapse
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
djsubterrain said:
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
Click to expand...
Click to collapse
Thank you. The phone has already been switched from T-Mobile to Global. I'm not sure if the OPS patcher was done yet. I will text my friend and ask him. I wonder if it is detrimental to do it again while I am still on 9.3.5?
UPDATE: My friend flashed the ops file with the MSM tool download
SUCCESS!! Thank you for all of your help!!
I have a Moto G3 XT1543 and since december I have given this device a second life and have been using it as a secondary phone. I decided to install LOS 14.1 because I feel is better for this device than LOS 17.1. Since then I had been using the phone and installing the updates without problems until a few weeks ago.
I thought I couldn't install the update because my version of TWRP was so out of date. So I decided to install the latest version for this device (twrp-3.5.2_9-0) and I was able to update the rom but it got me a lot of bugs, basically forced close in many processes.
So I decided to do a clean installation but still had a lot of bugs. So I installed previous versions of the rom, including the first one that I installed and worked fine, but it still had a lot of bugs (basically forced close in many processes, as I said before).
So I decided to go back to the TWRP I had before (twrp-3.4.0-0) and the bugs disappeared and I was able to use the rom without problems, but no matter what I do I cannot get youtube working now.
The gapps that I have been installed are open_gapps-arm-7.1-pico-xxxxxxxx and I have done all the possible combinations: old gapps with the most recent rom (lineage-14.1-20210829-UNOFFICIAL-osprey), the most recent gapps with the oldest rom I have (lineage-14.1-20201221-UNOFFICIAL-osprey), the oldest rom I have with old gapps and the most recent rom with the most recent gapps, but youtube still doesn't work
As I said before, it doesn't matter what combination I do, even the first one I installed and worked since last december, nor what version of YouTube I have installed, the application closes. As a possible solution I have deleted cache and data of youtube but the problem still. The funny thing is all the applications that I have, including other google apps (chrome, gmail, maps) work without problem.
I have tried alternatives like YT Go, YT Vanced and New Pipe and all three work without problem, but honestly, although they are better alternatives, I don't want to use them.
So does anyone know how to fix this?
I used this weekend for testing and long story short I can use youtube but I have no idea how it was fixed.
But I will tell you about everything I did in case someone in the future is going through a similar situation to mine.
Following the indications that FNetV1 gave me in another post, I downgraded my TWRP version to 3.0.2-r5, then I installed the oldest rom I have (lineage-14.1-20201221) with the oldest gapps I have (open_gapps-arm-7.1-pico-20210112) but youtube was not working.
So with that same version of TWRP I installed the most recent rom available (lineage-14.1-20210829) with the most recent gapps and still youtube did not work.
So I installed the latest unofficial version that Squid2 developed for this device (twrp-osprey-3.2.3-r1) and then installed the oldest rom I have with the oldest gapps I have. The result was the same, youtube was not working.
I thought the problem was the gapps, so I installed the latest rom available with the most recent gapps but now with the Nano package. But the result was the same, youtube was not working.
So I gave up and for the last time I reinstalled the latest rom avaible with the most recent gapps, again with the pico package and as expected youtube was not working.
The funny thing is after I finished setting up my phone, I restarted it, reinstalled YouTube and voilà, I can now use YouTube without any problem.
As I said at the beginning, I have no idea how the problem was fixed, especially because I also rebooted my phone on several occasions with the previous tests.
So if anyone has an idea what I did wrong from the beginning or how the problem was fixed, feel free to comment.