I've been trying to get init.d support to work on Deck's AOSP 2.3.7 (v1.3). It has the folder, but nothing seems to stick. Does anyone have a suggestion for this?
Tubes6al4v said:
I've been trying to get init.d support to work on Deck's AOSP 2.3.7 (v1.3). It has the folder, but nothing seems to stick. Does anyone have a suggestion for this?
Click to expand...
Click to collapse
maybe try a dffierent aosp rom, all of them are in the link in my sig. or uninstall it and reinstall it. if you have any questions just post them in the link in my sig
nd just wondering you searched in system/etc?
I may just do cyanogen as I change a bunch of things anyway. I have an init.d folder by default, and have reinstalled the ROM and various kernels.
I've tried editing init.rc, and have read there is a bootcomplete.supersonic.rc file in evos that overrides changes, but can't find it in deck's.
Sent from my Evo using xda premium
What exactly are you trying to do with init.d?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Tubes6al4v said:
I may just do cyanogen as I change a bunch of things anyway. I have an init.d folder by default, and have reinstalled the ROM and various kernels.
I've tried editing init.rc, and have read there is a bootcomplete.supersonic.rc file in evos that overrides changes, but can't find it in deck's.
Sent from my Evo using xda premium
Click to expand...
Click to collapse
use root explorer and when you make it to init.d click on the top right of root explorer where it says r/w when you click it, it will say r/o that will allow you to do what you want, when your done click it again to make it r/w and then your done
Crossrocker said:
What exactly are you trying to do with init.d?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Click to expand...
Click to collapse
I have read your guide and appreciate it. There are a number of system tweak scripts floating around xda that would be fun to test out. With system tuner pro and v6 I can have them run after boot is complete, but having init.d on my tab is just so streamlined.
Can I use run as root/at boot w/ any script?
Green_Arrow said:
use root explorer and when you make it to init.d click on the top right of root explorer where it says r/w when you click it, it will say r/o that will allow you to do what you want, when your done click it again to make it r/w and then your done
Click to expand...
Click to collapse
I've done that, and the file changes, but init.d is still not active. Build.prop changes work though.
Use script manager for scripts
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Related
I am running one of the new cm7 nightlys with godmod kernel. I cannot get the init.d scripts to run on boot. I've tried 3.3.7 and still no go. Anything I'm missing?
Do you have init.d folder in system/etc/??
Sent from my PC36100 using Tapatalk
I do, it also has a bunch of random scripts in there from the initial flash of the rom.
I just cannot figure out why my phone will not execute any of the scripts in the folder.
siris420 said:
I do, it also has a bunch of random scripts in there from the initial flash of the rom.
I just cannot figure out why my phone will not execute any of the scripts in the folder.
Click to expand...
Click to collapse
How do you know it's not running the scripts? What are you doing to verify if it is or not?
Sent from a Nifty Tomatoe
Hit that thanks button if I managed to help
Installed a ram script, and some other things. Reboot. Check minfree values and they are still stock.
Actually your ultimate ram script.
If you want to edit build prop to emulate a500 to see a500 games and apps from Market on ICS, you can follow crossix root mod and edit the build.prop under /data/local/rootme/loop
Thanks to crossix for his root and help with build prop location for his root method. Please thank him as I would not be able to figure this out if it weren't for him.
Another method root procedure. Can now R/O system folder.
Edit build.prop under /system for this root mod. Thanks to ZeroNull
Make sure to make a back up of original or rename it.
And remember this is for ICS only. HC build.prop mod can be found here.
Here's where I found the a500 ICS build.prop. I downloaded the ICS leak for a500 and extracted the build.prop file in the system folder.
Heres are the lines I edited on my a100 ICS build prop which worked the 1st time around. But according to crossix you probably just need to update the 2 ro.build lines but I havent done it that way yet.
-----------------------------------------------
ro.product.model=A500
ro.product.brand=acer
ro.product.name=a500_ww_gen1
ro.product.device=picasso
ro.product.board=picasso
ro.build.description=a500_ww_gen1-user 4.0.3 IML74K 1328620975 release-keys
ro.build.fingerprint=acer/a500_ww_gen1/picasso:4.0.3/IML74K/1328620975:user/release-keys
-----------------------------------------------
Save and reboot for it to take effect
Please be careful to edit the exact lines or you may brick your device. If you do brick a hard reset or flash update.zip again should bring the original back.
Crossix mentioned he will eventually work on an enhanced build.prop for us in the future so for now you can use this til then.
Good job.
Sent from my Incredible 2 HD using Tapatalk
I keep getting an error has occured, can't save.
jakob95 said:
I keep getting an error has occured, can't save.
Click to expand...
Click to collapse
Once you do crossix root and if its successful you will have a build.prop file in
/data/local/rootme/loop/
You need to edit this one. I think you're editing the one in /system
New root method. Thanks to ZeroNull. Updated OP.
thank you for this tutorial... i modified my build.prop and it works but i have a question for you guys...can anyone see hero of sparta on google play? Because i can not see it.
I edited build.prop under /system using ES File Explorer and the device recognizes it as A500 now, but I still have many apps missing from my Play Store.
eruisi said:
I edited build.prop under /system using ES File Explorer and the device recognizes it as A500 now, but I still have many apps missing from my Play Store.
Click to expand...
Click to collapse
If the apps are not compatible with the A500 (or at least stated as so), then those apps will still not be visible.
Theonew said:
If the apps are not compatible with the A500 (or at least stated as so), then those apps will still not be visible.
Click to expand...
Click to collapse
How to 100% eliminate this limitation then? Should I install a custom ROM (e.g., CM9 or FLEX-A100-REAPER-RF1-EXTREME-EDITION, etc)?
eruisi said:
How to 100% eliminate this limitation then? Should I install a custom ROM (e.g., CM9 or FLEX-A100-REAPER-RF1-EXTREME-EDITION, etc)?
Click to expand...
Click to collapse
Changing your rom will not help in this situation. There is no way to "100%" get rid of that limitation but there are ways to lessen it. You could try editing your build.prop to some other tab which lists those apps as compatible.
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
justjackyl said:
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I would just grab on of linuxsociety's build props from his tread. The ones ending in A500 will change it. Just grab the one that matches your android version, he has them for ICS 4.0.3 (stock), ICS 4.0.4 (cm9), and 4.1.1 (cm10).
http://forum.xda-developers.com/showthread.php?t=1799148
justjackyl said:
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Build.prop does sit in /system, that's the correct file you found.
I might suggest using a build.prop from Linux society, there is one for a500 device naming. Its the easy way, not what asked for, but its a start.
Es file manager had an editor that can make changes to build.prop or I would suggest notepad++ it similar for windows. Normal text editors in windows save extra garbage that will break android.
I'm sure others can chime in with additional info.
Tapatalked from my Galaxy S II.
Would I just backup the old one and just copy and paste in the other build file,or is there a special way I need to replace the file? This is starting to take me out of my knowledge zone so this part is new to me.
Thank you both for the information you are providing.
Sent from my A100 using xda app-developers app
justjackyl said:
Would I just backup the old one and just copy and paste in the other build file,or is there a special way I need to replace the file? This is starting to take me out of my knowledge zone so this part is new to me.
Thank you both for the information you are providing.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Yup, just save the one from the thread. Rename your current build prop from /system, by adding .bak to the name (backup). Then just copy the new one to the directory, making sure it is named 'build.prop'. Then reboot. All this can be done with es file explorer, with root explorer enabled in the options.
Wow. This made it look way harder: http://forum.xda-developers.com/showthread.php?p=22933062
Compatible Games for ICS
Sent from my LG-P999 using xda app-developers app
Now this is really out of my scope. I got all the way through to being ready to flash CWM but I don't have the SDK Tools, and I know nothing about them! Time to study.
justjackyl said:
Now this is really out of my scope. I got all the way through to being ready to flash CWM but I don't have the SDK Tools, and I know nothing about them! Time to study.
Click to expand...
Click to collapse
I would just install twrp recovery. Its very easy to use and install. http://forum.xda-developers.com/showthread.php?t=1799148
All you need is the Acer USB driver working and tee twrp install package. http://support.acer.com/product/default.aspx?modelId=3849
Have you unlocked the bootloader?
Yes. The boot loader is unlocked.
Sent from my A100 using xda app-developers app
Romman0 said:
I would just install twrp recovery. Its very easy to use and install. http://forum.xda-developers.com/showthread.php?t=1799148
All you need is the Acer USB driver working and tee twrp install package. http://support.acer.com/product/default.aspx?modelId=3849
Have you unlocked the bootloader?
Click to expand...
Click to collapse
twrp installed flawlessly. Thank you for the suggestion.
Moved to correct section..
Romman0 said:
Yup, just save the one from the thread. Rename your current build prop from /system, by adding .bak to the name (backup). Then just copy the new one to the directory, making sure it is named 'build.prop'. Then reboot. All this can be done with es file explorer, with root explorer enabled in the options.
Click to expand...
Click to collapse
I haven't had the chance to change build.prob on a100 yet (actually going to now) but everytime I've used a modded build.prop. I had to change the permissions to rw-r-r. Pretty sure you have to with a100 too. Just saying cause that's the only step you didn't mention. And I no how much of as pain it is when you mess up changing the build.prop. not fun at all lol
trevor7428 said:
I haven't had the chance to change build.prob on a100 yet (actually going to now) but everytime I've used a modded build.prop. I had to change the permissions to rw-r-r. Pretty sure you have to with a100 too. Just saying cause that's the only step you didn't mention. And I no how much of as pain it is when you mess up changing the build.prop. not fun at all lol
Click to expand...
Click to collapse
Never had to change permissions on my A100 to mod the /system files. The root process will do it.
I tyred once and umm, to put it shortly, YOU MUST change the permissions or be really familiar with Adb and linux and chmod it that way. I think theres a tool in twrp to do it also but I haven't a clue how it works.
Sent from my A100 using xda premium
I did as instructed. Worked fine.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
When rooting your making /system writable. Zeronulls "easy" script does it automatically, so most if not all users will not have to do anything. I guess in my instructions I should have mentioned you need root, I kinda thought it was implied as the instructions were written for the OP, which stated he had root access.
Hmm....
Sent from my A100 using xda premium
Is it possible to get init.d working on a SGH-T889 that is rooted, and running the latest stock rom and kernel?
I managed to make the folder, and chmod it to 777 via a terminal, and my tweaking apps create scripts in said folder that are pre-modded to 777, but they fail to launch at boot.
I would like to stay as close to stock as possible, but I love being rooted.
What can I do to find a happy medium?
Sent from my SGH-T889 using xda premium
EncryptedFile said:
Is it possible to get init.d working on a SGH-T889 that is rooted, and running the latest stock rom and kernel?
I managed to make the folder, and chmod it to 777 via a terminal, and my tweaking apps create scripts in said folder that are pre-modded to 777, but they fail to launch at boot.
I would like to stay as close to stock as possible, but I love being rooted.
What can I do to find a happy medium?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
You have to enable this in the ramdisk
Sent from my SGH-T889 using xda app-developers app
I believe apps like script manager can do this, but you can also get init.d support using busybox and an edited script in /system/etc/. Otherwise - what ptmr3 said
Busybox run-parts with installrecovery.sh, it works on many, many devices with stock kernels. Just make sure you don't inadvertently delete the script from recovery.
Darkshado said:
Busybox run-parts with installrecovery.sh, it works on many, many devices with stock kernels. Just make sure you don't inadvertently delete the script from recovery.
Click to expand...
Click to collapse
That would be the one
headscratch.gif
I'm extremely computer literate, but only fairly adept at matters pertaining to android/rooted actions.
I have above basic Linux knowledge as well, so if you point me in the right direction, I should be able to take it from there.
//I meant to add I have busy box installed.
Sent from my SGH-T889 using xda premium
So I just stumbled across this mod:
http://forum.xda-developers.com/show....php?t=2272317
I.e. It's not mine and I take no responsibility or credit, but so far it's made my phone even more blazingly fast and buttery smooth.
It was in the Lg optimus g at&t... I used it on my og and just installed it on my pro seems to be working great!!! will test for the next 24hrs. Theres a app on post 5.
Gotroot said:
So I just stumbled across this mod:
http://forum.xda-developers.com/show....php?t=2272317
Click to expand...
Click to collapse
Here's a clickable version of the link.
it says init.d is required, do we have init.d on the stock kernel?
Erik
download the init.d installer from the market for 99 cents, run it and it will install init.d. after reboot mount your system as rw and then install the projectxtreme app open it and click install and your done. check in the ect/init.d folder using a root file explorer and you'll see the projectelxtreme scripts in there. if not run install from app again reboot and check. ilan easy way to know is by seeing its granted su permissions at the bottom of your screen when you turn your phone on or reboot.
ricco333 said:
it says init.d is required, do we have init.d on the stock kernel?
Erik
Click to expand...
Click to collapse
Pimp my rom(free) can do that for you
Sent from my LT30p using xda premium
Which version did you apply in cwm?
Sent from my LG-E980 using Tapatalk 2