Related
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.
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
A factory reset clears all user data & apps. If you deleted the phone app from system, you will have to reflash a stock zip, which I'm assuming you don't have, or find the stock apk and put it back in the right place as a system app.
If you have Titanium Backup you can use that to do it, provided you can find the stock phone apk.
Well, a problem is, I doubt that I will be able to find any ROMs or Phone.apk's for my device. At least not for a little while. There are some ROMs out there I believe for the original Blu Touch Book - but the original has a diff processor and is running Froyo rather than ICS.
Now, if I somehow can find a workable Phone.apk or a workable ROM, how do I go about flashing/copying? I can hook up to a PC (though I'm not aware of any USB storage mode that I can turn on), but the phone itself is just about unusable unless I can manage to delete the wrong Phone.apk file, as long as the file is simply missing it will boot up without the relevant features. And - let me repeat that I did a factory reset to try and fix this - it didn't fix my problem but it erased my apps and my root access....I can probably restore root but it won't stop the warning notification from popping up non-stop.
I was able to boot into safe mode previously - but it didn't help. If there is an applicable recovery mode, I can't figure that out. To my knowledge, there is no USB Mass Storage option that I can turn on.
I purchased from Amazon, so luckily I can return the item, and worst case they review it's condition and charge a restocking fee. Of course, I was looking forward to receiving this device for more than a week and have been obsessed with it since it's arrived...and I am also temporarily back to using Sprint (in Phoenix) on a 3.5" Windows Phone (I am an ex Windows Mobile fan boy, Windows Phone disappoints) after experiencing 6 MB/s 3G speeds on T-Mobile for a day or so (on a 7 inch screen and on a prepaid plan far cheaper than what I pay Sprint). I was about to port my number. Basically I am depressed. An irony here - I'm pretty sure Amazon sold me a used device that was advertised as new. On initial boot, the Android set up program did not launch. Upon my first factory reset, the set up program launched, and the dialer skin was different than what it was out of the box. The 'refuse product if this seal is broken' sticker on the packaging was partially broken, too, although it appeared to be partially in tact. But now if I try to play that angle, I come off like a scam artist...
Anyways thank you very much for your reply...all attempts to help are appreciated quite a bit...
Taking things one step at a time, let me simplify my request:
How can I delete (or replace) a system file from my device (in this case, the incorrect Phone.apk) remotely via a USB connection? I have the sdk installed on my computer, I can connect the device to my computer, but I can't really use the device until the file is deleted. Is it possible to push via ADB? Something to that effect? Will the 'push <local> <remote>' command work even if I do not have root access? What syntax is used to specify the path? Is it possible to simply delete a file without replacing it?
Does the Phone.apk file have to be specific to my device or could it be specific simply to my mobile carrier/frequency bands and/or ICS? I realized the Phone.apk file I copied to the device earlier was for the Huawei m835, a CDMA phone running Froyo...
Or, am I simply SOL?
Thanks....
One of the things about Android devices, as a former Windows Mobile user also, is that factory resets work differently as you've found out the hard way. In WM you could delete any system file you wanted and a hard reset would restore it. On Android if a required /system file is deleted you are SOL unless you have a way of restoring a backed up version. Its highly recommended IMO to have a working recovery like CWM, TWRP and a backup before you go messing around with /system files. But with a generic android device its probably not possible to find a recovery to install. You cannot write to the /system directory without root access, adb will give you an error. You may be able to use a phone.apk from another device with the same version of android.
I did find a Phone.apk from a device with the same manufacturer, on the same frequencies, with the same screen res, running the same version of Android. I have the full System/App folder if needed.
And I may have restored root access using UnlockRoot (I have read iffy things about the program but again it's all that worked for me initially). (EDIT - I do now have root access, I was able to verify the Superuser app on the device)
However when I load the SDK and type in 'adb root,' after the 'daemon started successfully,' I quickly get an 'error: closed.' And then when I try to push the Phone.apk file to the relevant folder, I get 'failed to copy / permission denied' (EDIT as I was warned of)
Is there anything I can load onto my SD card to help? I can run probably install an APK off of my storage card. Although I am very limited in what I can do - between error messages I can only get in one quick touch of the screen (and it usually takes a few tries per touch)...I can't do anything that requires a long-click...and I had also deleted the stock keyboard and the stock browser...limits me further...
Now, if I can delete my current Phone.apk and upload the stock keyboard, I am certain I can figure this out. There has to be some way to do this....
EDIT// I packed it up to return to Amazon. If there was a solution out there, oh well...
Like I said you may have been able to use Titanium to install it as a system app and that may have taken care of things once you set it as the default app and/or removed the faulty one.
^^ Right, but the challenge was installing Titanium Backup, and then using it while the error notification popped up on the screen every split second. Unless I am missing something, only way to download it would have required me to buy a Bluetooth keyboard and struggle to pair it so I could type (I had a USB keyboard that didn't work), maybe reassociate my device with my Google account (struggling to type letter by letter between each 'OK' click), have the apk sent to my device over unsecured wifi, put the .apk on SD (or just delete the wrong apk and reboot), and then hope that I could use Titanium backup to do the trick without the ability to press anything on the screen for longer than a half second or so...
Actually, I guess that could have worked, provided the Bluetooth keyboard worked. Of course, there's the chance that the Phone.apk I found for the similar device, might not have worked. Anyways, late now. I have a new one on the way, and I was shipped a slightly used one to begin with anyways, might be for the better. I kinda feel bad that the phone is now 'defective' as a result of my impatience/etc but then again I didn't do anything that the instruction manual warned against, not to mention the instruction manual says a factory reset restores factory data, which I think infers that it restores essential system components. And as much as I was an idiot, I don't do anything which should have caused a nearly non-recoverable error. That's on Google's end. Google doesn't even really discourage rooting and if you allow Android on a device with 512MB rom...
Learning experience. One of the first things I do when I get my new one, I download a backup program and find out if there is a recovery mode. In any event, I won't make the same mistakes twice. Thanks to those who replied or considered replying. Anybody has tips for the future, that aren't obvious or easily found, feel free...
If u r rooted this is very easy.
Open sdk and type su if u get "#" then u r rooted.
If so let us know
---------- Post added at 10:05 AM ---------- Previous post was at 09:34 AM ----------
as a rethought I see u deleted system app so u were rooted
---------- Post added at 10:21 AM ---------- Previous post was at 10:05 AM ----------
Firstly adb pull the file "/proc/mounts" open it using notepad and see how system is mounted.
then remount system as rw using
"mount -o remount,rw -t yaffs2 /
<path to your system> /
system"
Now u can delete stuff or add new stuff without perm error
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
caponer said:
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
Click to expand...
Click to collapse
Eh, I already sent the phone back to Amazon. This, however, looks like a useful something to have access to in the future. Thank you for the link...
No way. Come on,why did u send it to amazon when u had me right here we could have fixed this so easily.
thref23 said:
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
Click to expand...
Click to collapse
Could you share how you did a factory reset please?
wizardofkoz said:
Could you share how you did a factory reset please?
Click to expand...
Click to collapse
Settings/Backup & reset/Factory data reset
Rooting Help
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
androidhelp1234 said:
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
Click to expand...
Click to collapse
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
DOH!
thref23 said:
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
Click to expand...
Click to collapse
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
LeeMarden said:
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
Click to expand...
Click to collapse
You do realise that this thread is 3+ Years old , right ?
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.
I rooted my S9+ following this thread:
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Since I tempered with some files in the folders data & android and a few others the root access for the modded camera app from zeroprobe says: „check root access“ and it won’t work properly.
In twrp boot mode, I tried wiping and all the apps I previously installed were gone, but upon reinstallation of said modding app the problem remains.
Is there a specific folder I should wipe or how would I go about starting from scratch?
And no, I didn't take a backup yet... (at least not on this phone, but on a second S9+, could I use that one?)
got it working again. As so often when assuming something, the problem was apparently not that I copied some files around. It seems that I needed to start magisk at least once. After that it worked. The modding differs slightly, maybe due to an update of the app. Just guessing here, but at least i got it working.