[Q] Google Apps on Stock Android - Fairphone

Hello,
I'm trying to install Google Apps on Stock Android on my Fairphone as described in this guide (http://forum.xda-developers.com/wik...pps_on_Fairphone_FP1_Stock_Android_.28AOSP.29), but installation always stops and says "installation aborted". What do I do wrong? Can anybody help?
I don't have to unzip the zip-file, do I?
Thanks for your help!
Cheers,
Felix

fedulix said:
Hello,
I'm trying to install Google Apps on Stock Android on my Fairphone as described in this guide (http://forum.xda-developers.com/wik...pps_on_Fairphone_FP1_Stock_Android_.28AOSP.29), but installation always stops and says "installation aborted". What do I do wrong? Can anybody help?
I don't have to unzip the zip-file, do I?
Thanks for your help!
Cheers,
Felix
Click to expand...
Click to collapse
The googleapps.zip I had uploaded 7 months ago was outdated; I just updated the link in the wiki (here's the file) after performing a fresh extraction from the newest AOSP ROM. You don't have to unzip the file; just move it into phone storage, reboot to recovery, and flash the zip. Should work.
Hope this helps!

simsalonaut said:
The googleapps.zip I had uploaded 7 months ago was outdated; I just updated the link in the wiki after performing a fresh extraction from the newest AOSP ROM.
Click to expand...
Click to collapse
I had to do this to install GApps on AOSP: install FPOS 1.6, start the GApps installation. Safe copy the GApps zip. Install AOSP. Istalls the GApps with the saved zip.
I opened a call with Fairphone to find out if they could publish the link to the GApps zip file so we can skip these steps next time.

Related

What is GAPPS?

Hi. I am planning to flash CM7 for a try. but i notice in some threads they mentioned installing GAPPS. what is this actually? an app available in market?
GAPPS stands for Google Apps... That includes stuff like the gmail app, google maps, google goggles, etc.
you can find some of these apps on the market, but not necessarily all of them. (I couldn't download gmail from the market)
Without GAPPS you have no Market, as Market is included in GAPPS.
Ic. so its apps related to Google's own app. Alright, thanks alot. x)
thanx so much for d info
Thank you for asking the question and all the answers. It helps.
And here's a link to all the GAPPS you'll ever need:
http://goo.im/gapps
:angel: (At least I hope that's all you'll ever need!) :silly:
Use archiver program (such as 7zip, WinRar... etc) to open, delete all unneeded and flash
hardsoft said:
Use archiver program (such as 7zip, WinRar... etc) to open, delete all unneeded and flash
Click to expand...
Click to collapse
What's unneeded?
I happen to have a problem installing gapps, if you would be so kind as to have a look at it here, I'd be most appreciative.
superstick1 said:
Hi. I am planning to flash CM7 for a try. but i notice in some threads they mentioned installing GAPPS. what is this actually? an app available in market?
Click to expand...
Click to collapse
I don't ever recall having to flash gapps with cm7. Please correct me if I'm wrong. However I've had to flash gapps with ICS and jellybean.
Sent from my Inspire 4G using xda app-developers app
superstick1 said:
Hi. I am planning to flash CM7 for a try. but i notice in some threads they mentioned installing GAPPS. what is this actually? an app available in market?
Click to expand...
Click to collapse
there are many unnoficial CM ROMs out there and each ROM reccommends a different set of GAPPS.
GAPSS are just a compiled list of apps and some might have calendar, some might not, every package is different.
They were made to reduce flashing time and reduce bloat, plus some regions of the world cannot use some apk's and need a localized GAPPS package (as some regions like Germany cannot download gmail and calendar fro the market)
brandub said:
there are many unnoficial CM ROMs out there and each ROM reccommends a different set of GAPPS.
GAPSS are just a compiled list of apps and some might have calendar, some might not, every package is different.
They were made to reduce flashing time and reduce bloat, plus some regions of the world cannot use some apk's and need a localized GAPPS package (as some regions like Germany cannot download gmail and calendar fro the market)
Click to expand...
Click to collapse
GAPPS are not included in Cyanogen Mod because they include proprietary software developed by Google...
See Wikipedia - CyanogenMod for the whole History:
http://en.wikipedia.org/wiki/CyanogenMod
here's a cutout:
"Following a statement from Google clarifying its position[56] and a subsequent negotiation between Google and Cyanogen, it was resolved that the CyanogenMod project would continue, in a form that did not directly bundle in the proprietary "Google Experience" components.[57][58] It was determined that the proprietary Google apps may be backed-up from the Google-supplied firmware on the phone and then re-installed onto CyanogenMod releases without infringing copyright."
GAPPS per Android Version
In the AOSP ROMs, most famously CyanogenMod and AOKP the GAPPS are not included in the ROM.
Here you can find some info about the Recommended Package of GAPPS per Android Version:
http://wiki.rootzwiki.com/Google_Apps
The primary mirrors for the Google Apps packages are here: http://goo.im/gapps
I hope this will help.
brandub said:
there are many unnoficial CM ROMs out there and each ROM reccommends a different set of GAPPS.
GAPSS are just a compiled list of apps and some might have calendar, some might not, every package is different.
They were made to reduce flashing time and reduce bloat, plus some regions of the world cannot use some apk's and need a localized GAPPS package (as some regions like Germany cannot download gmail and calendar fro the market)
Click to expand...
Click to collapse
galiato said:
In the AOSP ROMs, most famously CyanogenMod and AOKP the GAPPS are not included in the ROM.
Here you can find some info about the Recommended Package of GAPPS per Android Version:
The primary mirrors for the Google Apps packages are here:
I hope this will help.
Click to expand...
Click to collapse
So I'm attempting to get the latest Cyanogen Mod for my HTC Vivid.
This is all the instructions I see and this doesnt do enough for a noob like me.
Installation Instructions
Requirements
* Rooted (obviously) -- Check
* A brain -- debatable
Installation
1: If you are coming from another ROM do a full wipe -- Did that
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
2: Flash gapps (download below) -- Does the Gapp have the ROM in it? I think not from reading this thread
3: Reboot --- But I havent installed the ROM yet.
4: Enjoy CyanogenMod 10.1
I've looked everywhere on this site for a HOW-to-Install a ROM guide and I cant find one anywhere in the HTC Vivid boards.
Any links would be most helpful.
ddunleavy2 said:
So I'm attempting to get the latest Cyanogen Mod for my HTC Vivid.
This is all the instructions I see and this doesnt do enough for a noob like me.
Installation Instructions
Requirements
* Rooted (obviously) -- Check
* A brain -- debatable
Installation
1: If you are coming from another ROM do a full wipe -- Did that
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
2: Flash gapps (download below) -- Does the Gapp have the ROM in it? I think not from reading this thread
3: Reboot --- But I havent installed the ROM yet.
4: Enjoy CyanogenMod 10.1
I've looked everywhere on this site for a HOW-to-Install a ROM guide and I cant find one anywhere in the HTC Vivid boards.
Any links would be most helpful.
Click to expand...
Click to collapse
Ok, so you just don't have the 2nd thing (a brain)...
Just kidding
Ok. The way you install the rom is
You have to have a custom recovery
You download the rom.zip and put that on your SD card
You go to your recovery, and do a full wipe (search what that is)
Then you install the rom.zip and boot the phone
If you are not S-OFF then you have to extract the boot.img from the rom.zip and flash that separately (search how to flash a rom when S-ON).
When you've installed the rom boot the phone.
IF you want GAPPS then go to the recovery again and install GAPPS.zip
GAPPS are just APKs and are not the whole ROM.
Now just boot the phone again.
And that's it, you're done.
ilans93 said:
Ok, so you just don't have the 2nd thing (a brain)...
Just kidding
Ok. The way you install the rom is
You have to have a custom recovery
You download the rom.zip and put that on your SD card
You go to your recovery, and do a full wipe (search what that is)
Then you install the rom.zip and boot the phone
If you are not S-OFF then you have to extract the boot.img from the rom.zip and flash that separately (search how to flash a rom when S-ON).
When you've installed the rom boot the phone.
IF you want GAPPS then go to the recovery again and install GAPPS.zip
GAPPS are just APKs and are not the whole ROM.
Now just boot the phone again.
And that's it, you're done.
Click to expand...
Click to collapse
Is it too late to change my name to FUBAR?
So made a TWRP back-up of my phone.
I did the wipe
I loaded Cyanogen 10.1 but it just cycled at the Cyanogen splash screen for about 15 minutes.
I pulled the battery and tried it all again.
This time I did it via the ROM Manager.
I did a backup to Clockwork Mod recovery
I wiped
But now NADA -- Just the White HTC screen.
I can get to the Bootloader screen but when I do fastboot it comes up saying No image found.
Methinks I backed up something non-existent and then flashed back to that non-existent or empty ClockWork Mod.
Is the white HTC screen symptomatic of a hard brick or soft brick?
Thanks for your response.
As the saying goes "Experience is the best teacher because it costs to much."
By hook or by crook I will NOT be a noob forever
Thanks again all - Be Well
Are you S-On or S-Off? If you are S-On, did you fastboot flash the boot.img?
bananagranola said:
Are you S-On or S-Off? If you are S-On, did you fastboot flash the boot.img?
Click to expand...
Click to collapse
I dont what S-On/S-Off is.
When I fastboot it says no img found.
I can't find my card reader but I'm pretty sure, nay hopeful, that all the images I need are on the SD card. So at this point I believe that I just need to find a way to bootload off my sd card. But I can't do that just using the phone alone because my phone has no OS on it at this point. It's just a device.
The more I write about this, the more dumb I feel
Thanks again all
ddunleavy2 said:
I dont what S-On/S-Off is.
When I fastboot it says no img found.
I can't find my card reader but I'm pretty sure, nay hopeful, that all the images I need are on the SD card. So at this point I believe that I just need to find a way to bootload off my sd card. But I can't do that just using the phone alone because my phone has no OS on it at this point. It's just a device.
The more I write about this, the more dumb I feel
Thanks again all
Click to expand...
Click to collapse
So you are S-OFF, right?
TWRP has some problems flashing some ROMs... I recommend you to flash 4EXT recovery and try flashing the ROM once again.
Yeah, you haven't bricked anything
TWRP should be able to flash the stock rooted RUU. From there install 4ext recovery and from then on install what ever you want
ilans93 said:
So you are S-OFF, right?
Click to expand...
Click to collapse
Don't know what S-On/S-Off is. Don't know how I know if I am or not.
ilans93 said:
I recommend you to flash 4EXT recovery and try flashing the ROM once again.
Click to expand...
Click to collapse
Havent figured out how to flash anything because my phone is just a device and no OS. All I get is the HTC white screen. When I go to flashboot it complains that there is no image. Everything I've tried from just the device has come up nil. Not restore factory settings, not anything from the bootloader menu. The device not connected to anything is poo-poo platter.
Assuming I need to find out how bootload from an image loaded on my computer with the device attached via my cord.
ilans93 said:
Yeah, you haven't bricked anything
TWRP should be able to flash the stock rooted RUU. From there install 4ext recovery and from then on install what ever you want
Click to expand...
Click to collapse
Again, once I can get the phone to boot off an image from my computer connected via the cord I'll be good to go.
Thanks again for the replies. Be Well

[TUTORIAL] Flash CyanogenMod on TWRP

For CM11 Nightlies:
Find nightlies here:
http://download.cyanogenmod.com/?device=n1
If you're already on CM 10.2, just wipe cache and dalvik. Flash over your current build.
If you're coming from anything else, wipe cache, dalvik, data, and system. Then flash normally.
If you want gapps, you'll have to flash gapps as well.
No need for any modified files on nightlies. I assume that official stable builds will still be defaulted to flash on stock recovery though.
————————————————————————————————
CM 10.2 Information. Please do not use the following to flash CM11!
This is the method that I used to install CyanogenMod on TWRP.
I have tested this, and it is working perfectly on CM builds:
cm-10.2-WPPH47N-n1
cm-10.2-WPPH50O-n1
I will continue to test and update as new CM builds come out until CM flashes normally on TWRP
————————————————
First - Have TWRP as your recovery (2.6.3.1). Don't ask me how to do that.
Second - Backup your ROM! Just in-case something breaks, it's not my fault, and I'm not responsible.
————————————————
Now, we begin:
Download the newest CM build for the Oppo N1 from http://www.cyanogenmod.org/hardware/oppo-n1/#images
————————————————
After downloading your CM build from the above link, you'll need to follow these instructions to get setup for flashing in TWRP.
To modify your downloaded CM file, you can use either of the two methods below:
1: You can modify it yourself. It's actually very simple, just one line change.
2: I have attached an already modified updater-script to my post. You can use that and drop it into place (the file inside the zip, not the whole zip).[/b]
YOU ONLY NEED TO USE ONE OF THESE METHODS!
Method 1: To modify the file yourself:
First, open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Open the updater-script
Remove the first line only! You will remove:
Code:
assert(getprop("ro.product.device") == "N1" || getprop("ro.build.product") == "N1");
Do not remove anything else unless you know exactly what you're doing!
If you modified the file within the .zip, just save the file and it should save to the CM zip.
If you extracted the .zip, save the file and then go back and rebuild the zip.
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
——————————
Method 2: To download my pre-modified updater-script
Download my attached file (updater-script.zip)
Extract the file inside the zip (there's only one file)
Open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Simply copy your extracted updater-script from where you extracted it and drop it into the CM zip (It should save after)
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
————————————————
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
:victory:
I hope this all makes sense...
Basically you download the CM rom
Modify or copy the updater-script into the zip
Then you move the ROM to you phone
Then you go through the above area with wiping and flashing
* Pictures are attached
* Please let me know if there are any problems with this.
* Both versions of CM released so far have identical updater-script files. The .zip that I have attached will work on both builds.
* I will keep updating as needed
• Last updated: January 1, 2014
We're working on fixing TWRP so the asserts work properly.
https://github.com/omnirom/android_bionic/commit/4482d8513920d614e3799a214c5bad07b72580d2#diff-1 broke a lot of things.
https://github.com/omnirom/android_bionic/commit/ad76c85b9ca587084089d086f954158bc0eae905 allows flashing newer firmwares on older recoveries - but not the other way around.
The short-term fix is a TWRP build made from a 4.3 tree - this is 90% done.
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Entropy512 said:
We're working on fixing TWRP so the asserts work properly.
Click to expand...
Click to collapse
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
rayfin said:
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Click to expand...
Click to collapse
BTW, I'd prefer that my personal dropbox not be directly linked. The same file is now an attachment to my post in the TWRP thread.
Harfainx said:
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
Click to expand...
Click to collapse
i have some question can u help me :3
1. this download link is the file you already fix it right ?
https://www.4shared.com/download/UPP...N-N1_FIXED.zip - No wait - Direct download link - Full flashable ROM
Click to expand...
Click to collapse
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
kenjilolip0p said:
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
Click to expand...
Click to collapse
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Harfainx said:
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Click to expand...
Click to collapse
Camera orientation is handled by the camera HAL blobs.
CM does have back touchpad support but it's wonky (which is why omni hasn't merged it yet, we're still discussing whether to completely rearchitect it or just fix it.)
good work
Sent from my M045 using XDA Premium 4 mobile app
Except root it works
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
fesar said:
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
Click to expand...
Click to collapse
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
nowy57 said:
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
Click to expand...
Click to collapse
Go into SuperSU and remove it in the settings (unroot). That will get rid of all of the current SuperSU stuff.
Then flash SuperSU in TWRP.
To flash the unmodified CM, you can try the TWRP in post #3 of this thread HERE.
Or you'll have to remove the same line in the updater-script. The same method posted in the OP. Don't use the uploaded updater-script that I have there though. You'll need to change your own. It's a really simple fix. You don't have to extract all the files out. You can just modify the one file (I use Notepad++).
Sometime tomorrow I'll update the whole OP to include the newest CM version. I'm about to head out to our New Year's event, so I won't be available for the evening.
Enjoy the evening everyone. I wish you all the best! :good: :victory:
i have installed TWRP from #3 - not succes install CM newest version after this
i have unthick superSU and then install again via TWRP superSU.zip after that thick superSU on system android and no succes - root acces didnt come
happy new year
-------
I am a little dissapointed couse I downloaded CM ROM from OFFICIAL SITE http://www.cyanogenmod.org/hardware/oppo-n1/#images and I cannot install it SIMPLE on my device
OP updated! The newest release of CM has been added. I'll keep on top of it from now on, sorry about the delay.
I'm not going to host the CM builds anymore, since the modification is so small from the original CM build. Everyone flashing this should be capable of making the small change that's outlined in the OP.
:highfive:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
nowy57 said:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
Click to expand...
Click to collapse
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
okay , I will try it and confirm
I v got mac osx
under mac I unzip ROM , deleted first line from script then zip it , it doesent work .
but under windows - working good
Harfainx said:
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
Click to expand...
Click to collapse
What's wrong with wiping system?
You don't even wipe system if you go from ColorOS to CyanogenMod?
- Frank
cm11 nightlies are out and downloadable from cyanogenmod
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
Cm11 nightlies are out..
Do you think we can flash on twrp
If so what would you wipe...
I was thinking about using banks minimal.. 19 MB..
Please give the community tour thoughts and a step by step tutorial..
I would download the nightly from cyanogenmod and banks gapps.. Check md5 alla onmy phone
Reboot recovery and wipe all maybe even system except sdcard
Flash cyanogen then gapps then
Rewipe cache and dalvik
Reboot
I am on omni nightlies now.. Thanks in advance
where do you see nightlies for oppo n1 ?
edit:
ohhh I see
http://download.cyanogenmod.org/?device=n1
better later than never
I just lost hope for good support and sold my oppo n1
I didnt belive for good support having it from one month and non of help from CM team

[Q] Can't Install Gapps!! Please help!

Hello, Everyone.
I am new to XDA and rooting but i tend to follow instruction well
I am running Beanstalk 4.4 on my Hercules device. I have the latest TWRP Recovery installed as well.
So here's my problem. I downloaded the Beanstalk rom, along with the 'pa_gapps-stock-4.4.2-20140217-signed.zip' file and the 'pa_gapps-stock-4.4.2-20140217-signed.zip.md5' file. I put all the files in the root of my storage and I was able to install Beanstalk just fine, but whenever i tried to install Gapps right after
I have done full wipes and re-flashed everything and i always get this error.
Checking for MD5 file...
E:zip MD5 does not match.
Unable to install zip.
Error flashing zip '/sdcard/pa_gapps-stock04.4.2
Updating partition details...
I don't understand, am i doing something wrong? Please help!
Redownload the zip. Looks like a bad download since you're getting the md5 error.
Or try different gapps file.
Sent from my Moto X cellular telephone...
Or maybe try a GApps package meant for other roms.. like CM

gapps for cm12.1 not working

I got an update for cm12.1 snapshot on my Samsung galaxy mini i9195 after i got the update google play store wasn't working so I installed gapps for cm12.1 from the official webpagehttps://github.com/cgapps/vendor_google/blob/builds/arm/gapps-5.1-arm-2015-07-17-13-29.zip this is the link that I used now nothing is working i get errors from all the google apps and also from setup wizard when i press the home button. How can i fix this problem? and if there is another gapps file can someone guide me to it, please?
tomt003.310 said:
I got an update for cm12.1 snapshot on my Samsung galaxy mini i9195 after i got the update google play store wasn't working so I installed gapps for cm12.1 from the official webpagehttps://github.com/cgapps/vendor_google/blob/builds/arm/gapps-5.1-arm-2015-07-17-13-29.zip this is the link that I used now nothing is working i get errors from all the google apps and also from setup wizard when i press the home button. How can i fix this problem? and if there is another gapps file can someone guide me to it, please?
Click to expand...
Click to collapse
On which version were you prior to updating to 12.1 snapshot? If you were on 11.0 snapshot you might want to consider a clean flash (factory reset, then flash ROM, then flash gapps). I did it like that and had no problems so far.
Good luck
Z0K4 said:
On which version were you prior to updating to 12.1 snapshot? If you were on 11.0 snapshot you might want to consider a clean flash (factory reset, then flash ROM, then flash gapps). I did it like that and had no problems so far.
Good luck
Click to expand...
Click to collapse
Can u help me with the gapps file I should use. When I flash the gapps that I used I keep getting setup wizard and other Google apps errors
tomt003.310 said:
Can u help me with the gapps file I should use. When I flash the gapps that I used I keep getting setup wizard and other Google apps errors
Click to expand...
Click to collapse
Try "open gapps" I always have good results using those. Maybe try a fresh install of Lollipop though with FULL wipes including system. If not at least wipe cache and dalvik after flashing.
tomt003.310 said:
Can u help me with the gapps file I should use. When I flash the gapps that I used I keep getting setup wizard and other Google apps errors
Click to expand...
Click to collapse
Since I have less than 10 posts I can't paste links, but gapps file that I used is the one suggested by CyanogenMod. Google "CyanogenMod gapps". Go to first link (it should be CM wiki page). Scroll down until you find table with version 12.1 "Download: GitHub". Click on it. Now, when on GitHub scroll down and click "arm". Now select the latest zip file (at the time of writing this, it's "gapps-5.1-arm-2015-07-17-13-29.zip"). If it doesn't start downloading click on "view the full file" or "View Raw".
If that doesn't work, try doing as RuffBuster said.

Galaxy S5 (G900F/ klte) - Can't install APKs in LineageOS 14.1!

Hi,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
MDAman said:
Hi,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
Click to expand...
Click to collapse
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
I just installed lineage-14.1-20170131-nightly-klte-signed with open_gapps-arm-7.1-stock-20170131, rebooted, setup all my settings (Declined the restore from previous backup on first start) and went to Play to install all my apps. Rebooted to flash addonsu-arm-signed, then rebooted again and flashed SuperSU-v2.79-201612051815.
All working fine for now on my G900T and I had CM13 prior to this. From TWRP wiped all but the ExternalSD, rebooted to recovery and wiped again all but ExternalSD, then did a Factory Reset and installed LOS. The only thing not working is FolderMount, but I was expecting that until the next update.
Sent from my SM-G900T using Tapatalk
jhedfors said:
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
Click to expand...
Click to collapse
I've flashed TWRP using Odin3, booted into recovery, fully wiped stock (sys, data, cache, int sd, etc.) and installed LineageOS rom + GApps.
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
hanzaz said:
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
Click to expand...
Click to collapse
Done that. Still the same error.
Installed lineage-14.1-20170207-nightly-klte-signed (MD5 is fine). APKs still can't be parsed.
First I updated. Afterwards I wiped and tried clean install. No difference.
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
_-M-_ said:
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
Click to expand...
Click to collapse
simple yet elegant.
Thank you very much.

Categories

Resources