I want to change some proprieties of the default.prop(yeah, not build.prop )
(ro.secure=0==>1
ro.debuggable=1==>0
persist.service.adb.enable=1==>0)
But I don't know to change that in Rom 4.2 onwards (I could change it in Kayant's 4.1.1 AOKP Rom by changing /system/bootmenu/config/default.prop but this method don't work on another CM android 4.2 Rom, because of 2ndboot?)
How to change the default.prop (or the corresponding values)?
(Coz the app I want to use is checking those values, and refuses to start if it detects ro.secure=0 or ro.debuggable=1 or persist.service.adb.enable=1)
(I want to move to a new Rom but I have to solve this problem first)
Related
I'm trying to change $PATH to have /system/xbin/ before /system/bin/.
I could do this manually but I'm lazy, so I'm looking for a way to have it like that on boot. But no matter whether I change it in init.rc, fota.rc, recovery.rc, they're all back in the old order after a reboot.
Anyone know which file I have to change to make my path changes stick?
XlAfbk said:
I'm trying to change $PATH to have /system/xbin/ before /system/bin/.
I could do this manually but I'm lazy, so I'm looking for a way to have it like that on boot. But no matter whether I change it in init.rc, fota.rc, recovery.rc, they're all back in the old order after a reboot.
Anyone know which file I have to change to make my path changes stick?
Click to expand...
Click to collapse
The init.rc file is a part of the initramfs which is included in the kernel image (zImage). You need to change the init.rc and recompile the kernel with the updated initramfs to make the changes stick.
There is also a way to unpack and repack an existing kernel image, but IMHO recompiling the kernel is much simpler.
hm, compiling kernels isn't really my thing.
is there another way to insert commands into boot process or change path on startup?
XlAfbk said:
hm, compiling kernels isn't really my thing.
is there another way to insert commands into boot process or change path on startup?
Click to expand...
Click to collapse
I think if you have a kernel with init.d support, you can just drop a script in the init.d directory and it will get automatically executed.
I think all the custom kernels (at least ones based on Voodoo) have init.d support -- never actually tried this so I am not totally sure about this.
I'm using the hacked voodoo kernel for gingerbread, created a /init.d/test.rc with "export PATH ... " but it didn't work. Is it supposed to be a .rc script? supposed to work in gingerbread kernel?
edit: after a closer looks it seems that the script is not only not run but /init.d is completly and without a trace gone after rebooting
How are init.d tweaks set up and initialised at boot time? I have edited some values in init.u8800.rc, init.rc, and added a script to /system/etc/init.d so far and nothing seems to get changes to stick. Is it a kernel problem or is something else overriding changes later? This is in my CM 7.2 rom based off Ezet's Cm 7.2.
Any help would be great.
so yeah. i have done so themeing and i want to take this farther.. thing is i'm a total noob to the coding process. if you have any idea what your doing (and your DeOdexed, if nobody is DeOdexed i can send out my files..?) then please help me.
1. what i want
2. what i have
3. overclock (as of now)
4. how to test what i have so far
5. How to help me out
1.) what i want (for starters anyway):
-1% battery mod
- swipe to remove notifications from status bar
- an overclockable kernel? i have managed to overclock my CPU to 1305 Mhz by modifying my build.prop and using quickclock advanced overclock..
- a Rom name.. i'm not very creative. Post a cool Rom name for this maybe guys? cmon, right now its SaberTooth though.
- native screenshot ability
- status bar toggles, maybe? like WiFi toggle, airplane mode, etc. like cyanogen mod
-CRT on animation enabled
- is it possible to port sense 4.0 accordion effect?
2.) what i have:
-themed status bar
-some BlurHome icon changes
-CRT off animation enabled (only off animation, not on.. Yet
.. yeah i fail..
3.) find ro.product.model=MB612 in your build.prop (located at /system) and change that line ONLY to ro.product.model=XT720. this will trick most apps into thinking your xprt is a Motorola milestone.
you must do this because quickclock advanced overclock doesn't allow the overclock unless its a device that they tested, witch of course the XPRT wasn't tested.. then download quickclock advanced overclock, click calibrate,click automatic, check everything and press proceed. when it has finished do back to the main menu and click overclock and set ur values. mine are
1305 MHz 74 vsl
1000 MHZ 56 vsl
600 MHz 36 vsl
300 MHz 21 vsl
stability buffer: 15
click set CPU and keep.
after you have tested to make sure its stable, open the main menu, scroll down click advanced, boot, delay by (anything between 5-30) seconds, and enable it.
4.) NOTE:do not do this unless:
-Rooted
-Deodexed ( deodex gingerbread attempt {might help if ur lost? if ot i guess ill upload my DeOdexed files?})
-Running Gingerbread
-Using Sprint (maybe, not sure correct me if i'm wrong)
-Have backups. (clockwork-mod, and backup Ur current framework-res.apk, systemUI.apk, and BlurHome.apk -- in mine my .9 patches are screwed up and you cant compile them correctly anymore)
download the attachment and extract it. copy and paste framework-res.apk to /system. fix permissions (mine are rw rw rw, not sure if its supposed to be) and then paste it into /system/framework. (phone will auto reboot)
copy and paste BlurHome.apk and SystemUI.apk to /system, again, fix permissions, (mine are rw r r for BlurHome.apk and rw rw rw for SystemUI.apk) then copy and paste them one at a time to /system/app. (i believe they get force closes as soon as you copy, just lock screen, unlock and then power off phone and back on, then copy in the other app.)
done!
5.) If you downloaded what i have and change anything you feel is for the better, reply with the .apk you changed attached (any .apk, not just the ones i gave out) and tell me witch files inside the .apk were changed and there locations.(just so i can pull the modified files out and add everything to My current .apk)
i need like.. a team
Hahahaha this went no where xD i suck. Whatever
Sent from my EVOLTE using xda app-developers app
I want to change some proprieties of the default.prop(yeah, not build.prop )
(ro.secure=0==>1
ro.debuggable=1==>0
persist.service.adb.enable=1==>0)
But I don't know to change that in Rom 4.2 onwards (I could change it in Kayant's 4.1.1 AOKP Rom by changing /system/bootmenu/config/default.prop but this method don't work on another CM android 4.2 Rom, because of 2ndboot?)
How to change the default.prop (or the corresponding values)?
(Coz the app I want to use is checking those values, and refuses to start if it detects ro.secure=0 or ro.debuggable=1 or persist.service.adb.enable=1)
(I want to move to a new Rom but I have to solve this problem first)
default.prop is in the boot.img
You will need to unpack the boot.img, edit default.prop and then repack it.
This should help.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
This is something I wouldn't do until its very crucial.
DROID RAZR with Tapatalk 4
Where
neo.ank said:
default.prop is in the boot.img
You will need to unpack the boot.img, edit default.prop and then repack it.
This should help.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
This is something I wouldn't do until its very crucial.
DROID RAZR with Tapatalk 4
Click to expand...
Click to collapse
I know, but where is boot.omg, I can't find in the zip
I want to edit my default.prop such that:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Currently my default.prop
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
I tried to use setpropex to change it, but it doesn't seem to work in Android 4.4. When I type in getprop in ADB my default.prop shows that it has not been changed.
default.prop is stored in the ramdisk and it's values cannot be modified by setprop by design on all versions of android
prop files are merely text files that android loads the values of at runtime, if you change their values with setprop the files wont be changed unless you manually modify them.
You can either unpack the ramdisk, modify it's contents, repack it, flash the updated boot.img
or use something like: [root] adbd Insecure - Chainfire (there's a free version in the description)
Most custom kernels should already have those values, if you manually modify the stock one,
keep in mind that you will need to undo and redo it every time you use an official ota or it will fail to patch.