Database Info

[Q] How to change Kernel of ROM Before installatio in it's zip file.

I would like to learn how one can change the kernel/modem in a ROM's zip BEFORE flashing it. I often use the Entropy Kernel after I flash a new ROM. The Kernel has a zimage file. How do I incorporate it into the zip? Same for modem file.
Thanks in advance.

NeoMustain said:
I would like to learn how one can change the kernel/modem in a ROM's zip BEFORE flashing it. I often use the Entropy Kernel after I flash a new ROM. The Kernel has a zimage file. How do I incorporate it into the zip? Same for modem file.
Thanks in advance.
Click to expand...
Click to collapse
Whats worked for me:
First get 7zip if you are on windows
Open the kernel zip with 7zip move the redbend_ua and zImage into this location (rom name here).zip/updates
For modem do the same, open up the modem zip with 7zip, and then move the modim.bin into (rom name here).zip/update
You may need to delete the redbend and zImage already in the rom, but just overwriting it with the new ones should work
Once the new kernel/modem is copied over, just put it on your sdcard and you should be able to flash it without any problems
Sent from my SAMSUNG-SGH-I997 using XDA

or just the zimage...since the ua is same...

Never tried it without doing the ua when it came to the kernel, but it does make sense since i never moved the ua when ever id move the modem
Sent from my SAMSUNG-SGH-I997 using XDA

The ua is universal on all roms... its just an installer for the modem and kernel ... no need to change it. If the rom already has it then just replace the zimage and your good.
Sent from my SAMSUNG-SGH-I997 using xda premium

I request some experienced sr. member to comeup by posting new thread covering some of topics like safely adding and removing apks, libs. Fonts, apps, wallpapers, kernel. Modem etc. in Rom's zip with little flavouring. It will help new member to start some development work.

Thanks guys ... 1 more small step

hey can anyone give instructions on fixing RIL bug...it would be so much helpful...thnx

[overclock] /etc/init.d location 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

[Q] Updater script and build.prop

Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.

Zadeis said:
Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.
Click to expand...
Click to collapse
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.

elesbb said:
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.
Click to expand...
Click to collapse
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.

Zadeis said:
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.
Click to expand...
Click to collapse
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.

elesbb said:
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.
Click to expand...
Click to collapse
Hmm maybe. I'll try using winrar to see if it makes any difference using the same drag and drop new build.prop method just to satisfy my curiosity.

Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up

Reilly1812 said:
Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up
Click to expand...
Click to collapse
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.

Zadeis said:
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.
Click to expand...
Click to collapse
7zip works for me without any issues..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

How to create your own tw rom on your phone using root explorer

In this tutorial I will show you how to create your own T.W. rom using your GS3 and Root Explorer. There are many ways you can create a rom but not everyone has the time to sit at a computer every night. However, your phone is always on you and can find a few minutes here and there to create your own masterpiece.
For the sake of this tutorial, we will name our new rom "SLICK".
Here are a few things you will need...
1. The rom base from Scottsroms. I'm NOT talking about Cleanrom but the unmodified stock rooted rom.
2. Root Explorer.
3. Script Manager
4. Any mod you can flash or come up with on your own.
1. GET STARTED!
Download the base rom to your phones EXT-sdcard and extract it using Root Explorer. After it's extracted the new unziped rom will be located in /storage/sdcard0/SpeedSoftware/Extracted. The extracted rom is now your new base. At this point it would be a great idea to move it to your EXT-sdcard and create a new project folder for it and label the folder "Project SLICK". inside the folder is your rom. lets rename that rom "SLICK".
Lets open your new SLICK rom. You should have some folders...
BOOT IMAGE
DATA
META-INF
SYSTEM
3. THE SYSTEM FOLDER
/SYSTEM/APP
Most of your work will done in the System folder so lets open that up. This is the heart of your rom! There are many folders here but lets start with the app folder. This folder has every app installed in your rom. This is a good time to remove the bloat you don't want in your rom. Go ahead and delete the apk's you don't want or need.
/SYSTEM/BIN
Here you can speed up your system or make it more battery efficient by deleting things like "mpdecision" and things like that. Be careful what you delete though. In general you won't do much in here.
/SYSTEM/BUILD.PROP
Here you can change values or add values. The one value we are concerned with is "ro.build.display.id" This build property's value will be displayed in the end users settings menu under "about phone". So let's give this property the correct value "ro.build.display.id=SLICK ROM v1.0" The rest of the build properties you can do as you wish. Build.prop is simply a text file. You can use the text editor built into Root Explorer.
/SYSTEM/CSC
Open this file and you will see more files. Listed is "feature.xml". Here you can edit values for various items for texting and mms.
/SYSTEM/ETC
Here is where you will find a folder called "init.d". Located in this folder are various text files. The text files are scripts that are told to run when your phone boots. You can add or modify to the existing scripts or create a new text file.
So we went over a few of the basics of modding your new rom and molding it into something you can call your own but does it work??
4. TESTING YOUR NEW BASE.
So we have already modified our rom a considerable amount and should have a good solid base. Before we go any further we should really test things out first. If we did something wrong earlier we will at least have an idea where to look. So lets flash our new rom. Go to you EXT-sdcard and find our project folder. you should still have your SLICK file. Zip this file with Root Explorer. Make sure you have a good battery and a cool environment because it's going to take your GS3 about 30min of hard work to zip this file. When that is finally completed, flash your new rom located in /storage/sdcard0/SpeedSoftware/Archives. Flash it just like you would any other rom.
Test your new rom out on your GS3 and see how things are running. Check your existing modifications you did earlier. If everything looks good, we can continue modding. If not you will need to go back to your base to see where you went wrong. This is also a great time to check your init.d scripts. One way to do this is to download "Script manager" from the market and click on your init scripts to read there log. It will tell you if something went wrong.
If everything is looking good, we can continue modding...

5. THE MODS
So we have that nice clean base but what about all them mods in the roms we download and flash everyday? There are a few different ways we can do this and we will start with the easiest but first, do a nandroid backup of your new base. If one of your mods you perform next goes bad it's simply quicker to recover. Now, If you have flashable zips of some of the mods you like then you can flash them now and make sure they are working the way they should in your rom. Remember, just cause we have the d2vzw does not mean mods from the sprint or T-mobile won't work on our devices. Sometimes it's worth a try. It's all about which firmware they are on and what has changed with the firmware.
So we flashed a few mods but don't have everything we wanted. At this point you are left with only one option and that is to get on that PC of yours and learn to decompile a APK. I may touch on this subject later as it is a bit more involved for someone new to this sort of thing.
6. UNDERSTANDING THE FLASHABLE ZIP
The alternate method of a flashable zip is to extract your flashable using Root Explorer and picking it apart. For example we will use "Lean Kernel" and kill 2 topics with one stone. If you unzip the kernel you will see...
BOOT.IMG
META-INF
SYSTEM
As you can see there are some familiar files to us just like when we extracted our base rom in the beginning. Basically when you flash a mod like this or any flashable for that matter, it installs files into your rom in certain places. In this example we will be installing in BOOT.IMG and SYSTEM. But what? And what is that META-INF file for? Well this META-INF file is what tells your rom what files and what to do with those files. Inside META-INF is a text file called an "updater script".
Here is what it looks like...
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0777, "/system/etc/init.d/00leanKernel");
unmount("/system");
assert(package_extract_file("boot.img", "/cache/boot.img"),
write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7"),
delete("/cache/boot.img"));
show_progress(0.100000, 0);
Line 2 shows it mounting the system so we can write to it.
Line 3 shows us extracting the entire directory of the system file in the flashable into the system file of our rom.
Line 4 shows we are setting permissions for one of the system files we just installed in the rom. In this case it is an INIT.D file.
Line 5 shows us returning the system to an un-writable state.
Line 6 shows we are now installing the other file called BOOT.IMG.
So we installed BOOT.IMG and the SYSTEM file. The BOOT.IMG file is usually only found in a rom or kernel zip so most of the time you won't see this file in a flashable but I wanted to use this as an example to show a bit about the kernel side of things.
Ok, so lets get back to the original files of this flashable zip. The updater script stated we installed a new system file into the rom so whats in there? If we open the SYSTEM file from our flashable with Root Explorer you will find a file hierarchy...
SYSTEM
-- ETC
--- INIT.D
---- "00LEANKERNEL"
-- LIB
--- MODULES
---- Listed here are a bunch of ".ko" modules and i'm not listing them all.
So whats the point of all this? Well lets say when we originally debloated our rom in the begining we could of included some of our flashable mods like a custom kernel before we zip the rom to test the base. So in this case we can manually install this kernel before we zip the base. We can take the BOOT.IMG from our extracted kernel and replace the BOOT.IMG in our extracted rom. We only need the files from the flashable so we need to copy and paste the "00LEANKERNEL" file from our flashable to our roms /system/etc/init.d folder. We can also take those ".ko" files from the flashable and dump those into the /system/lib/module folder and we are done. You have now manually installed a kernel into your base rom before you zipped it. Now when you zip your rom and flash it, your new base rom will boot with your custom kernel. Since we manually installed the kernel we don't need the META-INF file provides an auto install script for installing through recovery. Technically we could take all of our flashable mods, extract them, look at the file hierarchy and copy and paste the those files to our extracted base rom. That way we can zip our rom and test it with the mods right off the bat. You can really make things quicker this way and is in general the way to go.
I think it's rather important to fully understand a flashable zip. How it's built and how it completes it's task. It's used so often and makes mods so incredibly easy to install but it is also what installs our rom! One of the files we see when we open "slick" is a META-INF and there inside is the updater script to flash the rom. Again we are doing the same thing as we do with the flashable mod but this time we are installing a lot more files with a lot more permissions. It is the exact same thing as shown above just a bit more extensive.

7. PUT THE PIECES TOGETHER
Ok so we have our base rom running on our phone and possibly a few mods installed. We also have our extracted and debloated "slick" rom on the EXT-sdcard inside our project folder. The next part is rather easy if you understand how those flashable mods were installed. If you understand the whole flashable and its files, your better off just extracting them and then copy and paste them where they need to go. After you have all your mod files in place you can now zip your official "Slick" rom using Root Explorer of course. Prepare yourself for another 30 minutes for it to zip. After it's zipped your done. You have now created your first fully modded rom! However...
Lets say you don't get the whole flashable thing and or you had made some other changes to the rom while you were testing. Lets say you flashed some mods and created a few init.d scripts or the build.prop along the way. NO WORRIES! We can put the rom together another way. A lot of the mods you flash will install files in some usual areas of the rom like your Framework folder and such. Lets just say we don't know though. You can actually copy complete folders from the rom you are running right there and now and paste them into your extracted "Slick" base rom using Root Explorer. So you can take "/system/framework" from your currently running rom, copy it, and paste it in "/storage/EXT-sdcard/project folder/slick/system/framework". In short just take your copy of the framework file and put it in your extracted base and paste it. Root Explorer will then ask you if you want to replace this file and click yes. You have just transferred any modded file that might have been in framework to your extracted rom. Any folder you may think was modded, simply copy and paste it to your extracted base rom on your EXT-sdcard. Once you think you have it all the modded files transferred you can zip your new "Slick rom! Flash and enjoy!!

FINISHED
So we have now completed our own rom on the device itself. It's really not too difficult just a bit more time consuming with zipping and that. However, you may need to do a bit more research on how to decompile and recompile an APK. This is one of things that can really be a pain to setup. It's again the basics that will kill you. The whole PITA is not decompiling or making changes to a framework file, it's setting up the environment that sucked for me. You have to get the Java and files in order and all the little crap to get it to work. IMO, if you haven't decompiled an APK yet it's really not difficult at all. Like I said. It's the basics. I encourage you to learn this because it's so freakin easy after it's all setup and you will be able to do so much more with your rom. Once you get this APK thing down don't be afraid to take someone elses work and reverse engineer it. Try to figure out what that developer did to accomplish what he wanted. It's a great way to learn and thats what it's about.
I may add to this somewhere down the road but for now it's all I have. I hope this helped and motivated someone to create a rom and begin there journey to become developer someday! We can all use fresh ideas for development. There is so much more to come for Android so get your hands dirty and share!
Thanks guys!

Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta

dincdoes.me said:
Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's another way. May not be the fastest way but it's another option. I also wanted to write this as a general rom creation and learning some basics. It's always the basics that will kill a project and motivation. I would like to see a complete newb to be able to complete a rom with this tutorial. Then I accomplished something. Going to have to finish this tomorrow though. It's taking longer than I thought lol.

Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta

Thank you for this post. This will definitely get me to try and make my own ROM the way I like, also I might just learn some new stuff. Great post thanks again
Sent from my SCH-I535 using xda app-developers app

Nice tutorial.
It's a great way to show what can be done just from your phone.
:good:

Right on man. Been waiting for this. Thank you.
Sent from my SCH-I535 using xda app-developers app

dincdoes.me said:
Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use androzip man.
Sent from my SCH-I535 using xda app-developers app

More added

So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?

Evil Genius Jr. said:
So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?
Click to expand...
Click to collapse
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.

razz1 said:
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.
Click to expand...
Click to collapse
You are the fu**ing man razz1.
Sent from my SCH-I535 using xda app-developers app

That's about all I have for now. OP completed!:sly:

Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app

Lehocki said:
Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol the whole time I was reading this I was waiting for you to say something didn't work out for you but it all did I guess. Nice!!

Yeah running for the past 24h no problems everything works. Thanks
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 02:24 AM ---------- Previous post was at 02:07 AM ----------
Only thing that that's annoying is the wifi in the taskbar. I read in one of the posts that I have to go into systemui and some other files within n delete lines 12 through 21 but that didn't work , am guessing I need to decompile systemui to do that. The person in the post didn't clarify and I'm not ready to do that yet. Reason is I don't know anything about programming or linux or decompiler or anything like that. Deleting files I can do replacing some sure. But I'm happy my first attempt to mix something together worked and I'll keep doing it till I actually figure out what it is that I am doing. Thanks again for the post
Sent from my SCH-I535 using xda app-developers app

Yea. Follow Didacts write ups to get you through it. It's all in framework res apk.

Any recommended init.d scripts for Stock?

Subject says it all. Just enabled init.d in stock and looking to see what scripts people are using and why?
And just to clarify, I'm already using "01permissive" and "08setperm", essentially the base scripts put in place Ryuinferno's init.sh file.