gapps not installing, "installation aborted" - General Questions and Answers

Q!
Apologies if this has already been resolved, I did a search but did not find my exact problem.
I screwed up, I installed the ROM from http://forum.xda-developers.com/showthread.php?t=1092332 but I failed to install the GAPPS zip the first time.
So I tried to install it again with gapps but I keep getting a "Verification failed Installation aborted" message.
So then I downloaded the stock HTC ROM from http://forum.xda-developers.com/showthread.php?t=804692 but I get the same error message.
Can somebody tell me how to either get this ROM to work with gapps or go back to stock? I need to learn to read the entire post before assuming every ROM installs the same.
Thanks for reading, and thanks for your time.

Download the correct gapps package and make sure the download is corrupted.
EDIT: isn't, lol fail

Thanks. I was not able to find a gapps package that worked. I dl'ed a signed version successfully but I couldn't get past the setup screen. It just was not working.
So I went with CM7 instead and I actually like it a lot better. I've got my Google apps and everything's running smooth. Yay for ROMs.

CM7 is very sexy... runs on my Wildfire S but the WIFI is broken on my specific model right now *sadface*
I think your problems lead you in a better direction at least!

Related

[Q] JellyBam Installation Problem!

I am a new member to XDA, though I have been to this site countless times before, and finally thought it was about time to join. I am not a noob to rooting or flashing or any of that-though I am still learning.
I have come across a problem and need help. I have a T-Mobile SGS III SGH-T999 and was running 4.1.2 Axis M rom, but I decided try something else. I've been searching for a good debloated stock touchwiz rom with the latest update, but until I find one I wanted to try something I found called JellyBam. Right now I'm back to 4.1.1 stock-I made a rooky mistake and had to reroot, just fyi.
I downloaded the latest JellyBam from get.jellybam.com and flashed it but all I got was, "status (7) error, Installation Aborted". I found out that "status (7)" happens when the phone checks to make sure the rom is compatible and the way to fix it is delete the line of coding above "show progress" in the "updater-script" file that causes the phone to check for compatibility and rezip the package and flash it. When I flash it now, it doesn't check for it to be compatible, which is good, so it goes straight to install. This time I don't get the "status (7) error" but it still aborts installation and I can't find out what's wrong.
I stopped trying to figure out how to get it to work. I just couldn't figure out what's wrong, I kept getting "status 7" and then "status 6"-and I have no clue what that one is-so I went with a rom my father used and I love it. I went with the inFAMOUS rom.
I would still appreciate some help with that whole "status 6/7" problem if anyone knows. Also, if anyone knows of a good debloated touchwiz rom that has the latest 4.2.2 or 4.2.1 tell me cause I've been searching for one and can't find one I like. I would like one that gets the latest updates.
Thanks.

Having trouble updating to 4.4.2

I'm on 4.4 right now and I just reviewed the ota but when it finished downloading, it went stock recovery and just said "error". Obviously I was pissed so I then went the adb root but that wouldn't work either. Something about it not being able to find "update.zip" when it is clearly in the same folder. After that I decided to flash a custom recovery, not clockwork but the other one. Whenever I try to go that route it still says it failed. I have been looking at posts and none have helped so far.
I am rooted, I don't have busybox/xposed, I am using art. I read something about having to have all of the stock apps. I had a modded playstore on here but I didn't work so I re-download one and installed it, could that have anything to do with my problems? And if so, where can I find another playstore app?
also, this is what it says in the custom recovery: /system/framework/core-libert. Jar unexpected E:Error executing updater in zip I tried googling but to no avail.
That modded play store might have changed some system files that prevent the update. You can try flashing one of the stock 4.4.2 Roms available in the android development forums. I used the one by bigxie.
Sent from my Nexus 5 using Tapatalk
Thanks man. Should I use an odex or deoxdex? And what's the difference?
I have this problem too....i'm rooted and get the error logo when i try to update too.....
paulbadassbriant said:
I have this problem too....i'm rooted and get the error logo when i try to update too.....
Click to expand...
Click to collapse
Try what the guy who replied to me said, it worked for me

[Q] Tmo Samsung S4 (SGH-M919) with Google Play Edition, need help

(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2

[ROM][UnOfficial]CyanogenMod 13 Semi-Nightlies for the Verizon Galaxy S3 (d2vzw)

CyanogenMod and D2VZW: Marshmallow Love!
To Make this easy, I am going to copy a bit of the common sense information Master Cylinder put up for the release of Lollipop, same basics apply here!
Huge thanks to Invisiblek for making these builds for us!
Thanks to Master Cylinder for all the super useful information!
De-unified Marshmallow builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances...)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x and up, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Google apps addon:
Open GApps opengapps.org They have many options for you to choose from based on your needs. Updated daily.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
I personally don't use GApps on my Daily Driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Dalvik and Cache, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs!
This page will be a work in progress, so please don't yell if something is missing. I just got the OK to share this with others and wanted to get it out there for you to enjoy. I have been playing with it for the last 24 hours and it is ROCK SOLID in my opinion. I haven't found any issues yet! Daily Driver for me for certain. If you have issues, please post them for discussion below!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
BUGS:
Need to possibly load a different File Explorer to access SD Card (DoctorImpossible)
Access to camera is not functioning correctly (DoctorImpossible) *EDIT 11-23 build camera works, camcorder fix coming next build!
Outgoing text messages show "not sent", but actually send fine. (Stealth111)
Incoming phone calls do not show caller information (Stealth111)
**When you get your ROM installed and up and running, please be kind and put a small post with information about your install so we can get as much info gathered as possible. (ROM build you installed, Recovery type/version, Clean install, or Dirty (and if dirty, over what version did you flash), what GApps package you installed(exact one please) as well as when you installed it (if on same initial install as ROM, or differently). And lastly maybe the firmware/modem combo you are running. Thanks!
***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!
Nuke IT Database Wiper
Profit!
Enjoy!
Stealth111
For Future Use
First
For Future Use
Second
Stealth111 said:
Second
Click to expand...
Click to collapse
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Master Cylinder said:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Click to expand...
Click to collapse
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Stealth111 said:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Click to expand...
Click to collapse
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!
Stealth111 said:
CyanogenMod and D2VZW: Marshmallow Love!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d..._NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
Enjoy!
Stealth111
Click to expand...
Click to collapse
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Ghost Protocol said:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
Click to expand...
Click to collapse
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Doctorimpossible said:
It seems pretty nice, and I only noticed a few things. . I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Click to expand...
Click to collapse
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Master Cylinder said:
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Click to expand...
Click to collapse
So is this a hit or miss when flashing or not?
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Stealth111 said:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Click to expand...
Click to collapse
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
Of course! It's the first unofficial build for us.
Stealth111 said:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Click to expand...
Click to collapse
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Master Cylinder said:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Of course! It's the first unofficial build for us.
Click to expand...
Click to collapse
Here is the MD5 from my file if it helps!
192BD2F6A83BCA791E0AFE9570134058
Doctorimpossible said:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Click to expand...
Click to collapse
Yuppers! Exposed for Android 6
Thanks for the report!
Fingers crossed for Master Cylinder!!
Stealth111 said:
If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
Click to expand...
Click to collapse
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Jaws4God said:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Click to expand...
Click to collapse
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Master Cylinder said:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Click to expand...
Click to collapse
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..
Sent from my SCH-I535

Noob trying to upgrade Asus TF101 to Lollipop and failed

Hey folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
set_metadata_recursive: Some changes failed.
E:error in sdcard/Kitkass/Katkiss-5.1_030c.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
xa3phod said:
Hey folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
Click to expand...
Click to collapse
I have this devices some were in a drawer lol anyways sounds like u mave have downloaded a bad copy try redownloading and get a md5 checker and check it. Also did you make a back up in twrp? If so could restore that in time being. Have a read trew kitkass thread agin and see if you missed any thing i know i had that rom running at one point but went back to kitkat cuz it was more stable.
Thanks for the help. I think I had a bad copy and a redownload fixed the issue. Android 5.1 is on the device and it sort of works. Well, not really. It runs poorly, reboots a lot and now it actually reboots before I can log in. I think I should hit a lower version of Android. Any suggestions on which version works best on the TF101? As of now its not usable.
Also, if I go to say, 4.4, can I use the same gapps-Katkiss-5.1 or do I need a correct version for 4.4? Can I just install it over 5.1 or do I need to wipe the device and start from scratch?
Again, thanks for the help.:good:
I tried to install 4.0.3, the official TF101 image from Asus but it wouldn't install. How do I go back to stock?

Categories

Resources