Root System files

[reppard]

Why can't I edit or remove system files such as init scripts. I've tried with the terminal, adb, and root explorer. Any ideas? I think I've found a way to over clock stock 2.2.1 but I need to replace or edit some parameter files

 

[joneidy]

Why can't I edit or remove system files such as init scripts. I've tried with the terminal, adb, and root explorer. Any ideas? I think I've found a way to over clock stock 2.2.1 but I need to replace or edit some parameter files

Exactly what files do you want to edit? Because some cannot be edited via those methods that you mentioned.

 

[reppard]

For files that can't be edited with those methods how would you go about editing then

 

[joneidy]

For files that can't be edited with those methods how would you go about editing then

It depends because some if them are incorporated on either boot.img or system.img and you need to unzip the image and then edit the files.

 

[reppard]

Ohhhh I gotcha. So I would have to do a nand back up and then i should be able to mount the img in linux right?

 

[joneidy]

Ohhhh I gotcha. So I would have to do a nand back up and then i should be able to mount the img in linux right?

No mount it you will need to split it to edit the files, And when you are donr repack it and flash it to your phone

 

[reppard]

I mounted it but I still don't have permissions. What do you mean split it? How do I do that?

 

[asadullah]

I mounted it but I still don't have permissions. What do you mean split it? How do I do that?

Do you have ubuntu installed if so watch
this

 

[reppard]

I'm running slack but I'll watch it anyway

 

[richiedaze]

The android system is almost identical to a ubuntu system.
The first image that gets mounted to the nand chip is the bootloader (SPL).
If the Bootloader has no commands( say from the recovery image) it mounts the boot image.
The bootloader mounts the boot image as READ ONLY. So any changes done to any of it's file will be deleted upond a reboot and the image is remounted as it was before the edits.

To edit this image, you must pull and push files to the image its self. But as in anything you do, ALWAYS make a backup. If your modified boot.img is non functionable, you can replace the original one and have a working device. The easiest way to edit a boot.img is with a Android kitchen.

 

[reppard]

Thanks for the info, I've tried to push system files via advanced but it always says I don't have permission. Is there a link to android kitchen that is compare with my phone?

 

[reppard]

There is a file located at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_frequently. If we change the value of this file would that not allow us to overclock this device?

 

[alexxseven]

There is a file located at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_frequently. If we change the value of this file would that not allow us to overclock this device?

i would think you are on to something there, personally i been looking into extracting the boot img and making a OC kernel for it. that and trying to port over the xoom 3.0 music player, your info is very helpful as the contents of the file max read 600000 and min is 122880

basically the stock max and min frequencies :O

i also found that the scaling max and min have the same info, as well as set speed having <unsupported> in it >.>

 

[reppard]

Yeah I looked at those values and even tried to change them. I just need to figure out how to unpack the img files in linux. I found a link to some Perl scripts but the link didn't work :/

 

[alexxseven]

Yeah I looked at those values and even tried to change them. I just need to figure out how to unpack the img files in linux. I found a link to some Perl scripts but the link didn't work :/

i think i know what links your talking about. i used the same post to try and understand stripping it apart in a hex editor. still working on getting that understood so i'll let you know if i do. i have a linux setup also though so i might try to mount it on that too

 

[reppard]

i think i know what links your talking about. i used the same post to try and understand stripping it apart in a hex editor. still working on getting that understood so i'll let you know if i do. i have a linux setup also though so i might try to mount it on that too

Thanks man, I am running slackware and I was actually able to mount the img to a folder(mount point) but I was unable to make any changes. Always says permission denied even though I chmod it and make sure its mounted rw

 

[reppard]

If you want to mount it in Linux you will need to mount it like this.

mount -t sysfs image.img /mount/point
You might have to modprobe loop and add -o loop. Depends on your setup

 

[alexxseven]

ok well i have actually been able to get into ubuntu, i have a copy of the perl scripts, i've ran them to get the GZ file for the ramdisk and the kernel binary.

as far as the ramdisk goes, alot of files are missing. but a few important ones are there and the RAW image files are there too,

as far as the kernel goes. i don't know how much i can do with it >.> lol

thats my update though. sorry it took a while but i've been having net issues as well as issues with my ubuntu installation >.<

 

[richiedaze]

There is a OC kernel posted on a thread somewhere. What is it that you guys are trying to do?

 

[reppard]

There is a OC kernel posted on a thread somewhere. What is it that you guys are trying to do?

OC kernel for 2.2.1? I know there is one for 2.2 but our phones can't run that one

 

[richiedaze]

Has anyone tried to run it? Backup first of course! They are both froyo roms and that is a froyo kernel...
Source code for froyo kernel is identical.

 

[andyo70]

Definitely not. You'd essentially be injecting the kernel code for 2.2 into the 2.2.1 firmware. They won't play very nice together me thinks.

 

[richiedaze]

Remember the differences between builds. 2.2.1 is just a patch for the security exploit!

 

[andyo70]

So you're saying the OC kernel and stagefright patch should work for 2.2.1 then?

 

[richiedaze]

Yes. But the boot.img ramdisk has to be changed to match the 2.2.1 build... I can fix and post it if you guys want.


Edit:
Well that OC kernel uses koush's any kernel updater, then no edit needed. Try it!