Yeah so basically everytime I try to download an app or game that needs to download additional data (Like Asphalt 8, or Ivona Amy or Fast and Furious 6) the entire download will complete, it will finish downloading till 100% even the additional data, and then it will suddenly just get an error saying 921 could not complete download. I have tried various different fixes to no avail. This happend all the way since stock 4.2. Flashed factory 4.2, 4.3, 4.4, 4.4.2 and the problem still occurs. On 4.3 it had become fixed for a while but again on 4.4.1/4.4.2 stock or custom roms, the same problem happens. I clean wipe the device and everything, even used different play store accounts and made a new play store account but the error still happens.
Thanks in advanced for any help, im really stumped and there is literally no one on the internet with this problem lol.
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Rezaei12 said:
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Click to expand...
Click to collapse
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Tkkg1994 said:
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Click to expand...
Click to collapse
No it's not a rom, I just restored my old back up of my OS before I started flashing any custom roms.
I did a factory reset on the phone hoping it might resolve it. Which hasn't, but I'm not sure now if it's got rid of CWM. Would as I can't seem to get it to boot into recovery (it maybe just me not releasing the volume up button at the right time).
Think I'm going to have to flash a clean stock firmware following the unroot process and hope that fixes it.
"Google Play services has stopped" on 3 different 7.1.1. ROMs (RR, AICP, Lin.)
Hey guys,
coming from a stock 5.0.2 I wanted to install Lineage Nougat. So first I installed TWRP 3.x and then Lineage and gApps.
After the installation I rebooted into the system and the setup wizard started (albeit this also has been crashing sometimes on all 3 roms), letting me go as far as the Google account login, "Checking info..." which crashed with the message "Google Play services has stopped". I can go through the wizard without doing anything, but it's the same in the system.
Can't open Play Store, can't add Google Account.
I've tried 3 roms, Resurrection Remix, Lineage, and AICP. All Android 7.1.1.
I've tried different builds, different builds for gApps, different versions (nano, micro, stock).
Tried the usual clear cache etc. stuff for Google Play that you find online. Tried installing a new Play Services apk from apkmirror.
Nothing works, it's the same thing every time. Recovery, Wipe, Install Rom+gApps, Reboot, Play Services crash.
It doesn't seem to have to do with the ROMs.
Any ideas are greatly appreciated.
So I found something while looking for answers that seems to be my problem, but I don't really understand what this person did.
https://forum.xda-developers.com/showpost.php?p=58818703&postcount=4
Somehow, after many hours spread over the last week, last night I seem to have fixed it.
I had suspected that it was an issue with a corrupt partition, (or permissions, or something!) on the internal storage, as it was only when I tried to download something that the browser crashed, and Play Store would generally only start crashing after a first time browsing with it. Also sometimes from within Recovery I wouldn't be able to wipe data properly (it would complete almost instantly, sometimes not removing a previous ROM...). Sometimes it did seem to work properly though.
I can't pin down exactly what I did that fixed it though. I tried 2 things at once: I manually wiped each of /system, /cache, etc through fastboot in the bootloader, and I also (from adb in recovery) manually did mkdir /data and mkdir /data/media
Click to expand...
Click to collapse
Can someone help me with this, what exactly did he do? When I go adb reboot-bootloader the phone restarts normally, I'm not going into a fastboot mode. And mkdir says the directory already exists.
Stupid question, are you using TWRP 3.1.0-1 by BlastGator? I remember reading something about the recovery being associated with this issue, I just don't remember where.
http://www.gregtwallace.com/lgg2-projects/twrp/
alarsama said:
Stupid question, are you using TWRP 3.1.0-1 by BlastGator? I remember reading something about the recovery being associated with this issue, I just don't remember where.
http://www.gregtwallace.com/lgg2-projects/twrp/
Click to expand...
Click to collapse
YES!
But I think I tried it with 2.8.xx as well, but I'll try again just in case.
Edit: So I tried it, to no avail.
Boot to Rec, Flash TWRP 2.8, Reboot, Wipe, Flash RR and Gapps, Reboot, Google Play Stopped.
Am I missing a step or anything I should try different?
I installed TWRP and root with SRK Tool 2.1, maybe there's something wrong there?
I have exactly same problem with you. I've tried many flashing methods and it went fail and fail again. Please tell me if your problem have been solved. Anyway I'm at CloudyG2 3.3 right now and using TWRP blastgator 3.1.0-1.
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.
Okay so, ive tried every 6.0 ROM on the Shield forum for my portable and they all seem to have app crashing issues with the 6.0.1 pico Gapps (Setup, Play services, framework, play store all crashing, boot loops etc.)
I noticed i dont get these crashing errors whenever i boot the ROMs with no Gapps.
I spent hours and days researching why the crashing happens and ive seen things from "outdated/corrupted SU binary" to "incorrect permissions for 6.0.1 gapps" and i still dont know the cause.
SO i figured id try the apk route. i went to a certain APK site (not sure if we can link those) and grabbed every version for each gapp to see if i could get any of them installed. I found out when theres a corrupted app or incompatible app, android OS doesnt show the image for said APK/APP so i was able to weed out which apps would work.
Linked here are the apks i used to get the MM roms working with google/google apps again.
Install the PICO 6.0 GAPPS and then these APKs after getting into the OS to get going
The Pico-Apps are gonna make the initial boot time longer-- dont worry just let it load everything up (sometimes i had to button mash the shield button & home buttons to get past the boot animation-- sometimes it works and idky)
after installing all of the APKs, reboot the system, the OS is gonna initialize your apps again, might do it twice. after that youre good to go.
https://drive.google.com/drive/folders/1T9AXTYFcLg-dEUAfA7LdksUo_oPZ9yIl?usp=sharing