Does anyone have a flash able zip that would kill these lights?
Sent from my Amaze 4G using xda app-developers app
jcjackjay said:
Does anyone have a flash able zip that would kill these lights?
Click to expand...
Click to collapse
Do the below - I posted it in the bug thread yesterday, its easy and works great.
This combination of Killing the Button Lights & Screen Dimming is the Shizzle
Try it if you have not done so yet, thanks to blast0id & dcacklam
blast0id said:
put this in a text file and name it "55killsoftbuttonlights" or whatever the hell you want to name it, just don't put an extension on it. then place the file in /system/etc/init.d and it will be killed on every boot... if you want them back then just delete or move the file out of that folder...
Code:
mount -o rw,remount /dev/block/mmcblk0p29 /system
chmod 777 /sys/devices/platform/leds-pm8058/leds/button-backlight/brightness
echo 0 > /sys/devices/platform/leds-pm8058/leds/button-backlight/brightness
chmod 444 /sys/devices/platform/leds-pm8058/leds/button-backlight/brightness
sysro
Click to expand...
Click to collapse
dcacklam said:
Settings -> Display -> Brightness -> Auto (Change to 'Checked')
Settings -> Display -> Auto Backlight -> Use Custom
Screen Dim Level -> 1
Edit Other Levels, set the middle collumn to:
2
10
20
30
40
50
80
120
200
The far-right (the buttons on the bottom) can either be on or off. 0 is off, any other number is on (So for all you guys who hate the 'light leak', you should be able to just set the far-right column to 0 for all options. Unfortunately though, this does not work.
Click to expand...
Click to collapse
I am using it on AOKP and it really is like a new screen.
I've attempted the creating the 55killsoftbuttonlights and placing it in /system/etc/init.d but for some reason its locked as read-only. I have ES File Explorer all root settings checking including mounting system rw. Hmmmm I rebooted to recovery & "fix permission" to no avail also.
rfunderburk39 said:
I've attempted the creating the 55killsoftbuttonlights and placing it in /system/etc/init.d but for some reason its locked as read-only. I have ES File Explorer all root settings checking including mounting system rw. Hmmmm I rebooted to recovery & "fix permission" to no avail also.
Click to expand...
Click to collapse
I use root explorer did not set permissions (he did not say to)....and it worked
Got it. Here is what I did originally.
I used my laptop and copied the info into notepad++ named the file. Then transfered the file via Bluetooth to my phone. Using ES file explorer attempted to copy the file to /system/etc/init.d and received " permission not allowed". So I checked the permission of the folder it was set to read-on, it would not allow a change to "writeable" once again getting "permission not allowed". Rebooted to recovery and "fix permission". Reboot and same issue. Tried a second root file browser, and same problem.
At this point I get an idea to check permission of the file. It was set to read-only also. Attempted to change the permission on 55killsoftbuttonlights I get the "permission not allowed".
So I downloaded jota editor used the xda app>view as web page copied and pasted into jota. Saved as 55killsoftbuttonlights and copied it to /system/etc/init.d
Rebooted and all functions as it should.
Stupid questions are better than stupid mistakes.
Japanese proverb
Related
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Copy it to another folder edit the copy and then move the edited file in the correct folder.
tried that already, didnt work. got another error
I use Root Explorer to do any editing.
Any other suggestions? I'd rather not have to pay for it
joshtb86 said:
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Click to expand...
Click to collapse
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# /system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
joshtb86 said:
Any other suggestions? I'd rather not have to pay for it
Click to expand...
Click to collapse
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
cbay said:
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
Click to expand...
Click to collapse
if i use CM Mod, i cant see any files. if i use HiAPK, all the files have -rw and a lot of stuff before it and i cant read anything, but it does mount. CW had problems mounting the drive. im gonna try out the terminal commands
rajeevvp said:
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
Click to expand...
Click to collapse
when i tried the mv command to move it back, i still got errors in moving it and was not able to
joshtb86 said:
when i tried the mv command to move it back, i still got errors in moving it and was not able to
Click to expand...
Click to collapse
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
rajeevvp said:
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
Click to expand...
Click to collapse
thanks so much again. i finally got it to work, but i just wanted to get netflix to work, and it still doesnt. after all that work. ugh.
JoTeC said:
I use Root Explorer to do any editing.
Click to expand...
Click to collapse
Thanks, I tried two other applications and they didn't work. Was able to edit with Root Explorer. didnt fix the Netflix playback. Bummer.
***** changing the Nexus S to HTC Vision and samsung to HTC did the trick.
Root explorer will work, and is a great app. Worht the money.
Also, ADB from a PC will work as well. Just install the android sdk and use ADB.
From windows cmd prompts the commands are just adb remount (to remount as root) then "adb pull /system/build.prop" (this will pull it to the sdk platform-tools folder that adb.exe is in) and then edit to your hearts delite.
"adb push build.prop /system/build.prop" to send it back.
I was able to use ES File System by unchecking the Mount File System option in the Root options menu and then rechecking it. I imagine that it forced a remount of the file system in a writable mode.
This worked on our nabi big tab hd24
We now have true multiuser, where everyone has their own login, files, emails, bookmarks, web history, etc; as it should be.
I first did a factory reset, then installed kingo root, then another reset, did the build prop edit this suggested (es file explorer did not work) but build prop editor did....
We now have the nabi big tab hd 24 running as our primary desktop workstation computer...
No we just wish for a room update to be made available with the latest version of Android.
4.4.2 is getting old, and as is common little manufacturer long term support...
Hey all,
I was wondering if there is an easy way to change the file permission on the widget.txt file found in /system/customize. I want to change the sync button on the pull down menu to brightness but can't right now because the file is read only. I have searhed, but have not been able to find the right fix. I am running BAMF stripped 1.8 with one of ZHP's battery icon mods. I tried setting the system to write mode in BAMF toolkit, but that didn't work. I use ADAO file manager for file browsing and unfortunately it doesn't have the ability to long press and change permissions. Is there code I can use in terminal emulator to change the permission? I would like to make the change on the phone but I am not against using adb if I have to.
Thanks
Josh
Up^^^
Need 10
You probably have to remount /system with read/write permissions. Root explorer is the easiest way but if you don't want to pay for the app, you can use terminal emulator.
Something like this:
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Thanks, I will give that a try. After I set the system to read/write and change the widget file do I need to type something similar in terminal emulator to set the system back to read only?
This requires root and ADB knowledge. The method will work for any boot animation, reference Xoom forums for additional resources.
I'm not responsible if you brick your Galaxy Tab 10.1!!!!! This has only been tested on a USA White 16GB Galaxy Tab 10.1
ADB METHOD:
Code:
Download bootanimation.zip from the bottom of the post, and copy it to your directory where adb.exe is located. The included boot animation is a stock honeycomb from the Xoom animation.
adb push bootanimation.zip /sdcard/bootanimation.zip
Next, get into ADB shell and mount system as writeable:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
Here is where it gets funny, in order to make the bootanimation.zip play correctly you will need to rename the program which calls the default animation to "playsoundBACKUP" and then copy/rename bootanimation to playsound. MAKE SURE YOU BACKUP JUST AS I TELL YOU TO:
cd /system/bin
mv playsound playsoundBACKUP
cp bootanimation playsound
Okay, now all that is left is to copy the bootanimation.zip to the proper directory:
mv /sdcard/bootanimation.zip /system/media/bootanimation.zip
ROOT EXPLORER METHOD, thanks Berner:
Code:
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
TO REVERT:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p4
cd /system/bin
rm playsound
mv playsoundBACKUP playsound
cd ../media
rm bootanimation.zip
Go ahead and reboot your tablet, and enjoy the boot animation. There are literally hundreds of animations available, and if you search through the Xoom forum you can download whichever.
Edit: Attached are the two files which are being manipulated, for those who accidentally delete playsoundBAK and want to revert. Note, "playsound" is the actual modified file where playsoundBAK is the original stock file.
Also too, the following animation is unbelievably awesome:
http://youtu.be/TxQ1DZHi1OA
download here : http://www.mediafire.com/?6aen7nlgelzgu6j
thanks for this ... fun to play with ...any link/intro to the animation file (video) format ? just curious if ican make one of my own ..
Sent from my SHW-M110S using XDA App
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Thanks for this, mang I've been dying to mod my boot screen!
it says failed cross device link...
actually i got it but i accidently delete the playsound can you hook me up with yours?
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Riztnack said:
its weird, i still get the samsung bootloader........sits for a good minute then for like 5 seconds the stock honeycomb comes up and plays then lockscreen shows up. should the samsung screen be up that long if at all?
Click to expand...
Click to collapse
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
G1_enthusiast said:
it says failed cross device link...
Click to expand...
Click to collapse
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
G1_enthusiast said:
actually i got it but i accidently delete the playsound can you hook me up with yours?
Click to expand...
Click to collapse
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Berner said:
Instructions work fine. ADB not required -- everything can be done with Root Explorer. Thanks for the post.
Click to expand...
Click to collapse
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
wesbalmer said:
Please run these commands and post the file as an attachment in your reply:
Open up windows command prompt, navigate to the directory which contains adb.exe,
adb shell
cd /
echo system.media >> /sdcard/LOG/BootAnimation.txt
ls /system/media > /sdcard/LOG/BootAnimation.txt
echo system.bin > /sdcard/LOG/BootAnimation.txt
ls /system/bin > /sdcard/LOG/BootAnimation.txt
Where does it say this? Please post some type of screen shot and method to reproduce. What operating system are you using, what folder are you located in when you're executing adb.exe, what Galaxy Tab are you using?
I've attached it to the OP, both playsoundBAK (original file, which executes stock boot animation) and playsound (modified file). Please be careful in the future to make a backup
Click to expand...
Click to collapse
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
jman391 said:
Hey man, if i'm doing this with root explorer what do i do with the playsoundBACKUP file in the /system/bin folder? His adb commands arent very clear if using root explorer. Also what do i do with the copied bootanimation playsound? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
G1_enthusiast said:
anyway to get rid of the samsung begining? it still show up but after that it show your custom booot animation
Click to expand...
Click to collapse
What do you mean? The initial Samsung Logo
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Thanks bro, I've never used Root Explorer. I'll add this to the OP.
Riztnack said:
http://img.photobucket.com/albums/v643/Riztnack/1.jpg
I am using windows 7
Click to expand...
Click to collapse
Very strange. I've never seen that error on any of the 30+ Android devices I've rooted.
Please confirm, are you on a 10.1 or 10.1v (as I really don't know the differences yet).
Please try the following:
adb shell mount -o remount,rw /dev/block/mmcblk0p4
adb push bootanimation.zip /system/media/bootanimation.zip
Berner said:
Keep the playsoundBACKUP in /system/bin so you can revert if you want. The copied (and renamed) bootanimation playsound also stays in /system/bin.
Basically the steps in Root Explorer:
1. Copy bootanimation.zip to /sdcard (USB mount, dropbox, whatever).
2. Select /system/bin/playsound
(note - you'll need to set /system/bin as R/W here)
3. Rename to playsoundBACKUP
4. Select /system/bin/bootanimation
5. Copy/paste - new file will be named bootanimation - Copy
6. Rename bootanimation - Copy to playsound
7. Select bootanimation.zip whereever its located on .sdcard
(note - you may need to set /system/media as R/W here)
8. Move to /system/media/
Click to expand...
Click to collapse
Very cool man! Thanks for putting it in laymen's terms for dummies like me.
I don't know what I'm doing wrong but I can't get it o work. I've changed the files and copied the bootanimation.zip to /system/media. The original is gone however the bootanimation is just the default android boot. The one with "android" (i.e the animation we get when using the android emulator)
EDIT: Got it to work, just needed to set the permissions.
[X][X][X]
[X][O][X]
[X][O][X]
I would also like to know if there is a way to remove the initial samsung animation the one where the sound used to play. Since the new animation plays afterwards where the bland samsung logo used to play.
Same here......
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Also - only after I set the permissions to 755 - maybe you should include this in your OP ?
Thanks anyway!
bert269 said:
I also get the original 'blue circling-Samsung' followed by the white 'SAMSUNG' letters on my screen...Then only do I see the HC bootanimation.
Click to expand...
Click to collapse
I renamed the bootsamsung.qmg file to bootsamsung.backup and that seemed to get rid of it, but the custom animation still only shows for the few seconds when the tablet buzzes before the lockscreen comes up.
I viewed the zip file and that is not the one that plays I set permissions but still no honeycomb boot animation! any ideas? will this work on custom rom?
step 4,5,6
use rootexplerer but somehow lose in step 4,5,6 thanks
I accidentally (sure!) removed all permissions on a folder in / so now the system can't even read it to display it in root explorer. Any way I can fix it? I've searched pretty hard and tried chmod and a couple other ideas in the terminal but nothing so far has worked.
Edit: Sry, didn't read properly. Please tell me which folder in / you removed all permissions from so I can look them up. The following commands with the given permissions should work though, but you have to replace / with the correct path to the folder.
Try it again with chmod:
Code:
su
chmod 755 /
"ls -ld /" should now show the flags "drwxr-xr-x".
Sent from my SGS2
Blacktremolo said:
Try it again with chmod:
Code:
su
chmod 755 /
"ls -ld /" should now show the flags "drwxr-xr-x".
Sent from my SGS2
Click to expand...
Click to collapse
That's what I tried. See the actual path is /.bak but when I chmod for that path, since it has no permissions, it says no such file or directory.
Even if it has no permission set u are able to operate on it with chmod. Please post the Output of "ls -ld /.bak"
If that also says "no such file or directory" then there simply is "no such file or directory"
Sent from my SGS2
Or are you maybe refering to a file in /mnt/sdcard (the internal user memory)?
Sent from my SGS2
Blacktremolo said:
Even if it has no permission set u are able to operate on it with chmod. Please post the Output of "ls -ld /.bak"
If that also says "no such file or directory" then there simply is "no such file or directory"
Sent from my SGS2
Click to expand...
Click to collapse
I suppose it's not there. I had created the folder last night to store a few backups of files but when I woke up this morning the entire folder was missing. I'm not sure. ls reported no such file or directory. I guess there just isn't one. Thanks for the help. I'll hit the buttons.
I guess the problem is that / is mounted read-only.
Sent from my SGS2
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
Theres other apps that use root that are free,just use google or try android/apps on here,the search function is your best friend.ES gives me issues also.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
You can use the terminal emulator, this way (assuming the host file is located in your sdcard):
Code:
su
mount -o rw,remount /system
cp /sdcard/hosts /system/etc/hosts
--set permissions here if you need
mount -o ro,remount /system
Personaly, I don't face any problem with ES File Explorer, but you can try this one (free, lightweight and useful)
cant is cant
RoberGalarga said:
You can use the terminagoing to be lator, this way (assuming the host file is located in your sdcard):
Code:
su
mount -o rw,remount /system
cp /sdcard/hosts /system/etc/hosts
--set permissions here if you need
mount -o ro,remount /system
Personaly, I don't face any problem with ES File Explorer, but you can try this one (free, lightweight and useful)
Click to expand...
Click to collapse
The problen was defined, he said he is rooted he set the permissions, set the system or as mounted read write... the answer is not just use this app, if you are rooted # not $ and you can not read or write something it is not going to be a standard answer... I have tje same problem, I thonk it is because I used a rooter for chines operating system, and it gained root but has some issues. A hint to this was that I had to run ot 2ce to do the rooting. This is for sure tho, if ypu cant do it in terminal as su, np app is going to be sble to do it for you. I suggest to do as I am going to to do, and that is to hard reset, and find a non chinese tablet rooter.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
its due to root permission............try reseting root permission through superuser app.................