Develop Bugs

Can't edit main.conf file

Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175

neomagik said:
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
Click to expand...
Click to collapse
As we don't have write access to /system on a normal booted desire, you have to do all your work in recovery-mode.

I can get into recovery mode ok but how do I edit the file I want from there?
The options I have are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off

Extract the file out of the rom, change it, than push it back to the rom.
You can do that from ADB shell while your phone is in recovery.
You can find commands how to backup files and push/delete them back to ROM on this forums, or you can search it on internet.

dont forget to mount /system
adb shell in a new terminal screen
then mount /system

I can't figure out what I'm doing wrong.
I've tried the method suggested by allla and ivicask ie, using adb commands in recovery mode and I get the same result as using root explorer, the file appears to have copied successfully it reboots but the original file is back again
I've also tried vastlopers method and after lots of reading found that the device needs to be booted normally to 'remount' however when I try to push the file now it says "Directory not empty"
It seems to me that this adb method is just a long winded alternative to root explorer, none of which get the desired result.
Please help?

Bump. Bump.

I've now tried adb file explorer but can't figure out how to install Busybox on my device.
I'm out of ideas. Someone must know how to edit/overwrite the main.conf file.

I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?

neomagik said:
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
Click to expand...
Click to collapse
Yes it is. It's also written in the root tutorial!

[Q] How to change Bluetooth MAC Address

Is it possible to change it using root or adb please?

Why would you want to?

Nope. Impossible

NeoTechni said:
Why would you want to?
Click to expand...
Click to collapse
just wanted to clone my wife's one for the hands free in the car to avoid having to switch through the menu in the car.

I was unable to locate /pds as per http://pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac from http://forum.xda-developers.com/showthread.php?t=992326. I suspect every phone maker puts Bluetooth address where they wish...
However I was able to locate a zero byte bt_mac_addr file with no extension in /proc folder. It is empty both when bluetooth is on and off.
I hope someone more technically skilled than me can figure out if it can be populated to change the bluetooth address succesfully.
Thanks in advance

I looked at the '/proc/bt_mac_addr' file again using root explorer this time and can see my bluetooth mad address in it and could edit the address and change permissions to it but the modifications don't stay saved even after reboot though the root explorer says changes saved successfully. Can someone help me modifying the file please.
I'm on rooted 2.3.3

/proc is a virtual Filesystem provided by the Linux Kernel. The changes you made there won't persist a reboot cause it only gets saved in Ram.

Thank you. Does it mean I need a script of some type? Is it possible to achieve a change some other way? The pocketnow article seems to do it for the motorola phone but by modifying text file in another folder which I cannot find.
I followed the same process as follows using below commands
C:\Program Files\Android\android-sdk\platform-tools>adb push C:\APK\bt_mac_addr /sdcard/download/bt_mac_addr
1 KB/s (18 bytes in 0.015s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell
$ su
su
# cp /sdcard/download/bt_mac_addr /proc/bt_mac_addr
cp /sdcard/download/bt_mac_addr /proc/bt_mac_addr
cp: can't create '/proc/bt_mac_addr': File exists
Is there another file I can change for it maybe?
Thanks again for all the help.

If you really want to do it then you can (On stock rom) use the same trick that is used for adb remount (Put an echo whatever into into /etc/install-recovery.sh)
You need to make sure it runs as root as well
Have a play around.
Installing the insecure adb apk (From Paul Modaco).
and
adding to the end.
/system/xbin/echo 8D:64:22:01:E2:A9 > /proc/bt_mac_addr
looks like it should work.
(If you have an unlocked bootloader then you can just do it from init.semc.rc in the initramfs)
Or you can look at the method (I posted the manual method in the rooting/insecure adb thread).
This presumes that this is actually working (Its possible you might have to restart a service to actually change it).

just make a simple init.d script

Thank you both. I Will look at it when i'm at the pc. A bit scared having never done anything similar. I Appreciate your guidance very much
Sent from my R800i

Thanks again for your previous replies. I tried "/system/xbin/echo 00:01:02:03:04:05 > /proc/bt_mac_addr" using script manager with superuser permissions granted and running in root mode but it gives the following error: "echo: write error: Input/output error". Same problem in gscript unfortunately.
Would you please tell me what this means and kindly suggest what I should do. I have not figured out yet how to do adb insecure or init.d but hope you could suggest the best way after seeing the above error.
Thanks in advance

ps3taker said:
Thanks again for your previous replies. I tried "/system/xbin/echo 00:01:02:03:04:05 > /proc/bt_mac_addr" using script manager with superuser permissions granted and running in root mode but it gives the following error: "echo: write error: Input/output error". Same problem in gscript unfortunately.
Would you please tell me what this means and kindly suggest what I should do.
Thanks in advance
Click to expand...
Click to collapse
You probably have to remount /system writable

Atarii said:
You probably have to remount /system writable
Click to expand...
Click to collapse
Thank you - I tried this but still same error

ps3taker said:
Thank you - I tried this but still same error
Click to expand...
Click to collapse
try this:
Code:
echo "00:01:02:03:04:05" > /proc/bt_mac_addr

DooMLoRD said:
try this:
Code:
echo "00:01:02:03:04:05" > /proc/bt_mac_addr
Click to expand...
Click to collapse
Thanks - I tried this but it still gives the same input/output error unfortunatelly
Besides mounting system as rw via script manager option I also enabled run at boot, run on network change, run as root but still no change before and after reboot.
I hope you could think of something please. Maybe /proc folder needs to be mounted rw but i'm not sure how or if it is not rw already - root explorer has no problem openning it rw straight away...
Thanks again for everybody's help in advance

ps3taker said:
Thanks - I tried this but it still gives the same input/output error unfortunatelly
Besides mounting system as rw via script manager option I also enabled run at boot, run on network change, run as root but still no change before and after reboot.
I hope you could think of something please. Maybe /proc folder needs to be mounted rw but i'm not sure how or if it is not rw already - root explorer has no problem openning it rw straight away...
Thanks again for everybody's help in advance
Click to expand...
Click to collapse
It won't work as that interface is read only
Sent from my R800i using XDA App

Thanks for trying to help.
I wonder if there is another file somewhere. Any idea what Play's equivalent of Motorola's Atrix 4G folder called "/pds" is - as it it seems to work for them: http://pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac
Thanks again for all the help - it was exiting to try scripts and other things you pointed me to.

[Q]

This is a follow-up of the thread " [Q] can't locate /mnt/sdcard/ ". That thread is now locked.
I was able to get ES File Explorer to display /mnt/ in the path to /sdcard/. But now, while in /mnt/sdcard/, I do not see /system/bin/. The routines that root the A100 require access to /system/xbin/.
I looked in ES File Explorer - Settings - File Settings - for an obvious solution but found none. "Show Hidden Files" is already checked.
I suspect that maybe the lines entered via the command prompt (like /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`' or /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`') will somehow unlock or allow access to /system/xbin/ but I'm not sure. I guess I could just plow ahead and see what happens but I much prefer to anticipate and prevent problems beforehand rather than try to fix things after I've screwed it up.
So 3 questions:
1. Will the command line entries automatically be able to write to /system/xbin/?
2. If yes, will I then be able to read and write to /system/xbin/ using ES File Explorer?
3. If not, how do I gain access to /system/xbin/?

I think your trying to make things more complicated for yourself than what they really are, of course it helps to know a little Linux when doing things like this.
1. Will the command line entries automatically be able to write to /system/xbin/?
Yes, that's what the mount -o remount,rw /system does in the command you run.
2. If yes, will I then be able to read and write to /system/xbin/ using ES File Explorer?
No, this is not needed as the commands handle this for you.
3. If not, how do I gain access to /system/xbin/?
You don't... just run the commands for rooting via the terminal and everything is done for you.
The ONLY thing you need to do with ES is to extract the downloaded su file and put the su file itself in /mnt/sdcard. Once you've done that, open the terminal emulator and run those 3 commands.

I do tend to over think things! haha But as I said, I much rather spend extra (possibly useless) time anticipating problems while my piece of equipment works than scratching my head with a brick in my hand.
Thanks for the tutoring, I shall plow ahead with confidence! ... right after I fix my water heater. Now there's a non-working piece of equipment one really can't do without!

ricknau said:
This is a follow-up of the thread " [Q] can't locate /mnt/sdcard/ ". That thread is now locked.
I was able to get ES File Explorer to display /mnt/ in the path to /sdcard/. But now, while in /mnt/sdcard/, I do not see /system/bin/. The routines that root the A100 require access to /system/xbin/.
I looked in ES File Explorer - Settings - File Settings - for an obvious solution but found none. "Show Hidden Files" is already checked.
Click to expand...
Click to collapse
Just a quick note for future reference: the /system/xbin directory isn't located under /mnt/sdcard.... its located under root.
Sent from my A100 using Tapatalk

Crap! Didn't work for me
I did all the steps ...
Extracted the su file (using Winzip on my PC), copied it to /mnt/sdcard/, then entered the commands lines with a terminal emulator. But the program Root Checker says I am not rooted. The Busybox installer program says the same.
I figured out how to display /system/xbin/ (in root ). And I can see the su file in /system/xbin/. It is 25.71 KB. So I figure my command lines ran OK. What could be wrong?
I've tried the process several times. I used a signed su (whatever that means). After each attempt the "modified" date and time stamp of the su file in /xbin/ matches the date and time of the attempt.
Busybox error screen said if I think I am rooted to "go into Superuser app and click on Busybox installer and then click "Forget" and restart this app". I guess I could try that even thought Root Checker agrees with the "not rooted" condition. Is it OK to attempt to install Superuser if you aren't rooted?
The good news is that so far the tablet is still working fine.
Any ideas anybody?

Im having this exact same problem, and havnt found a fix yet for it.

I finally got it!
Oh man I got it! I'm such a dumbass! I wasn't reading carefully enough. The Superuser app from the market is the key. Superuser must be installed first and opened before Busybox can even be installed. Now I have Busybox installed and Root Checker says I have root!
Thanks to all the smart and helpful people who provide the great info here and in the other forums to help us less learned ones make full use of these great tools!

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.

Reserved

Reserved

This is the same as https://github.com/saurik/mempodroid
saurik ftw.

times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.

Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!

Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus

Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium

This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium

Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.

Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk

efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links

try /data/local/tmp

Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb

Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk

OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.

Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.

convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers

Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.

[Q] Copying files to /system | S-ON | HTC One X

I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.

adb remount
adb push filename /system/xbin
Sent from my HTC One X

You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app

realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .

Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.

KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)

realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?

KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.

realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590

realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .

make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.

NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.

Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.