Hello I'm new to installing custom Roms and I am having a bit of trouble.
I am installing AOKP Milestone 1 and that goes fine but I am having trouble getting my gapps to work.
So what I do is reboot into CWM, factory reset, install aokp, install gapps 4.2.2 2013.03.01 then boot.
Once I start my titanium restore I get everything as it should but my camera app and a few other g apps like chrome show up as a little green android guy and says app not installed. I also get error messages non stop and if I try to open gmail for example it just crashes non stop.
Am I just using the wrong gapps file or something or am I missing a step?
the error message is Unfortunately, the process android.process.acore has stopped.
try a different, newer gapps http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=gapps
reflash your rom and the gapps.
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.
So I want to try out the newest CM 12.1 nightlies, but can't because of an issue that keeps popping up. I can flash a ROM and GApps package just fine, but when I boot the phone, I keep getting an error message saying "Google Play Services has stopped" or the same message for any of the included apps in a GApps package. I am unable to set up the phone because the pop-up is perpetual. I've tried multiple GApps packages from the CM Wiki page, but none for 12.1 are agreeable. Has anyone else encountered this? What did you do to fix it?
Hey guys, I ran into a rather odd issue yesterday and can't for the life of me figure out how to get my phone back to normal..
I upgraded TWRP to 3.0.2-0, wiped data, system, dalvik/cache, and attempted to install AOSiP 4.1 + Banks 4/08 Gapps, but after the boot, I get "Unfortunately SetupWizard has stopped", and after getting through the setup, "Unfortunately Theme Provider has stopped", if I click the Theme app it FC's.
This happens on EVERY single ROM I try to install, except Resurrection Remix. (The ROM I was on before flashing AOSiP.) I have tried going back to stock MHC19Q and starting fresh, but I still get FC's. I have also tried every recent TWRP, and MultiROM TWRP. Nothing is working.
Please help...
Edit: @big nu has the same issue..
https://tapatalk.com/shareLink?url=...share_tid=3357511&share_fid=3793&share_type=t
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Eric214 said:
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Click to expand...
Click to collapse
I fastboot everything. I flashed the stock image from my PC but still no luck...
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Casmo said:
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Click to expand...
Click to collapse
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
adzcache said:
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
Click to expand...
Click to collapse
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
jesssiii said:
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
Click to expand...
Click to collapse
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
adzcache said:
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
Click to expand...
Click to collapse
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
adzcache said:
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
Click to expand...
Click to collapse
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU! ?
adzcache said:
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU!
Click to expand...
Click to collapse
I had a problem like that. What I did was
Boot into Recover - TWRP 2.8 something
Did the Wipe Data / Factor Reset
Flashed The Rom - For me it was Pure Nexus - April 7, 2016
Flashed The Kernel - For Me Element X
Then wiped Davlik/Cache
Then after that I rebooted let it do what it had to do to boot up. Then rebooted to recovery
Then flashed the GAPPS - for me i used BaNkS-Dynamic-GApps-6.x.x-10-20-15
Then wiped DAvlik/Cache
Then rebooted and let it do its thing again. - I did not get any system startup failed.
Maybe you can not flash the GAPPS all together because the phone is a smart phone but it can still be DUMB.. LOL
Then I did not do a restore of apps from the automatic thing when it asks I just went to pla stoer and let it download what I needed from the my app section.
I'm still facing issues, but at least there are painfully long fixes to make everything work normally... Just pissed, every other android phone I have had, never faced such a persistent issue with rooting and flashing custom ROMs. Especially after restoring to stock..
Sorry to bump this thread, just hoping someone may have a suggestion that may fix up this rather odd issue I've been plagued with?
Quick fix for anyone else facing this:
Downgrade to MHC19I and when flashing recovery, flash TWRP 3.0.0-1, then format userdata in fastboot, copy your files over via PC and flash ROM + Gapps.
I have problem with flashing LineageOS second time.
I used LineageOS before. And I've decided to flash the updated nightly build. And I do the clean flash, wipe system, and data. Flash ROM, and then flash GApps again. (I knew after that I don't have to clean flash to update my nightly because it will erase your previous google account settings)
After installation I rebooted into the system. In the first setup wizard, At Google account login, it says "checking info..." and then crashed with the message "Google Play services has stopped". I've tried many flashing methods, and also flash ROM without GApps. But it same in the system. I can't add google account and can't open the playstore either. I tried with different build and different GApps packages and it went fail and fail again. Please tell me if you have any ideas so I could run 7.1.1 again. I would appreciated it. Anyway I'm at CloudyG2 3.3 right now and using TWRP blastgator 3.1.0-1.
Thanks.
That's why it's called "nightly".
http://wiki.audacityteam.org/wiki/Nightly_Builds :
Nightly builds are alpha builds from the latest development code. By their nature these builds are likely to contain bugs or might even cause data loss.
Click to expand...
Click to collapse
Sorry to say, but you got to deal with it till the next build shows up.