Just started to have issues downloading apps from the market. Im on any connection and im connected to the internet but they fail right away with this message "Download Unsuccessful" ..........rooted too. Any Ideas?
*Edit*
I need some others to check this out
Last night I reset to factory defaults and after 1-2 downloads from the market everything after I tried to download fails, rooted. Then I flashed the stock firmware downloaded a couple apps no problem, rooted, couple more downloaded then FAIL! Not able to download until I do a factory reset, even than I can only get 1- maybe 2 downloaded.
I'm having trouble as well. I'm rooted, I posted yesterday but nobody replied. Can somebody out hedre try and install fring?
Rooted. And no problems.
Are you signed into Talk for authentication?
I had similar problem on my EVO yesterday as well.. So i don't think it's a phone issue...
-CC
I did a reset back to stock pulled down a couple apps then dead after that...CAn anyone pull apps off the market right now?
I was having major problems with apps, then I did a cache wipe and factory reset. Problem solved.
I was also restoring apps from mybackup pro, which may have caused the issue. The apps were backuped from my evo and restored on the epic.
Its a apk I removed just don't know which one :/
I take that back...I lost market functionality again and have not removed any files only rooted AM i the only one experiencing this?
I rooted (using the older line by line instructions, not the single automatic script) and have not had any problems with the market.
i rooted with the one click script and have been downloading apps with no problem, downloaded an update to gps status tonight on 3g and barcode scanner over wifi tonight.
Im having the same issue, I rooted so i can do free wifi tethering (hotspot) and now i cant even download the ****ing app to do so.....
Hi,
The problem that I have is that everytime I turn on my S4 "Messages" crashes and afterwards "com.android.phone" keeps crashing.
It started when I was on Google Chrome Beta where I got a few crash notifications (I think it was 2, don't remember). I didn't think much about it then, but when I went to the Play Store to install Chrome, where it said it was already installed. Recently I have removed a lot of the bloatware including Chrome on the S4 and nothing happened by it and I have restarted my phone a few times after that. But in the Play Store when I clicked on the uninstall button it got stuck on uninstalling (most likely because it wasn't installed in the first place) and when I restarted my phone thinking it might solve the problem. The whole problem with "Messages" crashing and afterwards "com.android.phone" crashing again and again, started.
Now I have to keep Flight mode turned on or I can't even use my mobile.
I have tried following solutions:
- Wiped Cache & Dalvik Cache
- Factory Reset
- Reinstalled all the bloatware
- Reinserted SIM card
- Removed sdcard
My phone is a Samsung Galaxy S4 I9505 (XXUAMDM) - Root - Stock rom
I hope someone can help me figure out how to fix this.
I found out what the problem was. I didn't reinstall all the bloatware. I only got the first 20 installed instead of them all. So now it works again.
Hello!
Please help, this is driving me insane.I've had a galaxy S4 for almost a year now. I had it rooted and ****ed around with it a bit, it was all good. Then I was running low on space and got a disk checker or whatever it's called to show me how my space was being used. A lot of it was in caches. I downloaded a file manager and went on a cache deleting spree. One of the caches I deleted was google. Ever since that day everytime I start my phone:
Samsung Link has stopped
Dropbox has stopped
Google + has stopped
Google search has stopped
The phone in general just worked extremely ****ty.So I decided today that it was time for a factory reset. I run it, all good. The phone restarts in factory settings.. and I get the exact same error messages. ?So I decided that I would do the hard reset. Shut it off, volume up + home + power, wipe/delete all data. EXACT SAME PROBLEM. WHAT?How is that possible? I wipe my phone completely and end up with the same problems? How do I reinstall the OS? Since I'm going to be uninstalling the OS completely (probably the only solution to my problems), is there anyway to get a nice clean OS? And not the one full of bloatware from my carrier? I really just want to start over from a fresh OS.
I also tried just running a software update, but I got the error message 'this phone has been modified and cannot be updated'. I guess that's because it's rooted..
Thank you for your help
i checked manually for upates, 15 minutes ago. It showed me that an system update is avaible.
Update installed, rebooted and here starts the wierd things.
-Phone boots up but the only thing im able to access is the ''edge'' bar where is the edge people and other fun features.
-Pressing volume button down will bring the boot menu with : reboot, shutdown etc..
-Tried to boot in safe mode. no luck, only the safe mode bar appears in the left.
-Wiping cache, no luck.
-Not rooted. Stock.
Only thing that i installed outside the play store is the samsung lab application wich is shared here in the forums because its not avaible for s6 edge+ for some reason in the samsung's app store.
I managed to boot in recovery mode and this text took my attention : mmb29k.g928fxxs3bqa9 (frimware codename?) 6.0.1 android version
Made factory reset, works now but lots of important data (pictures, music etc..) lost in that.
I made an google search with mmb29k.g928fxxs3bqa9 and found nothing.
(edit: In the download folder, there seems to be a file with the rom build number/number)
Yeah I had the same problem, posted about it in the general forum. I flashed another stock ROM ontop of it from Sammobile and it saved me from doing the factory reset.
Tondern said:
Yeah I had the same problem, posted about it in the general forum. I flashed another stock ROM ontop of it from Sammobile and it saved me from doing the factory reset.
Click to expand...
Click to collapse
After the factory reset its been running fine with the update. I alerdy emailed samsung about this.
justanpotato said:
After the factory reset its been running fine with the update. I alerdy emailed samsung about this.
Click to expand...
Click to collapse
they are still sharing it.
Someone who's phone updated correctly needs to make these guys a firmware they can flash back with Odin otherwise they won't be able to find anything that works. (no downgrades allowed)
Make sure you backup what you can. Export contacts, everything on Phone when you connect your computer can be copied in/out, if you didn't know. App data will have to be individually backed up.
Hi,
A few days ago I experienced a boot loop on my Nexus 10 with Lineage OS 13, build 20170909.
I broke it down to a recent update of Nova Launcher - going back to an older version and preventing Google Play automatic updates fixed it for me.
There are a number of reports of the same symptom pointing to Nova Google Companion, TeslaUnread, IFTTT, and Action Launcher.
I don't think this is an issue in those apps, but rather caused in the OS - an App should not be able to bring down the OS to a reboot (and even worse, due to the automatic restart of the launcher, causing a reboot loop).
any ideas of a fix in the OS? something else to prevent this from happening again?
Regards
sthones
I confirm the same. Constant bootloop with Nova Launcher
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
stephendt0 said:
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
Click to expand...
Click to collapse
I had the same problem with a Galaxy S3 running OctOS (CM13 based Android 6.0.1). The Nova Launcher update caused my phone to crash and reboot as soon as it was unlocked.
I was able to disable Nova in recovery (TWRP) using the built-in TWRP file manager. navigate to /data/app/com.teslacoilsw.launcher/ and delete base.apk. This will keep Nova from loading on startup but will not delete your data. My phone worked fine after that, albeit without Nova.
Thanks a lot, removing base.apk stopped the reboot loop.
My device has just started a bootloop too, but I don't even have Nova installed on it (though I do on my phone), just the stock launcher in CM / LineageOS.
I reset it to factory defaults and then it boots, but when it restores my old apps it starts looping again, so one of them is the cause. I didn't learn anything from the log via adb.
Any ideas?
I discovered it was one of my apps causing this. I removed it and it boots ok. https://play.google.com/store/apps/details?id=au.com.realestate.app&hl=en
hmoffatt said:
I discovered it was one of my apps causing this. I removed it and it boots ok.
Click to expand...
Click to collapse
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Happening to me now, ffs im on the latest nightly and thats not fixed it.
TheRealSmurf said:
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Click to expand...
Click to collapse
Same here.
daseddy said:
Same here.
Click to expand...
Click to collapse
Mine just started boot looping yesterday, but I hadn't installed any new apps in a while, and I have automatic app updating turned off (I also don't have any real estate apps installed, German or otherwise). Any hints on how to track down the culprit? Is there a boot log to look at?
Thanks!
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Same here. Started happening after it updated my apps yesterday. Removed nova launcher and all other Teslacoil software, problem remains. Can only start the tablet in Safe mode.
Seeing this on my device as well, except I am not able to remove the base.apk file because the app I installed somehow corrupted my bootloader such that I cannot get into recovery mode.
The culprit app? LinkedIn. Automatic app updates were turned off, and just before the bootloop started, the last thing I did was install that app. It finished, it rebooted, and hasn't stopped rebooting since.
When I put it into bootloader mode, it stops the continual rebooting and displays the "open panel" robot and "Downloading... do not turn off target". From there, all I can do is press power to start, then it goes back into rebooting. There is no way to get into recovery mode from there.
Also, attempting to keystroke into recovery mode just restarted the lineos infinite reboot.
Can't get into recovery, can't get the bootloader out of "Downloading" mode, and lineos continually reboots... Any wise sage souls have any ideas on this one? It looks like my device is bricked
It got me too - I don't have Nova Launcher installed. A few weeks ago the device started bootlooping with a build I had installed since september. I updated to one of the latest builds and had the same issue again. At the moment i got it working most of the time, but when i start certain apps it just reboots.
Seems to be independent to build version and can occur with different apps (at least thats what I've read here...).
Is this a Lineage Os 13 only thing or can I throw the device away now?
Greetings
I started having this issue this week as well. Oddly enough, I was still on CM12.1. In the middle of watching Plex and it rebooted, and has been boot-looping since. I did a factory wipe and while installing apps, it started looping again. I then installed the latest nightly of LOS13.1 and again, once it got part-way installing apps, it started boot-looping again. So this is not just a LineageOS thing, it seems to be an app update (I do have auto-update turned on).
I´m having the same problem without ever have the Nove Launcher installed. The bootloop started on my device several weeks ago. I tried to fix it by wipe partly or total and reinstall the latest nightly of los13 (20171126) and opengapps micro 27.11.2017 (and everything else).
As soon as I reinstall my apps, los goes back to bootloop. Sometimes, when I manually install only few apps, the system seems stable, until die next updates come by the play store.
So now I went back to stock rom until I´m getting aware of the problem beeing solved.
workaround, maybe
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Removing offending apps works
Thank you!
I did the same with your advice... removed some apps and it works. I went back to September ROM, then update to Nov ASB ROM and it works fine.
ShevT is on it, here https://jira.lineageos.org/browse/BUGBASH-1052
and here: https://review.lineageos.org/#/c/197386/
Hope it gets fixed and merged soon... as this has been a pain the neck for a while, possibly related to a similar problem earlier this year.
loveandmarriage said:
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Click to expand...
Click to collapse
I'm running CM13 and I have the same problem. I am not tech savvy with installing ROMs but managed to get to TWRP and did a reset to factory. Got part way thru optimising apps and the problem came back. I could only turn the tablet off via TWRP!
I don't mind going back to stock rom but not sure how to do it..best I look on here and start to educate myself..I'm 73yo so might not get finished before my time is up