Posted by : Unknown
Wednesday, 9 October 2013
Part 2:Setting up a working folder
THERE ARE TWO METHODS FOR THIS.
1. WHEN YOU HAVE BASE ROM AVAILABLE.
2. WHEN YOU DON'T HAVE BASE ROM.
FIRST METHOD -
->First our folder structure should look like this:
Code:
cygwin folder/home/your user name/kitchen

-> Now we need a rom to work on,
-> Just Place the original rom zip in the original_update folder inside the kitchen.
run the cygwin.exe again type:
Code:
cd kitchen(enter) ./menu(enter)
you will be asked about changing the working folders name, at this point it makes no difference so just continue.
congratulations you have a working folder!!!

Second METHOD -it is almost like ROM Dumping works on any device!
Quote:
-> FIRST MAKE A WORKING FOLDER IN CYGWIN FOLDER IT SHOULD LOOK LIKE THIS cygwin folder/home/your user name/kitchen/WORKING_(your rom name) |
1. META-INF FOLDER - GET THIS FROM DOWNLOAD FILES LIST IN FIRST POST
2. SYSTEM FOLDER - TUTORIAL BELOW
3. BOOT.IMG - TUTORIAL BELOW
2. getting system folder
(NOTE - Rooted phone required!!)
This is universal method and can be done easily using terminal emulator.
For this simply download Terminal Emulator from Android Market.
we need freshly flashed device here. OTHERWISE YOU WILL HAVE LOT OF JUNK FILES.
Open it and type:
Code:
su tar -c system/* >> sdcard/system.tar
This will take some time to finish so be patient.
After it's done you should have a tar file in your /sdcard named system.tar
You can extract it using Winrar or 7zip software. But yes this will have huge size , as it has other useless folders so you will have to delete them. After extracting this system.tar file you will get following folders (Similar one)
Quote:
/etc /fonts /framework /lib /lost-found /media /sd /usr /xbin build.prop |
And the final files that we will have in our system folders will be
Quote:
/app /bin /etc /fonts /framework /lib /media /semc /usr /xbin build.prop |
Quote:
3. getting boot.img Here we have 2 options 1. stock boot.img from stock rom - simple kernel which we get in brand new mobile. 2. custom boot.img from custom kernel - kernel which are modified for overclock or other features 1. getting stock boot.img from stock rom. extract your stock rom with winrar or 7zip. you will see boot.img there. copy it to working folder 2. getting custom boot.img from custom kernel. download any custom kernel which is only for your device. extract it with winrar or 7zip and copy boot.img to working folder NOTE: many of new devices have kernel.bin and other files instead of boot.img so skip this part if your device don't have it... |
Post a Comment