Hello ALL!
Here is the long awaited HTC Tornado ROM kitchen
This Kitchen is in actual fact the Molski DEVPACK kitchen but its been MODIFIED by myself, Duke_Stix in order to be compatible with the HTC tornado and to make rom editing and cooking easier for EVERYONE!
Please note, before anybody starts pointing fingers, FULL permission was obtained from molski himself before any modifications were made and full permission was obtained in order for me to release this kitchen as the initial kitchen was of course, by MOLSKI!
This was the first kitchen that i learnt to use so it was the first kitchen i modified!
There will also be a modified CORE kitchen released soon too once i can iron out any and all bugs.
Anyway:
Pretty simple to run really. heres a few instructions to get you all started:
Download the attached file: Molskis_Devpack_modified_for_tornado_by_duke_stix.exe
READ THE PDF FILE THAT IS IN C:\DEVPACK\tools\batch\readme
Here are steps:
1) RUN the executable file, you should end up with TWO folders, DEVPACK and Molski.biz Devpack. MOVE the 'DEVPACK' folder to the ROOT of your C: drive.
2) Place ANY nk.nbf that you wish to 'unpack' into the source folder of the DEVPACK folder. so.....
' C:\DEVPACK\source ' Contains your NK.NBF file
3) Go to your desktop and into the 'molski.biz devpack' folder, this has lots of little shortcuts in it.
4) first of all, click the 'dump rom' script.
5) Let it do its thing
6) in the C:\DEVPACK folder there should now be a new folder called......ROMDUMP! (<-- guess whats in here?!)
7) Edit as much as you wish, dont forget to get rid of the first two bytes in the initflashfiles.dat file before you build rom again
8) once you've clicked the 'build rom' script go back into c:\devpack\tools and in there should be nb2nbf_tornado.exe
9) open that, dont touch anything atthe top apart fro the output field, here, I would suggest selecting your desktop and you MUST issue the file name as 'nb.nbf'
10) below that click the tick box next to 'File #1:' it will allow you to select 'file #1' point it to c:\DEVPACK\ROMDUMP and to the file called 82040000-OS.nb
11) back in the nb2nbf program select 'OS' under image name
click translate
go to your desktop, move the nk.nbf file there into C:\DEVPACK\tools\RUU_2001
run the 'ROMUpdateUtility.exe'
and away you go! should start flashing
IT IS IMPORTANT THAT YOU READ THE README FILE! i will also attach it to the post
also, anyone willing to donate can send any paypal donations to [email protected] and reference them 'duke'! very much appreciated!lol
MIRROR:
http://www.megaupload.com/?d=VWCLXM6Z
ENJOY!
post any questions here
AND DO NOT FORGET TO READ THE README FILE!!!!!
ALSO READ: http:\\www.molski.biz
HAPPY COOKING!
duke_stix said:
How to use this Rom Cooking Pack:
I tried to make everything as simple as possible, still you definitely need to know what you are doing!
Step 1:
Extract the nk.nbf file from a Rom archive (all Rom archives can be opened with tools like WinRAR) into the X:\DEVPACK\source directory.
Step 2:
Execute the DUMP_ROM script when the script is finished a ROMDUMP folder is created in X:\DEVPACK, with all the .nb files found in the nk.nbf file, the 80040000-OS.nb file will be splitted into 2 template (.bin) files and the contents of the OS templates is placed in the “dump” folder.
Step 3:
When the script is finished you can start adding and deleting (watch out what you delete!) files in the dump folder.
Step 4:
Editing the initflashfiles.dat file!
Execute the EDIT_INITFLASHFILES script so the file gets copied to the ROMDUMP directory, a backup of this file is placed in the Backup folder inside the ROMDUMP directory!
This is a very important file, when the Wizard gets a hard-reset or is flashed to another Rom, this file builds the directory structure, copys files from Windows to (as example) the Program Files directory.
These are some examples from the initflashfiles.dat file:
root:-Directory("My Documents")
Directory("My Documents"):-Directory("My Pictures")
Directory("\Windows\Start Menu")ermDir("Programs")
Directory("\Windows\Start Menu")ermDir("Settings")
Directory("\Windows\Start Menu"):-File("Messaging.lnk","\Windows\tmail.lnk")
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
Directory("\My Documents\Templates"):-File("love.gif","\Windows\love.gif")
As you can see, not so tough as it looks, I am not going to explain every single line of this file, but will give you one example….just to make things a little bit easier to understand!
All files from the “dump” folder are basically placed in \Windows and get copied to other directories from this point, so when a shortcut is copied from \Windows to \Windows\Start Menu\Programs you will have a shortcut in both directories (but that’s not a big deal!).
I am going to explain this line, to let you know what this line actually does
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
The shortcut fexplore.lnk in \Windows gets copied to the \Windows\Start Menu\Programs directory and gets renamed to File Explorer.lnk
Very easy….isn’t it? J
So…after adding all files to the “dump” directory, adding the lines of the added files (IF needed) to the initflashfiles.dat file you can save this file, make sure the last line in this file is a blank line (otherwise your device will be stuck at the second Splash Screen)!!
Example:
When you want to add a program named ABC.exe to \Start Menu\Programs, just copy the ABC.exe file to to the “dump” folder and place a shortcut named ABC.lnk in the “dump” folder and add a line for ABC.lnk into the initflashfiles.dat file.
To create a shortcut for ABC.exe, simply open Notepad, create a line like this:
24#"\Windows\ABC.exe"
(the number can be different), save it as ABC.lnk and add this to the initflashfiles.dat file:
Directory("\Windows\Start Menu\Programs"):-File("Alphabet.lnk","\Windows\ABC.lnk")
In this example the shortcut ABC.lnk, that points to ABC.exe gets placed in Programs with the name Alphabet.
After saving the initflashfiles.dat file, open the file in WinHex and remove the first 2 bytes (FF FE)!
If you don’t remove these 2 bytes your device will also be stuck at the second Splash Screen!!
After removing the 2 bytes and saving the file you can copy it to the “dump” folder (overwrite the original initflashfiles.dat file….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 5:
Editing the HV Files!
Okay, let’s say that the application used in the example (ABC.exe) has a few Registry Values and will not work without it, therefore we will need to edit the default.hv and/or user.hv files.
Execute the script CREATE_RGU_FILES, this will copy the default.hv and user.hv files from the “dump” folder into a directory called HV Files in the Romdump directory and convert the 2 .hv files into .rgu files so we can edit them with notepad.
When editing .rgu files there are 4 things that are very important!
Turn off Word Wrap in Notepad
The 1st line is a blank line, type “REGEDIT4” (without quotes) on this line
Make sure the last line of the file is a blank line
Make sure the files are saved in Unicode and not in ANSI
The Windows Mobile Registry has 4 keys:
[HKEY_CLASSES_ROOT] à These Registry keys gets insert in the default.rgu file
[HKEY_LOCAL_MACHINE] à These Registry keys gets insert in the default.rgu file
[HKEY_CURRENT_USER] à These Registry keys gets insert in the user.rgu file
[HKEY_USERS] à These Registry keys gets insert in the user.rgu file
When you are finished editing the .rgu files, execute the CREATE_HV_FILES, watch properly of the files get converted without errors, if everything went okay, copy the default.hv files from the HV Files directory to the “dump” folder (overwite the original files….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 6:
Okay, by now we have extracted and dumped the nk.nbf file, added and/or removed files from the “dump” folder, edited the initflashfiles.dat file, added registry values in default.hv & user.hv and copied the 3 edited files to the “dump” folder.
Now we are (finally…) ready to build the Rom!
Execute the script BUILD_ROM and wait till it’s finished (will take a couple of minutes depending on the speed of the computer).
This script will add the modified “dump” folder to the OS template files (.bin files) and when that is done it will build the 8004000-OS.nb file from the OS template file.
[\QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
reserved yet again
Thanks a lot for this tool i'll look that when i will go at home.
Thanks for all your job
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
ericjm said:
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
Click to expand...
Click to collapse
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
burkay said:
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
Click to expand...
Click to collapse
thanks dude!
anyone tried this yet then?!
\
im awaiting feedback!
When I tried to dump rom, I get this
Splitting 80040000-OS.nb into .bin files....
Unable to open source image [80040000-OS.nb]
Creating Dump directory....
Dumping Rom content into dump directory....
Please wait a couple of minutes, depending of the speed of your computer!
Dump folder is ready in ROMDUMP directory!
Press any key to continue . . .
Why is it that I am unable to open source image ?
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
jm012a9749 said:
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
Click to expand...
Click to collapse
Actually im dumping using Mozbi Devpack for Wizard, thought it is the same, it works now.
Thanks
oioi
I'll get to changing that right now. didnt notice that!
Good tools and good explanations.
I dumped I rebuilt a Qtek ROM today for my wizard, and the advices of this thread were the biggest help.
Thanks and well done.
Customized ROM hanging in spash screen
Hello Duke,
I am currently in the process of customizing my own ROMs from other user builds thanks to the tools you provided. I am having problems though...I have used multiple nk.nbf (different os) files and dumped then rebuilded without modification just to make sure I have the technique correct. That is without modifying initflash or hv files and going right to rebuilding after dumping and I am hanging on the first screen. I then need to manually go to bootloader for reinstall.
I then checked with my modified ROMs following pdf religiously (ie deleting first 2 bytes and leaving last empty line-initflash...and adding REGEDIT4 and leaving last line saving as unicode-rgu...following instructions provided) and yet I continue to hang on the first screen.
Do you have any suggestions??
Thanks again,
vjgrace
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to load, don't know how to modify it, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
if u wanna extract system.img then use dsixda kitchen.
put the img file in update original update folder then go to cygwin and choose make a working folder from rom.
it will identify your img file and then give an opt to extract it.
Hello everyone,
I am tying to make a "light" official rom of the Z3 by removing some *.apk of an *.ftf file.
I have extracted all the folders from the *.ftf (ftf - system.sin - system.ext4 - files...) and removed all the apk I don't want, but I don't know how to make a new "system.sin" from all the files I have extracted. I looked from the internet, but I am a little noob.
Can someone help me to build a new *.ftf file to flash it with Flashtool ? :crying:
Dracow said:
Hello everyone,
I am tying to make a "light" official rom of the Z3 by removing some *.apk of an *.ftf file.
I have extracted all the folders from the *.ftf (ftf - system.sin - system.ext4 - files...) and removed all the apk I don't want, but I don't know how to make a new "system.sin" from all the files I have extracted. I looked from the internet, but I am a little noob.
Can someone help me to build a new *.ftf file to flash it with Flashtool ? :crying:
Click to expand...
Click to collapse
As far as i known you can't edit .sin / .ftf files as they are signed using sony private key that no one has...
Technical info here:
https://gist.github.com/dosomder/8ed79b26a5e063efa5ef
"And that is the reason why we can not create custom firmwares for Xperia. If you still don't understand, RSA is an asymmetric function.
This means it's using a private key to create the signature and a public key to read it. So even if we find the public key
(which is somewhere on the device), we can never find or guess the private key. Therefore we can not create a valid signature."
But you can create a .zip firmware to be flashed via recovery
I used Flashtool-sin editor on "system.sin" that give me "system. ext4".
With ext2explore I opened " system.ext4" and extracts all files and folders (app, privateapp, etc, build.prop...).
From folders "app" and "privateapp", I removed the *.apk I don't want, but I don't know if I can build a new " system.sin".
There is really no way to reverse ? Make a "system. ext4" from the folders I modified, and convert it in "system.sin" ?
If we can do something in a way, can't we do it on "reverse way" ?
Dracow said:
I used Flashtool-sin editor on "system.sin" that give me "system. ext4".
With ext2explore I opened " system.ext4" and extracts all files and folders (app, privateapp, etc, build.prop...).
From folders "app" and "privateapp", I removed the *.apk I don't want, but I don't know if I can build a new " system.sin".
There is really no way to reverse ? Make a "system. ext4" from the folders I modified, and convert it in "system.sin" ?
If we can do something in a way, can't we do it on "reverse way" ?
Click to expand...
Click to collapse
It cannot be done. 100% impossible.
If you want to make your own rom Google [NUT]'s method to create your own rom.
There is also a tool to create your own prerooted flashable zip, but if course, all of this requires root
Thanks a lot for all your answers...
I won't try to make it in zip...
Welcome. Today I am going to teach you how to modify your android boot logo!
Modify at your own risk! I strongly recommend that you do not try this. But if your going to attempt this, make a BACKUP! I will explain the backup process down the page!
This method has been tested on the Galaxy S6. I RECOMMEND you do NOT attempt this method on any other smartphone other than the S6!
I own a Samsung Galaxy S6 [SDK21 ARM64] and my carrier is Straighttalk. This method might possibly work with the newer Android smartphones. In other words, attempting to do my method will probably not work with androids running 4.4.2 or lower. I will first explain why.
According to what I researched, there is a file in the root directory of the Android system that contains a file called "initlogo.rle". That is your boot logo. Older Android phones had this. The .rle is a bitmap extension and cannot be edited with Android. Actually, let me rephrase that, the .rle COULD MAYBE possibly be edited if you were to download the right tools off of the Play Store but computers can identify .rle as a bitmap very easily and can be opened. Windows computers can open .rle according to what I researched.
The initlogo.rle is also part of the boot.img. The boot.img contains the kernel and the boot files (like init.rc), that are necessary for the phone to boot up. Modifying your boot.img requires a computer. You can't just replace the initlogo.rle with another one. To make changes to a boot.img, you need to unpack the ramdisk, replace or modify the files, repack, and THEN flash the modified boot.img to make the changes.
Newer Android smartphones don't have initlogo.rle. Or at least MINE doesn't. Instead, I had to search for my boot logo which took my quite a while. After searching deep into the android system and messing around with the files, I came accross PARAM.
If you were to go in the /dev/block/platform directory, you would come accross a file called PARAM. Mine was in the directory /dev/block/platform/15577000.ufs/by-name. Inside that directory is basically the whole system. You will find files like BOOT, EFS, OTA and all that. You will also notice that all those files look empty. They all show 0.00B. I don't know exactly why that is, but they aren't really empty files.
My official boot logo was in the file "PARAM". What I did was copied it to my internal directory and attempted to extract it. After trying different extensions, I founded out that .tar is the correct extension. So to extract it, I renamed "PARAM", to "PARAM.tar". After doing that, you will be able to actually extracted it and be left with files with .jpg. Basically pictures inside it. I used root browser. :good:
Inside, you should find "logo.jpg". And whatta ya know! It's your boot logo!
I used PicArt to create a custom boot logo. It is a really great app! You can get it off the Play Store. Then I renamed it to logo.jpg and replaced the original logo.jpg with my newer one. Make sure it is named "logo.jpg" or there will be errors!
Now the last step is to archive the files through .tar format. I used root browser to do that. To correctly archive the files, multi-select the .jpg files. In other words, DON'T SELECT THE "PARAM" FOLDER!!!
When archiving the files, use LZMA compression option along with tar.(Look for that with root browser). This will not compress the files as much which will reduce the risk of errors.
Once it's archived, rename the new archive file to just "PARAM".
LAST STEP! Before overwriting your PARAM, copy your modified PARAM into the /system folder and set the correct attributes (PERMISSIONS) to -rwxrwxrwx. Now you are ready. Copy "PARAM" to the same director where you originally got your unmodified PARAM file. It will ask you if you want to overwrite. Say yes.
I was now introduced with a different boot logo. My phone never got bricked during the process. However, with Android, ANYTHING can happen, so I will give you some advice. If you have a custom recovery, you can easily restore PARAM. Make a copy of your original PARAM and put it in your internal directory. If something ever goes wrong, you can use the file manager (like with TeamWin) and replace the currupt PARAM with your backup PARAM. Then set the permissions to -rwxrwxrwx or 0777
I strongly recommend that you do not try this. Yes, I took the risk and was able to safely change my boot logo. However, not all Android devices are the same so be very careful if you are attempting to do this one an Android device OTHER than the Galaxy S6.
Leave comments if you have any questions!
Hi,
I am trying to port a rom, it had the file system.new.dat, I managed to extract the system folder from it, now I have made the changes I wanted, but I need to return the system folder to be system.new.dat
Or if there is any flash without having to go back to .new.dat
someone help me please!!