Serious Graphics Error - Touch HD Windows Mobile ROM Development

Hi all,
I suppose I've got a problem here. After having flashed different working versions/ROMs (with USPL), my phone started to hang during the boot-ups on a ROM working for 5 days. (A part of the problem may be CLEANRAM level 2, it deleted some essential files). A couple of hard-resets didn't solve the problem so I flashed the latest working ROM again (a XT 21884). Suddenly during boot-up the following happened and still happens:
- "smart mobility" is okay, in white
- The second screen "smart mobility" with the R, G, D information has the wrong colour. White is blue and R, G, D is orange instead of red
- windows itself looks like with about 4 bits of colour.
Hard-resets, re-flashing the ROM or flashing any other ROM didn't solve the problem. Flashing the WM 6.1 stock ROM solves the problem and works, but flashing any other version afterwards still produces the broken graphics.
Now I realised that even changing the SPL from stock 1.14.0000 to 1.54.0000 produces the error - so my normal stock WM 6.1 ROM has broken graphics.
Does anybody know a similar problem? Did I manage to damage the hardware somehow?

cleanram does not delete any file...
it just switchs off some running programs...
try to go back to an original rom and send it to htc for a revision...
you can also try several hard resets and see what happens...

If you have a stock wm 6.1 with spl 1.14.0000, changing the spl to 1.54.0000 will give you strange colours. The reason is that the rom and spl versions need to "match".
As to the rest of the problem, I'm not sure why the graphics would go wonky on roms that have been working to date. You say you used uspl, so I presume that you followed the steps correctly and first upgraded your spl to 1.54.0000 and the used uspl to flash your cooked roms, and that the colours were all okay previously. If that's the case you probably have some technical hardware related problem. So the best advice is to flash back to stock rom, radio and spl and take your device in for service.

I agree with ClydeB1 above to a certain extent. It sounds like mismatching rom and spl versions. I don't however think its a hardware issue. If you match your SPL & rom version as you appeared to do when you flashed back to wm6.1 the colour/graphic issues disappeared.
Follow this guide and check your SPL at each stage to ensure it is correct

Related

Flickering screen after ROM update

I recently upgraded to the official 1.93 WWE ROM (and new hard SPL), and now my screen flickers a lot when the phone is switched on. (The flickering starts at boot-up when the red writing appears at the bottom-right of the screen).
I have been able to solve it so far by pressing the power button twice to switch the display off and back on again, but wondered if anyone else had experienced this and could suggest a more permanent fix?
Thanks,
Neil
Most likely who hasnt experienced this.....lol
Anyway, when you get this after a reset, just turn on and off the display and all goes back to normal.
You need to flash another hard spl. The issue is caused by an outdated spl not being compatible to your lcd screen. Try hard spl 1.37 found here:
http://forum.xda-developers.com/showthread.php?t=400950
I want to flash
_QMR_RUU_Diamond_HTC_WWE_1.93.405.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
to my UK Vodafone Diamond which has SPL 1.37 from the factory.
Which Hard SPL should I use - 1.37? Signed or unsigned?
djvw said:
You need to flash another hard spl. The issue is caused by an outdated spl not being compatible to your lcd screen. Try hard spl 1.37 found here:
http://forum.xda-developers.com/showthread.php?t=400950
Click to expand...
Click to collapse
Thanks! I tried searching for "flicker", but got too many results and didn't find that thread.
i have the flickering screen too, i want to try this method but my activesync does not work. i try a hard-reset and now the device ask me to insert Getting STarted Disc to install synchronization software which I did. it still doesn't work. anyway to do this?
Thanks
i have the same problem i flashed the 1.93 hard SPL and still nothin... anyone know the problem?
i did managed to get the flikering out... flashed hard spl 1.38!
I want to try flash HardSPL but my USB port doesn't work, is there anyway to do this?

Corrupt HD?

Hi,
I've just upgraded to a new Dutch rom, but since then I only have trouble.
I get different colours (like drivers are not loaded), it keeps getting stuck or resets itself, and nothing helps.
I've tried to put on a different rom, with succes, but I still have the same problems.
On startup, however, I see the right colours.
I also put back the latest original ROM, but no luck...
Can anybody help me?
guessing you have hspl 1.14 installed
Yeah, I reinstalled that, as one of the latest things I did.
The problem you describe happens when you flash a 1.56 based rom with 1.14 HSPL. First flash a stock 1.56 ROM (a new SPL is then flashed as well) or use the new HSPL. Then you should be fine. So no, it's nor corrupt!
For more info, read crackwhore's guide (sticky)
Well, I'm trying to do so now, but it keeps getting stuck at 0%...
Does it matter I have an NLD-version, and not a WWE?
Update: I cannot get a proper connection via activesync, and through the bootloader it stays at 0%, and after a while the update utility says no.
Update 2: ah, thanks to troubleshooting, it looks fine!
THANKS!

Potentially Broken T.HD - Need help!

Hi All,
I have used the search function - but ended up getting confused.
I have a Touch HD that I bought in January of this year (2009) from Mobiles.co.uk (Carphone Warehouse) and is on the O2 network (UK).
I have been using Dutty's ROMs (both 6.1 and 6.5) for months now - and have always used USPL when flashing, using the SD card method.
Over the past 3 days, my HD has been playing up.
When it started, I was using Dutty's R7. The radio was 1.14.something.something. The device was working perfectly, and I was really happy with the ROM and the way the phone was working. I had installed NO other applications with the exception of a different taskbar and obviously SDKCerts.cab
First of all, HTC Sense stopped working - it would cycle between "Loading HTC Sense" and "Tap here to launch HTC Sense"
Then, when rebooting the device, it just hung on the "Smart Mobility" screen. I left it in case it just needed a while to boot, but nothing.
I had no other option than to hard reset.
It worked OK for a few hours, but then HTC Sense started to crash again. So I flashed a new ROM - Lost in Asia or whatever it is called.
Same symptoms.
I flashed Dutty's R7 back and also the new 1.17 radio.
No joy.
The phone also hangs for ages on the Smart Mobility screen - perhaps a full minute where as before, it used to be no more than 15 seconds or so.
The following is displayed on the "Smart Mobility Screen"
1.17.25.09
52.69.25.37H
1.59.Dutty
The bootloader screen (before running USPL) shows the following:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) V6
So the question I'm asking - is... Is my phone suffering some kind of hardware malfunction, or is this a known and fixable fault that I somehow have caused?
If the phone looks like it is malfunctioning, how would I go about returning it to stock so that the CPWH repair centre do not know it's had an unofficial ROM installed?
I'd like to add that whilst I'm very PC literate, I'm no programmer and a lot of the stuff here is alien to me hence my confusion - I just know how to flash a new ROM etc.
Thanks to anyone that takes the time to help me - I'd be really thankful to anyone that helps me sort this - be it tell me how to fix the device, or tells me to take it back!
Thanks in advance & Regards,
Chris.
Will D/L and flash Dutty's R0 Holy Grail ROM and see if that makes a difference...
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
a1gp said:
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
Click to expand...
Click to collapse
Thanks for the quick reply.
So is it perhaps better to revert to the original ROM before flashing a cooked ROM? I always Hard Reset twice after flashing as understand this helps.
OK - so the 1.56+ situation - I was under the impression that using the latest USPL (2.5) when flashing was OK? I have never had the colour problem... but perhaps if I'm flashing wrong then these problems could be to do with this?
Thanks again...
Chris
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
mcdull said:
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Click to expand...
Click to collapse
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
a1gp said:
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
Click to expand...
Click to collapse
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
constablechris said:
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
Click to expand...
Click to collapse
what do you mean hang for age?
1 minute is nothing if it turns out boot up.
There are chances that the nand flash needs to refresh and wasted some times. But it won't be forever.
constablechris said:
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
Click to expand...
Click to collapse
there's an original rom on htc.com for blackstone just use that one.
hope it will turn out right for you
I thought I'm the only one who had this problem. Last Sunday my blackstone started to freeze on the smart mobility screen too. I flash 3 different roms because I thought its an rom issue with no luck. On Monday it even managed to hardreset itself after I waited for about 15 min in the smart mobility screen.
After that I flashed a stock rom and it seem to be fine by now.
But now I will flash a custom again, the stock one is so 6.1

Change from Orange UK 1.59 ROM back to a generic HTC ROM

Hello all,
I've been searching non-stop now for over a month, and this is stressing me out. I cannot find any solution, so before I'm criticised for a repeat thread or something, I'd be really grateful if someone could point me in the right direction or explain to me how.
I upgraded my ROM on Orange UK's website and it's 1.59.61.2
But I hate it and want to go back to the original ROM as it all was. I've tried everything for downgrade or change it and nothing works. I'm not liking the Orange branding and all the changes that came with.
Can anyone help please?
Also, on a separate note, Advanced Config never saves new settings. Any ideas?
Thank you all in advance.
xlrmotorsport said:
I've tried everything for downgrade or change it and nothing works.
Click to expand...
Click to collapse
You've obviously not tried everything as you've not got it to work
Maybe if you list precisely what you've tried we can suggest alternatives...
By everything, I mean everything I can think of.
Tried installing ROMs below 1.59 i.e. 1.56, but loads to 1% and that an error message appears.
Tried reading some of the guides on here, but nothing has worked yet.
I'm not so up to speed with all the jargon, but I'm learning as I go along.
u need to use HSPL from olinex to downgrade roms or use custom roms...its a sticky...i'm also on orange as soon i got my HD i put on a custom rom asap and been trying different 1s since then...
Done all that, tried it all and it doesn't change a thing on my HD.
OK, so in August I upgraded my ROM on the Orange web site after the HTC web site wouldn't let me do it because it said "Sorry, this software download is not suitable for your device" after I put the S/N in. It installed no problems, but changed everything from HTC generic format to a customised Orange format.
Since then, I have used HSPL from OliNex, and tried custom ROMs. On the tri-colour screen it comes up with a different version each time (at the moment, it's BLAC100 32M SPL-1.54.0000). But on the 'Smart Mobility' screen, it comes up:
R 1.10.25.25
G 52.57.25.30U
D 1.59.48753
I used a S/N to download the ROM upgrade from the HTC web site (RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship). I go through everything where it says: "Verify you want to update the ROM version: From: 1.59.61.2 To: 1.56.405.1". It then appears to start, gets to 1% then fails coming up with "Error [294] : Invalid Vender ID"
I've done lots to the phone, installing lots of different versions of things, but it still remains the same.
Sorry for my ignorance and distinct lack of knowledge.
Not sure but the HD may be vendor locked to Orange roms when using an official rom update (clearly this isn't true with custom roms as they work on any HD). Try flashing one of the older Orange roms - 1.14 or 1.19. For my part my Orange phone came with the 1.19 Orange rom installed and had no Orange crap on it at all, it was identical to a generic rom. I did use the Orange 1.59 update but I don't remember seeing any Orange crap on that rom either, though I only used it for 10 minutes maximum as all I was after was a clean install of a custom rom.
By the looks of things you already know this but at the bottom of the first HSPL post there are instructions for flashing back the stock spl and roms http://forum.xda-developers.com/showthread.php?t=431217

Back from Android to WM6 problems

Hello everyone!
I recently installed Android Froyo 2.2 (Incubus26Jc's Super FroYo RLS15 All Language), following mainly this thread http://forum.xda-developers.com/newthread.php?do=newthread&f=602, and also reading many others, about hardspl etc.
Everything went perfect! The phone workes just fine, full functioning!
My problem is that, after deciding to go back to windows mobile for selling my phone, I followed these steps :
"Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH.
Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When the flashing is done you should be back to running Windows Mobile."
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Also, when I press the power button+camera button, for a new update flash, after the three colors screen(KAIS130, SPL-3.07.0000, CPLD-8), the message "Loading..." appears and stucks.
I guess, my phone no longer has hardspl, and there is no way to put it back, neither put back the signed rom, if there is no WM os????
Any help/suggestions???
Thank you very much, in advance
I suggest you follow the tutorial switch back to Windows Mobile by Dukenukemx ~ http://forum.xda-developers.com/showpost.php?p=6461906&postcount=1
looks like a really lost hardspl. Maybe this will help you get back to windows http://forum.xda-developers.com/wiki/index.php?title=Kaiser_stuck_at_bootloader
aris0602 said:
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Click to expand...
Click to collapse
One question:
What version radio was on the phone BEFORE attempting a WinMoBlows flash?
It looks like the shipped rom had the 1.27.12.17 radio included in the bundle and, if so, this would explain the error in flashing.
One thing to check would be at the bottom of "Settings" page, touch "About Phone". Towards the bottom you will see "Baseband Version". The numbers at the end are your radio version and should be the original radio numbers. If it says "1.27.12.17", you've found one problem...
I would say follow dukenukem's post and try to reflash HardSPL again.
I haven't run into this problem yet since I will probably never sell either of my Kaisers... lol.
same problem at my place...
installed android, about 2 month ago, wanted to switch back to win and couldnt do it that simple as say "Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. " in Dukenukemx's tutorial.
I have tried everything putting on sd card many ROM's Hardspl's, then i found this on my pc RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88. 07_1.27.12.11_Ship when i try to flash via usb (manually enter bootloader and connect usb cable) it get to 1% and reboots and ond rom update software says ERROR [294] : INVALID VENDER ID and above Exit button says: VER4-KBKV5867-HUEbc568-KBKV58670...
and when i try same rom to flash via sd card it says
Loading...
Checking...
0028002
Not Allow
with any other it stay's at 0% on phone and nothing is showed, then on RUU says ERROR [262] : UPDATE ERROR and down is button Recovery, tried a lot's of times nothing...
Then i saw that you PoXFreak said to check radio in baseband mine is 1.65.17.56
any sugestions please?
Another user with problems...
Tried a return from android to windows mobile because of the random locks that were happening in android (also some other weirdnessess...)
Now when it is put a microSD with kaisimg or kaisdiag it goes into white loading screen and stay there...
(tried flashing Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, that seemed to be the one who came with my phone)
The baseband message somebody talked above shows only "HTC"
When in tricolor bootloader the following is showed:
security unlocked
KAIS***
SPL-3.28.0000
CPLD-8
(Still gonna try updating it connected to the computer, seems like usb and serial dettection are working, for it will dettect the charger connection and start showing USB in the lower part of the screen, battery got very low overnight, still needing to charge it to really do some test)
_____________
Update:
Flashed ok through USB, just entered tricolor bootloaded, connected usb and executed the original rom installer.
hello everyone
I used to have this kind of problem.. my hard spl broke when i tried to flash a stock wm rom from android.
In my opinion, each stock roms comes with specific SPL, radio version, etc. It means that when you are trying to flash stock rom, you also flashing new SPL. the problem is, the new SPL broke your hard SPL so you won't be able to flash anything to your kaiser except your original stock rom which comes with your kaiser.
you can find some stock roms for kaiser here : http://shipped-roms.com
Since I'm only sure that my kaiser originaly comes with WWE version I almost tried all the WWE stock roms there, but my search ended when I flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe, this rom works for my phone and it seems that only this rom didn't give me "invalid vender ID" message.
so, keep trying to find your original stock rom
and after you managed to flash your stock rom, don't forget to flash hard-SPL again if you still want to mess around with your kaiser.
good luck
Another way to do it, albeit a little tougher, would be to use Oli's NBH tool and remove the SPL and radio from a stock rom. That way you get to keep the radio and SPL while flashing a stock rom.
Keep in mind that some WM roms only like certain radio versions, and you may end up having to flash an older (or newer) radio to find what works best.

Categories

Resources