Hey guys,
after years I finally had to update the apps on my mom's phone because what'sapp was about to quit working without it. I did that and after the first app update the phone crashed and ended up in a bootloop. It always crashes again when it says "starting apps". I also don't know which Rom I installed on the phone years before she got it.
1. How can I figure out the Rom name in TWRP?
2. How can I fix the bug without a full wipe?
Greez, skrippi
Related
Well hello! As you can already see I am a newbie into the site and the rooting community. I used odin to download CWM. I was happy I was able to root my S3. I then decided to back up my phone and apps blah blah blah. I rooted my phone to get the Premium Suite experience and I saw Hyperdrive RSL11 was close. So I saw a post on how to flash it and I was successful. I used Titanium and I got my phone back to normal. I then started to have problems. My Play store didnt want to allow me to download apps giving me an error ans such but i just erased my kelvin and cache. Once I restarted everything got worst.
The Play store situation got resolved, but now whenever I tried to open the message app it would freeze. I would either had to pull the battery or wait until it unfreeze. Now its just slow and freezes randomly when I open some apps. How do I fix this?
Sorry for the noobish question. I couldn't post on the official thread. I am starting to learn more by the hour.
I did a fresh install of the newer version of Hyperdrive RSL 12. Still freezes occasionally.
Don't restore system stuff, only data apps (play store apps)
T-Mobile SGS III
Thanks in advance for any advice given!
I was running Mahdi Rom, one build behind the latest, and all I can remember before things went tits up was I was updating a couple of apps through the play store.
Then I started getting repeated androidsystemui processs ended errors every few seconds. I rebooted into recovery and wiped everything through TWRP. Still got system errors after reboot, couldn't even get through the google account login and sync.
Downloaded the LG mobile support tool and flashed back to total stock -- can't go wrong, right?
Now I'm getting android.system.acore proccess ended errors, and Google Play won't run at all. Any hope, or am I fried?
Fingers crossed,
Yojimboj
Hi guys I hope i'm in the right place.
So i've had a samsung galaxy s3 t999v for 2-3 years now and just yesterday i decided to root and upgrade the rom.
so i've been messing with it and now in a difficult situation...
I installed Lollipop Custom ROM...
i followed this link
Everything worked out, i had installed the ROM and was working, but I hadn't put installed the GAPPS and when I tried to just get the apk files which i did but google services would keep crashing.
"unfortunately google services has stopped".
Now you may say, oh just go into recovery mode and reset to factory or w.e, well that's the thing... I can't get into Recovery mode.
and that's where I am now... Help.
Andro1dNoob said:
Hi guys I hope i'm in the right place.
So i've had a samsung galaxy s3 t999v for 2-3 years now and just yesterday i decided to root and upgrade the rom.
so i've been messing with it and now in a difficult situation...
I installed Lollipop Custom ROM...
i followed this link
Everything worked out, i had installed the ROM and was working, but I hadn't put installed the GAPPS and when I tried to just get the apk files which i did but google services would keep crashing.
"unfortunately google services has stopped".
Now you may say, oh just go into recovery mode and reset to factory or w.e, well that's the thing... I can't get into Recovery mode.
and that's where I am now... Help.
Click to expand...
Click to collapse
You can factory reset the phone in Settings > Backup and reset > Factory data reset. If that doesn't work, what happens when you try to get into recovery? It probably wouldn't hurt to try reflashing your recovery.
Just started to get this not so long ago, it seems that it will randomly reboot when it is trying to install app updates, but at times it will so it just because. No overheating noticed, phone have not been dropped or wet, no alterations to the FW were mad and it was running on it fine since install.
I did full cache wipe in TWRP, but that did not solve anything. Would like to refrain from full wipe and reinstall if possible. Any suggestions are welcome!
Mmmmmm, strange I've the exact same problem two days ago, I figured out that it happened after some apps required update and the play store wanted to install, But I've noticed that the problem with Snapchat latest update, it reboots and never installed, so I force stopped play store/uninstall Snapchat/grab the latest snapchat APK and installed it
Also I installed clean master X86 and done caches wipes just in case and that solved my problem, at least till now
While updating/installing apps from the google playstore, the phone will crash and bootloop, and requires a full reinstall to get it working normally. I've attached 2 logcat files for both roms which give the same problem - Mokee5.1, CM13 on a clean installation with pico gapps and manually selecting several apps to install. One other custom rom also gave the same problem so I didn't bother trying any other custom roms. Reverting back to stock MIUIv8 gave no issues.
CM13 used to be mostly problem free until a few months ago I think when the update/install issue started happening. The playstore auto update is normally kept disabled on my phone so I'm unaware about when the problem really started happening.
Edit-
It doesn't seem to be happening anymore from a short test after flashing my CM13 backup but I've moved on to LO14.1
It may have something to do with some other complaints that people are having. It looks like some issue with Cynogenmod since Sept/Oct 2017 which needs some patching.
https://forum.xda-developers.com/general/help/bootloop-updating-apps-telegram-t3700773
Update to/ Installation of newest version breaks system
https://github.com/signalapp/Signal-Android/issues/7171
Several apps causes a phone reboot or boot loop
https://gitlab.com/fdroid/fdroiddata/issues/979
Can confirm the issue with CM13 on my Galaxy S3. Unfortunately, I do not know a solution. Just stick to older app versions.