Database Develop

boot splash image

anybody know hoe to change BOOT splash image on WM5 ?????

Hmm, I tried the solution from Buzz - but haven't worked for me. Another chance would be "Promasters Autoinstaller". A small proggi, made by a german freak. All Ext. Rom Cab's from different providers are included, but I hadn't enouth space to install the whole cab files. I'll try it maybe today evening. There are the splash images from VF, O2, T-Mob etc. included, and you can change them with only one click.

Saisoku-R said:
Hmm, I tried the solution from Buzz - but haven't worked for me. Another chance would be "Promasters Autoinstaller". A small proggi, made by a german freak. All Ext. Rom Cab's from different providers are included, but I hadn't enouth space to install the whole cab files. I'll try it maybe today evening. There are the splash images from VF, O2, T-Mob etc. included, and you can change them with only one click.
Click to expand...
Click to collapse
I've just tried this and it hasn't worked ethier.

ok :lol:
@Indra: No solution yet :lol:

fortunately the procedure from himalaya lower OS ver to wm5 is the same...maybe the old procedure of BA works...

xda2jojo said:
fortunately the procedure from himalaya lower OS ver to wm5 is the same...maybe the old procedure of BA works...
Click to expand...
Click to collapse
So your saying to try it with a wm2003 splash screen for the angel, well i can give it a try, i think i skipped this one due all the commotion of this release 8)

I tried an tried it again. but nothing worked.
But the facts for me are now:
- Splash screen is not stored in the /my documents folder like wm2003
- External rom is only 128k, and not a couple of mb's
- Himalaya Splash screens are stored on the extended rom. they still have one.
- Jasjar Splash screen heard nobody complaining, and they have also a extended rom.
So i think i downgrade this weekend back to wm2003, create a extended rom of a few mb's
going back to wm2005, make my extended rom visible and try it again, i cannot figure out another way to do it, and if it not works,

wow, that's a lot of work dude, but maybe, just maybe, the procedure for the himalaya is the same with the BA, problem is, the BA has such a small extended, unless there is way to save my sms on my phone now, I don't even want to dare to downgrade at the moment (have alot of important messages), oh well, good luck then!

8)
Thanx.,
Think that this is the common way, the already used "made" screens for hima 1.60 and already tried it again, if you are reffering to /windows directory, it is not working for me. :evil:
What rests, anybody??

Still looking,
But anybody able to find a .nb file on his system?
I searched, but was not able to find something with splash or .nb on my system,Even not after i installed a screen,.
Where the hack supposes this to be stored, or whats the possible extention for it, or can we patch something with the bootloader to fix it? buzz? mamaich? anybody?

I think we are going to have a problem with this build of WM5 as far as the splash screen is concerned - looking through the boot code it seems as though the boot screen is generated programatically reather than from a bitmap in ANY memory area (Entirely generated in the CE ROM code area rather than referring to ext rom area as there isn't one!)!
There is a lot of test code in the bootstrap area from HTC and references to other HTC devices!?! - This is definitely a work in progress rather than any kind of complete WM5 build....
Without re-writing the bootstrap code I do not think we will be seeing nice splash screens on this version of WM5 .... Lets hope HTC are still tinkering with it .... I will post the decoded nk.nbf (nk.nba) file here if anyone is brave enough to hex edit it or try to re-write the bootstrap code (then again if you can do that I'm sure you are able to do a simple decode of the rom as well)

KJAM ROM on 9100 !!!!

yes this is real.
The KJAM rom, which can be found in the FTP of this site, is working on the Qtek9100 !!!
does anyone have any thoughts about that? is this ROM a better one than the 9100? I think it is!

From what I understand, The KJAM is slower with its rom then the QTEK. Because KJAM is full of apps which might not be needed. Once those apps are removed it should be exactly the same ( are the rom version numbers not the same )
ANyone have any views on this ?

I believe the ROM dates are different, with the K-JAM being 9/16/2005 and the Qtek at 9/22/2005. I don't know the difference between the two, but I'd be interested to find out. Also, I'm still trying to find out how to change the splash screens (HTC, then i-mate) when it boots, but it's different than previous HTC models so far (not splash?.nb).
As for the apps, the difference does lie in the Extended ROM, so once you've custom-tailored that area, they should be identical.
HOWEVER, people on HowardForums are complaining about the Bluetooth in the 9100, where K-JAM users don't seem to be having an issue. I didn't check up further on this, can anyone confirm?

Would yo umind sharing information about details? How to avoid device ID error? IS there hacked exe file? I need to flash my QTEK with IMATE ROM since I think BT performance in IMATE is way better.
TIA

bt on the qtek smells

Grill! Wake up and give us a clue,please!

I did the soft reset after the WM5 setup so that the crap wouldn't install and it works great

so what did you do?
imate rom on a qtek???

i got a vender error when try to install the k-mate rom on my qtek 9100. what´s the trick, that it work without the error? please help!

nice we have to get around that.

Anyone try to place the Wizard in bootloader mode first before running the upgrade utility?
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.

BeyondtheTech said:
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.
Click to expand...
Click to collapse
This one? ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
from here: http://wiki.xda-developers.com/index.php?pagename=BA_1.42.00_Upgrade

pimbo said:
BeyondtheTech said:
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.
Click to expand...
Click to collapse
This one? ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
from here: http://wiki.xda-developers.com/index.php?pagename=BA_1.42.00_Upgrade
Click to expand...
Click to collapse
Hi,
I don't think this is the good way because I unpacked the "KJAM_WWE_ROM_1010903_104_10110_cdl_wwe_ship.exe" (rename to rar)
and I've foud the following files:
EnterBootLoader.exe
nk.nbf (74 MB)
README.doc
ROMUpdateUtility.exe
RUUGetInfo.exe
RUUResource.dll
I don't know which file have to change to "MaUpgradeUt_noID.exe".
Any idea?
THX
TB

Again, if I can find out how the NoID utility bypasses the check by comparing it with the original (does anyone have the exact file before it was hacked?), and we can compare, it'll be a start to look for similar code or text in the EXEs or DLLs of K-JAM's upgrade utility.
Find me the unmodified version of the NoID utility. Look on the FTP, and check all the other Blue Angel ROM update utility's EXE files...

thebiker said:
"KJAM_WWE_ROM_1010903_104_10110_cdl_wwe_ship.exe" (rename to rar)
and I've foud the following files:
Well
EnterBootLoader.exe
nk.nbf (74 MB)
README.doc
ROMUpdateUtility.exe
RUUGetInfo.exe
RUUResource.dll
Click to expand...
Click to collapse
Looks to me that somebody who knows howto and has this phone for testing could to edit the The ROMUpdateUtility.exe to bypass the country id errors,
And use as refference maybe the hacked no id loader for the BA.
P.s. the original MA upgrade utility should be found in the original roms from the providers of the Magician devices, we got it from them if i'm right.
Hope it helpes a bit,

I'm no developer, but this file sticks out in my mind..."RUUGetInfo.exe" If that is part of the upgrade installer then it looks to me that it is looking for the actual device ID, and it probably has to fall within a certain range to allow the upgrade to proceed. Something to the effect that each country, language or brand has a range. If your device isn't in that range, you are SOL.
With each generation they do something different, and more difficult.
Dave

i think it has to be in the ROM if not then all we have to wait for is a update from qtek and switch the nkf file

vbguru613 said:
i think it has to be in the ROM if not then all we have to wait for is a update from qtek and switch the nkf file
Click to expand...
Click to collapse
Nah, it's Much more involved than that. Just look at the process taken to develop the method to do it on the JAM, PDA2K, and so on. With each generation they make it more difficult.

Dopod 838 > K-Jam rom upgrade.. need some work
I had under my hands the Dopod 838 which is infact the cH version of the WIZARD.
I would like to load the imate K-Jam rom to the Dopod
Playing a bit with the machine, it seems that the Boot loader is actually looks like the Typhoon, the TyphoonNBFTools utility will decode the NK.NBF file but I am not sure what is the Vendor ID of the Dopod.
On top of it after altering the Languge from English to WWE and made the vendor DOPOD, the romupgrade utility reports the new version going to Prodigy and the Lang is English. it seems that although the TyphoonNBFTools was able to decode the NK.NBF, the upgrade application did not take the header information.
I did run also the Boot loader command under the MTTY (on the usb port) and command that did work for the typhoon "R2ds all" responded that I do not have the authority to dump the rom image.
Tried the command password WIZARD and although it did take it, still was not authorized to dump the rom image.
If somebody could help find a method to bypass the protection of rom , upgrade (bypass vendor , Country code...) it would be very helpfull to exchange roms.

:shock:
I've been playing with the ROMUpdateUtility.exe
Well, i've also noticed that the rom is like a typhoon rom.
Ive removed some strings to RUUGetInfo.exe(since this one seems to do the thing), but i cannot test it,
I got error 222, device not responding, (DUH, its a BA :lol
Maybe somebody can replace this file for the original in the folder and try running it. (if it passes the country id and the model no)
But it is a test, use at your own risk.
Do not blame me for anything.

WM6 is coming :)

Fasten seat belts and prepare to catch WM6 for HTC Herald

tupisdin said:
Fasten seat belts and prepare to catch WM6 for HTC Herald
Click to expand...
Click to collapse
Sure?The link?......

Please wait.

Here is Official(not hand made) Herald WM6 OS dump!!!
Please do not ask me about anything!
I will not comment anything.
http://uploaded.de/?id=zi6wyz - ROM Ver 4.12
http://uploaded.de/?id=3duxyy - flasher for SuperCID devices only
All in you hands!
Enjoy!

Why it for Artenis? = Herald? I dont belive this ones for Herald, be careful to flash.....
Also Thanks for sharing!

Sorry mistyped!

Is this WWE?
Please do not ask me about anything!
I will not comment anything.
Click to expand...
Click to collapse
Sorry I had to ask this...

Sure WWE!!!

Thanks very much for this.
I have no idea how to use this at the moment. So I will wait until the experts come online before I try flashing.

tupisdin said:
Here is Official(not hand made) Herald WM6 OS dump!!!
Please do not ask me about anything!
I will not comment anything.
http://uploaded.de/?id=zi6wyz - ROM Ver 4.12
http://uploaded.de/?id=3duxyy - flasher for SuperCID devices only
All in you hands!
Enjoy!
Click to expand...
Click to collapse
Tried flashing with the provided files, but still same old issue, RUU stops @ 2% of update... doesn't seem to be superCID...
too bad, we'll wait for HTC...

Well since my device bricked anyway i'll mess around somewhat, let's see what this ROM's got thank you for sharing But too bad this does not flash SuperCID on the device, but requires it i'll wait for the official ROM

I bit the bullet and tried but got this error:
Error 294 INVALID VENDER ID
I guess my HTC P4350 is not CID unlocked.

tupisdin said:
Here is Official(not hand made) Herald WM6 OS dump!!!
http://uploaded.de/?id=3duxyy - flasher for SuperCID devices only
All in you hands!
Enjoy!
Click to expand...
Click to collapse
Thank you. is this file complete ROM update or just OS dump prepared for flashing to SuperCID device?

Hi all,
I have just flashed this new OS from the official rom (what people call, HERA_WM6_FLASHER.rar) on my P4350. This rom is for German device, like Wing's OS. There is not big difference, this is really for Herald. The mistake is the same, there are some wrong letters on the keyboard.
You can flash the OS with Aserg' way easily. Your device does not need to be unlocked.
IT RUNS LIKE HELL! )
MS Office is included. You can take a look at the below pics.

How did you flash? did you rename the os.nb0 to os.nb and followed azergs instructions as normal?

wondering about same thing..

Well, I tried replacing the os.nb file in asergs wm6, it gave a error, but when i did a hard reset, it worked just fine btw I renamed the os.nb0 to os.nb,and then replaced asergs os.nb....
im now testing out thecabs extracted from the touch and up to now its great

OK I could extract the files of the os.nb both the XIP sections and the IMGFS.
I used the Hermes NBH tools for that (see http://wiki.xda-developers.com/index.php?pagename=Hermes_NBH).
My problem si that rdmshflsh.pl does only extract files, not modules...
I'm trying to rebuild a ROM for the Wizard with this one, but if I don't get any modules, it is ok to have only files in the IMGFS?
-eluth.

itje said:
Well, I tried replacing the os.nb file in asergs wm6, it gave a error, but when i did a hard reset, it worked just fine btw I renamed the os.nb0 to os.nb,and then replaced asergs os.nb....
im now testing out thecabs extracted from the touch and up to now its great
Click to expand...
Click to collapse
i use this way to flash my c800
and ... unlucky it's bricked
i can go into the bootloader but i can't find one RUU-ROM for my c800
i try a lot of ROMS but they take a message"XXXXXXXXX ID" CID locking
my IPL/SPL all 1.09.0001
anybody knows how to unbirck it with another way?

eluth said:
OK I could extract the files of the os.nb both the XIP sections and the IMGFS.
I used the Hermes NBH tools for that (see http://wiki.xda-developers.com/index.php?pagename=Hermes_NBH).
My problem si that rdmshflsh.pl does only extract files, not modules...
I'm trying to rebuild a ROM for the Wizard with this one, but if I don't get any modules, it is ok to have only files in the IMGFS?
-eluth.
Click to expand...
Click to collapse
Eluth, use scoter's kitchen to extract the modules. BTW, PM me if you need help with this. I've already got the OEM side of a T-Mobile wing running on my device. Runs like hell .

Sorry

I posted this for the few people that were awaiting for the Herald kitchen.
So..i know that you must probably hate me till now, but sorry again i have to delay the porting of my Core Kitchen to the Herald.
It has come to my attention that there is still no way of flashing an Terra because there is no RUU and thus no means of flashing. I will see what i can do, meanwhile i got some work and i will leave for about 5 days.
If anybody has any ideas on how to help these people, please put it into action or give me a pm.
Cheers !

you can flash using Aserg's method which is what other cooker's have resorted to!

blackout203 said:
you can flash using Aserg's method which is what other cooker's have resorted to!
Click to expand...
Click to collapse
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.

Well hopefully they roll out that new RUU for WM6 before the months end. Would love to do some experimenting with it during my vacation next month.

anichillus said:
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Click to expand...
Click to collapse
Yes that´s true. And nothing to say sorry - you had enough trouble with your PC.
But this is what I got as away for falshing from bootloader.
The problem is that the singing of the nbh file doesn´t worfk correctly - i guess.
I've been using his tool from:
http://forum.xda-developers.com/showthread.php?t=311909
He doesn't really show a method, so what I've been doing is:
1. Using NBHExtract to dump an .nbh that's on the Herald Wiki.
2. I rebuild the .nbh using Dark Simpson's little utility using the information I had luckily written down before I bricked the phone. So I plug in my ROM (4.10.531.3) in the Version, HERA110 in Device ID. The only other thing is that I'm not sure about the CID.
3. Place the new .nbh file in a folder with an updater (the ROM Update Utility that comes with the ROMs from the Herald Wiki).
4. Get the phone into Bootloader mode, start the updater.
In this way I've got rid of the Invalid Device ID error (error 243 or something?) and now it goes to 3% and tells me that the image file is corrupt.
I'm very new at this so maybe you can see a flaw in what I'm doing, or maybe with your knowledge we can figure this out. I was *almost* to the point of trying to cook using a couple links you've posted (XIP, dumps, etc) and then put it all together in a signed .nbh, but Rapidshare was holding me back... making me wait 80 minutes between downloads -_-
Anyway... I've only been trying to update the OS.nb portion since I believe I only screwed up my OS, not anything else. I can still get into the bootloader, my IPL/SPL still reads 4.xxxxxx, and by "brick" I mean that the phone just hangs on bootup at the T-Mobile splash screen. Correct? Incorrect?
Click to expand...
Click to collapse
Perhaps we can work with it.

It is not a huge problem for HTC branded devices as there is a RUU to flash with if everything goes wrong. It's just a problem for our T-Mobile Wing and O2 Terra cousins (if they brick their devices). But it's nice to see some proper chefs taking an interest, never liked the pdaviet ROMS ever since they used a whole bunch of Faria's stuff without asking.

im running pdaviet now, but im hoping to see something other soon, its not bad though, just a bit slow..lots of "lagging" on the today plugin, I used the herald dump from tupisdin earlier, and installed my fav progs on that...was pretty dam fast on my phone...only problem was that it occupied more space on the main memory when stuff was not cooked into the rom itself...
trying to learn about cooking myself, not so easy as a thought
But I guess im lucky to have a unbranded htc p4350, If i brick, I just install the official Ruu from HTC
(btw, I DO use Vista for flashing, just changed the usb driver that WMDC uses to connect via USB to the old activesync 4.5 USB driver...)

Touch-It for CID locked wings!

I have no part in any of these programs; I just put the scattered pieces together. This worked on my brand new wing without any other modifications.
The included rom is the Touch-IT for The Wing Full http://forum.xda-developers.com/showthread.php?t=332789
Download the kit at:
http://rapidshare.com/files/58874111/herald.rar.html
Disclaimer:
This is free to use but at your own risk, I take no responsibility for any conflict, fault, or damage caused to your phone by this unlocking procedure. No warranties of any kind are given. Any commercial usage prohibited.
Instructions:
1. Unzip on c:\ use a folder name with no spaces on it.
2. Connect your phone to computer, make sure activesync is enabled (green icon)
3. Run herald-uspl.exe on your computer and follow instructions on screen.
4. If you have problems, install RAPI/EnableRapi.cab on your device, and retry after.
All credit goes to POF for HERALD-USPL-beta3.zip and of course the Touch-IT team for their great rom.

What about the XDA TErra? Someone tried??

It will most likely flash, but your keyboard will probably be messed up. Just download a more correct rom and pack the os.nb into a RUU_signed.nbh with the htc rom tool (by Dark Simpson). Then replace the RUU_signed.nbh in the RUU folder with one you made.

brazen1445 said:
It will most likely flash, but your keyboard will probably be messed up. Just download a more correct rom and pack the os.nb into a RUU_signed.nbh with the htc rom tool (by Dark Simpson). Then replace the RUU_signed.nbh in the RUU folder with one you made.
Click to expand...
Click to collapse
And that is the problem for ALL Terra user. There is no ROM!!! No RUU. Nothing for unbricking the devices if something goes wrong while flashing.....
That´s the big problem for ALL XDA terra user. O2 will not release an update...

papamopps said:
And that is the problem for ALL Terra user. There is no ROM!!! No RUU. Nothing for unbricking the devices if something goes wrong while flashing.....
That´s the big problem for ALL XDA terra user. O2 will not release an update...
Click to expand...
Click to collapse
they suck, they have not heard of customer service?

what about dumping the rom? picking out the oem folder and port a herald sys folder? maybe if the rgu files are intact in the terra device, they can be used somehow put into the kichen with sys and oem? hmm, xip might be a problem though.....nah, just a brainstorm....dont think its possible.
Dam, bribe a guy from terra service, make him leak a ruu on the net

Great work ! It's running on my O2 Terra with out great problems.
1. at any Softreset it send's an SMS to an nonexisted Reciver.
I changed the Keybord to Germen with this http://wiki.xda-developers.com/index.php?pagename=Changing_Device_Language
as i sayd great work
Ghostrider

I didnt know wings came CID locked.
Actually that comment sounds kind of retarded.
Reason I say all this is because I've instaled TouchIT and all the variations just fine on my stock Wing..
Are others having problems?

itje said:
what about dumping the rom? picking out the oem folder and port a herald sys folder? maybe if the rgu files are intact in the terra device, they can be used somehow put into the kichen with sys and oem? hmm, xip might be a problem though.....nah, just a brainstorm....dont think its possible.
Dam, bribe a guy from terra service, make him leak a ruu on the net
Click to expand...
Click to collapse
Have found one. But he will not release....
Damn. He is a real insider with a stupid brain. Germans are tooooooo near to rules.
Hehee.
And btw - the first Aserg ROM ever was based on my terra dump. But without an RUU - we cannot unbricke. Believe me - i tried everything

germans invented rules

TylerC161, I guess your just lucky. When I tied to flash with Aserg's method I would get an error that said:
ERROR [294] : INVALID VENDOR ID
This Update Utility cannot be used for your PDA Phone. Please check your Upgrade Utility.
Which, from what i gather, means your phone is CID locked. A quick search showed the following threads discussing the same thing.
http://forum.xda-developers.com/showthread.php?t=310790
http://forum.xda-developers.com/showthread.php?t=331324
http://forum.xda-developers.com/showthread.php?t=331443
http://forum.xda-developers.com/showthread.php?t=321144
http://forum.xda-developers.com/showthread.php?t=316512
http://forum.xda-developers.com/showthread.php?t=311628
Using this method saves you from going to IMEI-CHECK.CO.UK and paying $40. Also you can restore your phone back to factory for warranty work if need be. Am I the only one who finds this helpful?