Related
I've tried the MDA3Changer and that amazing program Promasters Autoinstaller 1.5 that changes bootloaders too, and what I found out is during the installation *.cab boot loading changer process it stops, and if you bring down your keyboard and hit enter, it says something like dsk1 cant find or something, so obviously the Splash image is on your Rom or EXT Rom, we need an application for WM2005 that actually unlocks it so we can change it!
Hi there,
I've unhided my 128k rom i can see it during installs where to install the file, (option to install on extrom)
i do not know as we increase the size of the rom it shall work??(reverting back to wm2003)
But generally the bootscreen is around 300kb
They say that the images are located somewhere else in the system.
What can we do to solve this, i really dont know.
WRONG!!!!
MDAIII application puts splash1 and splash2 in my documents :lol:
hdubli said:
WRONG!!!!
MDAIII application puts splash1 and splash2 in my documents :lol:
Click to expand...
Click to collapse
For wm2003 yes, for himalaya wm2005 it sees to me they do it on the extrom and for us on wm2005 somewhere else? any hints if maybe the extention is changed or the location? how can i find that out?
quote from Mamaich:
wm2005 unlock tool is not needed. Extrom is already unlocked. But all programs that change boot image would not work. It seems that bootlogo is stored in the different place on BA's WM5.
Click to expand...
Click to collapse
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
2nd STEP: You need to get a hold of the ROM file so you can extract the necessary files from it. This is provided by the phone manufacturer.
****To extract the file, someone recomended WinRAR. If you don't have it, follow this: Go to
My Computer
Your Drive (mine is Drive C: )
Show the contents of this drive
Documents and Settings
Choose your folder name
Local Settings
Look for the "Temp" Folder
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
3rd STEP: You need to extract the following files namely and add the MaUpgradeUt_NoID.exe File. These 10 files are found in one of the folders within the "TEMP" folder after running the file you got from Step 2.
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
*****You need these 11 files if you want to upgrade the ENTIRE ROM.
*****If you only want to upgrade to the RADIO VERSION then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf". So there are 9 files on it.
NOTE: The "TEMP" folder has many folders within it. It is your job to look which folder was created upon running the .exe file from step 2. You need to copy those 10 files and paste them on a new folder.
4th STEP: After gathering the necessary files and choosing which part you want to upgrade and keep, you need to put your device to boot loader mode by pressing 3 buttons simultaneously:
Power Button
Backlight Button
Reset Pin
5th STEP: Plug your Universal via USB. Wait for your computer to recognize a newly plugged device.
6th STEP: Now you are ready to upgrade. Double click the MaUpgradeUt_NoID.exe File to run it and follow the on screen instructions.
Hope this helps. Good luck.
Hi...
Nice guide indeed..but u forgot one important step....that is hard resetting after the complete upgrade... :lol:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Thanks for the input guys. I also remember, I did not perform a hard reset myself, just a soft reset at the end. But I choose not to include that on the steps as the computer will show a window as to what you're supposed to do or press during the upgrade anyway.
great post!
AG
radio version? Windows Mobile version? and EXT Rom?
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Re: radio version? Windows Mobile version? and EXT Rom?
tmglobe2004 said:
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Click to expand...
Click to collapse
I have tried all ROMs that came out on this site. The ones I recommend are only 2:
1st: QTEK's latest ROM
2nd: JWright's Modified ROM
From my post above these 3 files determine which part you want to upgrade:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
If you look at my signature below. I am using TMobile's Radio while using JWright's Modified ROM. It all depends on you which combination you feel is more stable. On my Universal, I never had any troble no matter what ROM I used, but these 2 I listed above surpasses any ROM released by other manufacturers on my opinion.
Pantaloonie said:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Click to expand...
Click to collapse
Yeah I heard the same thing, I did a soft reset after installation and it worked fine.
error 120 country id
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
artcsmota said:
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
Click to expand...
Click to collapse
What 3 files? If you are referring to the .nbf files, none of them are responsible. Follow the instructions above and keep repeating them, sometimes it takes more than one try for the Error 120 to disappear according to some who experienced it.
cktlcmd said:
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
Click to expand...
Click to collapse
A great post, Upgraded my O2 Exec using your procedure, worked a treat, Thank you!
Wooky
cktlcmd said:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
Click to expand...
Click to collapse
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
resetting
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
xiasma said:
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
Click to expand...
Click to collapse
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
mavrik64 said:
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
Click to expand...
Click to collapse
YES, if you perform a hard reset. The new upgraded ROM will be the default ROM restored on your device.
cktlcmd said:
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
Click to expand...
Click to collapse
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
I've now ran the T-mobile ext ROM upgrade, hard reset.
When the \extrom autoruns, should I just select T Mobile UK? Or cancel?
xiasma said:
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
Click to expand...
Click to collapse
I think you are doing what I was when it finaly clicked.
By the way, thanks to cktlcmd for the breakdown of the process.
The bit you will need to understand is that when you run the .exe, it unpacks the files into a folder in the Temp directory cktlcmd mentions. All i did then was to search for one of the files listed and i found the folder that way. I then copied the files into a more convinient folder and added the MAUpgrade as per the instructions. Once i did this, running the MAUpgrade does as described.
I know this may seem a bit long winded, but I got there in the end. Also, by saving the contents of the folder elsesware means I can play with it later as also discribed by cktlcmd.
The JASJAR rom is sofar great.
Thanks for all your hard work cktlcmd
regards
Mav
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
fuhayer said:
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
Click to expand...
Click to collapse
Have you tried my instructions yet? Try downloading the files again. Sometimes they get corrupted.
it is fixed by flashing with original t-mobile 1.30.232 rom.
but when i flash ivanb14 it is again freezing at 19% of stage3.
what can be the problem ? i have downloaded the ivanb14 rom 3 times and i receive the same error message.
im using a tytn and getting errore message
dows the official upgrade is for tytn or doopod ?
anyone can help ??
i try using hard sspl and still .. same
I think it may be because it is a rom for Asian networks... I got a similar error, and will have to manually import the settings for my network providor... other than that, everything else went fine...
I believe there are cabs kicking about this forum to auto setup for various providors.. I think it is trying to auto detect your vendor, and if not Asian, is returning the error
I think thats all the error is showing...
If you've downloaded one of the other cooked ROMs on this site, you should have an exe file called RUU_wrapper.exe.
Now, install WINRAR and right click on the dopod rom and choose extract and it will extract various files, one of which will be another exe file. Extract this exe file again and you should end up with a file RUU_Signed.nbh - this is th only file you'll need out of the lot.
You can delete all the other files from the dopod ROM now, just keeping the RUU_signed.nbh. Copy the RUU_wrapper.exe file into the same folder and run it and you will flash the dopod rom to your phone nicely - just make sure you're HARDSPL first!
Now, you could be even smarter at this point and use dutty's good nbhtool if you like to "unwrap" RUU_signed file and remove the IPL \ SPL (though with HARDSPL, I'm not sure this is necessary) and the Radio part if you like (and the boot splash screens if you're so inclined and then use it to wrap it all back up again.
HTH,
Smiffy.
Does someone have the original htc animated startup image? I've searched for all the forum but nothing!Can someone help me?
Thanks a lot
delivery1979 said:
Does someone have the original htc animated startup image? I've searched for all the forum but nothing!Can someone help me?
Thanks a lot
Click to expand...
Click to collapse
i think you search this...
thanks a lot brain!
what does this .gif do? it's just a black screen with no animation when i put that in my browser?
sfaguy said:
what does this .gif do? it's just a black screen with no animation when i put that in my browser?
Click to expand...
Click to collapse
this gif is the animated splash screen when you turn on your trinity
put in windows folder
brain_81 said:
this gif is the animated splash screen when you turn on your trinity
put in windows folder
Click to expand...
Click to collapse
It works by just putting it in the Windows folder, with the original name: HTC.gif?
Also, I have WM6 on my Trinity, does it still work with this operating system?
tnyynt said:
It works by just putting it in the Windows folder, with the original name: HTC.gif?
Also, I have WM6 on my Trinity, does it still work with this operating system?
Click to expand...
Click to collapse
yes, work with WM6 only put in windows directory with original name
download and open but got file corrupted error
CryptXus said:
download and open but got file corrupted error
Click to expand...
Click to collapse
Open with WinRAR!
Htc Splash
I am looking for the HTC second splash screen and sound file. I just flashed the HTC splash I got from Schaps over my AT&T build the first HTC screen comes up fine then that AT&T 5 bars with 3g I can't stand comes up . I want the HTC one where the HTC icon dances and there is a sound like a door bell, Does any one here have that .gif and .wav file I can just copy to windows and edit reg file.
Original boot screens needed
I was wondering: is there somewhere around or could someone make a ROM update utility (or another alternative way) containing only the default white HTC and the default Windows Mobile 6 boot/splash screens to use with Trinity already having cooked WM6 ROM installed?
Disregard that:
http://forum.xda-developers.com/showthread.php?t=341817
brain_81 said:
yes, work with WM6 only put in windows directory with original name
Click to expand...
Click to collapse
i can't put the file in the window folder, it says it's write protected. how do i get around this?
sfaguy said:
i can't put the file in the window folder, it says it's write protected. how do i get around this?
Click to expand...
Click to collapse
try with resco file expl
tnyynt said:
I was wondering: is there somewhere around or could someone make a ROM update utility (or another alternative way) containing only the default white HTC and the default Windows Mobile 6 boot/splash screens to use with Trinity already having cooked WM6 ROM installed?
Click to expand...
Click to collapse
windows mobile boot screen is welcomehead96.png , no flash need, simply replace file with original
download screenshot in jpg\png format (original WM6, original HTC withe, HTC animated)
http://rapidshare.com/files/68253041/boot.rar.html
i try to create only rupgradeutility with only splashscreen but when i start upgrade my device brick!! device formatted....lucky olipro
saveme....if dont have olipro my device now is bricked forever...with olipro i can instal roms and now all right...my suggest...install OLIPRO!!! thanks olipro you have saved my device again
brain_81 said:
windows mobile boot screen is welcomehead96.png , no flash need, simply replace file with original
download screenshot in jpg\png format (original WM6, original HTC withe, HTC animated)
http://rapidshare.com/files/68253041/boot.rar.html
i try to create only rupgradeutility with only splashscreen but when i start upgrade my device brick!! device formatted....lucky olipro
saveme....if dont have olipro my device now is bricked forever...with olipro i can instal roms and now all right...my suggest...install OLIPRO!!! thanks olipro you have saved my device again
Click to expand...
Click to collapse
Done: http://forum.xda-developers.com/showthread.php?t=341817
Has anyone been able to customize the welcome screen of WM6 or WM5?
Or anyone has got some suggestions on this issue?
Regards,
Hassan
Hassan101 said:
Has anyone been able to customize the welcome screen of WM6 or WM5?
Or anyone has got some suggestions on this issue?
Regards,
Hassan
Click to expand...
Click to collapse
If you look a bit further down this section you may find what you're looking for.
Jay
responderman said:
If you look a bit further down this section you may find what you're looking for.
Jay
Click to expand...
Click to collapse
Thanks a lot but the issue u r pointing at is about the boot splash and I want to change the welcome screen (green wm6 spash).
Any clue
You need to overwrite the Welcomehead.192.png in Windows\ with yours one.
Try search more on the forum!
unapproachable2kx said:
You need to overwrite the Welcomehead.192.png in Windows\ with yours one.
Try search more on the forum!
Click to expand...
Click to collapse
Wow ! .. Its all DONE !!!
I Reallyyyyyy appreciate ur help !!!
Regards
Your solution works, but look, there are 2 splash screens, that you talks are the second one, how i change the first?
gajodafeira said:
Your solution works, but look, there are 2 splash screens, that you talks are the second one, how i change the first?
Click to expand...
Click to collapse
Ah, on most HTC devices I've used the welcome screen is not the same as the splash screen and I think that might be the problem here. The welcomhead file is your welcome screen and easily replaced in your kitchen, but the splash screens (2 of, although sometimes seems like 1 as they might be identical) are installed as part of your ROM.
When you use get to the point in a kitchen of having an OS.nb or Windows.nb or however it's phrased, and you're ready to turn this into a full ROM file, you can add in other things like the IPL, SPL, 1st and 2nd splash screens, radio and extended ROM, each of which has its own .nb file.
Welcomehead is easy to change. The splash screens aren't hard to change and you should find instructions somewhere in any kitchen manual probably. Haven't time to look for you now though, you'll have to scan about in any kitchen-related docs or web pages you have or know of.
chunkymonkey said:
Ah, on most HTC devices I've used the welcome screen is not the same as the splash screen and I think that might be the problem here. The welcomhead file is your welcome screen and easily replaced in your kitchen, but the splash screens (2 of, although sometimes seems like 1 as they might be identical) are installed as part of your ROM.
When you use get to the point in a kitchen of having an OS.nb or Windows.nb or however it's phrased, and you're ready to turn this into a full ROM file, you can add in other things like the IPL, SPL, 1st and 2nd splash screens, radio and extended ROM, each of which has its own .nb file.
Welcomehead is easy to change. The splash screens aren't hard to change and you should find instructions somewhere in any kitchen manual probably. Haven't time to look for you now though, you'll have to scan about in any kitchen-related docs or web pages you have or know of.
Click to expand...
Click to collapse
When i changed for wm6 the rom changed the 1st and the second splash. I changed again into the 6.1 and only the 2nd was changed, so i think that the 1st aren't directly connected to the ROM.
gajodafeira said:
When i changed for wm6 the rom changed the 1st and the second splash. I changed again into the 6.1 and only the 2nd was changed, so i think that the 1st aren't directly connected to the ROM.
Click to expand...
Click to collapse
It just depends on whether the ROM you install happens to come with 1 or 2 or no splashscreens. There's a splash1.nb and splash2.nb (might be slightly different names to that but will be similar) in a full, original ROM - and a radio, IPL, SPL and Ext-ROM too. Each has its own .nb file. (The names of them vary a bit between devices but they're pretty much always easily-recognised.)
Cooked ROMs usually are OS-only, and only made from an OS.nb (or Windows.nb sometimes - you could actually call it anything and still use it). Sometimes however, someone bundles a splash1 or a splash2 with it or both. You could install a ROM and find no splashscreens change afterward - which is usually the case. Whenever I download a ROM and it comes with a splashscreen, I almost always break the ROM down into it's .nb files and then put it back without the splash1 or splash 2 in it.
If you have a go with any ROM using HyperCore you'll find ROMs with 1 splashscreen have 1 .nb file relating to splashscreen and ROMs with 2 splashscreens (or a splashscreen which apears to last ages, which is just identical splashscreens) have 2 .nb files relating to splashscreens.
I don't think not having splashscreens saves any space though as I'm fairly sure that the space is essentially allocated to the relevant .nb files (for splashscreens they're 256k each, the nb files, even if the picture you used was 1 0.5k black mono pic).
Learning to use HyperCore obliquely taught me and many others a fair bit about how these things tick. Not a techie, mind - just done a lot of phone flashing. It's brilliant.
By way of example, here's the .nb file-list from an official (OrangeUK) Hermes ROM. (The basic format is generally the same between devices, even if the names alter - it just happens to be the most recent ROM I broke up in this way and still have the files to list for you.)
RUU_Signed.nbh is the file one would flash. This is made up from:
Windows.nb
Herm_ExtendedRom.nb
IPL.nb
Radio.nb
PrimarySplash.nb
SecondarySplash.nb
SPL.nb
The format doesn't change much between most devices, even if the names change.
I used to have a tool (can't remember who made it) for creating the .nb files for splashscreens. If I find it I'll attach it.
chunkymonkey said:
I used to have a tool (can't remember who made it) for creating the .nb files for splashscreens. If I find it I'll attach it.
Click to expand...
Click to collapse
I think this is what you were looking for:
http://forum.xda-developers.com/showthread.php?t=317436
However, would you mind helping me with something? How in the world did you split the nk.nbf into Windows.nb, IPL.nb, PrimarySplash.nb, SecondarySplash.nb and SPL.nb?
Aaaany help would be muuuuch appriciated.
(and yea, I have hypercore and I'm too stupid to understand how to make use of it )
Verbato said:
I think this is what you were looking for:
http://forum.xda-developers.com/showthread.php?t=317436
However, would you mind helping me with something? How in the world did you split the nk.nbf into Windows.nb, IPL.nb, PrimarySplash.nb, SecondarySplash.nb and SPL.nb?
Aaaany help would be muuuuch appriciated.
(and yea, I have hypercore and I'm too stupid to understand how to make use of it )
Click to expand...
Click to collapse
Good news is you're okay with this already if you've got hypercore. Duttythroy's made a genius tool for it, appropriately entitled Dutty's Good NBH Tool. It splits .nbh files into the .nb files that comprise it, and that tool is in your hypercore.
It's also in just about every kitchen. Definitley on your hard drive somehere. Just use the page that disassembles (not in the programmer's sense) an .nbh file, not the page that puts one back together form the parts we've been talking about.
Good spot on Oli's tool, but it was another one. Had a very simple interface 1-click interface. Wish I could remember whose it was now 'cause I definitely don't have it any more. (Unfortunately, my external HDD went down recently and took ... well, everything with it from the last, ooh, 12 or 13 years. And yes I did have a backup: that was it; the proper HDD went down a few months earlier and, like a complete tool, I left it till the backup died before replacing it.)
EDIT: here it is, to save you searching mate.
Thanks
Uhm... Yea, I've been on the "right path" for so long, I have HypeCor, L26.v7, Helmi kitch r0... and I still haven't figured out how to make anything from the nk.nbf-file.
Reading a bit I thought typho5 would -x it into an nbh-file. No such luck. Just died on me telling me the .nbf-file has an "unknown header format".
I've even tried dumping from the phone with some "grab-it"-program.
http://forum.xda-developers.com/showthread.php?t=238945
It works, it spits out something. But what it is, what format etc I am unsure of.
Heeelp!
I am totally lost here...
Verbato said:
Thanks
Uhm... Yea, I've been on the "right path" for so long, I have HypeCor, L26.v7, Helmi kitch r0... and I still haven't figured out how to make anything from the nk.nbf-file.
Reading a bit I thought typho5 would -x it into an nbh-file. No such luck. Just died on me telling me the .nbf-file has an "unknown header format".
I've even tried dumping from the phone with some "grab-it"-program.
http://forum.xda-developers.com/showthread.php?t=238945
It works, it spits out something. But what it is, what format etc I am unsure of.
Heeelp!
I am totally lost here...
Click to expand...
Click to collapse
Ooh, I wouldn't go messing with that just now. If all you want is to take an .nbh file and break it up into the various .nb files, just run dutty's tool, browse to your nbh file and go. it'll dump all he .nb files in no time at all, maybe less.
If that's not what you're trying to do then I'm barking up the wrong tree and therefore not helping, but if that's the case just re-explain your needs and I'll have another go.
chunkymonkey said:
Ooh, I wouldn't go messing with that just now.
Click to expand...
Click to collapse
Oooohh... I love to mess around
Okay, exact mess I want to get my self in to:
swat4 was as kind as to drop a WM5-image with sdhc-drivers. I want to take out those .dll-files and add them to another image. Namely Helmi_UNI_AKU3.5_v1.3.1.
But so far all I have is this nk.nbf-image. That, and I found this grab-it-tool, which copys the roms image straight over to SD-card in raw format.
Hmmm... Any hints to point me in some general direction as to what to do next?
Verbato said:
Oooohh... I love to mess around
Okay, exact mess I want to get my self in to:
swat4 was as kind as to drop a WM5-image with sdhc-drivers. I want to take out those .dll-files and add them to another image. Namely Helmi_UNI_AKU3.5_v1.3.1.
But so far all I have is this nk.nbf-image. That, and I found this grab-it-tool, which copys the roms image straight over to SD-card in raw format.
Hmmm... Any hints to point me in some general direction as to what to do next?
Click to expand...
Click to collapse
Righto.
If I was trying to add SDHC drivers to a ROM that didn't have them already, I think I'd be using HyperCore to turn the nbh of that ROM into .nb files and then into the series structured files and folders that kitchens usually use, OEM, SYS, ROM, etc., and then just adding an SDHC OEM. After which HyperCore becomes very similar to most kitchens.
OR I'd be just popping a line into the preconfig file if there is one, such as "CAB: /Windows/SDHC_drivers_that_I_wish_were_already_included_in_this_ROM.CAB" for example and letting it install as a cab at the preconfig stage instead of an OEM. (I'm a big preconfig fan.)
Might be quicker to use a kitchen from scratch than HyperCore to edit a pre-existing ROM though.
Hey, wow, thanks for all your help!
I still don't understand how to make an .nbh-file out of an .nbf-file though.
However I've tried copying sdbus.dll, SDHC.dll and SDMemory.dll to /Windows on the device, like I was recommended by someone else.
All that did was make my sdhc dissapear. No luck there.
I'm so frustrated, just looks like getting a proper WM5-image to work with >4G sdhc isn't feasible. Or at least, not for now.
Which is so frustrating, since there is one that does work. Gnh!
However, thanks for your time. I appriciate it.
I use this one
Try the linked one. Easy to use, I find it somewhere here.
http://zolee-ka.uw.hu/CreateBootScreenPackage.rar
And here's an alternative one - the one I was referring to earlier. By a mad coincidence, I just came across this when I was looking for someting else entirely.