Hi,
I am a litte bit confused.
I took the latest build from NoThrill (WM 6.1 19202) and wants to add some more tools. (Using the kaiserkitchen from Alexis kaiserkitchen_01-20-08.rar).
The orginal RUU_signed.nbh has a size of approx. 90 MB, but after cooking the rom with the "HTC Rom Tool 1.1.0" the new nbd has only a size of 80MB.
I checked in "HTC Rom Tool" only the OS-File. Is that the reason ?
Regards
kuzco1
if you used kaiser kitchen then the OS.nb was run through Taz's imgfs tools so it makes the rom have more storage and also shrinks the rom size down a bit so you should be fine if you got no errors while building it.
Sounds about right, the NoThrills version has an OS but also has Radio rom and a SPlash screen, these will add to the size of the nbh
Is it possible to convert .nbh to nk.nbf to be able to flash this rom on a prophet?
It depends on where the nbh is from. To do it, you'll have to dump it into SYS/OEM (I'd use a hypercore related tool for this) and then rebuild it into an OS.nb before converting it to nk.nbf for flashing.
Its HTC ELF original Rom...where can i find all tools?
thanks dude
In the prophet WM6 forum, there is a link to HyperCore kitchen.
I'm not sure if the ROM will work straight away on a Prophet, as they have different hardware...
edit: to dump the ROM you will need to use the attached files. Put the *.nbh in the same directory as the two files and then run the batch file.
thanks man,am gonna work on it right now
hey guy .. when i use the nbh extract .. there write could not open the nbh file ..
how ?? can you all please help me ??
When NBHextract extracts different parts of the ROM it creates a file called 03_OS.nb IS that just the OS with no additional software?
Want I am trying to do is make a stripped version of this ROM RUU_Kaiser_HTCASIA_WWE_3.29.707.0_radio_sign_25.83.40.02_1.65.16.25_Ship
Thanks.
Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks
As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,
Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"
Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.
Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.
Hello,
I want to (re)flash WM6.1 from microSD, but can´t find a nbh. Flashing in softmode will hang up and freezing my screen on the tricolour.
Extracting from RUU_Kaiser_HTC_GER_3.28.407.0_radio_sign_25.83.40.02_1.65.16.25_Ship.zip
will create an exe-File.
Any chance to get out a kaiserimg.nbh from the exe or any link to a german WM6.1 Rom /NBH?
Regards
Check the Kaiser Wiki instead of starting a new thread. There're repositories for many versions of OEM ROM.
Of cause I´ve done this before. But the german ROMs I´m looking for will be extracted as exe-files, I couldn´t find the necessary hints.
Try open the exe using Winzip. You might see the NBH there.
Edit: I tried running the Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe I have, it installs there should be folder containing RUU_Signed.nbh (your temp file folder?). Use this file, rename as KAISIMG.nbh and flash using SD method.
Get Uniextract, then right-click on this installshield wizard and select "Uniextract to subdir" .
Uniextract can do thousands of formats. It's nice program lol.