Hi,
With the help from (maju) both me and my brother in-law has successful upgrade our SX66 to WM5 with the lazy version and would like to know if someone knows how to change the splash screen after the upgrade?
I don't mind the three color bands but something more attractive will be nice because before the upgrade I have installed the BA splash screen from the Standardized project and it didn't mention if that's going to work on the WM5.
If anyone know or if you have a custom splash screen wouldn't mind sharing please post.
Thanks
noyu said:
WM5 ... how to change the splash screen after the upgrade?
I don't mind the three color bands but something more attractive will be nice ...
Click to expand...
Click to collapse
Unfortunately if you want to use WM5, you'll need to live with the colour bars as your first 'splash screen' on the BA. This is because in the WM5 Kernel boot process (in the 'beta' leaked ROM build we're using), there is no support present for a splash screen.
I don't 'boot' my BA often during the week, and when I do, the reboot time is so fast now, I really couldn't care at all.
Thanks for your post!
I have a small issue:
After removal of the battery (change sim / replace battery etc) on first start up there is no radio rom in the bottom of the three color bar and I have to do a soft reset after the boot up then it will show radio rom etc and the phone will be working, otherwise without the soft set the phone will show an indicator "no network"
Is this normal or is there a way to fix it?
Thanks
noyu said:
Thanks for your post!
Click to expand...
Click to collapse
You're welcome ... (from one Canuck to another )
noyu said:
I have a small issue:
After removal of the battery (change sim / replace battery etc) on first start up there is no radio rom in the bottom of the three color bar and I have to do a soft reset after the boot up then it will show radio rom etc and the phone will be working, otherwise without the soft set the phone will show an indicator "no network"
Is this normal or is there a way to fix it?
Click to expand...
Click to collapse
My BA exhibits this exact same issue ... but only sometimes on a "full moon night", when Pluto isn't aligning with Venus nicely.
Basically, this is some kind of a startup issue in the beta ROM boot code we have to use in the BA ROM, by which the Radio ROM is sometimes not ready, and/or not initialized 100% by the time the OS is ready to start. I think that the hardware timeout is too short, but we have no ready way to fix this issue either. This will only happen from a COLD BOOT (i.e. battery dead, device completely off), and not from a reset or warm boot.
The answer as you figured out (and is on the forums here - just search!) is to simply 'reset' if you see "R.None" come up on the display, and on the second boot, everything will always work fine.
"The future is in beta, and we have to live with the bugs."
Hi Guys,
I'm using touch x ultimate on my xperia and its been amazing, but last night I had to use the soft-reset button because the HTC interface had jammed up, usually takes a few minutes but after the s-e logo showed up, it just went black. Tried for ages to make it work, nothing. I had to load up the boot-loader and update the rom, well 'update' as in re-install the same rom.
Its quite a worrying thing to happen, I lost all my data, loads of important stuff.
Just wondered if anyone else has had this problem, and If not why would it have occured!
Many thanks
Go for a change!
Hey u better go for touch it rom by itje or gtrab's 6.5 roms. Touch x ultimate is no longer updated and supported by the cook. It still has some bugs. I had to soft reset my device atleast twice a day when using touch x rom. It hangs so often. Right now im using gtrabs 6.5 rom. Until now its great. cheers!
Not sure why this occured on your device but.....It is still supported by the creator, he is just not cooking until a stable 6.5 platform comes out....ummm and if you look all (hense the hundreds of posts saying "Great rom...butttt"...lol)of the cooked roms have bugs, so if he is looking for a solution...then ask the creator of the rom...if you are worried about using a cooked rom....then the option to go back to a stock rom is always available.
Regards,
WC
Darkrider114 said:
Hey u better go for touch it rom by itje or gtrab's 6.5 roms. Touch x ultimate is no longer updated and supported by the cook. It still has some bugs. I had to soft reset my device atleast twice a day when using touch x rom. It hangs so often. Right now im using gtrabs 6.5 rom. Until now its great. cheers!
Click to expand...
Click to collapse
Hi,
same problem here, using Valkyrie Firestorm 2.1 ROM . Basically a good ROM, but since i can't trust it this will be the reason why i change the ROM again.
I use touch x 10.1 Blue and so far no problems at all. Could it be something you've installed after flashing that's caused it?
kinnyfaifai said:
I use touch x 10.1 Blue and so far no problems at all. Could it be something you've installed after flashing that's caused it?
Click to expand...
Click to collapse
I Use Firestorm since Wednesday. First Crash happened without any hint. After a normal Softreset it stuck and after a long time waiting suddenly the setup screen of windows mobile appeared.
The Second Crash was today after installing Fingerkeyboard 2.1 (wvga version) . After the konfig screen appeared the phone freezes and i had to reboot using the stylus, then Hardreset followed (and no, i did not press the two silverbuttons in the middle of the phone in addition)
btw: now, fingerkeyboard runs perfectly. I will wait and see, syncing my data all the time not to loose something.
When the Phone hardresets itself one more time, i must react. Fortunately i have vacation at the moment..
and sorry for my bad english, im from germany
Alex_de_Large said:
I Use Firestorm since Wednesday. First Crash happened without any hint. After a normal Softreset it stuck and after a long time waiting suddenly the setup screen of windows mobile appeared.
The Second Crash was today after installing Fingerkeyboard 2.1 (wvga version) . After the konfig screen appeared the phone freezes and i had to reboot using the stylus, then Hardreset followed (and no, i did not press the two silverbuttons in the middle of the phone in addition)
btw: now, fingerkeyboard runs perfectly. I will wait and see, syncing my data all the time not to loose something.
When the Phone hardresets itself one more time, i must react. Fortunately i have vacation at the moment..
and sorry for my bad english, im from germany
Click to expand...
Click to collapse
That´s exactly my problems with the Valkyrie 2.1 as well.
All I can say from my experience is this....sometimes when "beta" programs are used with other "beta" software...because in essence all of 6.5 is beta and ported from another device to work with the xperia....you will have random weirdness...things work one day...the next they don't....Yes they may look pretty and may have the latest and greatest so to speak in them, but with too many customizations,tweaks,mods....things are bound to break sooner or later....So this may be something to consider before flashing a cooked rom as opposed to sticking with a stock rom....
Regards,
WC
A few things guys...
On the old 6.1 ROM, when the TP2 was locked it automatically unlocked itself when you opened the keyboard (like it does with the stylus) but for some reason that option no longer works in 6.5. It unlocks if you take out the stylus still, but it doesn't unlock when you slide open the keyboard so any idea if there's a registry hack available?
Also, on 6.1, when the device was locked it returned to the TF3D home page whilst locking, but now it remains on the last viewed tab rather than returning home, so again, do you know if this can be rectified?
It does appear to be a lot slower than 6.1 now - using 73% resources on start-up which seems awfully high.
yes and when you get a sms when phone is locked then in 6.1 you get a red flashing led in winmobile 6.5 not.
Batterytime reduced from 2 days with 6.1 to 12 hours in winmob6.5
sometimes phone is locked at night the next morning phone is of !
when the phone is doing nothing how can the battery empty in few hours ?
oops hard reset did the job
Please use the Official 6.5 ROM thread : http://forum.xda-developers.com/showthread.php?t=570366
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.
hey guys OK this is my problem with my tp2 ever since i had install rom core cell evo 4 and switch to Energy RHODIUM 21916 Sense2.5 MaxSense, every time i start up my phone core cell evo animation pops up 1st n then energy animation starts after n it doesn't seem to be normal to do that at the time of boot up.. is there any way i can remove that?? i have also done tast29 twice n install energy back again n it doesnt go away.. any advice wat i can do? please
gisdman said:
hey guys OK this is my problem with my tp2 ever since i had install rom core cell evo 4 and switch to Energy RHODIUM 21916 Sense2.5 MaxSense, every time i start up my phone core cell evo animation pops up 1st n then energy animation starts after n it doesn't seem to be normal to do that at the time of boot up.. is there any way i can remove that?? i have also done tast29 twice n install energy back again n it doesnt go away.. any advice wat i can do? please
Click to expand...
Click to collapse
1.Task29
2.Flash Original Shipped Rom For Your TP2
3.Task29 (Yes Again)
4.Flash Energy Rom & You Should Be Good To Go
Hope This Helps!!!
thank you i will hop on it n try that..
Are there other start up images available?
Along the same lines, are there different start up or boot up images available for the TP2? I've searched a bit but not knowing exactly what this initial screen was called I had no luck with this.
I'm using a T-Mobile TP2 that has the white background with pink square and the words "stick together" on it that I'd really like to see go away. It hasn't been replaced when I've loaded the few ROMs that I've tried so far onto my TP2. So I obviously haven't tried the Core Cell ROM yet?
I've got ORD like a lot of other people here and probably will get around to trying it out one of these days.
Any suggestions?
jmpnjimbob said:
Along the same lines, are there different start up or boot up images available for the TP2? I've searched a bit but not knowing exactly what this initial screen was called I had no luck with this.
I'm using a T-Mobile TP2 that has the white background with pink square and the words "stick together" on it that I'd really like to see go away. It hasn't been replaced when I've loaded the few ROMs that I've tried so far onto my TP2. So I obviously haven't tried the Core Cell ROM yet?
I've got ORD like a lot of other people here and probably will get around to trying it out one of these days.
Any suggestions?
Click to expand...
Click to collapse
Its called the boot splash, or splash screen. So when you boot the phone, there is a splash screen, an animation, then another splash screen.
You can use Advanced Config to change the boot animation and the 2nd splash, to a .png (maybe other image formats) and .gif, respectively. But I believe the first splash (which is usually the carrier splash) can only be changed by flashing a new one using the usual RUU tool that is used when flashing a ROM, radio, or Task29. If you do a search for boot splash, you will find some different ones to flash.
original splash
i had the same problem. core splash was still there after i switched roms. this helped. connect via WMDC or active sync, unzip and run this exe. works like a charm.
Yeah, finally
Thanks.