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.
Related
BusyBox by STEPHEN & JRummy16 {confirmed} nukes WiFi, Bluetooth & Cellular Data
I had what appears to be the latest update to BusyBox by STEPHEN (STERICSON) nuke my WiFi, Bluetooth, and cellular data.
I was able to restore to an earlier backup which restored functionality. Once I installed BusyBox by STEPHEN (STERICSON) and went into it and ran it's internal install/update the above was nuked again.
Is there a different BusyBox we can use?
I saw 1 other person with this same issue... Anyone else?
How do we confront STEPHEN with this and see if he knows and can fix it before we all nuke our ATRIX's
update... I just created a recovery of my fully working system, went into Play, got BusyBox by STEPHEN, opened it and installed it, restarted phone and guess what....
WiFi will not connect to anything, Bluetooth will not come on and Cellular Data does not work.
CONFIRMED [latest, June 15, 2012] BusyBox by STEPHEN (STERICON) and the one by JRummy16 kills ALL data connections!
Are you replacing/symlinking all applets to Busybox? Do this can have the issue that you mentioned.
Also, have you tried installing to xbin rather than /bin?
I downloaded, installed, open and let it finish scanning and then use the Install, no changes to location or clicking any boxes.
I've done it this way with every update I receive.
What changed?
Nothings changed, however there was a bug with version 8.0 of my application which caused everything to be symlinked to busybox. This caused issues, like your describing, on some devices. However this was fixed with version 8.1 and above. Unfortunately, In order to resolve the problem, you need to reflash your rom which will restore the system applets that should not have been replaced by the symlinks to busybox.
After getting everything working, you should be able to use Busybox as normal to upgrade busybox.
Nope.... Reflashed the ROM... add the latest BusyBox, run it and bang. Once I restart all 3 fail.
I've had to flash it 3 times with this and the last couple of times I just made a recovery image before trying it.
Are there any alternative applications of this that we could try on the ATRIX?
Can I ask a silly question? Why are you trying to update it if the version you know works is not messing with things? Kind of a "if it ain't broke" thing to me.
Does this happen with all version of Busybox provided by myself, or does it only happen with, let's say, 1.20.1?
Whatever the latest upgrade is, as far as I can tell 8.4 as listed in Play. I also tried it with the other BusyBox by JRunmmy16 with the same results.
I would load an older one and check, if I had the apk to load.
...to answer pre4speed's "silly question"... Updates are out there for a purpose, I should hope, and I take advantage of them when offered unless I know of an issue and then I wait for the next update that we hope resolves it.
I don't mean the version of the installer, rather the version of Busybox. Select an older version from the dropdown and see if that works.
OK... I reloaded your BusyBox and restarted. No issues.
I have not run any of the internal "Install"
Question, do I need to run the internal install process?
I will come back to this later, got activities to attend tonight.
Stephen... Thanks for the help with this, I know I am not the only ATRIX user with this issue.
C0rr0ded said:
...to answer pre4speed's "silly question"... Updates are out there for a purpose, I should hope, and I take advantage of them when offered unless I know of an issue and then I wait for the next update that we hope resolves it.
Click to expand...
Click to collapse
I agree also with that. I am by no means saying you shouldn't try. And I guess by you testing the new version, you found a bug, reported it, and got a resolution. So Im truly sorry if I stepped on toes, I didn't think of that when asking. I do the same thing.
Lesson learned... pass it on.
... running good. Looks like as long as you do NOT open BusyBox and run its' internal install process everything stays working.
Lesson learned.
@pre4speed No sweat. I've "always" open utilities that I download and "ASS u ME" that you should be able to run whatever they offer inside them. My thinking is that if it is there run it... If it is a buried run command, I shy away until I find out more. As to BusyBox, all the prior installs I go into it and run the "Install" with no dire results. hence the thread...
Simply having the app installed does not upgrade Busybox, so you are accomplishing nothing by not running the install process.
This doesn't help fix the problem that you were/are having.
I don't know if it helps for debugging, but I've had the same problem today that the OP had. I'm on Nottachtrix 1.2.6.
Busybox installer showed up in my notification bar that an upgrade was available; I accepted it this morning (that is, I hit "Install" from within the Busybox installer app) and immediately my wifi, mobile data, and bluetooth were all dead. In addition, none of my root programs (Root Explorer, LBE Privacy, ROM toolbox, etc) would recognize that they had root access.
I then found this thread later this afternoon, and wiped/reflashed my rom which included the old Busybox version. That fixed the problem as you indicated. So far I have not re-installed Busybox installer; things are up and running with proper data access and all programs recognizing root, so I'm gonna hold here with everything running.
Are we talking about my installer, or Jrummy?
Also, Did you install 1.20.1 or an older one?
Could you test a new version if I provided it?
I will test it out... It does no good having an app that is "required" by other utilities if it nukes the phone.
Link me in a PM and I'll load it and tell you what happens.
Wish I'd have seen this thread before I tried to upgrade it.
Someone asked what the reason would be to upgrade BusyBox though. It can fix some Webtop2SD FC issues.
I'm currently with the same problem but on the Aura firmware. If i try to run any of the both apps to update my busybox it fails and leave it uninstalled.
I try the last version and a few older ones (1.19.4, 1.19, 1.18.4, 1.18, 1.14.3). Also i tried the Superuser updater to get the lastest su bin and it also fails when it tries to install busybox.
Right now on the JRummy16 installer it says:
Your device is rooted
Busybox Location: N/A
Busybox Version: N/A
System Storage: 39.78MB
Phone Model: MB860
ROM Version Aura 1.2.2.2
Click to expand...
Click to collapse
webtop2sd force close using the default busybox that come with the last rom build, thats why i tried to change the version.
Same here, I've tried to repair webtop2sd, using both installers, with 1.20 & 1.20.1 (didn't testes older one) but then system is unable to do any su or even use shell; none of the wireless connections work. I'll try older one. I'm on nottachtrix 1.3 with wraithdu's 1.19.4 busybox in /bin
Tab+ got nuked today Having hard time finding right firmware now to fix this. Wish I just left it alone and didn't try to update.
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
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
Background: I broke the screen on my Samsung Captivate Glide and realized I didn't have a decent backup except via MyPhoneExplorer and Google. I did replace the screen, so lack of a backup didn't bite me this time, and also bought a cheap rough around the edges second phone. I tried to use Helium without rooting to back up my phone and transfer to the spare, and is didn't work (somehow, permissions were not being granted). So I used the spare phone to practice and rooted it using CWMR and the current CWM superuser zip file. Everything went well. So, I did the same thing on my "real" phone.
Then the "fireworks" began. Every time I boot the phone, I get a bunch of unusual requests for root access. It slows the boot process to a crawl. Sometimes it seems as though nothing is happening, but it will evenyually get through the boot. SU Log shows multiple requests from "Kies via Wi-Fi" (which I don't even have enabled), "Settings". "USB Settings", "Android System", "com.samsung.InputEventApp","Application Installer", "com.samsung.app.playreadyui", "wssyncmlnps", "PhoneUtil", and com.sec.android.app.lcdtest". None of these should require SU access, and SU even warns that they don't declare "access_SU".
Once the phone finally gets through booting, all seems to be running well, though one other odd thing about this one vs. the spare is that SU shows up as using battery in Settings.
I suspect it is one of my apps that is creating the havoc, since the spare phone doesn't have all the same ones installed. And once I get a good Helium backup, I'm going to see if I can figure out which one. But before I start that painful process, I thought maybe somebody else can help point me to the problem.
I searched and didn't find anything like this in the forums. And what I did find on CWM SU was in device-specific forums where I don't think this is device specific since it only happened on one of two same model phones.
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???