Hi,
Just installed ZTE_A2017V1.0.0B11 via here following instructions. I have the Chinese phone version by default.
https://forum.xda-developers.com/showpost.php?p=68873487&postcount=4
Loads fine, I install SuperSU, couple of other minor packages through TWRP, everything works fine. Each time I'm clearing cache after install.
Then I install Gapps from http://opengapps.org/ (ARM64, 6.0), I have tried Nano and Micro, again clear cache and instead I get stuck at Axon boot logo.
Clearing cache again doesn't help, the only option I have is to wipe system and re-install OS but no gapps I have tried has worked.
Any idea why this might be the case? Thanks.
The phone that I got originally did have google play incidentally, probably installed by the aliexpress seller, but I'm not sure how. I had to wipe it earlier though.
Gapps are designed for custom roms. They probably don't work in the Stock ROM you are trying to use.
Have you unlocked your bootloader first? Have you installed the no-verity patch? Otherwise you won't be able to boot a modified system partition.
Yes, unlocked bootlader.
Oh wow, I had no idea, I thought gapps was a generic installer.
That explains it, I also didn't realize you could install Google Play through ZTE Market either.
All working now.
Related
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
rowdypixel said:
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
Click to expand...
Click to collapse
https://s.basketbuild.com/gapps
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
xDroidZz said:
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
Click to expand...
Click to collapse
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Same problem.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
Nexus 7 2013 WiFi
Any fix for this? I've been struggling with it for a whole day now.
I have not found a fix. I reverted back to KitKat since I needed to use my phone during the week.
Bump
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Do you know what version of CWM you were running? I might try updating it over the weekend and see if that works as an alternate solution.
Try this. This worked for me.
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
Gapps crashes
rowdypixel said:
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Click to expand...
Click to collapse
Before adding gapps after flashing cm-12 wipe dalvik and cache, flash ktoonz lollipop kernel then flash gapps for lollipop. This worked for me.
anonymousguy44 said:
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Click to expand...
Click to collapse
Hey I'm having the same problem, can you describe how in Odin you got back to stock? You flashed stock and lost your custom recovery? That's weird, I figured a custom recovery was like a bios
Hey guys, so i'm trying to install the following items:
-SlimLp F2FS (Android L)
-M-Kernel_a73.zip
and
-Slim_full_gapps.BETA.5.0.x.build.0.x-20150213-482
I use NRT to get into TWRP and from there I follow the following steps (my system is already in F2FS mode which i reformatted from the existing Ex?? one)
Clean Flash:
Wipe syste, data, cache, dalvik cache
Flash the rom
Flash Slim gapps or L Gapps (IDK WHAT THE DIFFERENCE BETWEEN GAAPS AND L GAAPS IS and they take me ultimately to the same link so wtf)
Reboot
The main issue is, after the tablet reboots and opens up I don't see the play store, i don't see ANY google items and I can't install anything. It seems to me that the GAAPS zip isn't being installed properly. I've already installed the main ROM, then GAAPS, then the M kernel and nothing seems to work. I don't see any playstore icons even in the app drawer. Can someone please explain to me what i'm doing wrong? Thanks!
Can someone please help?
bump for a response
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk
These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet
I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.
I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different
Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?
I have installed piex3lify from masgisk v18.
i have installed latest zip from pixel experience rom.
problem
now mobile opening with google logo and ask for android security password then blank screen.
after starting android it does not worked.
cannot login in screen.
solution i tried
wipe cache/delv cache from twrp.
installed old pixel experience zip version.
but sadly nothing works.
any solution most welcome.
solution
i need to wipe system, data that worked then re install latest zip from twrp.
can anyone suggest why viperforandroid cause problem.
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.