Related
[deleted]
[deleted]
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
if i'm not mistaken, there is no big difference whether it displays bash# or [email protected] as long as you see the hash tag, you are under the super user or root.
The bash prompt probably was not exported so it back to it's default when you open another shell.
The prompt can be changed to whatever you want, using PS1="my_prompt".
You want your prompt to be export PS1="\[email protected]\h:\W\$ ". You can add it to the initial command (add an semicolon as a separator if you have other initial command). Don't forget to left an space to the final of PS1 or your commands will appear concatenated with the prompt.
As conectix said, the only important character is the last one: if it is a sharp the shell is executing as user, and if it is a dollar then you have root privileges.
---------- Post added at 06:05 PM ---------- Previous post was at 05:30 PM ----------
Another thing to observe is that in the post you mentioned was said that a shell is open, what fits on what I said above.
Another observation is that sh and bash are different shells. On my Terminal Emulator the default shell is sh. So if I type 'bash' it enters on bash shell and the prompt changes. Once I exit (typing 'exit') of bash it returns to sh with a simple dollar prompt (which is wrong because I'm running as a user).
You can verify your prompt by typing 'echo $PS1'. On mine it just have a dollar with an space.
Oke sure thank you for this, but why can't I use "ui" ?
it will say that the command is not found but in the tutorials and videos on youtube you can see that after they do this they immediately get a red "[email protected]:~#" instead of the "bash-4.1" and after they enter "ui" it works for them. I do exactly the same but get to command not found error.
F4LLCON said:
Oke sure thank you for this, but why can't I use "ui" ?
it will say that the command is not found but in the tutorials and videos on youtube you can see that after they do this they immediately get a red "[email protected]:~#" instead of the "bash-4.1" and after they enter "ui" it works for them. I do exactly the same but get to command not found error.
Click to expand...
Click to collapse
Probably the command ui isn't in your path. The path is where your shell searches for the binaries to execute.
You need to locate the ui binary (his path) and export a new path:
Code:
export PATH=$PATH:[B]ui-binary-path[/B]
Where ui-binary-path is the path (directory) where the ui binary is located.
PS: You need to reply me so I'll be notified of your response.
This can help you to get solution
Try executing list of following commands:
cd /etc/profile.d/
vi bash_prompt.sh and type: export PS1='[\[email protected]\h \W]$ '
su - root
Hope so the problem is fixed :fingers-crossed:
Regards,
Abhishek Kalekar
This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/
Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J
In! Thanks Justin!
Billy
Damn, thanks a lot!
jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.
Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one
noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!
id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.
going on 10x for me and still nothing. Any suggestions?
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.
id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!
Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>
Root for ZTE z990g aka ZTE Merit
by jcase - [email protected] - http://twitter.com/TeamAndIRC
June 16 2012 - Copyright 2012 CunningLogic
Do Not Distribute or republish without permission. (Sad that this is needed, but people/blogs like to profit off the work of others without credit)
Want to support my work? Donations are always appreciated, but never required:
Paypal: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LZ62YFU3XCEK8
Amazon Giftcards: [email protected]
Required files:
http://dl.dropbox.com/u/8699733/chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Code:
adb shell
Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.
Code:
mkdir /data/local/logs
mkdir /data/local/logs/kernel
Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.
Code:
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
Code:
ls -l /data/local/logs/kernel/log_kernel.txt
If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.
Code:
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
Code:
ls -l /data/local.prop
Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.
Code:
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
Once you have rebooted, remount, install su.
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Clean up your mess!
Code:
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Code:
adb reboot
Might Not Work As Expected
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
bitshifter52 said:
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
Click to expand...
Click to collapse
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
jcase said:
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
Click to expand...
Click to collapse
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
Click to expand...
Click to collapse
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
Click to expand...
Click to collapse
It Worked - But Don't Know Why...
jcase said:
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
Click to expand...
Click to collapse
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
bitshifter52 said:
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
Click to expand...
Click to collapse
Generally you have to run superuser once to get it to work I've found, at least recent builds (or maybe its recent android builds)
Problem.
Hello, i have followed this entirely but at parts it says "Access denied" when im on certain parts when i tryed to check if the Kernel log was there it said "access denied" same with some folders.
root or no root
followed steps, ended up with this...
$ ls -l /system/xbin/su
ls -l /system/xbin/su
-rw-rw-rw- root root 22364 2012-07-15 09:25 su
the superuser app shows all blank under apps and logs, when i try to update it, it says "checking" for a few secs and then nothing... also wondering how to do a factory reset cuz if i didn't screw the phone up yet, i will thx in advance
Has you can see I'm new here. I'm old and retired I would love to root my ZTE Merit 2.3.5 but this is over my head.
I was wondering if there's any accomplished phone rooters in the NC area that would be willing to walk me through this or do this for me
I'd be more than willing to make a donation to make this happen,
custom recovery
I was wondering if someone would make q custom recovery for this phone because the stock recovery is really bad
Not working
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Worked!
omg I've wanted to root my phone. Thank you thank you! I thought I would brick my phone at first.
SIM Carrier unlock a ZTE Merit Z990G Straight Talk
I'm currently a T mobile prepaid customer and received the Merit from a friend of mine for doing some painting. I have looked for a month now and had a few unlock websites fail at attempting to unlock the phone via the IMEI (which the phone does have ). I have attempted to put my tmobile sim in the Merit but there is NO place to enter an unlock code. I really DONT wanna change my service to straight talk and would be willing to pay a decent amount to anyone that is capable of unlocking this phone for use with tmobile. If you think you have what it takes PM me and i will give you the IMEI and we can work out a deal. I challenge ANYONE achieve the impossible and get me the unlock code and a way to input it into the phone.
Cannot get local.prop
I have waited 20 minutes after trying to create the local.prop file and it simply won't create it. Any suggestions?
Can't get SU to upload
Hey I'm new to rooting android. I get to the point of installing SU but windows keeps telling me file not found. Would really like some help in fixing this issue. I have installed SU file to C:\Android\android-sdk\SU. Up to this point everything works fine.
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Any help would be really appreciated.
Thnks
Help getting Started
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Not a Damn thing...
Rather sad....I have everything going as it should....all input correct...still no root after final reboot...I followed every step to a T several times -rw-rw-rw- grrr...ive rooted many devices none this big of a pain in tha butt!
Used updated su binary on root just for fun...same result
Help plz!
im a noob to this but have been messing around with ubuntu for some time now can someone show me step by step on how to root my zte merit plz? is there a video tut on how? i tried all the quick methods but they don't work, this one obviously does on this page, can someone help start me out plz, im learning still and love to learn more!
---------- Post added at 08:59 AM ---------- Previous post was at 08:45 AM ----------
Univarseman said:
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Click to expand...
Click to collapse
help me, whats the first step then i can get the gearz in motion, i have not a clue on how to start this but if i do i can usually figure it out from them sometimes
Start menu
jjflappy said:
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Click to expand...
Click to collapse
Start menu then type CMD hit enter
I can't delete following malware app with root permission.
com.android.provider.down3-1.apk
com.google.model.mi-1.apk
com.google.fk.json.slo.apk
It shows an error:rm failed for com.hola.launcher-1.apk, Operation not permitted
Can any help me out?
This is a malware that changed the immutable attrib
---------- Post added at 11:44 PM ---------- Previous post was at 11:40 PM ----------
svprm said:
I can't delete following malware app with root permission.
com.android.provider.down3-1.apk
com.google.model.mi-1.apk
com.google.fk.json.slo.apk
It shows an error:rm failed for com.hola.launcher-1.apk, Operation not permitted
Can any help me out?
Click to expand...
Click to collapse
You need busybox installed.
Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name"
This time it will get removed without error
Enjoy
Bithacker01 said:
---------- Post added at 11:44 PM ---------- Previous post was at 11:40 PM ----------
You need busybox installed.
Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name"
This time it will get removed without error
Enjoy
Click to expand...
Click to collapse
thanks bro.
It worked.
thanks Bithacker it worked. thank a lot
I have problem to remove "com.aiwozhh.ph.cz.apk" on my Android even I followed the below;
(Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name" )
the error msg is "Operation not permitted".
Pls help!!!!!!!!!!
Thanks,
Piseth
Bithacker01 said:
---------- Post added at 11:44 PM ---------- Previous post was at 11:40 PM ----------
You need busybox installed.
Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name"
This time it will get removed without error
Enjoy
Click to expand...
Click to collapse
Can this be done using terminal emulator?
Wil53664 said:
Can this be done using terminal emulator?
Click to expand...
Click to collapse
Yes, You can use any terminal emulator.
---------- Post added at 09:30 AM ---------- Previous post was at 09:23 AM ----------
Lim Piseth said:
I have problem to remove "com.aiwozhh.ph.cz.apk" on my Android even I followed the below;
(Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name" )
the error msg is "Operation not permitted".
Pls help!!!!!!!!!!
Thanks,
Piseth
Click to expand...
Click to collapse
You need to have root access.
Try rooting your device, use Kingroot App
Then, try these commands
su
chattr -AacdDijsStu *.apk
rm "your package name"
How can I delete the su file from the /system/bin and /system/xbin I keep getting operation not permitted
Lim Piseth said:
I have problem to remove "com.aiwozhh.ph.cz.apk" on my Android even I followed the below;
(Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name" )
the error msg is "Operation not permitted".
Pls help!!!!!!!!!!
Thanks,
Piseth
Click to expand...
Click to collapse
U can try with titanium backup once
If it doesn't work, reboot the phone, freeze the app fast when it boots and then try to uninstall it with titanium
It worked for me once
---------- Post added at 06:00 AM ---------- Previous post was at 05:58 AM ----------
Lim Piseth said:
I have problem to remove "com.aiwozhh.ph.cz.apk" on my Android even I followed the below;
(Try this commands:
chattr -AacdDijsStu *.apk
rm "your package name" )
the error msg is "Operation not permitted".
Pls help!!!!!!!!!!
Thanks,
Piseth
Click to expand...
Click to collapse
Firstly, root ur phone
If it's rooted
Fir type SU and enter
Then try to do whatever u want
Hey! I've been following this problem because I have the same situation, I have a malware named:
VPN
net.qwe.vpn
ad.apk
And I am using this method you just explain BUT the terminal emulator says No such file Not found something like that, there is anything else for me to do? How the freaking hell can I find the real name of this thing? Or what can i do in the emulator in order to be able to find it... Please help
MissSofy said:
Hey! I've been following this problem because I have the same situation, I have a malware named:
VPN
net.qwe.vpn
ad.apk
And I am using this method you just explain BUT the terminal emulator says No such file Not found something like that, there is anything else for me to do? How the freaking hell can I find the real name of this thing? Or what can i do in the emulator in order to be able to find it... Please help
Click to expand...
Click to collapse
did u write the package name?
Yes, I did, I even tried on the three names one by one, correct me If im wrong, I wrote this:
su
chattr -AacdDijsStu ad.apk
rm ad.apk
And it appear a line saying No file in directory or something about not finding it. Then I tried the other name:
su
chattr -AacdDijsStu net.qwe.vpn
rm net.qwe.vpn
And nothing... could you please tell me if what i wrote was correct? Or write it in the correct way with the name included
---------- Post added at 07:05 PM ---------- Previous post was at 06:26 PM ----------
Nevermind... I just found out I delete the virus previously . I did so much stuff with the cellphone, I think what got rid of it was a "Format" I applied with the PC. Because I plugged in my cellphone and my laptop, browse its files and find the malware, and I try to delete it but it say that I was not allowed, so I just select the cellphone and did a "quick format" you know? That thing you do with the USB Flash drive, and i did, and later I found this website and I tried what you said and on the screen appear a message saying not found.... I just right now check the system apps with root brower and I cannot find the malware, even with my ikarus antivirus! Im so happy! Thank you anyways this is such a helpfull blog... Im still going to run some scans though, to really make sure the malware is gone for good! thanks again
I bring to you another script, courtesy of Amazon. This one might not suit a lot of you, so be prepared. Like most of the tricks we've tried this past week or so, even resetting the reset, may not be to your liking and can only be reverted via factory reset.
Titled 'Display,' it toggles at least three modes. i didn't quite understand them so I went ahead and ran the script in Terminal Emulator. This was also in /system/bin.
Code:
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ sh display.sh
usage: display [<device name>|reset]
<device name>: the name of device (e.g. apollo/thor/soho) reset: setting orignal value of display for this device.
It changes size, density and values. The last one sets it back to "original value." I don't have a before shot, because I wasn't expecting anything. Cleaner, brighter, crisper and in my opinion, more HD.
Edit: the picture does no justice unfortunately.
1. Go to /system/bin
2. Locate file: display
3. Rename to display.sh
4. Copy to internal storage
5. I used Terminal Emulator
Code:
$ sh /sdcard/display.sh
Enter the command that will "reset to original" and you get sharper screen, brighter and more vibrant. Your text may look a bit smaller and folders on home also. I think this is the HD the tablet was missing.
Display Configuration:
Code:
/system/etc/display_conf
Code:
# Please add new device using the same format.
# The comments begin with "#".
device=apollo, size=1600x2560, density=320
device=thor, size=1200x1920, density=320
device=soho, size=800x1280, density=240
Followed by...
Code:
/system/bin/display
Code:
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ sh display.sh
usage: display [<device name>|reset]
<device name>: the name of device (e.g. apollo/thor/soho) reset: setting orignal value of display for this device.
Hi
Is the actual command something like ./display.sh hostname
I ran the script with the above but said permission denied.
DragonFire1024 said:
I bring to you another script, courtesy of Amazon. This one might not suit a lot of you, so be prepared. Like most of the tricks we've tried this past week or so, even resetting the reset, may not be to your liking and can only be reverted via factory reset.
Titled 'Display,' it toggles at least three modes. i didn't quite understand them so I went ahead and ran the script in Terminal Emulator. This was also in /system/bin.
Code:
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ sh display.sh
usage: display [<device name>|reset]
<device name>: the name of device (e.g. apollo/thor/soho) reset: setting orignal value of display for this device.
It changes size, density and values. The last one sets it back to "original value." I don't have a before shot, because I wasn't expecting anything. Cleaner, brighter, crisper and in my opinion, more HD.
Edit: the picture does no justice unfortunately.
Click to expand...
Click to collapse
smileyint said:
Hi
Is the actual command something like ./display.sh hostname
I ran the script with the above but said permission denied.
Click to expand...
Click to collapse
Go to system/bin and locate display file. Copy it and paste to internal storage then rename to display.sh. Open ADB, get a shell and type:
Code:
$ cd /sdcard
$ sh display.sh
$ display reset
If your screen is already at its properly set stage, it won't change, but you shouldn't get an error. You would see something like:
Code:
$ wm change ...
Also in system/bin is the script 'wm' which you can use to manually change your DPI to whatever you want. Perform the same steps above for the wm file.
Code:
$ cd /sdcard
$ sh wm.sh
You can use this app to monitor the changes you make to your DPI in real time. Just make sure to note the starting DPI so you can go back to it.
Thanks DragonFire1024. i cannot tell the different after resetting the display though.
DragonFire1024 said:
Go to system/bin and locate display file. Copy it and paste to internal storage then rename to display.sh. Open ADB, get a shell and type:
Code:
$ cd /sdcard
$ sh display.sh
$ display reset
If your screen is already at its properly set stage, it won't change, but you shouldn't get an error. You would see something like:
Code:
$ wm change ...
Also in system/bin is the script 'wm' which you can use to manually change your DPI to whatever you want. Perform the same steps above for the wm file.
Code:
$ cd /sdcard
$ sh wm.sh
You can use this app to monitor the changes you make to your DPI in real time. Just make sure to note the starting DPI so you can go back to it.
Click to expand...
Click to collapse
---------- Post added at 08:39 AM ---------- Previous post was at 08:31 AM ----------
Thanks DragonFire1024. i cannot tell the different after resetting the display though.
DragonFire1024 said:
Go to system/bin and locate display file. Copy it and paste to internal storage then rename to display.sh. Open ADB, get a shell and type:
Code:
$ cd /sdcard
$ sh display.sh
$ display reset
If your screen is already at its properly set stage, it won't change, but you shouldn't get an error. You would see something like:
Code:
$ wm change ...
Also in system/bin is the script 'wm' which you can use to manually change your DPI to whatever you want. Perform the same steps above for the wm file.
Code:
$ cd /sdcard
$ sh wm.sh
You can use this app to monitor the changes you make to your DPI in real time. Just make sure to note the starting DPI so you can go back to it.
Click to expand...
Click to collapse