I have to test a new 32 MB rom that has been packaged as a nk.bin file.
The special HimaUpgradeUt lets me bypass bootloader 1.06 protection.
So I'd like to transform my nk.bin into a nk.nbf.
Is there some command line tool that allows to to this?
Thanks,
There is such a tool. It is your favorite hex-editor. Take any NBA file, and paste there your BIN just after the header. Then encrypt with xda2nbftool and flash.
nk.nbf generated this way does not boot
sorry but I'm stuck at bootloader level after flashing.
I took the .nba header (17 912 bytes), appended the .bin files (32 500 000 bytes), appended spaces to fill the exact nk.nba file (33 554 496 bytes), re-crypted the .nba into .nk.nbf, flashed with himupgradeut.exe, but no joy. Where may I be wrong?
thanks for your hint,
After months of learning and digging deep inside the Atom Life, I think now it's time for a newer Rombuild.
Cooking the imgfs is not the problem, but I didn't understand the XIP from Atom Life.
We have 2 XIP parts, compressed in SRPX format.
Grabbing them is no problem with Scoter Kitchen Tool MSFLSHTOOL.exe.
The kitchen contains 2 tools to change from SRPX to XIP and reverse.
As I described in the Atom Life Kitchen thread, repacking the XIP.bin to SRPX causes a smaler file than the source file.
The cooked OS doesn't boot.
That's the first big problem.
The second one are the two XIP sections. The first one is bigger and contains some files, the second one didn't has.
But some files are existing in both sections with different sizes.
So cooking the Atom Life XIP seems more complicated than in other devices.
Here are the 2 XIP sections. Hope someone has an Idea, how we can work with these files:
http://rapidshare.com/files/79622471/LifeXIP.rar.html
Edit:
The first problem is solved. I have compared the original XIP part with the new one in a hexeditor.
I've simply hexedited the beginning and filled the end of the new file with FF to match the needed filesize.
After comparing both, now the new file is identical.
Maybe later, we can use the space of 300kb to encrease the memory of Atom Life .
I wonder, where all the ROM-Cookers for Atom Life devices are hidden.
Another positive aspect is, now we can change the Pagepool of the Atom Life.
After changing the PP from 8MB to 4 MB, my device has a total Program memory of 52.41 MB. After a fresh setup and some tweaking with SKTools, I have, after a softreset more than 29 MB free Programmemory.
I know someone who can handle these files,and he has cooked a 18538 rom for atom life,here is the link:http://www.pdaclan.com/forum-7-1.html, btw,can you tell how to change pageing pool of life?Thanks and sorry for my poor english,hope you can understand what i mean
qq108108108 said:
I know someone who can handle these files,and he has cooked a 18538 rom for atom life,here is the link:http://www.pdaclan.com/forum-7-1.html, btw,can you tell how to change pageing pool of life?Thanks and sorry for my poor english,hope you can understand what i mean
Click to expand...
Click to collapse
Thank you for the hint.
As I can see (or guess, because I can't chinese) there are some ROMs for Atom Life. Even some Pagepool changed.
You can change pagepool only, if you extraxt the XIP, edit it and cook the new ROM and flash it.
But if there are already some ROMs, there is no need to explain, just download the OS of your choise.
I wonder, why nobody of the Rom cooker offers his work for english speaking people ?
As I can't read chinese, please can you or someone else post download links to the Atom Life ROMs of this site ?
Thank you
I want to help you,First,you should log in,use account:qq108108 password:aaaaaaaa,when you log in,simply chick the post,you will see the download link, you would not miss it!I have a problem:when I use Atom Life Simplified Kitchen - Sdh, I got a wrong message:The output sign-buffer is to smal for encrypted signs.Encryption from Unicode (UTF-8) in dodgeposition System.Text.DecoderReplacementFalback." I wonder how to solve this problem and make my rom bootable,Have you have a MSN or something,maybe we can talk about how to make a bootable using the rom Kitchen !!
qq108108108 said:
I have a problem:when I use Atom Life Simplified Kitchen - Sdh, I got a wrong message:The output sign-buffer is to smal for encrypted signs.Encryption from Unicode (UTF-8) in dodgeposition System.Text.DecoderReplacementFalback."
Click to expand...
Click to collapse
Thank you for helping
That's the same problem, I have with my german XDA Comet ROM.
Unfortunatly I have no idea to fix it.
If I find further solutions, I 'll post it.
The Atom Life WWE ROM runns fine with the kitchen. So I'll use this ROM .
I will take o look at pdaclan. Maybe google translation gives me more informations.
Bye
So can you just tell me how to change the pp please?Thank you!!
Of course
Hope I can explain it that everybody can understand. Because it's hard for me to explain thinks in a foreign language.
1. You need an original Atom Life FLASH.dio
2. remove the 12 bytes header with a hexeditor and rename the file to AL1.dio (you don't need these step, if your file is already prepared for MiniSD card flashing. Only for original ROMs from official Updates)
3. download Scoter Romkitchen.
http://rapidshare.com/files/15460590/Scoter_Kitchen_1.0.exe.html
or http://www.megashare.com/107480
4. You need the SRPX tools from this kitchen.
5. put the ROM in the SRPX folder
6. in commandline change in SRPX folder and type:
Code:
msflshtool AL1.dio -d -p 1
7. You'll get a new file called AL1.dio.part1
8. Now type:
Code:
SRPX2XIP AL1.dio.part1 xip.bin
this will produce xip.bin
The SRPX compressed XIP will be changed in the regular XIP format.
9. Locate the following hexstring with an hexeditor:
Code:
FFFFFFFFFFFFFFFF9B4FFFFF64B00000
One line below, you will see:
Code:
00008000
That's the actual pagepool from 8 MB
10. change the value to:
Code:
00004000
or an other prefered pagepoolsize. Save the file first.
11. Now the tricky part, I don't know an easier way yet.
12. type:
Code:
XIP2SRPX xip.bin
You will get a new file called: xip.bin.xiporg
13. As you can see the new file is much smaller than the original one part1.
So you must fix it with the hexeditor. You must compare the original file with the new one.
14. the beginning of the new file should look like the original one, so you must edit the values in the new one till the word SRPX.
After I take a learning lesson by my "teacher" ferryboat, I found out that steps 15 - 17 are not neccessary !! Jump to 18.
(Will edit the howto, after further compare)
15. the old file is bigger and the end is filled with the value FF.
16. just copy the FF -block and paste it to the end of the new one. Save it.
17. Compare if the new file has the same size like the old one.
18. type
Code:
msflshtool AL1.dio -r xip.bin.xiporg -p 1
19. the new file will be written in the AL1.dio ROM image.
20. put the image to the MiniSD . Bring the Atom Life in bootloader-mode and flash it.
Done and ready
You can test several pagepool sizes.
CU
scorpio16v
Thank you!!!Now I have download the new 18538 rom,BUT the Programmemory only have 22MB free,So I need to do something to make it larger.Thanks for you great work!!If you need any help,just tell me!!!And pdaclan have a new rom kitchen for atom life too.
After reading your stuff,It seem that a little bit diffcult for me to understand,But since you explain so well,I think i can make it happen!!
qq108108108 said:
After reading your stuff,It seem that a little bit diffcult for me to understand,But since you explain so well,I think i can make it happen!!
Click to expand...
Click to collapse
You need only to copy and paste the quoted commands in commandline.
The whole procedure needs only about 10 minutest from editing the ROM till to the ready flashed device.
Even the hexeditor is included in Scoter Kitchen, so you have all tools that you need.
The hexeditor in Scoter Kitchen called XVI32. For editing, just open it twice and load the original SRPX.part1 in one and the edited in the other opened instance.
At the beginning of the file, you will see the difference. Only edit the values that are different, till the text "SRPX" (you'll see it).
To copy the "FF" block, just go to the end of the edited file, you'll see where the file ends.
At the original file, there is the beginning of the "FF" block.
Go to first "FF" value,
press CTRL+B , goto the last "FF" value, press CTRL+B again, you will see the block red marked.
Go to "copy to clipboard" button and push.
Now go to the end of the new file and press the "paste from clipboard" button and save.
Hope that some of the new ROMS, tools and knowledge from PDAClan find the way to XDA-Developers, because that'll be bring "life" in the Atom Life comunity.
Thank you for YOUR help.
I hope so,The one who made the 18538 atom life rom had ask you question before.If I meet him ,I will tell him to come here and teach both of us the method to port the xip!!
Done!!Thanks for your tutor!!
I don't understand what it's mean:"cut the 12 bytes header with a hexeditor and rename it to AL1.dio". Could you please explain it more? I'm a new with Atom Life. Thank so much Mr. scorpio16v.
nhathoa said:
I don't understand what it's mean:"cut the 12 bytes header with a hexeditor and rename it to AL1.dio". Could you please explain it more?
Click to expand...
Click to collapse
Sorry, but if you don't know what an hexeditor is and how you should use it and you even can't simply rename a file, it's not the right thing for you to do these job.
Sorry, I tried to make everything you told, rename Flash.dio to AL1.dio and put AL1.dio into SRPX tools folder, then run cmd with command: msflshtool AL1.dio -p 1. Final, it show: "the file is not msflsh50 format" ??? and there is no file "AL1.dio.part1" was generated in SRPX tool folder???
Maybe I don't undersatand "cut 12 bytes header"
nhathoa said:
Sorry, I tried to make everything you told, rename Flash.dio to AL1.dio and put AL1.dio into SRPX tools folder, then run cmd with command: msflshtool AL1.dio -p 1. Final, it show: "the file is not msflsh50 format" ??? and there is no file "AL1.dio.part1" was generated in SRPX tool folder???
Maybe I don't undersatand "cut 12 bytes header"
Click to expand...
Click to collapse
Just open the file with the hexeditor and cut the first 12 bytes to remove the header of the file. than save it.
For example:
XX XX XX XX XX XX XX XX XX XX XX XX E9 FD FF 00
You must delete the XX.
So the new file beginns now with E9.
Thats only an example, maybe your file looks different at the beginning, but you must cut the header.
(XX are only placeholder. You'll see other entries in Your file)
Okok just "remove" 12 bytes header, not "cut" 12 bytes header. Now I can do that. Thank you very much.
An idea: there is a simple tool to change papetool only for "Hermes". With this tool, just load Os.nbh and set 4/6/8/12 Mb, then you will get a new OS.nbh file with papepool you want. That's so easy... You will make a tool like that? I hope so, great man.
nhathoa said:
That's so easy... You will make a tool like that? I hope so, great man.
Click to expand...
Click to collapse
I'm not a programmer or IT expert. So someone other will do that.
I was told that the guy who made 18538 ROM would make a WWE 18538 rom for atom life.So you can just wait for the new rom.Also ,he told me that if we want to edit XIP part ,just need to edit the part1.
Hello All,
I'm new to this kitchen thing and over the last 2 weeks i have been here (in this great community) trying to learn how to become a cooker...or something like that!
Now i think it's time to ask you Cheafs to clarify me because after all this reading i'm getting a little confused....
First of all i'm a HERM200 owner and i'm very happy with it...it’s a great machine!!!
A few weeks ago i tried to install a wm6.1 rom (cooked rom) and all this reading started from here, so i installed Hard-SPL-V7 from Olipro and successful installed a cooked rom.
I also learned that to start cooking a rom I must follow these steps:
a) Get a RUU_signed.nbh: I used a original shipped WM6 ROM version
b) Extract the contents from that NBH file: I used nbhextract.exe
c) After the extraction I get some NB files and I choose the 06_OS.nb (this is WM operative system)
d) I “prepare” the 06_OS.nb to be cooked with aChef (delete or add files). This will generate a raw data BIN file.
e) Optionally I can “mount” in the local disk all the files (or the majority of them) that compose the raw bin file generated in step d) with the viewimgfs.exe tool...
f) I cook the ROM with AddFile.exe or DelFile.exe utilities
g) After all the cooking I must “close” the 06_OS.nb with aChef (option -2)
h) At the end I must compile the NB files in one NBH file that I want to flash to the device. For this I use nbhgen.exe tool.
Here is a resume of all this:
Nbhextract.exe ruu_signed.nbh (this will extract some NB files and one of them is 06_OS.nb)
java -jar achef.jar -1 06_OS.nb (this generates a imgfs_raw_data.bin file)
viewimgfs.exe imgfs_raw_data.bin (OPTIONAL. It generates a DUMP folder with all the files)
AddFile.exe FileToBeAdded.extension
DelFile.exe FileToBeDeleted.extension
java -jar achef.jar -2 06_OS.nb
nbhgen.exe ListOfNBs.txt
Then i put the resulting NBH file and the RUUWrapper.exe (Custom RUU V5.2) in the same folder and it’s ready to flash…..
At the end I’ve find some nice tools that do all this stuff and much more like “hermes rom koch v0.99” and others….
Now my doubts:
Can I cook a cooked rom?
Can I cook a Kaiser original shipped rom for my Hermes?
Can I Flash a different language cooked/original rom in my Hermes?
Where can I find base wm6.1 rom (not cooked) for Hermes?
That’s all for now!
Thanks in advance
apnaf
ola
Can I cook a cooked rom?
Yes, you can do it. It is matter of following the same steps over and over.
But over cooking may produce bad blocks. HarSPL is nice stuff right?
========
Can I cook a Kaiser original shipped rom for my Hermes?
Learn more about the structure of the files...
co relate and check if these match up... so of them in fact do match.
Many of them have built ROMS using different ROMS. it is not rocket science for them but me.
========
Can I Flash a different language cooked/original rom in my Hermes?
Yess, Google, Search, lastly ask!!
=======
Where can I find base wm6.1 rom (not cooked) for Hermes?
forum.xda-developers.com :: Look around?? Many many of them.
I am new as well but i love to read stickies!!!
A very warm Hi! to the XDA community
My phone, the Sony Xperia E4, does not have a recovery - so I am slowly learning how to develop one. It has an MT6582 chip.
In the process I have obtained the stock boot.img (via boot.sin) from the phone's stock .ftf firmaware file.
I wish to use MTK droid tools to create the recovery, however it first gave me the error that the boot.img file is not split. After some research I came to learn that such boot.img files need to be split into the kernal (Zimage i believe) and ramdisk.
After some further research I came across this seemingly helpful guide and tool on how to split the boot.img file on Windows (unfortunately I do not have Linux at my disposal atm).
Now to my issue: (referring to the aforementioned guide & tool) When running the command
Code:
bootimg.exe --unpack-bootimg boot.img
I get this error:
Code:
AssertionError: invald bootimg
Which leads me to believe the boot.img file I have extracted may be corrupt or extracted from the wrong .sin file.
If you are still with me, how can i confirm that the boot.img file from the stock rom is indeed "working" and contains ramdisk and kernal?
Some extra information:
This is the guide I used to initially extract the boot.img file from my phones stock firmware. They highlight that boot.img is extracted from the kernal.sin file. My firmware has no such file. Later in the comments it mentions that newer Sony phones have the boot.img file in the appropriately named "boot.sin" file. This is the file i used to extract my boot.img. Thus from here I cannot see why the boot.img file cannot be split.
The full command line and response is:
Code:
C:\Users\\Downloads\Cofface>bootimg.exe --unpack-bootimg boot.img
arguments: [bootimg file]
bootimg file: boot.img
output: kernel[.gz] ramdisk[.gz] second[.gz]
Traceback (most recent call last):
File "<string>", line 2213, in <module>
File "<string>", line 1424, in unpack_bootimg
File "<string>", line 151, in parse_bootimg
AssertionError: invald bootimg
Thanks very much in advance!