Database Develop

Upgrade Problems..Need Help

Hello to anyone with knowledge on this topic. I recently was upgrading to a new rom and while in the upgrade process my computer shut off and now my MDA when it turns on is showing a red, green, and blue screen and I was looking around on some way to fix this. I tried reloading the rom again and it doesnt seem to work and gets stuck at 95%. If anyone has any advice on how I can fix my MDA, it would be awesome. Thank you in advance.

The rainbow screen is the boot loader (This is a good thing ). It always helps if you tell us what numbers show up for IPL and SPL, and what error messages you get. Note that ALL roms will pause at a certain point (usually around 80% or 95%) and can look stuck / frozen for up to 10 mins (usually no more than 5 mins, but I had one that sat for well over 5 mins on 96% one time). So be patient and wait for it to finish or for an error to show up on your PC that something failed.
Since you are at the boot loader (rainbow screen), just go grab an official rom from your provider and flash that with the phone sitting at this screen (if you are CID unlocked then you can go grab any official rom, like the TMobile 2.26 Ship ROM). Once you do that, you are good to go again
If for some reason, that doesn't work (99% of the time that WILL work though), find the Wizard Love ROM and try that one as it seems to get people out of sticky situations that sometimes other roms can't get you out of (but do an official one first).

BTW: I love your username... One of my all time favorite movies... And no, I'm not the six fingered man

Thank you very much. It seems to have worked and I am back to the T-mobile 2.26 rom. I guess its all in the trial and error. Im new at this stuff and its good to know there's help. Take care my friend.

mfrazzz said:
BTW: I love your username... One of my all time favorite movies... And no, I'm not the six fingered man
Click to expand...
Click to collapse
Yeah, great movie
But, his name was Inigo not Indigo
You keep on using that word. I do not think it means what you think it means.

Indigo is one of my fav colors, I know how it is supposed to be spelled but he's quite the popular character and getting the name is tough, unless I wanted to be inigomontoya3948576849.4

Changing splash screen after the upgrade to WM5 on my SX66?

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."

Android on Wizard

I have some links to Android in case anyone wants to try it out
http://www.connect-utb.com/htcandroid/viewtopic.php?f=5&t=24&p=65#p65
I cant download right now but let's see if we can get this working on our phones

the links attached are not available

all you have to do is goto
http://www.myhtcphone.com/downloads/14-files/3-file-for-automatic-and-easy-installation
and download them direct, i found them after looking around for 5 mins I am downloading now to give it a try

It takes up all my space on my rom 38kb. Has anyone else tried it?

android
Wizard running SPC Unnamed 6.1 Alpha Preview Release rom
Installed on phone
Android starts to boot up but then just sits on white screen. No luck but was fun to try

kingdmc said:
Wizard running SPC Unnamed 6.1 Alpha Preview Release rom
Installed on phone
Android starts to boot up but then just sits on white screen. No luck but was fun to try
Click to expand...
Click to collapse
That is what I was going to install it off until I saw how much space it takes up.
It probably ran out of ram when trying to boot up. I would try and use this rom http://forum.xda-developers.com/showthread.php?t=395173

I have the last TnT and I have the White screen of death too ^^^^

Same here start to boot then a white screen, I have see earlier builds running on the Wizard though

http://www.youtube.com/watch?v=M9U-zF_6sm8&feature=related
Why cant worck on myne

has someone tryed with overclock to 220

isent there any way we can mix up Android and liniwizard somehow to make this work..im running GM v3 and ive got like only 12 MB left after almost nothing except s2u2 is installed..but i tried this on my Himalaya...it stops at loading kernel

Everybody!!!
does anybody see the htc web its amazing!!!!!! we can not have the android we need more POWER!!! that omap doesnt have.
So this thread is duplicated search for the genius one its amazing how they wants to load it, but stucks on boots... red point side by side...

I'm sad...in theory android runs on anything...seems our wizards are not included in that description....I'm hoping we can get this up and running soon...I too continue to get the white screen of death.....anyone else have any luck?...i saw someone say earlier builds worked..can we get copies of those on this thread?

kingdmc said:
Wizard running SPC Unnamed 6.1 Alpha Preview Release rom
Installed on phone
Android starts to boot up but then just sits on white screen. No luck but was fun to try
Click to expand...
Click to collapse
I would recommend a Rom that's finished
And just a bit slimmer TNT for instance the light version or J.Vd.Spanks rom.
But maybe a cleaner Rom with the files already in there should do the trick.

I was getting the white screen of death on linwizard too. Then I followed the boot instructions better. You cant have anyting running in the background and you have to put the phone in flight mode. (linwizard) I haven't tried Android yet.

thanks mr. incredible
i will try this now
Edit: don't work too...

Sorry to raise an old thread, but I am actively trying to get this too boot now. I have a little bit of android experience, so I am gonna see if I can help us out a little bit here!

Well its good to see someone trying it out wishing u the best of luck and as always i offer my services as a guine pig

Well, I feel that I am close....I have extensivly dedited the default.txt file to try and get it to boot....but still no luck. I have found however that you can indeed mix-and-match the various "distrobutions" of Android and make a semi-working version. The closest I have got to booting it is by using the zimage from the working Kaiser release, my modified default.txt, and the regular initrd-android.zip from here....it gets to the red ping pong ball, THEN the screen fades away, THEN a white scream comes up.......and then nothing. SOOOO close to booting it ain't funny! There is a guy on youtube that has done it on the Wizard, but for whatever reason he wont release his files, or tell how he did it! Heres the link to the videos=http://www.youtube.com/watch?v=iS_AmG8fCR4

actually i had seen that video before but since i havent found anyone here ( which i consider the holy grail of win mobile/HTC phones) saying they were able to do it i assumed that it might have been a fake or something
still wishing you luck again

Slow boot up : 1min48

Hi guys,
I always found that the diamond was very slow to boot up... and I just considered it a lost cause....
Just to be sure, can you confirm to me that you have the same timing during the startup ?
Once I switch on the phone, and I feel the vibration, it takes 12 seconds to go from the "HTC Diamond screen" to the "HTC Diamond w/ firmware;radio version screen", then I have to wait for 20 sec to get the Windows mobile startup animation.
So I loose 32sec at each bootup just seeing this damn black HTC Diamond screen.....
Then at around 1min10sec I can see the Start menu
and finally, at 1min48 : SPB Mobile Shell appears and I can use my phone !
(Maybe my phone is slow down a bit by fingermenu and fingermsgbox... but it is still long, don't you think ?)
Thanks for your feedback.
Btw, I had a Touch Diamond 2 in my hands yesterday, and it was much more faster (for the first screen and to reach WinMo). I've also seen he has a kind of fingermenu/fingermsgbox integrated, it is only with the new manilla or is it system wide ? (i.e. even for the WinMo menus).
My Rom is Dutty rom 5.2.20764.1.4.3_V4
my hardspl is SPL-1.40.OliNex (it is maybe because of the hardspl that I have to wait so long at the first Diamond screen).

mine is slow too, I think it's normal !
HardSPL 1.90, rom netDrg 2.8
A startup : showcase, X menu and PocketShield
but I reboot my phone only about once per week, so time to boot it's not important for me

I measured mine. Startup time is important for me as I shutdown my phone every night.
0s Start ("Vibration")
~11s Boot Loader Screen
23s htc
33s WinMo animated
38s WinMo start and a bit later "TouchFlo 3D getting started"
53s Phone is usable
For ROM version see my sig. I disabled the dialer skin and the one or other service. I'm using pBar as "task manager".

I think I'll go first with the 1.93HSPL instead of the 1.90. Based on your timing, it should help a bit.
fwmone said:
I measured mine. Startup time is important for me as I shutdown my phone every night.
0s Start ("Vibration")
~11s Boot Loader Screen
23s htc
33s WinMo animated
38s WinMo start and a bit later "TouchFlo 3D getting started"
53s Phone is usable
For ROM version see my sig. I disabled the dialer skin and the one or other service. I'm using pBar as "task manager".
Click to expand...
Click to collapse

uh oh... 1.93 is faster, that's the good news !
the bad news is : WinMo reinstalled by itself !!! Wtf ?? I thought it was just the loader !! Oo
Is it always like that when you change the hardspl ??? didn't know :|
megosu said:
I think I'll go first with the 1.93HSPL instead of the 1.90. Based on your timing, it should help a bit.
Click to expand...
Click to collapse

I absolutely don't know but when thinking about it, I had the same. After flashing 1.93, my original ROM restarted from the beginning.

Sleep of Death" on (almost) every recent custom & stock ROM

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.