Google on Chinese Variant (BND-AL10) - Installing core GMS packages - Honor 7X Questions & Answers

I have the Chinese Variant (BND-AL10) of the honor 7x am trying to get Google services to work; has anyone done so successfully?
In an attempt to do so i unlocked the bootloader, installed TWRP and installed from SD card zip the arm64, android 7.0, Pico version of Google apps from opengapps.org. After doing so when I went to boot the phone it would not go past the honor logo - so used Huawei's recovery to return it to normal again.

Returning to normal Huawei Recovery Will Wipe Data Factory Data reset because of these gapps will be removed u have to keep twrp installed for gapps to be worked or install play store services externally without twrp nor gapps find the package by searching on google and install each app manually.

Air Dronzer said:
Returning to normal Huawei Recovery Will Wipe Data Factory Data reset because of these gapps will be removed u have to keep twrp installed for gapps to be worked or install play store services externally without twrp nor gapps find the package by searching on google and install each app manually.
Click to expand...
Click to collapse
I was forced to do a factory reset as while TWRP and gapps was installed the phone would not turn on; it would only go to the honor logo and then no further. There was some critical error which meant I couldn't use android - hence I reset it and am now looking for a different process.
The problem isn't necessarily getting the apps - none of them run as the core GMS packages? (google framework I assume?) are missing.

Related

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

Opengapps crashing lineageOS setup

I have a samsung galaxy s4 mini G19195 serranoltexx and I can install the latest lineage os nightly build (20171103) for this phone no problem. But as soon as I try flashing open G apps I get a "System Setup keeps crashing" error notification and no matter how many times I click on "close application" this error keeps popping up.
It's very frustrating as I would like to use Gapps but I'm not even sure what the problem is. Am I flashing the correct version of openGapps? Is this a bug with openGapps or LineageOS? It's very frustrating as there are many versions of openGapps available for download but no clear guide on which exact version I should download.
The same problm
I deleted the lineage os. & replaced with resurrection remix 5.8.4.
I am getting problms with battry
If you want to keep using lineage os. Instal the os without installing gapps.
After make sur that the os fully installed then install gapps and update service Google play
Injoy
@daloonik
You must flash the Rom and gapps at the same time without booting.
The right gapps are V7.x and Arm Version,use nano or pico Version.
@bierma32 Yes that's what I tried. Except that the Open Gapps version (both nano and pico) would crash the Lineage OS setup and I would get into an error notification loop. Anyway I ended up foregoing Google Apps and using Aptoide instead. I just would like to know where I should report this bug because it's unclear if it's an Open Gapps problem or Lineage OS problem.
@yahiahedna Even after completing the setup for Lineage OS and flashing gapps I still had the Google apps crashing error
I use an Opengapps Version Pico from 04.02.2017 ARM 7.x without problems.
Other question ,which TWRP Version you are using 3.1.x , if yes try a 3.0 or 2.8.7.0 Version
daloonik;74426452 [user=8691966 said:
@yahiahedna[/user] Even after completing the setup for Lineage OS and flashing gapps I still had the Google apps crashing error
Click to expand...
Click to collapse
It doesn't sound like you are flashing them together before booting . Flash LOS then Gapps and only then boot to system setup otherwise the permissions are not set, and you will get problem what you describe @yahiahedna
Download official linageos 14
https://forum.xda-developers.com/ga.../rom-cyanogenmod-14-0-s4-mini-3g-lte-t3471761
Then download gapps
1) wipe the data & cash. flash the lineage zip.
2) reboot your phone & complete installation
Make sure that the lineage fully started and runs without problems
3) reboot your phone into recovery mode
& flash the gapps without wiping cash or data.
Shut your device on and sign in into Google account.
Notes:
Use arm gapps for arm device.
Use twrp recovery. Bcs cwmr 6.0.4.7 is incompatible with gapps

LineageOS install with gapps HELP

Hi,
I managed to successfully install LOS 16 on my XA2 H4113 using the guide from this forum. On the first try I managed to get the screen issue, but in the end I could correct it and run a clean LOS16.
What I want now is to either install the google apps or reinstall the OS along with the gapps.
I tried to follow the help provided here and reinstall the OS together with the gapps but whenever I try to sideload the gapps after sideloading LOS I get bootloop, which still happens after factory reset.
Can someone tell me when should I sideload the gapps zip during the sideloading of LOS in slot A and B and does it make a difference to which slot I start first?
spam1408 said:
Hi,
I managed to successfully install LOS 16 on my XA2 H4113 using the guide from this forum. On the first try I managed to get the screen issue, but in the end I could correct it and run a clean LOS16.
What I want now is to either install the google apps or reinstall the OS along with the gapps.
I tried to follow the help provided here and reinstall the OS together with the gapps but whenever I try to sideload the gapps after sideloading LOS I get bootloop, which still happens after factory reset.
Can someone tell me when should I sideload the gapps zip during the sideloading of LOS in slot A and B and does it make a difference to which slot I start first?
Click to expand...
Click to collapse
I think you need to flash your os and then boot into system and again go to recovery (twrp) and flash your gapps and boot into the system.
Personally, I find it much easier to save all the zip files on my SD card and flash the zips directly from twrp....again one by one separating each by booting into system once.
Some senior member expert opinion however should be awaited.

HELP! Bootloop when trying to Install Pixel Experience Plus

Have tried to clean flash latest PE Plus ROM 3 times today. I have a recovery backup of Havoc that I was able to get back to, but can't get past Google boot screen when flashing PE Plus.
Here is my process.
- Download latest Pixel Experience Plus (file name PixelExperience_Plus_whyred-9.0-20190906-0859-OFFICIAL.zip from Pixel Experience website) and save to SD card
- Download Magisk 19.3.zip from Magisk and save to SD card
- Download latest firmware from xiaomifirmwareupdater.com (stable, V10.3.2.0.PEIMIXM, 9.0 Global)
- Boot to TWRP 3.3.1-0
- Press Wipe - Wipe - Davlik, Cache, Data, System, Vendor
- Press install - Choose firmware file (stable V10.3.2.0.PEIMIXM 9.0 Global)
- Swipe to install
- Back home
- Press Install - Choose PixelExperience file from SD Card, press Add Zip, Choose Magisk 19.3zip from SD card
- Swipe to install
- After install finishes, choose swipe to reboot. Then choose swipe to install TWRP.
Phone reboots. Shows Mi logo for a couple seconds. Shows "Google" logo for a couple seconds. Google logo becomes the google multi-colored "G" with a progress bar going below the "G". Phone will stay here and not go any further.
Advice? Am I missing something in my flashing process?
Thank you in advance if you can help.
try not install magik on the first time booting
Tried to flash PE plus
used the same process
didn't flash magisk or any other type of root
same outcome, only thing different is that I lost my backup data after getting a password prompt on twrp and solve it like an idiot by wiping everything.
any help is appreciated I really like this rom :crying:
Edit: Fixed the problem by flashing again twrp recovery right after flashing the firmware, than proceeding with the same steps, Didn't take long in the fist boot. yet another problem, It's detecting my sim card and can't connect to wifi so I'm stuck on the setup; tried clean flashing another rom ( bootleggers) after I gave up on PEE but the same problem. I have no idea what to do now
I would start over with original miui fastboot rom via mi flash tool. It should make everything work again. Then you could try orangefox recovery instead of twrp to flash pixel experience rom.
lcdkhoa said:
try not install magik on the first time booting
Click to expand...
Click to collapse
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
Use magisk 20 .1
Redmi note 8 pro PE stuck bootloop G logo
nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
I have a Redmi Note 8 pro used orange fox recovery and still the G google logo stuck. i tried everything its just not working
---------- Post added at 05:42 PM ---------- Previous post was at 05:38 PM ----------
nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
Can you explain what steps you took to get the google PE to install safe
Hello,
I have a Redmi Note 8 Pro. I downloaded the ROM from PE site. https://download.pixelexperience.org/begonia. I install this ROM but after a reboot I can only see the REDMI Logog and than is a bootloop.
Any ideas?
Only way
the only way out is try clearing data partition in manage partition section of orange fox recovery or twrp,this would help but all data would be wiped.
Rarohd said:
Tried to flash PE plus
used the same process
didn't flash magisk or any other type of root
same outcome, only thing different is that I lost my backup data after getting a password prompt on twrp and solve it like an idiot by wiping everything.
any help is appreciated I really like this rom :crying:
Edit: Fixed the problem by flashing again twrp recovery right after flashing the firmware, than proceeding with the same steps, Didn't take long in the fist boot. yet another problem, It's detecting my sim card and can't connect to wifi so I'm stuck on the setup; tried clean flashing another rom ( bootleggers) after I gave up on PEE but the same problem. I have no idea what to do now
Click to expand...
Click to collapse
This is one freakin helpful information.Worked right away when facing same issue in my redmi 5a
Barker88 said:
Have tried to clean flash latest PE Plus ROM 3 times today. I have a recovery backup of Havoc that I was able to get back to, but can't get past Google boot screen when flashing PE Plus.
Here is my process.
- Download latest Pixel Experience Plus (file name PixelExperience_Plus_whyred-9.0-20190906-0859-OFFICIAL.zip from Pixel Experience website) and save to SD card
- Download Magisk 19.3.zip from Magisk and save to SD card
- Download latest firmware from xiaomifirmwareupdater.com (stable, V10.3.2.0.PEIMIXM, 9.0 Global)
- Boot to TWRP 3.3.1-0
- Press Wipe - Wipe - Davlik, Cache, Data, System, Vendor
- Press install - Choose firmware file (stable V10.3.2.0.PEIMIXM 9.0 Global)
- Swipe to install
- Back home
- Press Install - Choose PixelExperience file from SD Card, press Add Zip, Choose Magisk 19.3zip from SD card
- Swipe to install
- After install finishes, choose swipe to reboot. Then choose swipe to install TWRP.
Phone reboots. Shows Mi logo for a couple seconds. Shows "Google" logo for a couple seconds. Google logo becomes the google multi-colored "G" with a progress bar going below the "G". Phone will stay here and not go any further.
Advice? Am I missing something in my flashing process?
Thank you in advance if you can help.
Click to expand...
Click to collapse
WAIT FOR SOME TIME LIKE 10 MINUTES.. EVEN I THOUGHT IT WAS IN BOOT LOOP

Help fixing S20 Ultra Bootloop

I rooted my S20 Ultra (Hong Kong version) last year with Magisk. I was recently trying to install an OTA update, when I realized that I had not created a backup of my original system, so I could not use Magisk to restore the original image and then install updates, so I decided that I would just uninstall Magisk and root it again after updating. Unfortunately, when I pressed the "uninstall Magisk completely" button, the device ended up in a boot loop. I can access the recovery menu, but neither clearing the cache nor a factory data reset resolved the issue.
Does anyone have any suggestions?
It did installed on the root stock ROM?
If so, you can't do OTA update, unroot won't be the solution
If you have TWRP installed, you can install a custom rom without deleting your data.

Categories

Resources