I am currently working on a custom rom but I can't get the init.d start up scripts to rewrite the values of certain files and do the thing I want them to do. Anyone have any ideas why?
Sent from my SGH-T839 using XDA Premium App
Busybox? Ask dev.
Depending on which files you are trying to overwrite, it may be writing them before the system sets their values.
if this is the problem any ideas on how i can overwrite the system values AFTER the system sets the values?
i'm currently using the 01insert_file_name_here - 98insert_file_name_here
method and i have it set to 98 so that means that the system should be writing those values last which should mean the values would be overwritten like i wanted but yet NONE of the init.d scripts are running.
hmmm.....
Which kernel are you using?
your kernel from glorious overdose that you said i could use haha
i even also tried switching to a kg2 stock deodex base and doing the same mods and the same result happened.....
i thought that the #filename method in the system/etc/init.d folder was the method used for running startup scripts.....i also gave the ect/init.d folder rwx-rwx-rwx permissions (0777) in the updater-script yet nothing.....
it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.
sduvick said:
it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.
Click to expand...
Click to collapse
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s
-x]Trunks[x- said:
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s
Click to expand...
Click to collapse
it seems galaxy s phones need the script to start with "S" followed by a number between 01-98 then a file name.....so the 2nd option I posted is correct.
but yet even with using your kernel i can't get the script to set the values i'd like it to for the rom i'm working on.....here's the script i have made (don't worry those who have work that is contributed to that file will be credited when i post the rom w/ this working script)
i've been trying for almost a week with different people's "solutions" yet none work
rom base: kj2 deodex w/ root
modem: kj2
kernel: glorious overdose 2 kernel
hopefully you can figure out the problem
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
unreallove said:
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
Click to expand...
Click to collapse
I would recommend using a pre made ROM with this feature integrated already. Much easier.
Sent from my locked MB865 on Ice Cream Sandwich.
What ROM are you running, let's start there. Some ROMs use different init.d files, but for each they all have the ability to be edited properly. Would have been nice for you to post in the OC thread you listed, rather than creating a new one. Rules o' the Forum, they're good for everyone...
http://forum.xda-developers.com/showthread.php?t=1857631
[GUIDE] How To Be A New Member, Not A NØØB
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
unreallove said:
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
Click to expand...
Click to collapse
Those two locations are the same. Don't sweat it. Create a file in one location, the cd to the other and you will see the file you created.
DemosZevasa said:
I would recommend using a pre made ROM with this feature integrated already. Much easier.
Sent from my locked MB865 on Ice Cream Sandwich.
Click to expand...
Click to collapse
I missed to mention it
my rom is stock one
hong kong 2.3.6 stock one
thx!
Apex_Strider said:
What ROM are you running, let's start there. Some ROMs use different init.d files, but for each they all have the ability to be edited properly. Would have been nice for you to post in the OC thread you listed, rather than creating a new one. Rules o' the Forum, they're good for everyone...
http://forum.xda-developers.com/showthread.php?t=1857631
[GUIDE] How To Be A New Member, Not A NØØB
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
what's in my mind is.......
where in that thread it says "without init.d(stock rom)"
but I am using stock rom and sees there is a init.d there
just it is located in different location, not in /system folder
so I need to ask for help
thx
and I do think, if I don't ask
then after I cannot succeed, then go into this forum ask for help
it will be troublesome to do so, as it may even become more complicated to solve after I do something wrong
I just wanted to say...
I have searched before ask
I searched google, but don't seem a result answering
and also none
then I ask here
All you have to do is follow the instructions I gave. You'll need to DL the new init.d file and flash in CWM- this will overwrite any existing init.d folders you have. From there, you can choose your OC method (either using Terminal Emulator or Root Explorer file manager) to edit the frequency scaling of the echo table values...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
new thread?
by seeing your no. of post ..... u r a noob like me
u shud've asked Apex_strider directly in his thread (instead creatin new, but hey ! u r noob so forget it :silly: )
he is strong enough to take ur fone to ur desired frequency
but as far as overclockin is concerned ...... it will SUCK ur battery more !!
u can surely try overclockin n see result urself. All the best :good:
n one thing ..... post some detail abt ur firmware, hardware in next thread so that it will be easy to understand to devs
shardul.phatak said:
by seeing your no. of post ..... u r a noob like me
[snip]
n one thing ..... post some detail abt ur firmware, hardware in next thread so that it will be easy to understand to devs
Click to expand...
Click to collapse
And one more thing, next time please don't use text-messaging speak but instead use complete sentences so that is easy for the devs (and the rest of us) to understand.
troycarpenter said:
And one more thing, next time please don't use text-messaging speak but instead use complete sentences so that is easy for the devs (and the rest of us) to understand.
Click to expand...
Click to collapse
I had no troubles understanding this. Let's not get into worrying over completely innocuous verbiage such as this. It might get have been different had it been an absolutely broken and butchered usage of the English language, so as for is to have to piece that "puzzle" together, but it really wasn't.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Apex_Strider said:
All you have to do is follow the instructions I gave. You'll need to DL the new init.d file and flash in CWM- this will overwrite any existing init.d folders you have. From there, you can choose your OC method (either using Terminal Emulator or Root Explorer file manager) to edit the frequency scaling of the echo table values...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
2. are there really no shortcuts if I only want to try to overclock?
unreallove said:
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
2. are there really no shortcuts if I only want to try to overclock?
Click to expand...
Click to collapse
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
A) Even with a custom ROM that has 'built-in' over clicked init.d files, it's still using the stock kernel. Because of the locked bootloader on the Atrix 2, we do not have the ability to flash custom kernels. That being so, you have to flash the init.d file through CWM to gain init.d support to overclock.
2. are there really no shortcuts if I only want to try to overclock?
A) I'm not sure what you mean by "shortcut". The methods I outline are fairly easy and have noted success both with the stock Motorola ROM and with custom ones as well.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
I don't know....
I am new to all this thing
I just don't wanna get too deep into the "bootloader" stuff
but then, I'll have to ask again....
now, actually I have a init.d folder, just in different directory
will your "without init.d support" method create another WHOLE init.d in /system ?
or it just only rewrite everything in my existing /etc/init.d
I'll have to ask is because, there's plenty files there
I am quite afraid if that method rewrite too many files(and even some is lost)
I don't know what will be the consequences
unreallove said:
I don't know....
I am new to all this thing
I just don't wanna get too deep into the "bootloader" stuff
but then, I'll have to ask again....
now, actually I have a init.d folder, just in different directory
will your "without init.d support" method create another WHOLE init.d in /system ?
or it just only rewrite everything in my existing /etc/init.d
I'll have to ask is because, there's plenty files there
I am quite afraid if that method rewrite too many files(and even some is lost)
I don't know what will be the consequences
Click to expand...
Click to collapse
Don't worry yourself about the bootloader, there's nothing you nor myself nor anyone else can do with it/to it. It's locked, and that's that.
When you DL the file in the "prerequisites" section, and flash it, it will overwrite your existing init.d files. It's all spelled out for you there, not sure why this isn't connecting with you.
Make sure you backup via CWM prior to doing anything, just in case. If you can attach a screenshot of what your init.d folder includes, it might be more helpful.
Everything you'll need is in the guide thread I posted, files, instructions for adding the init.d support, and two ways of Overclocking the CPU. I wrote it to be "n00b friendly"... :thumbup:
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
unreallove said:
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
Click to expand...
Click to collapse
You are looking in the wrong place, since you are on 2.3.6 you are looking in /etc which is webtop, not your ROM.
You will need to install a GB ROM with init.d support, if you start trying to do this yourself with not much knowledge of linux or android, it is easy to mess something up. If you install a ROM with init.d support, you can take a look at the rom and see what it is doing.
/etc and /system/etc are two completely different operating systems, so be very carefull, if you decide to try and get init.d working on your own!
unreallove said:
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
Click to expand...
Click to collapse
The /etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appropriate to files in the rc?.d directories, where "?" is a single character corresponding to the init state. Every ROM including the stock Moto ROM has an init folder.
The init.d linked in the guide provides and 00pptimze foder, which allows for the editing of the echo table values to modify CPU frequency scaling. This is necessary for overclocking your CPU.
Apex_Strider said:
The /etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appropriate to files in the rc?.d directories, where "?" is a single character corresponding to the init state. Every ROM including the stock Moto ROM has an init folder.
The init.d linked in the guide provides and 00pptimze foder, which allows for the editing of the echo table values to modify CPU frequency scaling. This is necessary for overclocking your CPU.
Click to expand...
Click to collapse
No that is webtop...
/system/etc is the rom.... please be careful... 2.3.6 is not the same as ICS.
jimbridgman said:
No that is webtop...
/system/etc is the rom.... please be careful... 2.3.6 is not the same as ICS.
Click to expand...
Click to collapse
Oops.
Left out the "system/"... My apologies.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Building Your Own ROM
This took forever. Please hit the thanks button if this helped you lol
I'm the Developer who's currently working on Delta ROM, and I developed Vengeance ROM all the way through Version 3.2. I've had MANY people message me asking how they can develop their own ROM, so, instead of helping everyone individually, I've decided to make a guide for the whole community to use. The preliminary part of this guide will take you through getting a base using two methods, giving your ROM it's own name, debloating your ROM, adding the kernel of your choice, and editing build.prop and adding init.d tweaks.
Future posts will include everything from adding Aroma Installer to adding mods.
So with that, let's begin.
Building A Base
Building from a stock, rooted, de-odexed base WITHOUT the kitchen (recommended):
Downloading and moving the Base
This is how I create my ROMs. Other developers along with myself have found that Dsixda's android kitchen can create issues with your ROM (namely the updater-script), so building from an already existing base is always the safest in my opinion.
First, we will need to get a base. There are many different versions out there, however, they almost are all the exact same. I use Scrosler's base for my ROMs. You can find his base, along with the stock Modem, RPM, and kernel with custom boot animation support here.
Download Scott's base, and extract the files within the ZIP archive somewhere on your computer. I recommend creating a development directory somewhere on your computer.
I work on Mac OS X, so my development directory is in my home folder under /dev.
In Windows, this sample directory would be in C:\\Users\YourName\Dev
Linux is similar to OS X. I recommend placing your Development directory in ~/Dev (~/ is your home folder's directory)
Of course, you can place these files wherever you want this is just how I have my computer set up.
_________________________________________________________________________________________________________________________
Building a base WITH the kitchen (not recommended due to incompatibilities and time consumption):
Downloading and Installing the Kitchen
This will teach you how to create a base of your own using Samsung's ODIN file and Dsixda's Kitchen.
First of all, you must download Dsixda's Kitchen. Luckily, the Verizon S3 is supported by the kitchen, so BUILDING your base using the kitchen is practically painless. Getting the kitchen running is difficult at times, and you may run into issues later. If you want to evade these issues, I suggest building your ROM from an already existing base. If you don't want to do that, keep reading . The kitchen can be downloaded from here. Just click on the latest version, and press the button with the cloud and the word "ZIP" to download the repo as a zip file. Keep that somewhere on your computer...
Setting up the kitchen is a different story. It's relatively easy on Mac and Linux, but because the kitchen is designed to run in UNIX environments, it's a little bit tougher on Windows. You can find a guide for setting up the kitchen here.
Adding The Odin Files for the Kitchen To Compile
The next step to compiling a base using the kitchen is to take Samsung's files, and add them to the kitchen folder. This is pretty simple. Download the VRBLK3 Stock ODIN from here (thanks open1your1eyes0).
Extract the files to the original_update folder in your kitchen folder.
Building Using the Kitchen
Finally, we're ready to build your base using the kitchen. Start the kitchen by navigating to your kitchen folder in terminal (or command prompt through Cygwin on Windows), and typing "./menu" on mac and linux, or just typing "menu" on Windows.
Option 1 within the kitchen should compile a base ROM for you. You can then root, deodex, zipalign, and change the name of your ROM, and much more, from within the kitchen.
When you're done, option 99 will compile your ROM and move a ZIP file to your OUTPUT_ZIP folder within your kitchen folder.
_________________________________________________________________________________________________________________________
Renaming your ROM
Renaming your ROM is very simple. After building your base, unzip the files and navigate to /system/build.prop. In the build prop, find the line that says "ro.build.display.id=". Replace the rest of the text on this line with your desired name. Save your build.prop. Thats it
Debloating Your ROM
Debloating your ROM is fairly simple as well. The list of removable Apps on the S3 can be found here (thanks to whoever made this, you are a god lol). This is a list for the international version of the S3, but most of the files are the same and MOST Verizon Apps can be removed as well.
Just delete the apks that you want to remove from your /system/app folder within your ROM files.
Init.d Tweaks
Init.d tweaks are scripts that allow your ROM to execute certain actions upon boot. For example, in my Delta ROM, I have an init.d tweak that zipaligns all apks upon boot.
While this guide won't cover creating your own init.d tweaks, adding them is simple. Take the init.d script that you find somewhere online, and simply drop it into your /system/etc/init.d folder. That's all.
Be aware that a lot of people make claims for their tweaks like "best RAM management tweaks" whn posing the tweaks in another device forum. For example, if you found a thread with the "best RAM management tweaks" in the Galaxy S forums, those tweaks are probably not good for our device since we have more available RAM than they do. Overall, it's best to DO YOUR RESEARCH and design your own scripts.
Build.prop Tweaks
Build.prop tweaks are lines added to your build.prop file within /system. They can do many things, and many of them improve performance and battery life on your ROM. A simple list of build.prop tweaks can be found here (Thanks for the new link, upndwn4par). Please note that not all build.prop tweaks out there will work for your device. Just add the lines that you want to add to the BOTTOM of your build.prop file, and save it.
Adding a Custom Kernel
When I first started building ROMs, one of the things that I couldn't figure out was how to add a custom kernel to my ROM. It's actually very simple. Find the kernel you want, download it, extract the zip file, and copy it's files into your ROM in the right locations. For example, you would replace the boot.img in your ROM with the boot.img from your custom kernel, and you would replace the modules in your /system/lib/modules folder with the module files from the kernel. Continue doing this until all of the kernels files are in your ROM. However, NEVER copy over the META-INF folder.
Flashing Your ROM
This is pretty simple. Simply compress your ROM files (boot.img, system folder, Meta-inf folder, and anything else) into a regular ZIP file, move the ZIP to your phone, boot into recovery, wipe data, cache, and dalvik cache, and flash your ROM.
If you did everything right, you should now be running your ROM Hopefully my guide helped you. Feel free to message me if you run into any issues or just have any general questions.
There is much more to development than just this. But this is meant to get you guys started
KANGING
Do NOT, I repeat DO NOT, take anything from another developer's ROM without his/her permission. This is called kanging, and it is extremely frowned upon and even rude because another Dev has spent A LOT of time slaving over the work, and then you take it and use it as your own. I can't speak for other Devs, but if you want something from my ROM, just ask. I'm a pretty open-minded guy, and chances are that I'm gonna say yes.
Credit
Always give credit where credit is due. If a developer helped you out in any way with your ROM, it is always courteous to include them in the credits section of your ROM.
Thanks guys
reserved
this is mine too
Re: [GUIDE] Edgehood's All Inclusive ROM Making Guide
First
Thanks I think I'll give it a go.. the best Rom is your own I suppose. .when your adding in some of your init.d when do find weather they will work properly? Is there a program to run your rom on with windows pc or ubuntu before flashing perhaps?
I would like to get Reim's builds props and such(with all do respect)
Nice!!! Thanks for this. You da man!
Sent from my SCH-I535 using xda premium
Edgehood said:
Building Your Own ROM
This took forever. Please hit the thanks button if this helped you lol
I'm the Developer who's currently working on Delta ROM, and I developed Vengeance ROM all the way through Version 3.2. I've had MANY people message me asking how they can develop their own ROM, so, instead of helping everyone individually, I've decided to make a guide for the whole community to use. The preliminary part of this guide will take you through getting a base using two methods, giving your ROM it's own name, debloating your ROM, adding the kernel of your choice, and editing build.prop and adding init.d tweaks.
Future posts will include everything from adding Aroma Installer to adding mods.
So with that, let's begin.
Building A Base
Building from a stock, rooted, de-odexed base WITHOUT the kitchen (recommended):
Downloading and moving the Base
This is how I create my ROMs. Other developers along with myself have found that Dsixda's android kitchen can create issues with your ROM, so building from an already existing base is always the safest in my opinion.
First, we will need to get a base. There are many different versions out there, however, they almost are all the exact same. I use beanstown106's base for my ROMs. You can find his base, along with the stock Modem, RPM, and kernel with custom boot animation support here.
Download Bean's base, and extract the files within the ZIP archive somewhere on your computer. I recommend creating a development directory somewhere on your computer.
I work on Mac OS X, so my development directory is in my home folder under /dev.
In Windows, this sample directory would be in C:\\Users\YourName\Dev
Linux is similar to OS X. I recommend placing your Development directory in ~/Dev (~/ is your home folder's directory)
Of course, you can place these files wherever you want this is just how I have my computer set up.
_________________________________________________________________________________________________________________________
Building a base WITH the kitchen (not recommended due to incompatibilities and time consumption):
Downloading and Installing the Kitchen
This will teach you how to create a base of your own using Samsung's ODIN file and Dsixda's Kitchen.
First of all, you must download Dsixda's Kitchen. Luckily, the Verizon S3 is supported by the kitchen, so BUILDING your base using the kitchen is practically painless. Getting the kitchen running is difficult at times, and you may run into issues later. If you want to evade these issues, I suggest building your ROM from an already existing base. If you don't want to do that, keep reading . The kitchen can be downloaded from here. Just click on the latest version, and press the button with the cloud and the word "ZIP" to download the repo as a zip file. Keep that somewhere on your computer...
Setting up the kitchen is a different story. It's relatively easy on Mac and Linux, but because the kitchen is designed to run in UNIX environments, it's a little bit tougher on Windows. You can find a guide for setting up the kitchen here.
Adding The Odin Files for the Kitchen To Compile
The next step to compiling a base using the kitchen is to take Samsung's files, and add them to the kitchen folder. This is pretty simple. Download the VRBLK3 Stock ODIN from here (thanks open1your1eyes0).
Extract the files to the original_update folder in your kitchen folder.
Building Using the Kitchen
Finally, we're ready to build your base using the kitchen. Start the kitchen by navigating to your kitchen folder in terminal (or command prompt through Cygwin on Windows), and typing "./menu" on mac and linux, or just typing "menu" on Windows.
Option 1 within the kitchen should compile a base ROM for you. You can then root, deodex, zipalign, and change the name of your ROM, and much more, from within the kitchen.
When you're done, option 99 will compile your ROM and move a ZIP file to your OUTPUT_ZIP folder within your kitchen folder.
_________________________________________________________________________________________________________________________
Renaming your ROM
Renaming your ROM is very simple. After building your base, unzip the files and navigate to /system/build.prop. In the build prop, find the line that says "ro.build.display.id=". Replace the rest of the text on this line with your desired name. Save your build.prop. Thats it
Debloating Your ROM
Debloating your ROM is fairly simple as well. The list of removable Apps on the S3 can be found here (thanks to whoever made this, you are a god lol). This is a list for the international version of the S3, but most of the files are the same and MOST Verizon Apps can be removed as well.
Just delete the apks that you want to remove from your /system/app folder within your ROM files.
Init.d Tweaks
Init.d tweaks are scripts that allow your ROM to execute certain actions upon boot. For example, in my Delta ROM, I have an init.d tweak that zipaligns all apks upon boot.
While this guide won't cover creating your own init.d tweaks, adding them is simple. Take the init.d script that you find somewhere online, and simply drop it into your /system/etc/init.d folder. That's all.
Be aware that a lot of people make claims for their tweaks like "best RAM management tweaks" whn posing the tweaks in another device forum. For example, if you found a thread with the "best RAM management tweaks" in the Galaxy S forums, those tweaks are probably not good for our device since we have more available RAM than they do. Overall, it's best to DO YOUR RESEARCH and design your own scripts.
Build.prop Tweaks
Build.prop tweaks are lines added to your build.prop file within /system. They can do many things, and many of them improve performance and battery life on your ROM. A simple list of build.prop tweaks can be found here. Just add the lines that you want to add to the BOTTOM of your build.prop file, and save it.
Adding a Custom Kernel
When I first started building ROMs, one of the things that I couldn't figure out was how to add a custom kernel to my ROM. It's actually very simple. Find the kernel you want, download it, extract the zip file, and copy it's files into your ROM in the right locations. For example, you would replace the boot.img in your ROM with the boot.img from your custom kernel, and you would replace the modules in your /system/lib/modules folder with the module files from the kernel. Continue doing this until all of the kernels files are in your ROM.
Flashing Your ROM
This is pretty simple. Simply compress your ROM files (boot.img, system folder, Meta-inf folder, and anything else) into a regular ZIP file, move the ZIP to your phone, boot into recovery, wipe data, cache, and dalvik cache, and flash your ROM.
If you did everything right, you should now be running your ROM Hopefully my guide helped you. Feel free to message me if you run into any issues or just have any general questions.
There is much more to development than just this. But this is meant to get you guys started
KANGING
Do NOT, I repeat DO NOT, take anything from another developer's ROM without his/her permission. This is called kanging, and it is extremely frowned upon and even rude because another Dev has spent A LOT of time slaving over the work, and then you take it and use it as your own. I can't speak for other Devs, but if you want something from my ROM, just ask. I'm a pretty open-minded guy, and chances are that I'm gonna say yes.
Credit
Always give credit where credit is due. If a developer helped you out in any way with your ROM, it is always courteous to include them in the credits section of your ROM.
Thanks guys
Click to expand...
Click to collapse
you make it look easy. lol nice job. someday possibly. someday....
Thanks for this Edge. I'm gonna try and build my own rom now thanks to you. I really appreciate all the guides. Keep them coming when u get a chance.
Sent from my SCH-I535 using xda premium
Fantastic work,thanks
how do you open the build.prop file?
You sure we should use that link for build props as reference? Seems like a lot of bad reviews fir only 2 pages.
Sent from my SCH-I535 using Tapatalk 2
These threads are always great to encourage people to get involved. Nice work!
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Nice guide. These are always great to get people started.
Though I must disagree with your comments on using the kitchen for a few reasons.
1) There are no compatibility problems that I have experienced.
2) It is not time consuming. It actually saves a lot of time. For example, if you have a decent PC you can:
a) Deodex a ROM in about 5 minutes.
b) Zipalign every apk in about 30 seconds.
c) Add init.d support, root, and buybox in about 2 minutes.
3) The kitchen builds ROMs, it does not compile them.
Also, most of the build.prop tweaks in the reference you linked (and just about every guide you can find) are bogus. Most have been completely debunked. Also, any tweak with a "mot" in it is strictly for Motorola devices.
Jeff Mixon article on build.prop tweaks.
upndwn4par said:
Nice guide. These are always great to get people started.
Though I must disagree with your comments on using the kitchen for a few reasons.
1) There are no compatibility problems that I have experienced.
2) It is not time consuming. It actually saves a lot of time. For example, if you have a decent PC you can:
a) Deodex a ROM in about 5 minutes.
b) Zipalign every apk in about 30 seconds.
c) Add init.d support, root, and buybox in about 2 minutes.
3) The kitchen builds ROMs, it does not compile them.
Also, most of the build.prop tweaks in the reference you linked (and just about every guide you can find) are bogus. Most have been completely debunked. Also, any tweak with a "mot" in it is strictly for Motorola devices.
Jeff Mixon article on build.prop tweaks.
Click to expand...
Click to collapse
I've experienced a few issues when building with the kitchen. For example, the ROM wouldn't flash after cooking it because it said there was no MD5.
The kitchen does save time once you get it set up. However, its much faster to download a 700-800mb base and move it into a folder than download >1GB ODIN file and get the kitchen set up correctly. Especially if you have to set up Cygwin or a VM if you're on windows. I agree with you that with a good PC, the kitchen will build a ROM fast. But not everyone (including myself lol) has a PC that can build them that fast.
It is completely a matter of preference though. I prefer to build my ROMs from a base, but you prefer to use the kitchen. After all, that's why I included both methods in the guide
I'll look at the build.prop thing, I might've posted the wrong link. I was exhausted lol
Thanks,
Edge
EDIT: I changed the build.prop link to the article you posted. Thanks man
awesome.. will give it a shot when I have some time
thank you
I assume this is for building when one doesn't want to change any other files than the ones you mention. But if I want to alter something, say, on the notification bar, I would need instructions on what files to alter and, if relevant, how to compile my changes into a binary that can then be included in the ROM. This is a good start so thank you.
thornev said:
I assume this is for building when one doesn't want to change any other files than the ones you mention. But if I want to alter something, say, on the notification bar, I would need instructions on what files to alter and, if relevant, how to compile my changes into a binary that can then be included in the ROM. This is a good start so thank you.
Click to expand...
Click to collapse
Correct. It says that there is more to developing and that this should get you started
Nice and quick guide! Good job! It really is simple stuff once you get familiar w/ files and all.
HaVoK C89 said:
Nice and quick guide! Good job! It really is simple stuff once you get familiar w/ files and all.
Click to expand...
Click to collapse
Thanks!
Nice work