Hi,
I have an xperia sola with build .54. I did everything according to the instructions (http://forum.xda-developers.com/showthread.php?t=1417375) to make init.d scripts work on closed bootloaders also. I wrote one for myself also:
#!/system/bin/sh
echo "0,0,6144,0,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
But unfortunately it does not work. If I run it in terminal the value changes, but it reverts after restarting.
Sorry, for my bad english.
Hey mate,
First, check if init.d support was added correctly. Paste this in init.d with 777 permission, then restart phone, Go to/data/local/tmp/ and see if init.d_log_test.txt exists
If it does, then its an issue with script,else init.d Issue Report back and we'll look into your problem
Cheers
There it is. So, the init.d is working.
Which editor did you use to make the file ? And you did set the right permissions, no ?
I'm use notepad++, and the permission: rwxrwxrwx
Ok.. hm.. next thing, Click the "Show All Characters" option in notepad++. It looks like a "P' button.. See if the end of each line says LF or CR-LF
I see LF
Then I cant see any issues Can you send me the file ? Might be a typo or something missed out when you copy-pasted
Here: http://d-h.st/3Sk
Edit: I tried to edit init.rc. I added this line:
write /sys/module/lowmemorykiller/parameters/minfree 0,0,6144,0,14336,18432
but it doesn't work
Sorry my english.
Still couldnt find an issue Just to be sure its not an init.d issue,can you delete that file in data/local/... and reboot to see if its made again ? Maybe init.d support got broken somewhere in between
I delete the file, but it's recreated. I tried to change the sys/module/mali/parametrs/mali_mem file, and it was succeeded. It's let to change either files, but the minefree not.
Related
Ok, basically my linux knowledge is very limited and i need help modifying a file that gets written on boot (i don't know if this would even work, so if someone could answer that it would be very much appreciated).
The file i'm looking to change is '/sys/module/q6audio/parameters/speaker_max_gain'. In the latest 2.1 build this file is set to '602', which i think explains the slight volume increase from 1.6 (it was set to '600', but located in 'sys/module/msm8k_cad_volume/parameters/handset_max_gain' instead)
So, does anyone know how to alter this file? I know it gets re-written every time you boot the phone, but i can't find where it's being written from. Is it a kernel thing or am I completely wasting my time with this?
Cheers
UPDATE - Thanks to @VogelDerNacht, i've tried a few things like trying to change the value in the init.rc (echo "value" > sys/module/q6audio/parameters/speaker_max_gain) which didn't work, and i then tried to use a sysctl.conf in /system/etc/ to do the same thing, which also didn't work (don't think the kernel supports this), so now i'm pretty stuck
It seems like i may have to wait for the kernel source to be release now ><
how about creating a simple shell script and having it execute as a service from one of the init scripts ?
its possible the sys entry is not created until later in the boot sequence
DJ_Steve said:
how about creating a simple shell script and having it execute as a service from one of the init scripts ?
its possible the sys entry is not created until later in the boot sequence
Click to expand...
Click to collapse
could you give me an example please? i'm pretty new to all this linux stuff
The problem seems to be that when i add the line in to the init.rc (or any of the init files) it gets overridden by something else (probably the kernel) and i can't get it to apply my changes. I can change it fine whilst the phone is running, but that doesn't do anything because i think these files only get read from once when the phone boots.
I could be completely wrong though, like i said, my linux knowledge is pretty bad ><
First you need to confirm that entry boosts what you want
DJ_Steve said:
First you need to confirm that entry boosts what you want
Click to expand...
Click to collapse
That's the problem. I think it reads from the file only once when the phone boots but i don't know, that's why i want to change it on boot to see if it works
their should be a simple script (.sh extension) in /system/etc that you may be able to edit to add echo *your value > sys path to end of
DJ_Steve said:
their should be a simple script (.sh extension) in /system/etc that you may be able to edit to add echo *your value > sys path to end of
Click to expand...
Click to collapse
Tried that. Tired editing the init.rc, that didn't help. I tried adding a sysctl.conf but i don't think the kernel supports it. I tried editing every .sh file i could find but it looks like the kernel just overwrites everything
ok if you fancy a hand trying to get the volume to boost drop me a pm as i woudln mind being a tester ffor playing with werid options (and since iport android anyway i know my way around
this is regarding this thread http://forum.xda-developers.com/showthread.php?t=1064558
can sumone please give me a very detailed instructions how to do this...its really confusing for me since im a newbie..i really want the multitouch feature on my phone...pleaseeeeeeeee..i dont get when the say "goto any shell.the so on so forth....i really dont know wat to nxt. can sumone be so kind to explain it step by step...please......
"Also edit your build.prop and add the lines below:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2 "
^what does this mean????really cluless
I rooted my phone already...downloaded the driver the extracted it then im stuck...
thanks a bunch!!!
Bump...sumone please help!!!
More info, rom, baseband ??
still has the original Sony Ericcsson OS...never changer ...changes ive done was just by rooting it...thanks so much..my concern were just ignored by others
You need to do this:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
attached here
http://forum.xda-developers.com/showpost.php?p=13498312&postcount=53
Please thanks to teapea
D4rKn3sSyS said:
You need to do this:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
attached here
http://forum.xda-developers.com/showpost.php?p=13498312&postcount=53
Please thanks to teapea
Click to expand...
Click to collapse
I followed your advice, ive downloaded the file but it wont let me paste it to the given directory (/system/etc/permissions...).I dont get it...what should i do so it'll allow me...help... also, once it transferred,should it work immediately after that???
HELPPPP!!!! Thanks!!!
wilger_18 said:
I followed your advice, ive downloaded the file but it wont let me paste it to the given directory (/system/etc/permissions...).I dont get it...what should i do so it'll allow me...help... also, once it transferred,should it work immediately after that???
HELPPPP!!!! Thanks!!!
Click to expand...
Click to collapse
Have you mount rw?
In rootexplorer theres a button in the right corner. Press the button once n test again
Ro=read only
Rw=read,write
Sent from my U20i using Tapatalk
X10_minipro said:
Have you mount rw?
In rootexplorer theres a button in the right corner. Press the button once n test again
Ro=read only
Rw=read,write
Sent from my U20i using Tapatalk
Click to expand...
Click to collapse
ive transferred the file "android.hardware.touchscreen.multitouch.xml" to /syste/etc/permissions already...rebooted and still nothing...what am i missing....???HELP!!!
Instructions:
Copy .ko
Edit hw_config
Copy permissions
Enjoy ?
D4rKn3sSyS said:
Instructions:
Copy .ko
Edit hw_config
Copy permissions
Enjoy ?
Click to expand...
Click to collapse
Sorry if im berng stupid....i didnt understand everything u posted above....if you dont mind telling it step by step....coz i really dont speak ur language (technically, i meant)...pardon me from getting on ur nerves...and thanks for the patience...
i rooted my phone (still in original SE OS)...downloaded ES file/root explorer...copied the .xml file to the said directory....thats all what ive done...sorry...if im bering really slow...
bump!!! Bump!!!
well now do that.
1.copy cy8ctma300_ser.ko to system/lib/modules and set permisions
x-x
x
x
2.edit hw_cofing.sh in system/etc
add line: insmod /system/lib/modules/cy8ctma300_ser.ko
and save it.
3.edit build.prop in system/
add lines: ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
reboot phone and enjoy
1. copy cy8ctma300_ser.ko to /system/lib/modules/
2. go to hw_config.sh in the /system/etc/hw_config.sh
3. open it with a text editor
4. add this code in the beginning of the file:
"insmod /system/lib/modules/cy8ctma300_ser.ko"
"sleep 1"
5.save the changes u have made to hw_config.sh
6. also edit the build,prop in the system folder:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
7. reboot the phone and u r good to go.
can someone pls send me "hw_config.sh" for mini pro, i accidently deleted it
twingley said:
can someone pls send me "hw_config.sh" for mini pro, i accidently deleted it
Click to expand...
Click to collapse
You got it in rom zip and copy it to your phone
Sent from my U20i using XDA Premium App
samanvai said:
1. copy cy8ctma300_ser.ko to /system/lib/modules/
2. go to hw_config.sh in the /system/etc/hw_config.sh
3. open it with a text editor
4. add this code in the beginning of the file:
"insmod /system/lib/modules/cy8ctma300_ser.ko"
"sleep 1"
5.save the changes u have made to hw_config.sh
6. also edit the build,prop in the system folder:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
7. reboot the phone and u r good to go.
Click to expand...
Click to collapse
i did everything u said still nothing....my phone still has the original os just to let you know.... not sure where exactly i should type those lines....i mean beginning or end...plsss...help!!!
wouldn't it be easier for you to just flash a rom which already has a multitouch in itself? you already rooted your phone, there's not much you can do wrong, and you can always restore if you do your backups on time
edit: plus, custom roms are in many cases much better than stock
thanks....its already working...thank you for all the walkthroughs you have posted....!!!!!
So I was reading on OC and I changed the AWAKE_MAX_FREQ="AUTO" line from AUTO to 1728000 but now that I wanna go back it says error file won't save.
I noticed there's this file underneath init.post_boot.sh and it's called init.post_boot.sh.bak I don't remember seeing that there, or if it was, what did I do wrong?
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
cobraboy85 said:
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
Click to expand...
Click to collapse
Nice post. Good to see people on xda still helping out the fellow user.
Sent from my PG86100 using xda premium
I tried to put them back to AUTO how it was before but it won't save it says error and that it won't save
EDIT:
Idk if this mattered but I clicked mount /system as writable and that saved it, and got rid of the .bak file
using root ex?
infEcted
marioca said:
I tried to put them back to AUTO how it was before but it won't save it says error and that it won't save
EDIT:
Idk if this mattered but I clicked mount /system as writable and that saved it, and got rid of the .bak file
Click to expand...
Click to collapse
This was the solution to the problem.....
It wouldn't allow you to save it the first go around because you didn't give the system permission to save it... When you mounted the system as writable that allows you to save it to the "system"
Sent from my PG86100 using Tapatalk
How come the first time I changed it I didnt have to do it
cobraboy85 said:
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
Click to expand...
Click to collapse
hey that part up top where u said not to change its just for references.. well when i change.. where it says AUTO.. i changed it to 1566000 and it works fine for me.. i saved it rebooted the phone and its sticks just fine.. i didnt have to change the part near the bottom...
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
jeremywh7 has explained how to fix the issue with the ICSROM governor so that it runs with min 216Mhz and causes less heating - http://forum.xda-developers.com/showpost.php?p=58093061&postcount=1051
Here's the entire post -
Quote:
Originally Posted by jeremywh7
I just wanted to mention that I think I found the cause of ICSROM with the latest 3.1.10 kernel not running at 216MHz:
http://forum.xda-developers.com/show...postcount=1018
I have rebooted*, and its still working fine.
[*edit: forgot to update this post...a power off and cold boot does reset it. I've made an init.d script to fix it for now; will provide details later, as its now the wife's main phone.]
[...]
Better late than never, right? :-/ Here is the script I made as '/etc/init.d/01cpufreq' and set to chmod 755 (manually, using ES File Explorer, actually):
Code:
#!/system/bin/sh
#ramdisk cpu scaling min fix
chown root.root /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "216000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
I installed Universal Init.d (by Androguide.fr) to apply it at boot. I had to run the Test part w/ the tool set to Off, to enable SuperUser privileges. [Update: if you click a file to edit, it will also prompt for su, so that would be easier than running the test; K's July kernels don't support init.d obviously; I'm using kernel-2014_07_04_19_18_atrics.] After setting the tool On, and rebooting...voila, file permission fixed and min frequency 216 MHz.
Since I converted my old CM9-based Atrix to ICSROM (the reason I'm working on all this again), I recalled another mod, rain drop detect issue, for future reference:
http://forum.xda-developers.com/show...&postcount=117
Make sure to leave the extra character at the end the config line [ref: post 119].
Hope this helps...
Click to expand...
Click to collapse
Needless to say, I don't understand the instructions and I really want to be able to do this fix, so if anyone can help me, please let me know. How can I run this script?
aamil4u said:
jeremywh7 has explained how to fix the issue with the ICSROM governor so that it runs with min 216Mhz and causes less heating - http://forum.xda-developers.com/showpost.php?p=58093061&postcount=1051
Here's the entire post -
Needless to say, I don't understand the instructions and I really want to be able to do this fix, so if anyone can help me, please let me know. How can I run this script?
Click to expand...
Click to collapse
This is more like a how to use ES Explorer or Root Browser to put a script in a location and set permissions question and not what you asked
palmbeach05 said:
This is more like a how to use ES Explorer or Root Browser to put a script in a location and set permissions question and not what you asked
Click to expand...
Click to collapse
Thanks for the quick reply!
So basically I have to save this in a file and set permissions for it on a root explorer? I'm a bit of a noon in this, so I'd really appreciate if you could please explain this procedure in a noob-friendly way. What exactly should I do and what should the permissions be.
Thanks!
aamil4u said:
Thanks for the quick reply!
So basically I have to save this in a file and set permissions for it on a root explorer? I'm a bit of a noon in this, so I'd really appreciate if you could please explain this procedure in a noob-friendly way. What exactly should I do and what should the permissions be.
Thanks!
Click to expand...
Click to collapse
Actually you hit the nail on the head after i pointed out what i did in my last post. For permissions, i find it easier to manually change them instead of the chmod thing that it was talking about. For permissions, 755 the same as*rwxr-xr-x
Sent from my ATRIX HD using XDA Free mobile app
Okay. I got so far as that. But what should I name the file and what extension should I use? Am I supposed to replace a system file? Or is this a separate file I have to create? I'm not clear what he means by universal init.d, is it a file? What should I do with it?
Dude, you're seriously overcomplicating this. You're making it way more difficult than it needs to be, both for yourself and for XDA.
The post you quoted contains literally all the information you need, including all the questions you've asked in here. Just read it again.