Changin boot splash image - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

Quick question as I know this has been covered for other devices. Is the process of changing the boot splash image the same as on devices like the universal and the wizard?
Thanks.
James

It seems from some further googling that the answer is no for the simpler solutions, but still possibly yes for the process of making your own rom with something like mkrom...

not possible yet on the Hermes, see the "rom cooking" (very experimental) method described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
and more info on NBH format:
http://wiki.xda-developers.com/index.php?pagename=Hermes_NBH

Thanks pof. Didn't find that on the wiki when I looked!

Related

Install Japanese input on a UK Tytn..

Hi!
I am thinking of upgrading to a Vodafone v1605 on Monday.. and I can see lots of information about changing languages etc... but it is getting confusing for me...
Is there are concise account on how to install Japanese on a UK Vodafone V1605?
I am new to this and only have experience with Palm PDA's. I am a bit worried about editing registeries etc..
Ofiaich
search the forum
hanmin
yes,
been there, done that.. that's why I posted.
Ofiaich
Have you read this?
http://forum.xda-developers.com/showthread.php?t=282997&highlight=
What have you read?
Hi hanmin,
thanks for your reply,
" Have you read this?
http://forum.xda-developers.com/show...997&highlight= "
Yes, I have read aquasesh's thread and also the links posted within.
I think perhaps. this thread is most useful.
http://forum.xda-developers.com/showthread.php?t=281617&page=8
and I can see these links to asukal's site.
http://www.asukal.jp/WM5/LetsJapanNo5.zip
then install this
http://www.asukal.jp/WM5/BagojsINPUT.zip
I have also read this over at Brighthand
http://forum.brighthand.com/showthread.php?t=217045
Reading all of these makes the process seem quite simple, but later on in the threads people post idffierent problems. I know it is perhaps true that they did not follow the instructions to the letter.....
I have also read this thread
http://www.aximsite.com/boards/showthread.php?t=103305&pp=20
So you see, I did use the search, but was hoping to find a summary of how to install full Japanese support, like a beginers guide.
I will read these again to try to get the process into my head. And will also read these pages thoroughly
http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
Currently I use a Tungsten T3 PDA paired to a 802SE and can see Japanese in my email, and also reply in Japanese. But my T3 's battery only lasts an hour when out and about.
I also use a Sony Vaio VGN-TX51B which has the Japanese OS but of course, it is not always convenient to carry it around.
I know very little about the TyTn and things like re-flashing roms. and am wondering whether to buy a sim free unlocked no branding TyTn or just go for a Vodafone one as my upgrade is now due.
Thanks again for your reply,
Ofiaich
Ofiaich,
Read this one if you read Japanese. It has the step by step comprehensive instruction on how to do it.
http://www.yasukawa.com/blog/archives/000297.html
Well, from my experience, Asukal's works.
http://forum.xda-developers.com/showthread.php?t=262918&highlight=
Anyway, I personally wouldn't suggest a ROM flashing for other language support unless you very much prefer having interfaces in other languages. I had my Chinese language support from Asukal, it works wonderfully. I did a beginner's guide at the Wiki under WM5.
Anyway, I'm sure you can get your stuff working. It is difficult to judge the difficulty of a certain task based on posts as many that got the thing working won't post at all. So, the success rate may be much higher than what you thought.
Anyway, Tytn or Hermes are waaaaay out my league (I'm poor), so I can't comment on which one you ought to be getting. You can look for some other thread discussing this issue.
Anyway, if you can, once you got your thing working, do a begineer's guide at the Wiki then.
Thanks harryk1372 and hanmin!
harryk1372, I will check out the link you gave now,
hanmin,
Yes, many people who have success do not post.
I did find this page just a few minutes ago,
http://www.suninet.org/japinput/_README.TXT
and deleting the _README.TXT reveals fonts, cabs and exe files.
http://www.suninet.org/japinput/
" Anyway, if you can, once you got your thing working, do a begineer's guide at the Wiki then. "
Yes, I will do !
Thanks again !
Ofiaich
ofiaich said:
Thanks harryk1372 and hanmin!
harryk1372, I will check out the link you gave now,
hanmin,
Yes, many people who have success do not post.
I did find this page just a few minutes ago,
http://www.suninet.org/japinput/_README.TXT
and deleting the _README.TXT reveals fonts, cabs and exe files.
http://www.suninet.org/japinput/
" Anyway, if you can, once you got your thing working, do a begineer's guide at the Wiki then. "
Yes, I will do !
Thanks again !
Ofiaich
Click to expand...
Click to collapse
the rough process is as follows. i think you can find details yourself.
1) override wince.nls
2) install a japanese font
3) change font registry
4) install atok for ppc (don't reboot yet)
5) install DefSipChange to change default sip from atok to something else
6) install pqzii to map a key to start ime
the key is that atok tries to become default sip after installation. when atok is the default sip, the system just gets hung up, and all you can do is hard-reset. defsipchange detects and prevents atok from becoming default, and you can choose another sip as default. english key map does not have KANJI (ime) key. pqzii is a very useful program to map the ime start function to any key.
if you wanna save disk space, i recommend you use docomo rom.
thanks qtotter!
I got the idea but need to do more serious reading, looks daunting for a beginner !
I got a chance to buy an unbranded, unlocked TyTn, or use my Vodafone upgrade and get a V1605.
Ofiaich
qtotter said:
the rough process is as follows. i think you can find details yourself.
if you wanna save disk space, i recommend you docomo rom.
Click to expand...
Click to collapse
qtotter,
i had a problem when i was experimenting the docomo rom that you can find at the wiki site. no matter how many times i tried flashing it, it stopped exactly at 47% all the time giving me an error that there is a communication error. looks like there are many of those who succeeded flashing it though. were you able to flash it?
harryk1372 said:
qtotter,
i had a problem when i was experimenting the docomo rom that you can find at the wiki site. no matter how many times i tried flashing it, it stopped exactly at 47% all the time giving me an error that there is a communication error. looks like there are many of those who succeeded flashing it though. were you able to flash it?
Click to expand...
Click to collapse
i am using docomo rom on x01ht since it does not have a sim-monitoring process although i don't want to see docomo logo everyday. i could update the rom w/o any problems, but i did not download it from here.
try to download the file from here again or look for "Herm_China.rar" (it was named like this, originally) elsewhere on the net.
and before you update the rom, be certain that your device is fully charged, that there is no anti-virus software, no screen saver, no unnecessary software running on PC, and that there is no sim or no microsd left in the device.
if you still get the same error, simply chage the cable or try on another pc.
Hi qtotter,
thanks for your reply...
i do have "Herm_China.rar" downloaded but just thought that the one uploaded here by pof is from that and is the same thing. i too didn't want to see docomo bootsplash on x01ht and flashing it was only experimental after seeing Asukal's post on his web that he succeeded flashing it on x01ht.
i personally prefer i-mate roms and i have i-mate rom flashed on my Universal although i have changed the bootsplash by following the instructions on buzzdev.net and i don't have to see i-mate logo on a Dopod device. i now have TyTN rom flashed on my x01ht as it doesn't have any brand logos other than HTC bootsplash. I'll stick with TyTN rom until someone finds the way to cook nbh roms and the way to change bootsplash and so forth.
thanks again for your advice anyways...
change bootsplash and rom cooking will be possible soon
Hi pof,
that's fantasitic. you are the man!
pof said:
change bootsplash and rom cooking will be possible soon
Click to expand...
Click to collapse
wonderful news! i really hate the docomo logo.

Custom Splash Screen ;)

Hello there,...
because several design thinks of me and also the possibility to do that know... i have made a custom splash screen for me and my tytn/hermes...
2nd cause is that the brand new htc p3300 of my friend is stolen just infront of our eyes.... and i'm sure that the phone get back to daylight in a small handy shop .... and with that costumization i think they must be very clever to reflash that... (hopefully the don't know about this forum )
in the attechment there are the 2 splash files (main + sub - not ident!! )
never mind me if it look for someone not nice about... i like it and maybe anyone too...
futureshock said:
.......2nd cause is that the brand new htc p3300 of my friend is stolen just infront of our eyes....
Click to expand...
Click to collapse
I also have thought about adding a custom splash screen, incase it is stolen. Would be even better (if....IF...the gps chip gets working) if a small app was made that can act as a homing device if it also ever gets stolen.?!?!
mrvanx said:
I also have thought about adding a custom splash screen, incase it is stolen. Would be even better (if....IF...the gps chip gets working) if a small app was made that can act as a homing device if it also ever gets stolen.?!?!
Click to expand...
Click to collapse
if the device connects to an Exchange Server 2007 or Exchange Server 2003 with SP2 they both support remote wiping which can be good
I just created a custom splash screen as well. BL 1.01 is pretty neat.
Someone point me to the utility to generate custom splashes for the Hermes (if it's out there!) as I've lost touch with the xda devs forum recently, been very busy and unable to keep up with what's going on :/
come guys, let's see some more splashscreens!
My Splash Screen
I pity the phewl that steals this pda
Mwhahahahaha
Kinda lame but still
Jules
Hi All,
I'm attempting to create a custom boot screen. Followed all the instructions in the wiki. My device has the 1.01 MFG bootloader, is SuperCID, currently with the imate rom etc etc.
Now I go ahead and enter in the commands as exactly in the wiki to change the mainsplash and subsplash with the following output (in this case the output for the subsplash):
USB>task 32
Level = 0
USB>lnb finalsplash.nb 50140000
:F=finalsplash.nb
:A=50140000
:O=00000000
:L=FFFFFFFFF
start NB image download.
Now this is all well and good, but nothing happens. It sits there for a long long time, and the result is I have to do the bad thing on shutting down mtty.exe and rebooting my hermes. What exactly am I missing?
I've checked the filename and filesize (262144 bytes) of the finalsplash.nb, all the orginal bitmaps/finalsplash.nb/splash.nb/padding.nb are there in the same folder. etc etc.
Do I have to be more patient or have I broken something somewhere, because the first time I attempted it, I got the filename wrong and typed in finalspash.nb (forgot the l), so had to disconnect the hermes and restart.
I've rebooted the device after pulling out the cable since doing the above. And it appears to be working (touch wood) still.
Thanks for you help in advance.
GeneNZ said:
Hi All,
I'm attempting to create a custom boot screen. Followed all the instructions in the wiki. My device has the 1.01 MFG bootloader, is SuperCID, currently with the imate rom etc etc.
Now I go ahead and enter in the commands as exactly in the wiki to change the mainsplash and subsplash with the following output (in this case the output for the subsplash):
USB>task 32
Level = 0
USB>lnb finalsplash.nb 50140000
:F=finalsplash.nb
:A=50140000
:O=00000000
:L=FFFFFFFFF
start NB image download.
Now this is all well and good, but nothing happens. It sits there for a long long time, and the result is I have to do the bad thing on shutting down mtty.exe and rebooting my hermes. What exactly am I missing?
I've checked the filename and filesize (262144 bytes) of the finalsplash.nb, all the orginal bitmaps/finalsplash.nb/splash.nb/padding.nb are there in the same folder. etc etc.
Do I have to be more patient or have I broken something somewhere, because the first time I attempted it, I got the filename wrong and typed in finalspash.nb (forgot the l), so had to disconnect the hermes and restart.
I've rebooted the device after pulling out the cable since doing the above. And it appears to be working (touch wood) still.
Thanks for you help in advance.
Click to expand...
Click to collapse
it should start instantlly... check that mtty is in the same folder that the .nb files are...
walshieau said:
it should start instantlly... check that mtty is in the same folder that the .nb files are...
Click to expand...
Click to collapse
All the files I used to generate the finalsplash.nb are in the same folder, including the mtty.exe. I've remade the finalsplash.nb file twice to no avail.
Any other ideas? Should something appear on the hermes bootloader screen? As nothing appears on my bootloader screen at all.
I've tried recreating the finalsplash.nb using the bitmap image directly from the HTC 1.35 Rom. Again followed the exact same steps, but no joy.
One thing I must mention however, is that I had problems starting the nb_image_converter.exe. It kept giving me an error message that the comdlg32.ocx was missing or not registered. A quite search on the forum told me to download the ocx file and place it in the same directory as the exe application, which I did so by searching google (as recommended). This started the application, but may have something to do with this failure?
Okay I sorted out the problem. Seems that the mtty.exe I was using was a strange one. Dunno where I got it from, but it didn't seem to do the job.
All I did was take the mtty.exe from the 1.0.1bootloader zip file from the wiki, and use that. Then it worked instantly.
Thanks for you help though!
i did this
Here is what I have and here is what I hope to have as soon as Kyphur and crew get done.
Well decided to give something back to the community, even though its not that major. Thought someone might want it. I've adapted these existing images from images I've found on the net (through google) and unashamedly stolen.
One of them is supposed to be hermes's (the greek god) winged helmet. Attached some previews, and the bitmap images in the zip file.
anybody tried to make animated splash screen like cingular AKU 3.3 rom?
the image is from *.gif file in %windir% and also the startup sound.
but maybe there is some engine to load the gif image and sound.
is it still related to *splash.nb ?
Hi, can anyone explain more the animated splashscreen?
i think thats not the splashscreen that we speak here about,... maybe its the windows startscreen (in test rom: green (mobile))
@ GeneNZ
velly nice...
good work.
GeneNZ said:
All I did was take the mtty.exe from the 1.0.1bootloader zip file from the wiki, and use that. Then it worked instantly.
Thanks for you help though!
Click to expand...
Click to collapse
I've found that there are 2 versions of mtty in the wiki.
One version 48 kb (version 0.01) - this is the one that stalls.
The version in the 1.0.1bootloader zip file is 56kb (version 1.11a) - this one works perfectly.
I kinda liked the AT&T logo from 2.06, so I made this for my new Xda-live install. Enjoy
I use my VJSihaya babe for my boot screen and welcome96.png screen (sorry, don't have cab to hand, but imagine this cropped to 320x240 in top right):
So the phone is booting up, and the wife wacks me on the shoulder and says "why are you looking at other girls?". Good thing she didn't look at what was on the storage card
V

How to change boot screen on HTC Iolite

I have a T4242 device. I had up a custom rom that changed my boot screen (the very first screen after boot the device). Now I want to change this to my favourite imagine. Is there any way to change it?
Can some one helps me?
Thanks in advantage.
You can not change the first boot screen as is part of rom. But you can change the welcome screen. If you mean this, you must rename your image to welcomehead.96.png and copy it to windows folder(replace the original)
Thanks for your answer. Some device have a method to change 1st splash screen like prophet, raphael, kaiser, wizards...
http://forum.xda-developers.com/showthread.php?t=284006
http://forum.xda-developers.com/showthread.php?t=431161
http://forum.xda-developers.com/showthread.php?t=334907
etc,.
Maybe Iolite has not yet got a tool like that.
Yes, I know that there are some utils solutions, and you may try. But have in mind that all cases require a flashing proccess, and not an easy replace of a device's file. I've tried a similar solution on a qtek device a long time ago, but the result was a blank screen in place of the image.
This link seems to have more posibilities to succeed:
http://forum.xda-developers.com/showthread.php?t=334907
Please give us some feedback if you were succesfull and what method used......
thanks

[Q] Can anyone make/provide Task29 for the boot splash

This question is probably for the more experienced chefs
I would like to remove (erase) the very first boot splash in my HTC Leo. I looked through the forums and found many posts which tell you how to make your own boot splash and replace the existing one, but nothing about how to completely erase the area in the rom, where the bootsplash resides. I tried to make my own "blank" nbh, which would do the trick of clearing the bits of the splash by simply overwriting them, but was unsuccessful. My expectation was that I would just make a normal splash.nbh (using nbimg.exe) and then replace the BMP image data with 0x00 or 0xFF and that would do it... Well, it didn't. I even examined the nbh from Task29 with a hex editor, but imagine my surprise, when I found out, that it is not empty at all but has a lot of stuff in it.
So I beg the experienced chefs to please make an empty/blank splash.nbh which can be used to erase the boot splash, or point me in the direction of what to read, so I can understand how to make one myself
Best regards and thank you for your help!

[Q] Another bricked Athena?

Ok, after 2 days of fighting, sweating, a pc hdd full with roms,tools,mtty,etc...
...i'm giving up. i am posting a help request for the first time since i am a xda user,
and that's been for almost 2 years now. i rather solve problems by doing research on the xda forums but this time i am out of energy.
i had an raphael before where the hacking process was pretty straightforward
and flashing a cooked rom was really idiotproof.
now i got an cool athena in my hands. i was like yeah, let's flash baby....and
the original OS didn't even last for half of a day. quick enough i realised that
this baby shouldn't be flashed the raphael way - the sd card method...
ok let's get on topic:
what i did:
flashed with the AP4 SPL 3.5 AthenaUpdater (following the howto exactly)
and well. that worked fine. the OS was booting and everything. but to my
surprise it looked like that AP4 update flash thing didn't ship another cooked
rom, but flashed my SPL only. i rather expected a SPL, CID unlock and ROM
install in one single package. i don't know what made me think that, since the
raphael has to be flashed with different stuff too before beeing able to...bla
since i was so happy to find that AP4 update howto i guess i was assuming
that this is the whole deal since it doesn't say anything about seperate CID
unlocking in that .pdf
anyway, i looked for a cooked spl 3.5 compatible rom and there i found it:
[ROM] *Updated Mar/4/2010* AGB V3.00.0 (WM6.5.5 build 23534)
and well, that was basically it. the flash went ok, but after booting only
the rom's splash screen appears and nothing further happens. hard reset
doesn't help.
i tried a few other roms after that, and again. only the rom-specific custom
flash image appears and nothing happens.
tried to flash the AP3 for SPL 3.5 ROM - same thing: flash screen says "operating system is loading", which is an bitmap picture i guess...
downgrade to SPL 1.2 doesn't seem possible since this requires a running
WM, which i don't have.
bootloader works by the way, hard reset works too, but no fix...
after a little reading i get the idea that i should have cid unlocked the device
before flashing with a cooked rom? or did i something else wrong?
any help would be appreciated
oh yeah, and mtty:
the recover from invalid id procedure doesn't fix the issue.
and:
set 14 0
task 8
doesn't fix anything too, just boots the device into the never ending flash screen....
quick questions
what does your boot screen say
and did you remove your sd and simcard before flashing
yeah, the i ofcourse removed the sd card and sim card before everything.
i am at work now but afaik my bootloader screen says:
ATHE100
IPL 2.02
SPL 3.50.Olipro
before the attempt with mtty it said
ATHE400
IPL 2.02
SPL 3.50.Olipro
something like that. is that helpful?
i'm wondering that almost nobody replies. is the athena projcet kinda dead
or am i just asking BS, i don't know. anyway, i'll keep this one posted.
i have a new status of my athena: it boots a ROM for the first time. i have flashed
it with a test rom, called:
Windows Mobile 6.1 Base ROM (Testing)
It can be found on the athena latest ROM links page.
And ofcourse there is a BUT(T)....
BUT..the configuration wizard keeps looping. Means the device boots WM6.1,
asks me to calibrate the screen. after that touchflo (or sense) shows up for a few seconds, a progress bar appears and installs some (invisible) stuff and the device reboots. Normal behaviour you'd say, but the calibration screen comes again, and the progress bar too, and reboots, and again, and again...
maybe somebody could tell me how to stop that process? it seems like the
device doesn't save the first time setup settings. how to fix it?
ultrasonyk said:
i'm wondering that almost nobody replies. is the athena projcet kinda dead
or am i just asking BS, i don't know. anyway, i'll keep this one posted.
i have a new status of my athena: it boots a ROM for the first time. i have flashed
it with a test rom, called:
Windows Mobile 6.1 Base ROM (Testing)
It can be found on the athena latest ROM links page.
And ofcourse there is a BUT(T)....
BUT..the configuration wizard keeps looping. Means the device boots WM6.1,
asks me to calibrate the screen. after that touchflo (or sense) shows up for a few seconds, a progress bar appears and installs some (invisible) stuff and the device reboots. Normal behaviour you'd say, but the calibration screen comes again, and the progress bar too, and reboots, and again, and again...
maybe somebody could tell me how to stop that process? it seems like the
device doesn't save the first time setup settings. how to fix it?
Click to expand...
Click to collapse
Hi mate
I live in a different time zone and my daily email about updates to posts comes late in my day and probably when you sleep.
There are not many people who use this device and it is really a legacy machine.
However your post gives a clue to what happened.
with the bootscreen showing athe400 initially are you sure you have an x7500/x7501 or is it the x7510?
Just make sure before you follow the solution in this thread
http://forum.xda-developers.com/showthread.php?t=387596&highlight=endless+loop
the roms are very different
Check out exactly which hardware you have
this thread is from the x7510 thread and may be worth a read if you have the x7510
Additionally cmonex has the knowlege to fix your issuues if the above doesn,t work
http://forum.xda-developers.com/showthread.php?t=441684
thank god, somebody replied with useful information
well, i must be honest i didn't pay too much attention on the model number.
after reading your post, i checked and i see that i have a X7510 advantage device.
which means as far as i can understand it:
i SHOULD have the modelid ATHE400?
which means, i messed it up by flashing it with mtty to modelID ATHE100?
which means, all the time i was installing X7500 stuff on the wrong device
and bricked it that way?
so the AP4 3.5 SPL solution is not for X7510?
which means, the AP4 3.5 SPL is a hard SPL but for another device?
and after all, what do you suggest? do i need to revert my modelID
to ATHE400 and if yes, how? and after that i should follow the 2nd
thread to install a proper hardSPL and a WM6.5 ROM of my choice?
try contacting cmonex
the author of this thread
http://forum.xda-developers.com/showthread.php?t=441684
wrote the script you used to change the device id and may have a way to reverse this
good luck
lakeman, my friend!
you pointed me to the right direction. i followed the steps for installing
hardspl for x7510 from cmonex, and yeah, the modelid changed back
to athe400 and the device was booting! seems like that hardspl also
corrects the modelid automatically.
i am still curious why the device was working after flashing with AP4 3.5 SPL
in first place, since that one is actually for X7500 devices.
i should 've read some more before going to flash that thing, i must admit.
many thanks to you lakeman, and big ups for that cmonex guy!
now it's time to look for a nice wm6.5 rom for my ATHE400
fantastic
happy to help

Categories

Resources