My N7 is rooted and encrypted (manually, no toolkit) with stock rom.
I left it unattended for a couple of days, and when I flip open the cover, there's a process called "myls" asking for root permission. I denied it twice, and hasn't been asked since.
I went to terminal and tried to find the process/file named "myls" and found nothing. Nothing out of ordinary shows up on installed apps list. Search for myls+android yields nothing relevant.
How do I find the app/process responsible for this root request? Is this something I should worry about?
Thanks!
Sent from my Nexus 7 using xda app-developers app
bump
I have the same process now requesting root access on my galaxy nexus phone. I am rooted and running codename android ROM. I'm also curious to know what this myls process is that would like root access...
Hi. I was curious too about this process who popped up today asking for su after i was playing with scripts etc. Then i searched on active processes from terminal and noticed that myls proc is used by ScriptManager app ?. I'm using that app from two years and today is the first time i see myls proc. Maybe that's depending on what script we use with the SM's widget becouse myls popped when i run the "flush.sh" script of V6 Supercharger from the widget. You can try yourself: type su on terminal, then type ps and check the aplication that has the same USER as mysl. On my case is app_91 same as SM. Hope that helps ?
Bump?
Yeah, this requested access after I rebooted my CM10 device. My only root apps are:
Titanium Backup
AdAway
SetCPU
Pimp My ROM
PDroid 2.0
Script Manager
Root Explorer
Android Firewall
GOO Manager
Lucky Patcher (for an irritating license nag -I pay for my apps)
BusyBox Pro
SuperSU (paid version)
I run v6 and KAK scripts, too but have been doing that for ages. It's the randomness of it that I find suspect. Any further thoughts in this would be quite helpful as this seems to be the only discussion about it on the internets, period.
Hi,
I recently rooted my Galaxy Note 4 (SM-910-C). At first when I was trying to change the Boot Animation I was able to copy files specifically "bootanimation.zip" to the "System/Media" folder using ES Explorer. Now whenever I try to copy that type of file or a "bootsamsung.qmg" file the phone just reboots itself. When the phone restarts and I go back to the folder I find the file is there but only with a size of 0.00 bites. Which means it did not copy correctly. Does anyone know why the phone is suddenly rebooting? Is it possible that the root is corrupted some way? Please advise how I can fix this issue. Thanks.
If you could produce a catlog we could look into it and assist you. Request you to produce them. Have u installed any xposed modules ?
Module
aukhan said:
If you could produce a catlog we could look into it and assist you. Request you to produce them. Have u installed any xposed modules ?
Click to expand...
Click to collapse
The Modules I have installed using Xposed are:
> Amplify
> Grennify
> Recent App Cleaner
> Wanam Xposed
YouTube AdAway
How do I produce the catalog?
Amplify should be causing the issue even I had same I've cleared the amplify data now I've not timed any wake locks, I would you to do same and try. Also I would suggest you to install Samsung server crash fix module and enable it to check if your still facing the issue.
Still
aukhan said:
Amplify should be causing the issue even I had same I've cleared the amplify data now I've not timed any wake locks, I would you to do same and try. Also I would suggest you to install Samsung server crash fix module and enable it to check if your still facing the issue.
Click to expand...
Click to collapse
Ok, I did as recommended but still have the same issue... how do I get to the correct log file or catalog to understand the issue better?
malmihdar said:
Ok, I did as recommended but still have the same issue... how do I get to the correct log file or catalog to understand the issue better?
Click to expand...
Click to collapse
Kindly install Catlog and from there you can extract the log file.
Hi, after I unlock my phone screen, BusyBox is often open. I always close it and when I unlock again, the busybox window is still open
My question, How to know which app or what process launch the busybox windows ?
Nougat 7.1.1
Rooted with SuperSU SR1-SuperSU-v2.78-SR1-20160915123031
TWRP twrp-3.0.2-2-angler
Elemental X Kernel (Left Swipe Sleep and double tap gesture activated)
Viper4Android (ARISE+Sound+Systems+Leviticus+1.3)
Themed with Pixel Experience - Update v9
tomz997 said:
Hi, after I unlock my phone screen, BusyBox is often open. I always close it and when I unlock again, the busybox window is still open
My question, How to know which app or what process launch the busybox windows ?
Nougat 7.1.1
Rooted with SuperSU SR1-SuperSU-v2.78-SR1-20160915123031
TWRP twrp-3.0.2-2-angler
Elemental X Kernel (Left Swipe Sleep and double tap gesture activated)
Viper4Android (ARISE+Sound+Systems+Leviticus+1.3)
Themed with Pixel Experience - Update v9
Click to expand...
Click to collapse
You mean the busybox app is open? If it's the STEricson one it doesn't do anything other than update the binary.
Logcat should tell you what's going on though.
krs360 said:
You mean the busybox app is open? If it's the STEricson one it doesn't do anything other than update the binary.
Logcat should tell you what's going on though.
Click to expand...
Click to collapse
Yes that's the Stericson busy box... yes I mean open after an unlock even if I closed it (swipe to remove app from "running" app) It's not a big problem but It's annoying
Where the logcat are located (path) ?
In attached file : Image of opened windows after unlock
tomz997 said:
Yes that's the Stericson busy box... yes I mean open after an unlock even if I closed it (swipe to remove app from "running" app) It's not a big problem but It's annoying
Where the logcat are located (path) ?
Click to expand...
Click to collapse
I would clear the app data/cache for the app, then uninstall and re-install it.
I use this app to read logcats: https://play.google.com/store/apps/details?id=com.nolanlawson.logcat Or just adb it.
krs360 said:
I would clear the app data/cache for the app, then uninstall and re-install it.
I use this app to read logcats: https://play.google.com/store/apps/details?id=com.nolanlawson.logcat Or just adb it.
Click to expand...
Click to collapse
Thanks for the suggestion, i'll try it !
PS- Logcat flooded with LightFlow events almost unreadable! lol
Clear Cache + Data didn't solved the "problem" ..
It doesn't everytime so it's no easy to diagnostic with Logcat (as mention earlier, lightflow flood the logcat!)
Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.