Database Develop

help with user.conf

can someone give me a tutorial on how to update the user.conf..i have looked at the compcache threads and linux swap but im not getting it...i want to be able to update it through terminal emulator and do i have to do nething to the userinit.sh if i change the user.conf...because numerous configs i have done for swappiness and linux swap...etc, have shown no difference..can somone give me a walkthrough...thanks so much..sry if i have a lot of questions just want to make myself more knowledgeable so i can hopefully return the favor to somone else one day

i do not know if you can edit it through the terminal sorry. i do know that you do not have to change the userinit.sh if you change user.conf, also i do know that you can open it up with PSPad (thats what i use) on a computer edit it there and push it back to phone and reboot. sorry i couldn't answer all of your questions

well i have had no problems editing it...its just putting it back nd making sure it works..now i have no problem using adb if u know of a tutorial to use it on mac...or know how to use it on mac

when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command

david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
delete this post; see below...

david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
this applies to tools and location of user.conf on cyanogen's roms ->
-transfer it to the root of your sdcard from your pc or mac to the g1.
-unmount sdcard from dropdown on the g1
-open up terminal on the g1
type and hit enter afterwards: cp /sdcard/user.conf /system/sd
type and hit enter afterwards: dos2unix /system/sd/user.conf
type and hit enter afterwards: chmod 664 /system/sd/user.conf
type and hit enter afterwards: exit
reboot

see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them

bonkasnucca said:
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
Click to expand...
Click to collapse
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works

david1171 said:
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
Click to expand...
Click to collapse
775 = rwx-rwx-rx. conf file does not need executable in u-g nor x in o groups.
664 = rw-rw-r
if it is in /system/bin do this:
open up terminal
dos2unix /sdcard/user.conf
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/user.conf /system/bin
chmod 664 /system/bin/user.conf
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
reboot

RWSystem and ROSystem

a friend wanted myfaves but I know there is any easier way than to type mount -o rw,remount and the rest I've tried rwsystem and rosystem what am I not doing?
It says rwsystem is not found

you typing it into adb or the terminal?

RWSystem and ROSystem are custom scripts some devs are placing in their /system/bin. Find a build that has them (I think JAC's do) and then push them to the phone with
Code:
adb remount
adb push RWSystem /system/bin
adb push ROSystem /system/bin
adb shell
#cd system/bin
#chmod 0755 RWSystem
#chmod 0755 ROSystem
#exit

oh ok thanks for the help I appreciate it.

when I type it in it says permission denied. I used both ADB and terminal.

PlatinumMOTO said:
when I type it in it says permission denied. I used both ADB and terminal.
Click to expand...
Click to collapse
you must type "su" first and choose always allow when promted to grant root access.

I did. and I followed all the instructions here it still doesn't work.
do I need to reboot afterwards?

PlatinumMOTO said:
I did. and I followed all the instructions here it still doesn't work.
do I need to reboot afterwards?
Click to expand...
Click to collapse
you did make sure to chmod 755 them didnt' you

yep I used adb shell chmod 755.
and then used SU File Browser to chmod 755

[ROOT] Linux command lines if SuperOneClick fails

Hi.
I've tried many times to root my LG2X with Z4root, UniversalAndRoot, Visionary and SuperOneClick since I've bought it but it failed each time.
I've seen the [Root] topic in the developpement thread but I can't post there (less than 10 posts...) but I want to help someone to root his/her mobile.
I've searched a long time a good way to do so without SuperOneClick (which doesn't respond with Windows Seven or Ubuntu 11.04) but there is none.
There we go...
Disclaimer : I can't be responsible if you break your phone, cancel your warranty or launch your LG2X on the wall in rage.
If you want, there is already SuperOneClick which run smoothly for many geeks : LG2X SuperOneClick Forum and SuperOneClick Forum
My HTC Magic had been rooted with the command line and I've tried myself to do so with every bit of informations and tips I could find on Internet.
I recommand to test the SuperOneClick method and if it fails, come test this with a Linux terminal (psneuter, su-v2, busybox and the SuperUser.apk can be found in the SuperOneClick archive) :
Code:
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
adb remount
adb shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 6755 /system/xbin/su
# busybox chown 0.0 /system/xbin/su
# busybox cp /system/xbin/su /system/bin/su
# busybox chown 0.2000 /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
adb install Superuser.apk
adb reboot
And... Normally you have permanent root on your LG2X.
You can check the files permissions with
Code:
ls -l /system/xbin/su /system/bin/su
-rwsr-sr-x root root 26264 2011-04-23 20:07 su
-rwsr-sr-x root shell 26264 2011-04-23 23:20 su
It seems that /system/xbin/su isn't necessary at all. The su command which gave you the root is the one in /system/bin/. And I had some problems with /system/xbin, I've deleted the folder (with rm /system/xbin or mv /system/xbin /dev/null, I can't recall) and applied mkdir on it again.
If this can be of help, I'll update this later.

thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed

Thanks but with Windows Seven 64 bits, Linux ou Windows Seven 32 bits with Virtualbox I end up with "SuperOneClick doesn't respond" or stuck on with "chmod psneuter" (with the drivers properly installed).
It's only an alternative solution if SuperOneClick doesn't run properly for another guy.

Thanks a lot for that tips.
The problem I have now is that su isn't persistant.
When I use
$ su
It hangs up few seconds... and says "Permission denied"
I've used su-v2
Here are the su permission :
-rwsr-sr-x root shell 26324 2011-02-13 14:43 su
Is there a more up-to-date su, that will maybe fix the problem ?
Thanks.
EDIT :
Ok.
The wait time seems to come from SuperUser, I've removed it.
Now I have directly the "permission denied", and "stat failed with 2: No such file or directory" in the logcat.
Maybe that can help.

Hannes The Hun said:
thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed
Click to expand...
Click to collapse
It didn't for me (after installing nightly 51)
With the step-by-step instructions I get "Failed to set prot mask (inappropriate ioctl for device)" when trying to execute psneuter.

Hi.
Sorry for the wait.
Have you resolved your problem with your rooting?

How do I root S5570MJKT3 or XWKTU?

HI, The latest version of stock firmware for galaxy mini is MJKT3, now how do I root it?

http://www.mediafire.com/?p0oh96olw9h2v72

hi
this will root all versions even the latest one? or like released by 1 minute? or new ones that has been released 1-10 seconds ago?

just try it if it worked just thank me and the Dev of the update package
if not do something else
I forgot to tell you that you will need to flash that package in stock recovery (in CWM it will not work)

It doesn't work.

it doesn't work for me too
super one click can't be used too

Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)

i did flash it
---------- Post added at 06:42 AM ---------- Previous post was at 06:14 AM ----------

can
ashu.bigsmoke said:
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
Click to expand...
Click to collapse
can someone tell me if this one will work?

17thGwydion said:
can someone tell me if this one will work?
Click to expand...
Click to collapse
no
I did try another .zip but not succeeded, it just installed super user

you can flash cwm then with the help of adb you can remount system and can push su to /system

tut
dheeraj (dhlalit11) said:
you can flash cwm then with the help of adb you can remount system and can push su to /system
Click to expand...
Click to collapse
can u give me a tutorial on how to push SU to system? or remount system? or full tutorial.. thanks

full tut plz

still no good
still no good feedback, someone try it please

flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted

Can't set SetUID or SetGID bit.
adb shell chmod 06755 /system/xbin/su
"chmod: operation not permitted"
SuperOneClick doesn't work also.
/system partition is 100% full, you have to delete something to push su binary. (i deleted stock samsung apps, and wallpapers)
dheeraj (dhlalit11) said:
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Click to expand...
Click to collapse

you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that

Unfortunately permission change is a must. You must set setuid and setgid (06755), because upon the su binary execution it will pass the owner's (root) permissions.
Can't use aroma file manager to set permissions because /system/xbin/su owner is root and a plain user can't change permission on files that he doesn't own.
I don't know how to solve this issue.
edit:
I can mount the system partition as rfs:
mount -rw -t rfs /dev/block/stl12 /system
Then, i can set chmod 06755 su.
But after unmount or reboot, permission will be set back to 00755...
dheeraj (dhlalit11) said:
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Click to expand...
Click to collapse

it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same

Ok, it's solved!
I tried with ubuntu's adb. Unpacked the universal_gb_root_v25.zip. I mounted the system partition in adb. Then pushed all files with correct permissions to /system/xbin (the apks goes to /system/app).
First:
chown all files to root:shell
Second:
chmod 06755 /system/xbin/su
chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/sqlite3
chmod 04755 /system/xbin/ssh
now it looks like this:
-rwsr-xr-x 1 root shell 853044 Jun 22 2011 busybox
-rwxr-xr-x 1 root shell 60264 Dec 6 10:28 dexdump
-rwsr-xr-x 1 root shell 125024 Jun 22 2011 sqlite3
-rwsr-xr-x 1 root shell 146720 Jun 22 2011 ssh
-rwsr-sr-x 1 root shell 91980 Jun 22 2011 su
It works after unmount or reboot.
Finally i have root access.
dheeraj (dhlalit11) said:
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Click to expand...
Click to collapse

[tutorial]Root any latest firmware with ease

Firstly what i would like to say is this is not a one click root like update.zip or superoneclick you will need to have some basic knowledge of adb and ubuntu and a little bit working mind which can follow the provided steps.
Requirements:-
*cwm recovery already flashed (if not refer here)
* Working linux distro (ubuntu, mint, kubuntu etc.) with atleast sudo rights
* adb setted-up (if not refer here, may not need to follow the usb drivers steps)
* must know how to use adb
* superuser package from here
Click to expand...
Click to collapse
So we are now ready to start
STEPS:-
1. Extract all file (su, busybox) from the downloaded package to the folder where you have adb setted-up
2. open a terminal
3. cd to the directory where you have placed adb and files
4. boot your phone into cwm recovery mode (home power) connect through usb
5. type "sudo chown root:shell /path to su"
6. type "sudo chmod 06755 /path to su"
7. type " sudo chmod 04755 /path to busybox"
8. type " adb devices" if you will see anything attached you are good to go
9. type " adb remount" if you get remount succedd then you can do below steps if not you are doing something wrong do again
10. type "adb push su /system/xbin"
11. type "adb push busybox /system/xbin
12. type adb push supersu.apk ( or what it is called) /system/app
13. now type "adb shell"
14. type su if accepted then you are rooted
15. now type "reboot"
Click to expand...
Click to collapse
you are successfully rooted
enjoy your phone

awesome guide buddy very useful for n0obs

First of all great guide! But please correct these:
You have to mount the system partition manually. Adb remount won't do it!
adb shell
# mount -rw -t rfs /dev/block/stl12 /system
Do chmod/chown in adb. It isn't enough to set it before copying.
# chown root:shell /system/xbin/*
# chmod 06755 /system/xbin/su
# chmod 04755 /system/xbin/busybox
# chmod 04755 /system/xbin/sqlite3
# chmod 04755 /system/xbin/ssh

if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
and thanks for chown part

dheeraj (dhlalit11) said:
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
Click to expand...
Click to collapse
Hi!
For me, adb remount didn't work. It exited with an error code. I don't remember the exact error code... (cwm couldn't mount too)
When I experienced "operation not permitted" while chmoding, the partition was mounted as vfat! Because if you do "mount /dev/... /system" without switches, it automatically mounts it as vfat. In vfat you can't set setuid, setgid permissions.
I think it was just a coincidence that i could rooted with ubuntu. But it worked, so better to use linux (better adb perhaps?).
Rooting is a bit strange in this new firmware. For example when you do "adb shell" while the phone is in cwm, you have root access. So you have to do those things manually while you have temporary root access.

how can you mount rfs file system as vfat i dont think it can be done

dheeraj (dhlalit11) said:
how can you mount rfs file system as vfat i dont think it can be done
Click to expand...
Click to collapse
Yes it's really strange. I don't know how this thing possible too...
But I checked multiple times with "cat /proc/mounts" , and mounting without "-t rfs" it was mounted as vfat.
a bit of googling:
"You can mount as rfs as Fat in ubuntu and read/copy the files
editing them wont work at all ."
So maybe it is possible.