Sony Xperia SP C5306
Jellybean 4.1.2
Rooted
I'm having an issue, wherein the stock browser uninstalls itself on every boot.
The .apk is still in the 'system/app' folder but the icon is gone from the app list, and when I try to open a link, I'm told there is no application with which to perform the task.
I've deleted the app and it's .odex file, as well as the data in 'data/data' etc, and reinstalled it both manually as well as with Titanium Backup.
It works fine, (using it now in fact), but upon rebooting, it's gone again.
The only thing that has significantly changed prior to this was the installation of 'Cydia Backport'.
After uninstalling 'Cydia', I lost the browser.
I reinstalled 'Backport', hoping to regain functionality, but the issue persists.
Also, when I boot into TWRP and attempt to backup or restore, I'm informed that it was unable to 'unmount' the system.
This behavior did not pre-exist 'Cydia' either.
'Cydia Backport', is intended to insert recent Android security updates, into older OS's.
Any ideas, folks?
Is there a command somewhere in the boot script that could be doing this?
If so... Can I edit it?
I, have emulators and editors available, I just can't find the 'uninstall your browser every boot', command.
Is boot logging available somehow so I can see where the command initiates?
:-S
Solved!!!
As per usual, I slashed and burned, and raped and pillaged, and after a harrowing fight with the demon, I once again have full control of my browser (post boot), and 'Cydia' is a thing of the past. No thanks to Avast, and Malwearbytes - neither of which detected significant changes to the OS.
Why doesn't Android have an equivalent of Windows SFC???
Related
I'm sorry if I stuck this in the wrong place. I'm not actually developing a ROM for consumption; I'm just customizing what I have a bit so this seemed like the best place.
I'm clearly doing something wrong. I just need help figuring out what that is and how to fix it.
I've tried integrating the latest build of "Flash" into my ROM several different ways. Everything I've tried failed in exactly the same way. Classic animations like games and things work fine, but encoded movies do not work. (The movies on YouTube don't work.) A simple version check shows that there was no change in the version.
I am rooted. I have a terminal emulator and a file browser installed. I have `adb'/`fastboot' ready to go. I have managed to integrate many other bits and remove many others simply enough following the various tutorials here at XDA.
I grabbed the latest update and tried to integrate it manually the way I did in the past on my Sensation by simply copying the relevant APK and SO to the relevant directories. (Copying the file `libflashplayer.so' to `/system/lib' for example.)
I tried using a script from these forums. It didn't work. It wasn't written specifically for the Flyer. That might have been the problem. I don't know what all HTC does to "Android".
I also tried using the "Convert to System App" feature of "Titanium Backup". It didn't work and after used "Titanium Backup" to revert the APK as a normal user installation movies stopped working. (Movies work fine until I try integrating it when I install the APK normally from my computer.)
I think this matters, but I'm not entirely sure. Anyway, I did restart after each attempt to integrate the APK/SO. I've also tried clearing the cache with "CWR" after an attempt to integrate.
I've been rooted for a while now on my Sensation and View. (I also have a rooted Flyer.)
Sorry if I've managed to overshoot in the "include relevant information" category.
Cheers,
Soma
So I used the ACS/Shabbypenguin root method (do a Google search, I can't post links...) and followed the directions exactly. Well almost exactly, I knew of some issues so this is what I did...
First I downloaded Superuser & Superuser Elite (I previously paid for it on a different phone).
Then I downloaded the drivers and Odin and both kernals.
I installed the drivers and put my phone into development mode.
Next, I turned off my phone then turned it back on in download mode and flashed the pre-rooted kernal as per the instructions there.
Finally, I went through the process again to flash in the stock kernal.
Now the other users had issues with USB connection and the phone not being recognised, the answer to that was on page 11 of the above linked thread (editing the vold.fstab file). I did this (using ES Root Explorer) as per the instructions and restarted.
Things seemed fine for half a day. Now my phone randomly restarts, but not always randomly. I can perform specific actions to cause it to freeze and reboot (example, simply opening the vold.fstab file does this EVERY TIME, but I was able to copy/paste it to the SD card and then open and edit it and even copy/paste it back, all using ES root explorer, and no crash/reboot unless I open it specifically and yes, that's with having the system mounted as R/W).
Another thing I noticed since rooting, and it still has maintained the rooted status, is that any time my phone restarts or I restart it, I open the system tray and this stupid "tip" toast message comes up that, prior to rooting, only came up once. Now, it comes up only once after a restart but resets every time.
I tried to sign up for the ACS forums but for some reason, I've not gotten a single registration e-mail from them and messaged half their admin with no response (the fact that the site has no cancel account and no re-send activation option troubles me enough as it is and in my opinion, should be internationally illegal).
Anyway, that's the issue, I need to resolve these random restarts, which may or may not be caused by this vold.fstab file.
Also, I connect now (before when I did the fix, it worked), the computer doesn't recognise the phone so I can't even re-flash using Odin, but the phone works (until randomly restarting which is a pain...), so I am at a loss as to what the actual cause was and since nothing I change sticks when it restarts, I have no idea what the deal is.
Some more information...
Nothing I change sticks. I have programs that I uninstalled, but they still show up in the system tray after a reboot (if I click it, it says that the program is not installed, but it still shows up).
I tried swapping back the original build.prop - didn't stick.
I tried factory data reset - didn't do anything.
I tried a restore in BusyboxPro (stericon or something is the dev) - restored but there were some "errors".
Tried temporarily unrooting (Superuser Elite) - nothing.
I read about a power button issue - my power button is fine.
There is something wrong specifically with the OS in some way that certain actions cause it to freeze and restart. I have a game, "Deathworm" that I can play with no issues or freezes. I can do a few things but:
if I get on the mobile browser, sometimes it will freeze and reboot.
if I run AppManagerPro III, sometimes it crashes when calculating the cache size (always when it gets to 70/125 or whatever the total is, but always at 70 if it DOES crash).
Now I went into task manager and went through and cleared all the app data individually app per app. Before when I tried to do this (before restoring in Busybox, before restoring the original build.prop, etc), it would crash when I went into the downloaded tab of the thing to clear the cache. This time it didn't crash on me.
Other root stuff I have installed which was working before the random rebooting issue:
Script manager (free) and V6 supercharger (also unsupercharging wouldn't stick, which I tried before restoring the build.prop manually)
SuperUserElite
App Manager Pro III
SD Maid Pro
ES File Explorer (free version I think)
BusyBox Pro
SU Update Fixer
Screenshot It
After everything I just did, it seems to (for the moment) be working again, I am just waiting to see if it crashes again. So far I have opened and closed App Manager Pro III a few times and it calculated cache sizes with no crash. Right now, SD Maid Pro hasn't crashed yet open, hide certain tabs (clearing the data so I had to reset those options), close, reopen, scanned with system clean and app clean and actually did the app clean, so far no crashes (my phone would normally have crashed by now), cleared databases and no crash.
Also while I was in there, two programs I uninstalled via the system tray (menu button, edit, uninstall) that kept coming back were a buld.prop editor and some wonkey game (Fall down) or something, anyway those were in the downloaded section of task manager and I uninstalled them through there. Maybe that did it?
And no... still freeze, reboot and not saving any changes.
So far I've also tried uninstalling practically everything I installed and those changes aren't persisting (the uninstalled apps remain uninstalled, but reappear in the system tray or on the home screen if I had an icon there for it).
No changes I make to anything persist except things I save or copy to the SD card.
Tried factory reset again, still didn't stick.
So apparently SOME others have this issue without rooting, I can't tell, there's not a ton of reviews that I can find beyond "F*** STRAIGHT TALK CUSTOMER SERVICE THIS PHONE IS CRAP".
I hate to keep bumping this, but every time I have an issue, I am highly detailed in things and I NEVER EVER have EVER gotten a response EVER on this site, EVERRRRRRRRRRRRRR.
I really really really don't want to waste another ~$200 for nothing.
I would appreciate even a response of "yeah I have this problem too".
I don't want this to die like all the other threads I started...
Does anyone even have a clue as to where I can begin attempting to troubleshoot this on my own then?
What tools should I look into or what logs in what folders?
I know this post is very outdated but there may still be someone tinkering with these older phones still as I am.
Over the past few days I have been trying to get this Straight Talk Samsung Galaxy Proclaim rooted and working just for something to do.
I'm not one to ask for help to often so I end up doing a lot of reading and a lot of trial / error.
In my reading I have seen quite a few posts / comments around the net stating not to use the Shabbypenguin root method
as it is very buggy and unstable.... I can not tell you from experience so please do not quote me. I ended up using the TeamProlusion
root method and all has went very well other than a few minor problems I need to work out.
In all honesty I'm not real sure what I may post or may not.... ( Yes I need to REread the rules for sure ) but I
will leave this link for anyone that may be in need... Mods / Admins please feel free to edit this post if this is not permitted and
please accept my apologies.
Please google androidarea51
I just bought a Samsung Galaxy S3 SGH-T999L with Android 4.3, then downloaded Titanium Back-up, and then started removing several apps (in an attempt to strip the bloatware). Now when I go to Google Play and try to install a new app, I click the "Install" button and wait for the progress meter to reach 100%, but no "Open" button appears afterward (which used to happen). When I search my phone, there are no icons for any of the new apps I try installing.
Does anyone know which app I deleted that caused this problem? Thank you.
Put back you're nandroid backup. (I assume you make one before you start deleting some apps.)
Or flash a stock rom back without whipping. So you dont lose some data.
Send From A Devil3 - f2fs - Dualboot Jb4.3/cm11 Powered Machine
Have you tried rebooting the phone?
if you have installed TB then you have rooted the phone obviously. Explore your data folder from the root directory using TB or any advanced file explorers like Root explorer or Es file explorer. Find the apk files of the apps you have installed just to verify if your play store has downloaded the apps to your phone.
Also are you sure if you removed only bloatware or any core apks related to your android system... like eg: application provider.apk
I did not make a backup. Before flashing a ROM, I wanted to post here and see if anyone knows what app being deleted caused the behavior I described. That's what I'm wondering: Do you know which specific app being deleted would cause Google Play to have the described problem? When I try to install a new app, it gets to "100%" on the status bar, but subsequently fails to display the "Open" button. Everything else on the phone works flawlessly and I put a lot of time into customizing the phone with apps I like.
Having said that, I am curious about the option to flash a ROM that you mentioned. The reason I did not want an Apple phone is because they seemed to restrictive of options and freedom. But lately I am thinking about Google censoring AdBlock from Google Play, the EFF's criticism of doing away with AppOpps, and shoving Google+ down the throats of YouTube users. So, I looked into Cyanogen but my model of phone was not listed on Cyanogen's website for phones tested to work. I am interested to exploring the idea of flashing a ROM (which I never did before) but I definitely want to keep my 4G LTE functioning via T-Mobile. Any ideas?
Hi all! Please solve my issue - it is getting real serious. Before starting a thread I have already researched a lot about this problem and now, XDA is my second last hope!
I own a XOLO Q1010 (with Android 4.2.2) phone. Recently, the company has released KitKat update for this device. I was real excited about it as the new ROM has already arrived luckily to my phone as well! But, unfortunately, it is not that easy. I start upgrading by downloading the system update of 316.14 mb, and as soon as it enters Recovery mode, after few seconds, an error occurs. First, I thought there might be some problem with the Zip file, next, I downloaded update again and kept it at a safe place to reuse it.
Now, I don't know why but as I analyzed that error, it wrote:
warning:no file_contexts verifying current system
"/system/app/Browser.apk" has unexpected content,
installation aborted.
update.zip is not correct
I thought that once few months earlier, I disabled this browser app (after rooting) so that may be the issue. I'll update that browser and it will apply the update to my phone.
After this, I started troubleshooting.
I checked Browser.apk file, and saw that it was working fine.
After this, when I started Browser, it showed: "Unfortunately, the Browser has stopped".
I later reset the app preferences, but it didn't worked.
I decided to re-install the fresh version and paste it manually within /system/app folder.
I did as many times as possible and with trusted installers (like the one I got on some thread on XDA itself), but nothing really worked.
I decided to do clear the cache partition but that doesn't work either.
Right now, the browser is also not working and I cannot upgrade my system as well.
I have gone for Factory Reset as well. But as soon as setup completes and everything get backs to normal, I start the default browser, it pops-up the message again that unfortunately, the browser has..
So this is what bothering me a lot. I have already gone for a Factory reset and tried the methods that I was aware of and found suitable. But nothing actually worked. The Recovery still displays the same error as above and I cannot upgrade my OS to KitKat.
Tired and irritated now, please anyone help me.
Thanks in advance! :good:
I have the same issue.
I also deleted the system browser.apk.
_swarp said:
Hi all! Please solve my issue - it is getting real serious. Before starting a thread I have already researched a lot about this problem and now, XDA is my second last hope!
I own a XOLO Q1010 (with Android 4.2.2) phone. Recently, the company has released KitKat update for this device. I was real excited about it as the new ROM has already arrived luckily to my phone as well! But, unfortunately, it is not that easy. I start upgrading by downloading the system update of 316.14 mb, and as soon as it enters Recovery mode, after few seconds, an error occurs. First, I thought there might be some problem with the Zip file, next, I downloaded update again and kept it at a safe place to reuse it.
Now, I don't know why but as I analyzed that error, it wrote:
warning:no file_contexts verifying current system
"/system/app/Browser.apk" has unexpected content,
installation aborted.
update.zip is not correct
I thought that once few months earlier, I disabled this browser app (after rooting) so that may be the issue. I'll update that browser and it will apply the update to my phone.
After this, I started troubleshooting.
I checked Browser.apk file, and saw that it was working fine.
After this, when I started Browser, it showed: "Unfortunately, the Browser has stopped".
I later reset the app preferences, but it didn't worked.
I decided to re-install the fresh version and paste it manually within /system/app folder.
I did as many times as possible and with trusted installers (like the one I got on some thread on XDA itself), but nothing really worked.
I decided to do clear the cache partition but that doesn't work either.
Right now, the browser is also not working and I cannot upgrade my system as well.
I have gone for Factory Reset as well. But as soon as setup completes and everything get backs to normal, I start the default browser, it pops-up the message again that unfortunately, the browser has..
So this is what bothering me a lot. I have already gone for a Factory reset and tried the methods that I was aware of and found suitable. But nothing actually worked. The Recovery still displays the same error as above and I cannot upgrade my OS to KitKat.
Tired and irritated now, please anyone help me.
Thanks in advance! :good:
Click to expand...
Click to collapse
You need to flash stock 4.2.2 rom via spflashtools then update
My phone is a Samsung Galaxy Core Prime SM-S820L (Tracphone) running Psilocelium's custom KitKat 4.4.4 ROM (rooted, build.prop tweaked, init.d support, deKNOXed, deBloated, deODEXed, ZipAligned, etc, etc) flashed with Odin. I also have TWRP recovery v2.8.7.0 installed.
This is a little involved so please excuse me if my description is disjointed.
There seems to be a problem (two, actually) caused by installing BusyBox. The first problem is that it breaks AirDroid's AirMirror function. After installing BusyBox and rebooting, AirDroid program on PC no longer can connect via AirMirror to AirDroid on the phone.
When it connects successfully, when the PC interrogates the phone, there is a one-line SuperSU pop-up message reading "AirDroid has been granted superuser permissions." There are other messages to follow, but I'm speaking only of the initial SuperSU message. But if BusyBox is installed, there is a second line included in that initial message which reads, "kill -15 ..." followed by a process number. The process number increments upward each time the attempt is made to connect. I haven't been able to find out which process it's killing but I have determined (by capturing the output from a "ps" command in Android Terminal Emulator) that it's a process number higher than anything that was running before making the attempt to connect with AirMirror (so I'm guessing it's some AiMirror process that it's killing).
If BusyBox is installed, the attempt to connect via AirMirror ALWAYS produces the two-line initial SuperSU message with the extra "kill -15" line. And the Windows-side AirMirror application ALWAYS errors out saying, "AirDroid failed to get root permissions...."
Using the AirDroid web client, AirDroid itself connects to the phone fine but when I try to run the AirMirror function the phone shows the same "kill -15" message from SuperSU and the web client displays a generic "Failed to start service" message.
On one occasion when trying to connect with AirMirror from web.airdroid.com, SuperSU pop-up displayed the usual "kill -15" message followed briefly by a "kill -9" and the same process number. So whatever it is it's killing, it wants it dead pretty bad.
I've tried using several alternate versions of Stericson's BusyBox, from 5.5 back to 4.9. All that I've tried fail in the same fashion with identical messages.
I also tried this after wiping the phone, flashing to the stock ROM and rooting with KingRoot. Psilocelium's pared-down ROM is pre-rooted so I didn't have to mess with KingRoot. With KingRoot (and after BusyBox is installed), it fails identically to the pre-rooted ROM except that there is no telltale "kill -15" message as SuperSU produces.
I know there are methods for uninstalling KingRoot and turning over its duties to SuperSU but I haven't tried that yet because the advantages of Psilocelium's custom ROM are too numerous.
The second problem (seemingly) being caused by BusyBox has only occurred (thus far) when using Psilocelium's custom ROM. It sometimes but not always provokes the "Android is upgrading..." error. Whether the error occurs might have something to do with which other apps I have installed previous to it but as yet I haven't been able to pin that down.
It goes through "Android is upgrading..." and ends with "Unfortunately, the process android.process.acore has stopped," or "Unfortunately, LogsProvider has stopped" or both. Sometiumes there is a third message but they switch back and forth too quickly to read the one sandwiched in the middle.
At that point the boot process is halted and when I long press the power button, the button on the screen offering to let me reboot is blocked by the error messages, so the only way forward is to remove the battery.
I've found quite a few claimed fixes for this but the most of them seem to involve changes that only can be made once the OS has loaded. But when my phone is experiencing this problem, the OS won't load, even if I try rebooting repeatedly. What I have tried is clearing the cache cache by itself, clearing the Dalvik cache by itself, and then both caches together but the problem persisted. In every case, all I need do is restore a Nandroid backup from before I installed BusyBox and it boots normally.
Another claimed 'fix' involved disabling "System Updates" from within Application Manager but there is no such applet in my (Samsung) phone. And since the phone won't boot, the best I could do would be to clear its cache beforehand anyway. I do have a "Samsung Updates" applet but turning it off does not affect the problem.
I also have found references to the problem being caused by .odex files in the /data/app directory, but I have no .odex files in that directory.
Other tips said to delete the contacts but this is a clean install and I haven't yet populated the contacts manager. Still another said to edit the file /system/csc/others.xml and change the line that reads this:
<CscFeature_Calendar_EnableLunar> TRUE </CscFeature_Calendar_EnableLunar>
... to this ...
<CscFeature_Calendar_EnableLunar> false </CscFeature_Calendar_EnableLunar>
My 'others.xml' didn't have the line to start with but out of desperation I added the 'false' version anyway. It didn't help.
So if you know how either of these might be fixed, or even can point me to a resource that might help, I'd be obliged.
After a ridiculous amount of trial-and-error, I think I finally have it worked out.
Stericson's BusyBox was a no-go, all the way back to v3.0, for reasons I already detailed, even with the stock ROM installed. So I went back to Psilocelium's custom ROM and started auditioning alternatives to Stericson's BB.
Jrummy's BusyBox also was a no-go. It raised my hopes because it worked with AirMirror but every app I tried that relies on BusyBox denied that Jrummy's was installed.
But BusyBox X seems to have turned the trick. AirMirror still works and although I did have one instance of the "Android is upgrading ...," the upgrade completed successfully and has yet to reoccur.
I had meefik's BusyBox in the on-deck circle but I never got that far because BusyBox X seems to be doing the trick.
I hated to give up on Stericson's since it does seem to be the 'gold standard,' and I can't be sure there won't be any hiccups with BusyBox X because I'm waiting to complete the build-up (and grow some confidence in it) before I risk putting it into service and porting my existing number to it.
The best news is that this enables me to use Psilocelium's custom ROM. When I bought this phone I had hopes of running CWM on it (or even LineageOS) but I didn't then understand that, unlike my old LG phones, Samsung phones can have a slew of model numbers all sold as the same model name. Here's me thinking that if there's a CWM ROM for any Core Prime, there's a CWM ROM for all Core Primes.
So I'm glad to be able to use Psilocelium's ROM because it sheds so much of the google bloatware that there's close to 25% more free storage after a clean install, >1GB extra, despite the inclusion of SuperSu and Xposed.