NOTE: I've already posted this into the Development & Hacking forum, but got no reply yet. As it is an Hermes specific topic it is probably better to place it here, sorry for reposting if you've already read this.
The available original shipped ROMs for the HTC Hermes have .nbh files with the RUU, instead of the usual .nbf files found in other HTC rom updates.
By now, there are two shipped ROMs available, containing:
HERMIMG_Dopod_1.23.707.1_SHIP.nbh
hermimg_QtekNOR_1.18.255.3_Ship.nbh
So, it seems that the usual nk.nbf file is no longer used by the Hermes RUU
I cannot extract the various rom components (ExtROM, OS, IPL/SPL, SplashScreen, GSM radio, etc...) out of these files using the usual TyphoonNbfTool, however mamaich's prepare_imgfs finds the imgfs and dumps it apparently ok, but it cannot be read using viewimgfs or itsme's rdmsflsh.pl, so I guess the dumped file is invalid.
Anybody knows about this new format?
is it possible to convert it to nk.nbf so we can cook our own roms?
Would it be possible for example to extract the radio rom from Dopod and replace it on QtekNOR rom?
I think we will have to wait for the rom guru's to advise on this. I hope this would be possible so we can get the best rom possible.
I've tried to decode.nbh files with alpinenbfdecode.pl, himalayanbfdecode.pl and typhoonnbfdecode.pl. None of them works, so this must be a completely new format.
Opening nbh files in hex heditor shows interesting strings, but I don't know how to procede to identify each part and decompress or decrypt it...
Is it possible to decrypt Extended_ROM of HTC TyTN? I'v found a great extRom, but I can't upgrade my ExtRom because I have only borrowed tytn from my friend and Iam looking for one special aplicattion which is included in this. Any solutions ? Thanks
Jerry, you can unlock & unhide the ExtRom just with a registry tweak, look here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Downloading a ROM now to experiment
If I crack it, you guys better donate something to my get-theblasphemer-a-hermes-too-fund (yet to set up that fund though )
Mate if you crack it I'll be donating to your fund!
Hmmm, a very weird file format indeed :S
All files start with "R000FF\r", next 16 bytes of what appears to be random data.
After that it consists of several blocks.
Each block starts with a header:
4-bytes block-length
4-bytes footer-length
1-byte always 1
After that follows the actual data (block-length bytes) + a footer, which appears to be random data but which I suspect to be some kind of checksum
I'm uploading a full USB log of a complete ROM-flash here:
ftp://xda:[email protected]/Hermes/Technical/
Watch for the file Dopod2-FullRomUpgrade.txt.gz, when it is full uploaded it will be around 102Mb.
This is from this ROM file:
HER_DopodAsia_1237074_1060010_WWE_SHIP.exe
______
EDIT: Upload finished.
I created a wiki page with all the info we have about NBH format:
http://wiki.xda-developers.com/index.php?pagename=Hermes_NBH
i added my scripts to extract nbh files to the wiki page
willem
itsme said:
i added my scripts to extract nbh files to the wiki page
Click to expand...
Click to collapse
Cool :shock:
you always come with splendid work, so pleasant to see... thanks a lot!
Hmmm... just took a peek at the USB-dump of a ROM upgrade.
It appears that the whole file is just sent to the device.
The flashing utility doesn't even look at the CID or even the device type, it was happy to start flashing my Universal (however it didn't get very far, as the bootloader doesn't understand all commands ).
This makes it incredibly difficult to make a RomUpgradeUtility that doesn't look at the CID, or to figure out how the signatures in the .nbh files are generated
willem,
I've been trying to extract the roms using your commands, everything runs fine until I have to run the gsmsplit batch file, as in this line you call "bcl" and I don't know what bcl is:
Code:
for %%i in (_bcl*) do bcl d %%i _x%%i.nb
I am runing it on WinXP SP2 + cywin 1.5.21-1, this is the error I get:
Code:
[email protected] /cygdrive/c/nbh/files
$ gsmsplit.bat GSM.nb gsm.nbx
'bcl' is not recognized as an internal or external command,
operable program or batch file.
'bcl' is not recognized as an internal or external command,
operable program or batch file.
[...]
'bcl' is not recognized as an internal or external command,
operable program or batch file.
'bcl' is not recognized as an internal or external command,
operable program or batch file.
_x_bcl*.nb
The system cannot find the file specified.
0 file(s) copied.
Could Not Find c:\nbh\files\cing\_x_bcl*
[email protected] /cygdrive/c/nbh/files
$ dir
GSM.nb MainSplash.nb SPL.nb nksigned.dbh signatures.txt
IPL.nb OS.nb SubSplash.nb nksigned.nbh unknown_601.nb
Is the line correct? if yes, what is bcl and where can I get it?
Thanks!
Ok, almost everything went fine... i don't know yet about the bcl command i asked before, and i cannot extract the contents of imgfs from OS.nb using rdmsflsh:
Code:
$ rdmsflsh.pl -d files OS.nb > rd.txt
could not find imgfs header
I've also tried prepare_imgfs.exe with OS.nb, it found IMGFS there and dumped it to imgfs_raw_data.bin, but then I cannot use viewimgfs.exe with this file, it complains about "unknown header type", and the file seems corrupt as it is only 6Mb...
BTW... SubSplash.nb seems to be the ExtROM, not the SubSplash.
I get a "Check cert error!" from the bootloader when I try to flash a modified NBH file (thanks TheBlasphemer for your help).
From spv-developers:
"getting a developer CID (SuperCID) will allow you to flash your system with a ROM that is not digitally signed (i.e. a ROM that you have modified). If you do not modify it, you'll not be able to install a modified ROM on the device."
Click to expand...
Click to collapse
Is it possible that we can flash NBH files without signing in the Hermes if we get a SuperCID?
I tried using SPV-Services to change the Hermes CID, but when I execute the CID tool (Alpha) I get the error: INVALID Storage Manager Handle (SAFE)
The NBH format is also used by HTC STARTrek, more info here.
bcl is from bcl.sourceforge.net, and in the latest release called 'bfc'.
willem
pof said:
Ok, almost everything went fine... i don't know yet about the bcl command i asked before ...
Click to expand...
Click to collapse
Hey pof, you need to rename the bfc.exe to bcl.exe ...! then you dont get the error but alot other zero lenght values ...
so did anyone manage to get the extraction of the OS.nb done correctly?
Hi! Do you think is possible to manage that NBH file and change htc logo splashscreen in some ways?
I'd like to create a ROM file upgrade with different spalshcreen for my TYTN.
Related
In case you have a preproduction HERMES and you can not update the ROM (due to the fact that your bootloader is <1.04) here the very easy solution:
- format a SD card with FAT32
- extract the .NBH file from the rom image you like
- rename the .NBH to HERMIMG.NBH and copy it to your SD card
- put SD card in phone and start it in bootloader (hold OK button on left side and POWER button at same time and stick with stylus in RESET on bottom)
- confirm flashing on screen
- flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes.
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work.
John
P.S. Same applies to other devices: BREEIMG.NBH, STARIMG.NBH, ...
Re: Solution for flashing HERMES preproduction devices found
Hi J.S.!
This is a very great finding!! How did you find that???
J.S. said:
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work.
Click to expand...
Click to collapse
Preproduction devices are superCID, so they should be able to flash any image using that method.
J.S. said:
P.S. Same applies to other devices: BREEIMG.NBH, STARIMG.NBH, ...
Click to expand...
Click to collapse
I guess BREEIMG is for HTC Breeze and STARIMG for HTC Startrk, right?
Holy Sweet Jiminy Cristmas, OK, now this is what mine is doing so far, (which is further than any thing else we have done)
Sitting at Checking..., and has been for around 10 minutes or so now
Will keep you updated, hey anyone able to get access to the holy grail of HTC support site?
Excellent news!
I just need to get my hands on a micro SD card and I'll give it a whirl!
Thanks again, buddy.
I'll let you all know how I get along.
Oz
So how long did your screen stay with the Checking..., as I am now on my 4th IMG to try, and all have taken over 10mins each while on the checking.
I need some slepp so this one i will let run while i sleep.
Any way of changing the CID, as mine is not preproduction.
darkoverlord said:
Any way of changing the CID, as mine is not preproduction.
Click to expand...
Click to collapse
No known method yet...
But you have a TyTN as I have seen in your other post, so you can flash the HERMIMG.nbh from HTC TyTN rom which will match your CID.
OK, but how can I know my CID, and which one to choose.
darkoverlord said:
OK, but how can I know my CID, and which one to choose.
Click to expand...
Click to collapse
The bootloader command "info 2" returns your CID, on a TyTN that is:
"HTCS" + "QTEK_001" + (4-byte checksum) + "HTCE"
You can also find it by running GetDeviceData.exe.
These are the ROMs an it's CID lock:
HTC: QTEK_001
Dopod: DOPOD001
JasJam: CDL__001
Cingular: CWS__001
O2: O2___102
great stuff, J.S. )
buzz
Hi Guys, At this point is it possible to get an .NBH file from a .RAW file and so flash back to my original shipped ROM?
wwaveydave: It is not possible, see my answer here:
http://forum.xda-developers.com/viewtopic.php?t=62730
The Hermes SPL searches for two files on SD card, one is HERMIMG.nbh as pointed out by J.S. on this topic, the other one is HERMDIAG.nbh.
Anyone knows about what is HERMDIAG? looking at the name seems some kind of DIAGnostic SD card... :?
I've been told by itsme that HTC StarTrek supports 2 ways of sd-card flashing:
1) with 'starimg.nbh' on a fat32 filesystem (same as in hermes, but using hermimg.nbh instead)
2) with a typhoonnbfdecode.pl generated sdcard
I've tried to generate a cooked rom for TyTN using typhoonnbfdecode.pl, but the .nb files extracted using nbh2dbh.pl and dbhdecode.pl are not valid, it seems that typhoonnbfdecode.pl expects the .nb files to be decoded as sd header image (using flag "-i" of typhoonnbfdecode.pl itself), but this tool is not useful to handle NBH files.
Also trying to make a NBF file with typhoonnbfdecode.pl out of .nb files extracted from original shiped NBH file gives an image validation error on each module specified in ' -r '.
Any help will be much appreciated!
hermdiag.nbh is a diagnostic/setup/lock/unlock SPL image.
buzz
If you compare the NBF file you've created to the NHB file pulled from one of the shipped ROMs will that help? I'd like to help, but need time to get up to speed on the whole ROM cooking process.
The problem is that I cannot even create the NBF... I get a validation error in every module, like if all the .nb files where invalid:
- no sm signature at 0 in Splash
- no 7 * jump +5 at start of gsm
- no ECEC at 0x40 in OS image
- no IPL at 4 in IPL image
- no ECEC at 0x0040 in SPL image
any ideas?
Right guys,
I've tried the method outlined in the originating post but it doesn't seem to work for me on my Preproduction Hermes. This is what happens:
1) Format 1GB Micro SD card to FAT32 via Windows (right click and select Format).
2) Extract .nbh file from ROM image.
3) Rename .nbh file to HERMIMG.nbh and copy to SD card.
4) Put SD card in phone and start in bootloader (as specified)
5) The screen goes white for a second and then an error message pops briefly (about a millisecond! I had to do about 20 times before I could be sure about what it said). The error message was "No Image file!"
6) Reverts back to bootloader.
Have tried this with all of the English ROMs listed on the Wiki and get the same result each time. I'm not connected to the PC during all of this. The only file that exists on the SD card is the HERMIMG.NBH (exactly that naming format).
Any help would be much appreciated.
Oz
ok, follow these instructions:
1) Use the "Explore" option on activesync
2) Erase all the files in storage card
3) Copy HERMIMG.nbh
4) Enter into bootloader
No need to remove the microSD card from your device at all... this is how it worked for me.
No such luck for me I'm afraid. I still get the same error. I don't understand it, what is this Image file it's looking for? Is there anyway of determining it?
@pof - is your Hermes preproduction?
I've tried a smaller SD card of 128MB and renamed the file to HERMIMG.NBH but still no luck. I don't know if it's my phone or if preproduction phones except the filename to be different.
Is a .nbh file an image file?
mine is not preproduction, it's an HTC TyTN (HERM200). My microSD card is 1Gb.
I renamed the .nbh file extracted from the rom upgrade exe to "HERMIMG.nbh", I don't know if it's case sensitive or not. It worked for me this way...
And yes, nbh files are rom upgrade files which contain all the rom parts (splash image, radio, ipl, spl, etc...) and are signed by HTC.
i am following all steps thru SAFE WM5 upgrade guide. I make it thru the Flashing HardSPL and Upgrading to Radio version 1.41.00.10 with no problems. But on Rebuilding the ROM file I cannot get passed this step....
____________________________________________
When you have downloaded the ROM file you must extract the contents of it using winrar into a folder, to make the process simple i suggest extracting to "original". Now delete ALL the files EXCEPT THE .NBH FILE. We are only interested in this file as it contains the nbh data which is flashed to the device.
The next step is to extract the contents of the file and split it into the seperate components.
Download duttys nbh tool and run it,
_____________________________________________
When I run that tool and try to Decompile NBH File the only thing it show me is radio.nb
It does not show me files like Windows.nb or Herm_ExtendedRom.nb and so on. Just radio.nb
So i am stuck I would really like your help on this.
Here is the link to the step i get stuck on.
http://www.mrvanx.org/cms/index.php...ask=view&id=27&Itemid=26&limit=1&limitstart=4
I can download all the files and programs but as you read above i am having problems. Thanks for any help
Next time wait for me to read this thread rather than PM-ing me the same EXACT thing!
Like I said in the PM it sounds like you are decompiling a radio upgrade rather than a ROM upgrade. Verify you are extracting the nbh from the correct file.
Hi
Now I'm trying once again tho change from M$ Windows to Linux. My experiences with Linux are only 3 weeks old, so I've many open questions.
I'm currently searching tools to extract, cook and repack .nbh files.
An tool to extract an complete ROM in his parts that works under Linux too is NBHDump from Olipro, but I haven't currently found an solution to repack this .nh parts in one .nbh again.
How can I extract the OS.nb ? Is it possible to extract in packages like Bepe's tool ?
I know many (stupid ?) questions, but a short help would be nice.
Thanks
scorpio16v
scorpio16v said:
I'm currently searching tools to extract, cook and repack .nbh files.
Click to expand...
Click to collapse
Extract: nbh2dbh.pl & dbhdecode.pl from itsme (see wiki), and to exctract the shipped roms exe use cabextract.
Repack: no tool available, i've one unfinished attempt, probably someday i can finish it.
scorpio16v said:
How can I extract the OS.nb ? Is it possible to extract in packages like Bepe's tool ?
Click to expand...
Click to collapse
No
And the usual tadzio / mamaich tools don't work under wine because of the ce compression dll dependancy.
But... you can also flash your hermes under linux too, i'm planning to release stable version soon, now in teesting phase:
http://forum.xda-developers.com/showthread.php?t=296436
Thanks for your answer pof.
Of course I've your HTCFlasher on my harddisk.
And it's possible to use it with Bootloader 1.01 MFG to flash an .nb, right ?
One additional question I have is, if I split the complete ROM in .nbh with NBHDump.exe in it's parts (under Linux), is it save to use this .nb files to flash ?
Or are the files corrupt, because NBHDump is written for Windows ?
Ok
Have tried a few things:
1. NBHDump.exe works
2. To extract to imgfs_raw_data.bin I can use aChef.jar
3. To make a Dump I can use Tadzio's ImgfsToDump.exe with the msvcr71.dll inside the directory.
4. Tadzio's tools, tested from OS.nb to Dump works too.
OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
Click to expand...
Click to collapse
5. Tadzio's tool from Dump to OS-new.nb works too.
dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb
Click to expand...
Click to collapse
Theoreticaly I can now add or delete something, right ?
I've tested this procedure with the T-Mobile WM5 germany OS.
I've attached the dll.
Unfortunately I have no clue, how I can use the two batch files from Tadzio (NBDump.bat /NBBuild.bat) to automate this procedure .
And the usual tadzio / mamaich tools don't work under wine because of the ce compression dll dependancy.
Click to expand...
Click to collapse
I've done this in a terminal not under Wine
pof said:
And the usual tadzio / mamaich tools don't work under wine because of the ce compression dll dependancy.
Click to expand...
Click to collapse
AFAIR it was a different bug, and tadzio has added a better error message
recently.
I don't know about assembling nbh (not really interested in that but
all dissecting tools worked with wine for me.
Hi, I've just dumped a Hermes ROM and now I'm trying to recontruct it, but I need the OS.nb file. I read the Trinity Rom Reconstr.procedure (I think it should work for Tytn too...) and it says to extract the ROM to \shell (a folder)...etc...Well, I've downloaded a ROM, but I don't understand what I have to extract from a .exe file...
Can someone help me, please?
Thxs,
Giangi.
you better keep on reading son....
Yeah, I read, but maybe I didn't understand well, right? This is my first try in dumping ROM...Anyway, I tried the "extract procedure" here
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoExtractImgfs
but I'm still a little confused, and I'm sorry for this, but maybe I'm limited...
Anyway, when I download and install ActiveState Perl, what do I have to run in order to write the line commands? (I mean repository and install commands).
I'm sorry for my bad english too.
Thanks.
Where do I have find the OS.nb file?
Can someone post a detailed procedure, please? I dumped the ROM, but I've some difficulties in extracting the imgfs and ricontructing it...
Thank you for your support, I found the anwer!
but on another site...
dude its all about sharing
please post the answer
its not a secret. all you have to do is use tadzio's tools here and follow the steps
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
Here you'll edit the 'dump' directory. I recommend using bepe's excellent *Package Tool for this.
The reverse process is:
'dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb ---(*NBHGen)--->
RUU-signed-new.nbh
(The tools marked with '*' are not part of the ImgfsTools, but are also available for free from xda-developers.com. There is also one additional tool, NBInfo, in this package.)
Click to expand...
Click to collapse
Hi
I'm searching for information about ROMcooking for ATOM Life, but unfortunately there are not many informations about this device.
1.The Wiki explains only the ATOM Romupdate:
ROM Update File Composition:
* diskimage_Ver.nb0 - ROM file
* EBOOT.nb0 - bootloader file
* ExtendedRom.img - hidden partition image file
* nova_pda_033105.mot - checksum partition ??????
* vl1d_pda_Ver.mot - radio file
* Device Software Update Utility.exe - ROM upgrade utility file
Click to expand...
Click to collapse
The ATOM Life Update .exe contains:
Device Software Update Utility.exe
EBOOT.nb0 - Bootloader ?
IPL.nb0 - initial Bootloader ?
cpld.img
XLDR.nb0
FLASH.DIO - OS image ?
ExtRom.img - ExtROM ?
pass.32
and some .mbn files
Click to expand...
Click to collapse
Can someone explain the different files ?
OK I read some threads and learned Howto dump the OS image with Scooterkitchen. Howto add or remove files is an easy job (I hope),
but how can I rebuild this dump to a flashable image?
Hope some of you can lightup me. and sorry for my bad english
thank you
scorpio16v
FLASH.DIO - OS
ExtRom.img - ExtROM
now,get a new rom update method:
it's get from atom life room replant from exec
filename is
AL1.DIO -os
EXROM.IMG -extrom
copy these 2 files to mini sd card,reboot+record enter bootloader mode
system updated!
and use this rom we can updta life to chinese rom version
based on this method
i guess we can copy these FLASH.DIO,ExtRom.img,2 files to mini sd card,reboot+record enter bootloader mode
loading OS
u can try to update your own room update in life.
Thank you for reply
yes, but that'll be the easier part of the job.
My problem is, if I dump the FLASH.DIO in Scooterkitchen I use the following way, posted in an other thread:
To dump files from FLASH.DIO use "Scoter Kitchen".
Just remove first 12 bytes from this file, then use
\Scoter Kitchen\Utilities\TOOLS\SRPX tools>msflshtool.exe
after this use
\Scoter Kitchen\Utilities\TOOLS\imgfs_tools\viewimgfs.exe
Click to expand...
Click to collapse
This pocedure runs fine, but If you running the FLASH.DIO throug msflshtool.exe it splits in 3 parts. (OS and 2 ?? XIP parts).
At this point, I don't know how to rebuild.
The second problem is:
The device will be released as XDA Comet in germany (my country) in about 2 weeks with german language WM6 and at this state I have no backup ROM to restore it to manufacturer settings if something went wrong.
I will try to dump my german ROM and rebuild it with the XIP part of the english XDA ATOM Life ROM but I need an experienced guide to do that.
Is this AL1.DIO SD-update on Developer FTP the actual english version? Where comes it from ?
I don't find the thread about it.
"AL1.DIO" seems the same like the name "HERM.img" for the HTC Hermes. If you update via SD the Bootloader recognized it as the OS-file.
another edit (thanks again to ferryboat):
3.Before next step, go to \windows\temp , u will find the extractable files.
4.find the file "pass.32"
5.Use ultraedit-32 to open it
6.Check first line,u will find "WWE"
7.Change "WWE" to "CHT" then save it.
8.Go to next step, u will pass the phone-check.
9.About 15 mins, u atom life will be the WM6 ENG.
Click to expand...
Click to collapse
That explains the pass.32 file, but you don't need it to SDcard update ?
"buildimgfs.exe" command to build rom and
"make_imgfs FLASH.NB0 -nosplit" update FLASH.NB0 file
rename it to "Flash.dio"
i havn't test rom made by this method.i also try to find an safe method to update rom so i can try my own rom.it's not so much info about life 's rom
i see this chinese rom from blow links,and a lots of people have updated their life to this version.
http://www.52dopod.net/thread-33648-1-1.html
modify 'pass.32' file is only used when use USB link cable to update rom simultaneity you want to change your life rom language from eng to chn or chn to eng.this method is replant from atom and exec.we do not need to modity this file when we update rom in bootloader mode.
ferryboat said:
"buildimgfs.exe" command to build rom and
"make_imgfs FLASH.NB0 -nosplit" update FLASH.NB0 file
rename it to "Flash.dio"
i havn't test rom made by this method.i also try to find an safe method to update rom so i can try my own rom.it's not so much info about life 's rom
Click to expand...
Click to collapse
I've made a short test with mamaich's imgfstools like in your example, if I dump the ROM and rebuild it without any changes (with -nosplit option) the rebuild file has the same size.
But if I compare both files shouldn't the new file be a perfect clone from the scource ?
The new file has the same structure in some parts, but most of it is different.
Please help me!
I want to upgrade only radio Atom Life (not ExtROM, OS) by bootleader mode! what file it need? how will i do? ...
Please help me!
Many thanks.
scorpio16v said:
I've made a short test with mamaich's imgfstools like in your example, if I dump the ROM and rebuild it without any changes (with -nosplit option) the rebuild file has the same size.
But if I compare both files shouldn't the new file be a perfect clone from the scource ?
The new file has the same structure in some parts, but most of it is different.
Click to expand...
Click to collapse
Nope. It wouldn't be a perfect clone. Even in the ATOM, it does not generate a perfect clone. But it still works with mamaich tools anyway. If you want just to edit the IMGFS section, I think it's okay. Just test...
Just don't touch the bootloader eboot.nb0; so, you won't brick your phone. Also, if possible, always update in bootloader mode. Because if you can't update in bootloader mode, You won't be able to restore your device if you have a none working ROM.
Here's a batch file I wrote in opening and closing part1 of atom life. The user who requested was afraid to try it anyway. The purpose of this was to modify the pagepool for the atom life. There are tools available now that can edit the pagepool on the fly, but the atom is not supported. I don't know with atom life.
Code:
<<<< breakdown >>>>
msflshtool.exe flash.dio -d -p1
SRPX2XIP flash.dio.part1
del flash.dio.part1
<<<< rebuild >>>>
XIP2SRPX flash.dio.part1.xip
msflshtool.exe flash.dio -r flash.dio.part1.xip.xiporg
Well I only use breakdown because we will just import the atom life components into our atom devices anyway.
The Atom Life sure could use some update... official AKU0.7 is coming out and atom life is still at AKU0.2.
Our Atoms have AKU0.3 already and we're moving to AKU0.4
Rom Dumper
search for buzz romgrabber / romdumper and dump it to your SDCARD or you internal memory.
This is the RAW file that should be read during bootloader update thru SDCARD. For the ATOM, (if we compare dump with update file) only the header was removed. I don't know with atom life. I don't recommend updating bootloader file with SDCard because SDCard might have a bad block and it will kill your device.