Develop Bugs

Enabling the read/write on fonts folder

Hi everyone,
I have been trying to enable the read and write on fonts folder by chmod
Unfortunately, nothing worked for me
everytime I write chmod 777 system/fonts/ on CMD it gives me an error message saying read only.
My device is rooted.
would appreciate any help
Thanks & Regards

Try adding su before chmod
For example
su chmod 777 directory

Thanks for your help C45hY
But that didn't work also
it says Permission denied

any clues???

/system is mounted read only

I know mopodo
How can I change it to read/write?

mopodo said:
/system is mounted read only
Click to expand...
Click to collapse
Exactly!
What you need to do is go to the terminal and type in the following commands:
Code:
su # gain root shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system #remount the /system partition read/writte
regards

[Q] Rooting Problem Please Help

so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
what am i doing wrong
heres a pic
{
"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"
}
after cd /data/local it says permission denied what do i do?

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
are you working from this page? http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
why are you cd'ing to data/local? what's in that folder? in the other thread you said you had your files in gfree_02??

http://forum.xda-developers.com/showthread.php?t=855764
im using this method

why would you cd to data/local? you need to put files there, not pull files from there...

martonikaj said:
why would you cd to data/local? you need to put files there, not pull files from there...
Click to expand...
Click to collapse
what should i do then
what commands do i do thanks for the help i appreciate it

On your computer's terminal/command line, navigate to where the gfree file is, and then...
Code:
adb push gfree /data/local
adb shell
This copies gfree to your phone, then puts you in your phone's terminal. Then do this:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764

zbrah said:
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764
Click to expand...
Click to collapse
Aren't you supposed to be running the commands:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
In terminal emulator on your phone? from what I remember this is the way I did it. Could be mistaken by the wording though... I just remember using ADB to push all the files then just running terminal emulator on my phone instead of running a shell. Worth a try if you can't get ADB shell to work properly.

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
From the look of this you still have a $ sign this means you dont have root permission, it should be a # sign after typing su in adb shell . Looks like your temp root didn't work or your not allowing root user permission on your phone right after typing su in adb shell.

The guide you are trying to use specifically says "So we're assuming you've permarooted already and usb debugging is on" but from the thread title, it sounds like you are trying to get permanent root. The guide does not work if you don't already have root.
You should probably use the guide in the Wiki linked to earlier.

The problem is the very first command you type into the command prompt on your phone, i.e. "su", is giving you "permission denied". So as others have said, you are not getting root permissions. If you have rooted previously then the "Superuser" app pops up and asks for permissions the first time you try "su", check it's not coming up with a box on your phone which you're failing to see (then it times out after a few seconds and says "permission denied").

[Q] Deleted su file.. how can I restore..?

Hi,
I've been having problems with my root and superuser. I tried to install supersu also but was crashing every time. The superuser could not get the new su version and generally my A100 acted as not rooted. I tried to do the rooting process again and again with no luck. I downloaded the latest su version and tried the commands again.
Then it crossed my mind to remove the old su from xbin (since I got the new version) and give the commands. So I rm it but then I gave it a closer look and saw that the command did not copy the new su to xbin but was using the cat command. The commands I gave are
(The su version is supposed to be the latest one)
$ export PATH=/data/local/bin:$PATH
$ pwd
/
$ cd sdcard
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ ls -al /system/xbin/su
-rwsr-sr-x root root 91980 2012-03-24 01:40 su
$ /system/bin/cmdclient ec_micswitch '`chmod 6777 /system/xbin/su`'
$ ls -al /system/xbin/su
-rwsrwsrwx root root 91980 2012-03-24 01:40 su
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ mv /system/xbin/su /mnt/sdcard/temp
failed on '/system/xbin/su' - Cross-device link
$ /system/bin/cmdclient ec_micswitch '`rm /system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su: No such file or directory
Now I have no su file... how can I restore it? Can anyone send me the su from their A100 (I guess it would be the same)
I can't understand why the rooting stopped. It use to work ok...maybe the interference of superuser and supersu caused this..
It happened after a restart...
Anyhow... how do I get my root back...? Any ideas...?
Sent from my A100 using Tapatalk

SuperSu and Superuser both use different su binaries. Which one are you going to use (it's not wise to have both or else they are going to interfere with each other).

The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk

dkaratasos said:
The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Are you running honeycomb or ICS?

Theonew said:
Are you running honeycomb or ICS?
Click to expand...
Click to collapse
Honeycomb
Sent from my A100 using Tapatalk

dkaratasos said:
Honeycomb
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.

Theonew said:
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.
Click to expand...
Click to collapse
I did but did not work
$ sh root.sh
Copying root file & changing permissions (making your tab super!) Please wait...
-rwsr-sr-x root root 22148 2012-04-01 01:45 su
If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!
Now you need to install superuser and open it, then go to the wrench icon and tap it
Find the update area and tap it, tap update now to update the super user file that this script copied over earlier
Once its updated, install busybox from the market and your all set!
$
Both superuser and supersu could not gain root shell...
If you check the size of the su file in xbin now and initially you will see a big difference ...
Can someone upload their su file...? Isn't it the same...?
Sent from my A100 using Tapatalk

I opened the root.sh ...
It has the same commands as a script... it would not do anything different...
Root.sh:
echo "Copying root file & changing permissions (making your tab super!) Please wait..."
sleep 2
/system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
sleep 2
/system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
sleep 2
/system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
sleep 1
rm /mnt/sdcard/su
echo " "
ls -l /system/xbin/su
echo " "
echo "If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!"
echo " "
echo "Now you need to install superuser and open it, then go to the wrench icon and tap it"
echo "Find the update area and tap it, tap update now to update the super user file that this script copied over earlier"
echo "Once its updated, install busybox from the market and your all set!"
Sent from my A100 using Tapatalk

The only thing left to try is a factory reset (or update to ICS if you want to keep all your data) then re-root (that will work). In these cases, one would just flash superuser via recovery, but since you are on HC and have no custom recovery, that simple fix is not possible.

How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk

dkaratasos said:
How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).

Theonew said:
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).
Click to expand...
Click to collapse
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk

I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Thanx for your help...
Sent from my A100 using Tapatalk

dkaratasos said:
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
1. Corruption.
2. That's the chosen "exploit".
3. SuperSu's su binary will be a different size than Superuser's su binary.
4. No non-rooted device has a su binary. The su binary allows root access (which a non-rooted device does not have). The rooting process places the su binary in a device.
dkaratasos said:
I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Click to expand...
Click to collapse
Great.
P.S. - You should have said you still had SuperSu installed.

And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4

raphsabb said:
And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Well according to chainfire here
http://forum.xda-developers.com/showpost.php?p=23442897&postcount=43
Both can be installed and whichever you update the su file grants you the superuser ....
It crashes thought having both...
Sent from my A100 using Tapatalk

They can both be installed but not used together, I added a screenshot of the description in play store, hopefully u can see it from my screenshot
{
"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"
}
Sent from my A100 using tapatalk

Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!

aharol said:
Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!
Click to expand...
Click to collapse
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Tapatalked from my Galaxy S II.

pio_masaki said:
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Click to expand...
Click to collapse
I'm a relative noob so let me restate to make sure I understand.
- do a reboot in recovery mode
- go to the .zip file of the current rom (CM7 --- the file I have is the latest) and run it
- AFTER that is done (and not before?), wipe the cache and dalvik cache
Is this correct. Any critical step that I'm missing?
Thanks

ADB Help

Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?

Antalor said:
Hello there,
does anyone know how to mount the galaxy s4 as writeable via adb?
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9 /system
is the Red Coloured the right Path?
Click to expand...
Click to collapse
omg no no no no.
if you are talking about trying to use "adb push <name of file> <destination file>"
Then you must use "adb remount" if it fails, you are not on an insecure kernel. Thus your only option is to push to the sdcard then use "adb shell" and navigate to your sd card and use "cp <name of file on sdcard> <destination file location>"
as for the commands, it is NOT what you have posted. it is simply
mount -o rw,remount /system
nothing else is needed. You will seriously mess something up if you try mounting it as yaffs2 considering we use ext4 now. FYI, the above command can only be entered AFTER first entering "adb shell" which gives you a command line on the device to execute commands.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app

Antalor said:
No, i want uninstall apk's/apps via adb and theerfore i have to mount it as writeable, and, also i want to:
pm list packages -f > file.txt and got error read only system...
What exactly is yaffs2?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Then you need to use
adb shell mount -o rw,remount /system
thats it. To uninstall apks, use:
adb uninstall <package name>
And you are getting a read only system error because you are trying to create that "file.txt" file onto your "root" directory.
do this:
adb shell cd /data/media/0
then try to do your list packages.

Working viper4a with easy steps.

STEP 1: Root the phone with the link provided in the op7t forum.Now you have magisk.
STEP 2: Install the SE LINUX SWITCH APP link: https://labs.xda-developers.com/store/app/com.ibuprophen.selinux
STEP 3: change selinux to permissive. now to go settings-battery optimisation-change the selinux app to not optimised.turn off googleplay protect.
STEP 4:now all you need is a modded stock recovery. download it from here. link: https://drive.google.com/file/d/1S-1Np5CFx9z98Ntp8vUTWFU1ksqIeBSN/view
STEP 5:now go to fastboot and flash the stock modded recovery. CODE: fastboot flash recovery RECOVERYNAME.zip now you have adb enabled stock recovery.
STEP 6:now boot to stock recovery while connected to pc and type adb devices in cmd. it should go to adb. if yes proceed to next step.
STEP 7:now install viper4fx from magisk. phone will reboot. go into viper4a app and install drivers. it will go to fastboot ofcourse.
STEP 8: boot to recovery from fastboot. then just type in the following commands/
1. adb shell
2. cd data
3. cd adb
4. cd modules
5. cd ViPER4AndroidFX
6. rm post-fs-data.sh
7. exit
STEP 8: phone will now boot. again go to viper4a app and install drivers and repeat step 8 again.
VOILA now you have viper fully working on our beloved op7t.
NOTE: disable bluetooth absolute volume for bluetooth to work in v4a.
Dont try installing viper in 10.3.1. you will be stuck in fastboot. so instead download 10.3.0 fastboot image and flash it. then follow the above steps and update the phone by the following.
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot. Root, viper and all the magisk modules will be retained. Give a thumbsup

Anyone tried this?

VIZT said:
Anyone tried this?
Click to expand...
Click to collapse
perfectly working in mine.
{
"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"
}

why do i need always to set os to permissive?

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
Permissive sets SELinux to behave in a different way than Enforcing(default), which is required for V4A to work.
As far as technical details, I have no idea.

Permissive is dangerous.

Batfink33 said:
Permissive is dangerous.
Click to expand...
Click to collapse
Why ? Explain more please

Snake.s9 said:
Why ? Explain more please
Click to expand...
Click to collapse
Leaves the kernel open to any malicious apps that want to take control of your phone.

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
permissive mode allows some features to run on some instances which are not allowed in enforcing mode. like for example debugging.

Apparently its not meant for me to have viper. Modded recovery won't even work.

i tired it says no such file or directory on rm command
had to load app and install driver first

shorty1993 said:
Apparently its not meant for me to have viper. Modded recovery won't even work.
Click to expand...
Click to collapse
not working in the sense? not able to flash or adb isnt responding?

chwads2k8 said:
i tired it says no such file or directory on rm command
had to load app and install driver first
Click to expand...
Click to collapse
yes. postfs file will be generated only after installing the app. it is necessary to remove it for the phone to boot and for viper to work aswell.

I got to step five say
C:\adb>adb shell
error: device not found

AboNaya said:
I got to step five say
C:\adb>adb shell
error: device not found
Click to expand...
Click to collapse
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts

AboNaya said:
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts
Click to expand...
Click to collapse
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.

not working
adb shell
# cd data
cd data
# cd adb
cd adb
/system/bin/sh: cd: /data/adb: No such file or directory
what to do now?

grandpajiver said:
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.
Click to expand...
Click to collapse
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#

AboNaya said:
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#
Click to expand...
Click to collapse
Don't type su, just adb shell and proceed
Sent from my OnePlus7TPro using XDA Labs