Related
Hello all.
By flashing my device many times, I am always fed up to plug it and remove all the application I don't want, or open the zip file, remove the apk and resign the ROM.
What I have in mind is making a little app that show us all the applications in system/app ( easy) and them when clicking on them just like a adb shell rm system/app/myUnwantedApp.apk.
The browser is easy to program, but the command line is not easy. I tried with eStrongs and Astro, but they cannot remove the apk..
Cam someone help me or teach me how to enter a adb command line in my phone?
Thank a lot.
profete162 said:
Hello all.
By flashing my device many times, I am always fed up to plug it and remove all the application I don't want, or open the zip file, remove the apk and resign the ROM.
What I have in mind is making a little app that show us all the applications in system/app ( easy) and them when clicking on them just like a adb shell rm system/app/myUnwantedApp.apk.
The browser is easy to program, but the command line is not easy. I tried with eStrongs and Astro, but they cannot remove the apk..
Cam someone help me or teach me how to enter a adb command line in my phone?
Thank a lot.
Click to expand...
Click to collapse
You can use a terminal emulator application like Better Term etc to run shell commands. There is nothing special about adb.
The command adb shell rm is simply running the shell first and then the "rm" command. Now, depending upon the ROM that you are using, the command adb shell will give you a root shell (or not). In any case, when you use a terminal emulator, simply use the "su" command to gain super user privileges (you have to have "su" and SuperUser.apk installed).
Since you are talking about a custom ROM, I think that root access is implied.
In any case, look at programs like Android Scripting Environment. It allows you to code scripts in an interpreted language like shell script, python etc... In your case simply write a shell script with the desired "rm ...." commands and execute them after gaining superuser permissions and make sure that your /system partition is mounted in rw mode.
I used the eacy one click to root phone. I would like to unroot it now. I am having touch screen freezing problem. I need to start removing applications to see which one is causing the problem or if it is a hardware issue or software.
I downloaded the zip file 1-click_exploit. I expanded the files and ran the application. I have read that there is an option to uninstall with in that file but I don't see one. Where do I find it. If I just do a factory reset will it remove it? If I do a reset do I have to repurchase all of my apps?
Thank you in advance!
A factory data reset will not remove root.
Also, a reset does not delete your purchases. They are all stored in your google account. So, if they do get deleted, just reinstall them.
As far as unrooting, I do not know. Someone else may chime in here...probably going to tell you to post in the Q&A section as well.
Doesn't the one-click have an un-root feature?
Sent from my bootloader-locked MB865.
The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app
Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su
kousik said:
Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su
Click to expand...
Click to collapse
I have no idea what the above manual steps are for. I can uninstall the application but where and how do I remove the su binary. On the phone? Please send directions for a non technical type of user.
Thank you!
MaTrixJ said:
The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.
bushbaum said:
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.
Click to expand...
Click to collapse
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/su
rm /system/app/Superuser.apk
exit
kousik said:
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/wu
rm /system/app/Superuser.apk
exit
Click to expand...
Click to collapse
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks
bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks
Click to expand...
Click to collapse
I was wondering do I have to have the elite version superuser installed to grant permission to system? I just have the free version.
bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Click to expand...
Click to collapse
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.
kousik said:
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.
Click to expand...
Click to collapse
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted
bushbaum said:
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted
Click to expand...
Click to collapse
Then try remounting manually:
Code:
C:\> adb.exe shell
edison$/ su
edison#/ mount -o remount,rw /dev/block/system /system
Afterwards proceed with rest of the script.
Hi guys, i tried to root Bluestacks Apps Player Beta for Mac OS X on Windows by using a method similar to the one used to root BS for Windows.
But unfortunately i am not able to test the modded files as i do not actually own a Mac OS X device, and i am not familiar with the OS either.
So i am asking, any volunteer here willing to help me test this experimental modded files?
How to use
1) Download BlueStacks AppPlayer Beta .dmg for Mac OS X & install it.
2) Download modded files provided below, make sure the targeted version is same as your installed version.
3) Extract the downloaded zip and use the modded files to replace the following folders:
Code:
~/Library/BlueStacks App Player/Android/Root.sparsefs/
~/Library/BlueStacks App Player/Android/Prebundled.sparsefs/
~/Library/BlueStacks App Player/Android/Data.sparsefs/
~/Library/BlueStacks App Player/Android/SDCard.sparsefs/
Downloads & Changelogs:
Code:
[URL="http://goo.gl/wJYSR"][SIZE="3"]BSRoot_0.3.6.102d.zip[/SIZE][/URL] (99.88 MB, Pass: [COLOR="Red"][email protected][/COLOR], Last Update: [COLOR="Red"]03/04/2013[/COLOR])
~ Target: BlueStacks for Mac OS X v[URL="http://goo.gl/ILhtK"]0.3.6.102[/URL] Only (Released: 21/03/2013)
+ Allow /system rw
+ su (standalone/on the fly)
+ Google Play v3.10.14
+ Google Contacts/Calendar Sync
+ Flash Player v11.1
+ Holo Launcher v2.0.2 Free
+ Terminal Emulator v1.0.52 OS
- Most bloatware
Notes:
- By replacing above folders, your existing settings & data will be gone, you are advised to create a backup before trying the mod.
* Please note that all version prior to the 03/04/2013 update probably will not work, try the latest version.
* If you tried please at least COME BACK TO VOTE so that i can know how it goes. Thank you!
-Reserved-
I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)
efdisastet said:
I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)
Click to expand...
Click to collapse
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.
codelover said:
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.
Click to expand...
Click to collapse
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
(sorry that it's a picture, copy seems to be an option, but can't find a way to paste.)
why does xda resize the pictures so small?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
efdisastet said:
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
Click to expand...
Click to collapse
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.
meatlocker said:
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Click to expand...
Click to collapse
Hi meatlocker, Thank you for your interest. The answer is no, i have no chance to test it because i do not actually own a Mac.
But i have been working with BS for Windows for months that i am pretty sure Mac version can be rooted too.
I am just trying to help, it's really up to Mac users effort if they really want to see it get rooted.
The more feedback the faster it can be done. If i got a Mac that would be easier since i got several test cases that i can run on my own.
For now, everything is based on my assumption.
codelover said:
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.
Click to expand...
Click to collapse
yup, I've got adb installed and it see bluestacks, haven't tried to run any commands or anything
still get the Segmentation Fault and never get a typical su request popup for any app.
uninstalled superuser.
tried su in terminal, still Segmentation fault
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data
efdisastet said:
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data
Click to expand...
Click to collapse
You cannot install Superuser/SuperSU directly from market because it will install an arm version of the binary instead of the x86 that we need.
Now we need to identify which su binary version works with BS for Mac.
Please download the attached su-test.zip that contains various versions of su, extract to adb folder and then run the following commands:
Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
adb shell /data/local/tmp/su-3.1.1-x86 -v
adb shell /data/local/tmp/su-3.2-x86 -v
adb shell /data/local/tmp/su-bin-3.1 -v
adb shell /data/local/tmp/su-1.25 -v
adb shell /data/local/tmp/su.x86 -v
adb shell /data/local/tmp/su.orig -v
* Also try to run above su without -v
We are expecting su to returns a version number or 'permission denied' message from a working copy, instead of segmentation fault.
Please let me know which version works. I think we can finalize this soon. Thank you again.
Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Also, how can we get into the contents of the Android disk image files on a Mac to extract android files, etc?
And how much space do we have in the simulated Android to install apps?
Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
adb shell /data/local/tmp/su-3.1.1-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-3.2-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-bin-3.1 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su-1.25 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su.x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
* Also try to run above su without -v
[COLOR="red"]same results as above except that I got Segmentation fault on the ones that hung with -v[/COLOR]
efdisastet said:
Code:
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
.....
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
Click to expand...
Click to collapse
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.
I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?
nudawa said:
I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?
Click to expand...
Click to collapse
1) Make sure you are using the required version, as these rooted files only works for v0.3.6.102.
2) Once you have replaced Data & SDCard, non of your existing apps should remain; If the apps still there you probably did it wrong.
3) Make sure you close your Bluestacks before replacing those files.
* Please note that the 'rooted files' mentioned above are 4 folders that contains 2 files in each folder.
codelover said:
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.
Click to expand...
Click to collapse
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied
efdisastet said:
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied
Click to expand...
Click to collapse
Have you tried executing 'su' from adb instead of Terminal?
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
- Create the following public accessible folder if not exists: /data/root
- Create the following test files: /data/root/test
- Change ownership, group & permissions needed for su for all files found inside /data/root/ on every boot.
Click to expand...
Click to collapse
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.
codelover said:
Have you tried executing 'su' from adb instead of Terminal?
Click to expand...
Click to collapse
tried running it from an adb shell, still permission denied
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
Click to expand...
Click to collapse
tried this: segmentation fault
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.
Click to expand...
Click to collapse
did all that. /data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied)
but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?
efdisastet said:
tried running it from an adb shell, still permission denied
/data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied) but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?
Click to expand...
Click to collapse
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.
codelover said:
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.
Click to expand...
Click to collapse
/data/root/ may be working as expected, but there still seems to be a "su" in the path somewhere, whose permissions are denied. Will that cause problems
I put the 3.1 file from the su-test folder into /data/root, restarted bluestacks, and then went to terminal, I've attached a screenshot of those results, including calling just "su" to note the difference
Maybe if I had a better handle on what we wanted all the permissions to be and where we wanted this executable su to be, and what su an app/apk like superuser tries to use, I could help more.
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
mount -o remount,rw /system
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Money test and time service virus removal
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?
drdkundu said:
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?
Click to expand...
Click to collapse
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely
Nuh99 said:
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely
Click to expand...
Click to collapse
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?
drdkundu said:
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?
Click to expand...
Click to collapse
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.
screenshots
Nuh99 said:
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.
Click to expand...
Click to collapse
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_
drdkundu said:
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_
Click to expand...
Click to collapse
They are not opening. Error!
Kindly send me @ my fb.
Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to sytem/app/cameraupdate.apk
but time service refer to data/app/com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Note:
if you find ...Error... chattr -iaA not found
WHAT TO DO ? its mean you only install app not yet istall busybox
after install Busybox Installer by JRummy Apps Inc. from play store open app
on tab installer, select busybox ver1.2 select intall location /system/xbin/ then touch Install
agzpur said:
Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to cameraupdate.apk
but time service refer to com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Click to expand...
Click to collapse
Yes you don't need cache clear but doing it on a safe side is better.
If this post helped you please give a thumbs up!
i can't change the permission on root explorer.
Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
1) Turn off wifi/3G/4G Open settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me
dsamivai said:
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me
Click to expand...
Click to collapse
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.
Nuh99 said:
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.
Click to expand...
Click to collapse
Hi, Im a user of 8.31 O+ phone. Ive downloaded all the 3 apps youve mentioned. But after installing busybox (the app) I cant install any version of it.. thats why everytime I'll type the commands in emulator indicated above, it says error...
please help... thank you
Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?
Nuh99 said:
I'm not a developer and That's it!
Click to expand...
Click to collapse
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.
OK
joshuas_79 said:
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?
Click to expand...
Click to collapse
If you are having this error it means you have installed busybox app not busy box.
To do this open busybox app in your device, select busybox ver1.2, select intall location /system/xbin/ and tap install.
Then try the procedure
optimumpro said:
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.
Click to expand...
Click to collapse
but my problem is that I can't find firmware for my tablet: engel tb0725ips
joshuas_79 said:
but my problem is that I can't find firmware for my tablet: engel tb0725ips
Click to expand...
Click to collapse
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.
Brother Nuh has helped me solving cameraupdate and time service android malwares without flashing, may the Almighty bless him abundantly I really learnt some new things from him Thumbs Up for Brother Nuh:good:
optimumpro said:
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.
Click to expand...
Click to collapse
I can't find a custom recovery either, so only stock recovery with not many options. :crying:
A few weeks ago one of my important apps started crashing on open.
Since I have important informaiton saved on that app I need to obtain it.
Is there a way to access that package folder (and that app is not debuggable) with adb or shell?
When I try to access via adb and shell the result it Permission denied.
I can't root the phone, so this is out of the quesiton.
I'm using Google Pixel 1 with Android 10 Build - Build/QP1A.191005.007.A3)
There isn't any way to access /data/data/ as a normal user or shell user, the only user able to access that is root, at least according to the permissions.
You could try to backup using "adb backup package", then you could apply this backup back on another phone or on this same app after reinstalling it.
bystroy said:
A few weeks ago one of my important apps started crashing on open.
Since I have important informaiton saved on that app I need to obtain it.
Is there a way to access that package folder (and that app is not debuggable) with adb or shell?
When I try to access via adb and shell the result it Permission denied.
I can't root the phone, so this is out of the quesiton.
I'm using Google Pixel 1 with Android 10 Build - Build/QP1A.191005.007.A3)
Click to expand...
Click to collapse
Temporarily root phone's Android, means add su cmdlet what is suitable, and then mount the partition in question as RW by means of ADB applying su.
Example:
Code:
adb devices
adb push <SU-BINARY> / data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'mount -t auto -o rw,remount <PARTITION-IN-QUESTION>'"
adb pull "<DIRECTORY-TO-PULL>" <LOCATION-ON-PC>