hello guys. battery of my zf5 is dead. i have dissambled it and get the controller, and i have conected another battery (bigger one, 6000mah) to controller.
now device work, but it using only 2100 mah from battery, because this value is setted in framework-res.apk, and in the charge-full file from /sys/class/power_supply/battery.
now, i have modified value in the framework-res.apk, recompiled it and pushed to device (no problem with this).
now, i have pulled charge-full file from /sys/class/power_supply/battery folder, modified it, but i cannot copy/replace it back to device.
i have root, i have rw permisions to root of device.
i have chmod 777 -R /sys/class/power_supply/battery folder, chmod +x -R /sys/class/power_supply/battery folder. i have try to change owner of /sys/class/power_supply/battery/charge-full file. but no luck, allways i get Failed: operation not permited.
tryed copy/replace from adb shell, from twrp file manager, from twrp terminal. no luck
can please anyone help me?
thx!!
Related
This is probably a noob question but I've searched and tinkered and I cant get this file altered or replaced. It's located on the device under /system/media. I've rooted my device(if this is relevant??). and copies he xml file first to my sd card and then to my pc where I've altered it(trying to get rid of the Orange logo) and now i want to copy it back to the Hero. So I've tried adb shell and then
> adb push boot_animation.xml /system/media
but that doesn't work I have also tried to chmod 777 boot_animation.xml but still no go. There has to be some way right?
roeblerrieland said:
This is probably a noob question but I've searched and tinkered and I cant get this file altered or replaced. It's located on the device under /system/media. I've rooted my device(if this is relevant??). and copies he xml file first to my sd card and then to my pc where I've altered it(trying to get rid of the Orange logo) and now i want to copy it back to the Hero. So I've tried adb shell and then
> adb push boot_animation.xml /system/media
but that doesn't work I have also tried to chmod 777 boot_animation.xml but still no go. There has to be some way right?
Click to expand...
Click to collapse
try:
adb push boot_animation.xml /system/media/bootscreen
Thanks for helping me out.
My Vibrant is rooted. When I adb shell into my phone and try to ./file or chmod 755 file it gives me a permission denied.
I believe I am already running as su in the terminal. Anyway I can get Android to let me modify the file? The file in question in on my sdcard, not in /system.
Thanks!
symbit said:
Thanks for helping me out.
My Vibrant is rooted. When I adb shell into my phone and try to ./file or chmod 755 file it gives me a permission denied.
I believe I am already running as su in the terminal. Anyway I can get Android to let me modify the file? The file in question in on my sdcard, not in /system.
Thanks!
Click to expand...
Click to collapse
/sdcard is mounted noexec, you can't mark files executable on it. You could remount it, but it's handled by vold so you probably meted to change the configuration for vold to get it to stick. If you are trying to run a script, use "sh script.sh".
can you help me with this module ??
make zip file who will work when i install in xrecovery?
Im noob and i dont know how to do it
http://forum.xda-developers.com/showthread.php?t=1135965
just follow the instruction, there's nothing complicated...
??
- push ax8mt.ko to /system/lib/modules
how to do it. ??
just cut/paste it there using root explorer, or whatever file manager ur using.
What I do is rename x8gesture.ko to x8gesture.bak from /system/lib/modules and then rename ax8mt.ko to x8gesture.ko and copy it to /system/lib/modules , reboot and it work like a charm, no push, pull or adb shell commands, GL!!!
Hmm well renaming will also work since x8gesture.ko is already ismoded in hwconfig, but this is not advisable.
Well ill explain it to you so that you will not have to rename any other modules in the future.
- push ax8mt.ko to /system/lib/modules - push means to move, copy or paste.
- run the following command phone terminal or adb on pc
Code:
insmod /system/lib/modules/ax8mt.ko - command to put the module in the system.
In your hwconfig.sh there is a line
insmod /system/lib/modules/x8gesture.ko that's why it works when you renamed ax8mt.ko
So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!
You did a good job of explaining the situation. I am in the same position.
Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market
I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2
FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?
Not sure....I don't think so. Good luck!
RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.
I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!
Everything was good until I started messing with the 4.4 roms. Now no matter what I do. Full Wipe, Factory Image restore, try different Roms/Kernels, etc, my MAC Address will reset after every reboot. This is an issues as I use Mac Filtering on my router. Any Ideas?
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
joaocadide said:
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
Click to expand...
Click to collapse
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
..
chainup said:
For me it's only the last 6 numbers/letters that keep changing on reboot. For both Wifi and Bluetooth. Is it the same for you guys?
Click to expand...
Click to collapse
Yeah first are always 11:22:33
Thank you, bandit97!
It's working fine now! =D
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
i came from your link too but this didn't work for me
anyone know why?
Hi. This has been driving me crazy! My Nexus 4 also gets a new Mac address on each reboot. My local WiFi hotspot thinks i am a new customer every time I visit (as it uses Mac address filtering) which is frustrating. I got onto Google about it but they said i should return the phone to the retailer (didn't get it on the Play store). I tried reverting the phone to Android 4.3, resetting etc but nothing works. I the phone was fine at first so I can only assume it is a hardware fault. Does anyone have any more incite into this or a solution?
Could someone explain how I run the commands in an adb shell? I'm familiar with adb and android toolkit etc. Many thanks! PS. I tried it using root explorer and it did not work
Sent from my Nexus 4 using xda app-developers app
Where is /persist directory?
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
You DO need to be rooted
ayonbaxter said:
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
Click to expand...
Click to collapse
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on Google Play).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found here.
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
furboom1240 said:
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on ).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found .
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
Click to expand...
Click to collapse
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Lack of Details
tommy0014 said:
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Click to expand...
Click to collapse
First of all, do you have Superuser-managed root access? In order for me to assist, you need to answer that. The /persist directory should certainly exist, as it was so on all devices I own, rooted or not. When browsing the filesystem, please be careful what you mess with. Even with root access, you must exercise judgment in what you modify.
As always, Root Responsibly.
Stay custom, my friends...