yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] asci:
@pw120

The miri WM6.5 v.7.2 is based on 1.56 rom...it should match new SPL...but I still have the same issue...

Now I flashed the stock 1.56 and the weird color issue has gone. Uhm...it should be related to WM 6.5 ROM. Now I will flash once again a 6.1 coocked rom based on 1.56 and see what happens...
[Touch HD Windows Mobile ROM Development] AllTheWay:
Problem fixed.

thanks guys.

1.) Revert to original SPL

2.) Flash USPL 2.5

3.) Flash 1.56 ROM

4.) Complete.

if anybody else has problems with this just hit me up on MSN at alltheway7@hotmail.com or via PM.
[Touch HD Windows Mobile ROM Development] asci:
@AllTheWay

The problem is not fixed for me. I did that procedure 3 days ago and then I installed last Laurentius Beta ROM which is 1.56 one. The problem occured when I decided to flash some WM 6.5 ROM and also last 6.1 Davidhuck. Now I'm flashing back Laurentius beta to see what happen...
[Touch HD Windows Mobile ROM Development] pw120:
some cooked roms based on 1.56 have changed one of the .dll files so they work with old spl and hspl
[Touch HD Windows Mobile ROM Development] asci:
@ PW 120

U r veru right! This is the problem! So to all coockers please

SPECIFY IF YOUR ROM ARE FULL 1.56 BASED OR NOT...
[Touch HD Windows Mobile ROM Development] custardo01:
Flashing stock ROM won't give you stock SPL if you had already flashed new ROM with 1.54 SPL. You have to flash stock SPL separately to get back to it. Had colour screen problem with stock ROM and realised I still had 1.54 SPL from upgrading newer ROM. Flashing 1.14 SPL the risky way with USPL solved the problem for me.
[Touch HD Windows Mobile ROM Development] sternas:
Same problem after NEW WWE 1.56.401.1 ROM

I just Reflash with OLD Europe 1.14.401.2 ROM from WIKI

All is OK now,

no colour screen problem and the 1.14 SPL is back to my HD
[Touch HD Windows Mobile ROM Development] ALF@be:
You can find the solution here and why => Wiki Rom 1.56 and color issues...:D
[Touch HD Windows Mobile ROM Development] asci:
Well, I falshed stock ROM when I was HSPL in order to get original 1.14. Now I'm with 1.54. I suppose that if I would go back to 1.14 and than HSPL, I should follow a different procedure that, as are you telling me, couldn't be the simply flashing 1.14 original stock.

The problem of wired color under 1.56, is that the most of the ROM avaible are designed for lower SPL, and also the one which are based on 1.56, were modified by replacing a dll file which allow all people with 1.14 HSPL device to flash every rom. ATM I'm running a beta ROM by Laurentius which is "full" 1.56 and I have no problem. So, once you upgrade to 1.56 and flash with USPL (since HSPL for 1.54 is still not avaible), if yuu want to flash all the rest of the rom you have to downgrade to 1.14 spl:

* Download an older stock ROM for your CID (region/operator)

* Flash ROM (to downgrade SPL)

* Install HardSPL

The problem is that for a period we will have this double way in ROM coocking, one with full 1.56 base and another one with a 1.56 modified dll. All coockers should point out when a new rom will be released, if it is for HSPL 1.14 or USPL 1.56.

...at least I think this is the problem...

;)
[Touch HD Windows Mobile ROM Development] fjevel:
Hmm...

Here's what I did:

Had HardSPL, flashed to original rom with original SPL.

Then upgraded to original 1.56 without problems.

When I now use USPL to flash cooked ROMs based on 1.56 (like Miri's 7.2), I get the green screen until I turn the screen off and back on again.

Is this fixed by flashing the original 1.56 from USPL? Sounds a bit weird to me.

-KJ
[Touch HD Windows Mobile ROM Development] HDuser:
You sure that 7.2 is based on 1.56 ?

"* [ROM][WWE][11.04.2009] Miri WM 6.5 21500 :: V 7.2 [ONLINE]

This ROM is based on Windows Mobile 6.5 build 21500." first post of his thread

The way I see it is once you have 1.56 you can't flash cooked roms with out getting the color issue.

I think the exeptions are roms based on 1.56 as they have the correct version and combination of disptools.dll.

Now you dont want a stock rom so why would you still need SPL 1.54 on your decvice were you can run the risk of the color issue.

Would not a down grade of the SPL to 1.14 be enough for you to flash any rom as you did in the past (HSPL, USPL).

Now what I am not sure about is if you downgrade SPL 1.54 to 1.14 and still have a 1.56 rom installed will you get color issues ???

As allways info taken out of this wiki page

http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Rom156
[Touch HD Windows Mobile ROM Development] asci:
@fjevel

Miri's 7.2 is not a full 1.56 based rom. He should have modifed a dll in order to make it run under 1.14 HSPL device. To have it to work correctly you should flash a full 1.56 ROM, like stock one or Leo Beta I'm currently testing.
[Touch HD Windows Mobile ROM Development] fjevel:
Thank you for your quick reply.

According to the changelog from miri's 7.2, his ROM is based on 1.56 (ref), so I was under the impression that if I flashed to stock SPL, then upgraded to stock 1.56 and then USPL to miri's I'd be fine.

But there seems to be something missing here.

-KJ
[Touch HD Windows Mobile ROM Development] fjevel:
As you can see from my initial post, I already flashed 1.56 stock before USPL to miri's. I still have the problem.

-KJ
[Touch HD Windows Mobile ROM Development] asci:
Did u read my post? I said that miri's ROM is based on 1.56 rom with 1.54 SPL BUT HE REPLACED ONE DLL IN ORDER TO MAKE HIS ROM SUITABLE TO 1.14 HSPL ROM AND NOT TO 1.54 USPL ROM
[Touch HD Windows Mobile ROM Development] fjevel:
Yes, I read your post, but it made no sense to me. From what I read, you told me to upgrade to a full 1.56 before I went on to miris ROM, which was exactly what I had done.

And there's really no need for the uppercase shouting. I am perfectly able to both read and reason.

Do you have a link to the info where miri says that he has used the disptolls.dll from 1.19, as I can't seem to find it. In all the places I have looked he lists that the ROM is fully 1.56 based.

-KJ
[Touch HD Windows Mobile ROM Development] asci:
No, I didn't say it. I said that:

It means you have to flash a full 1.56 ROM, since you have a new SPL now (1.54), and miri's one is not designed to run over 1.54 SPL. Try the last Dutty ROM which is a full 1.56 based rom and you will have no problem (as I'm running it without weird color issue).

Miri didn't talk about dll in his post. But I came to this conclusion after a long discussion with Laurentius, Davidhuck and other Devs...It's a known issue now.

;)
[Touch HD Windows Mobile ROM Development] X3mE:
Hi,

I have installed Olinex HardSPL 1.14 and tried to install the official RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe ROM.

I did everything and when it tried to start I've got the green color issue. The problem is, the screen freezes sometimes and I'm stuck at calibrating the screen (when it doesn't freeze it returns me back to calibrate it after I've already done it), so I can't start it up and connect it to ActiveSync to restore the stock SPL.

What should I do?
[Touch HD Windows Mobile ROM Development] d.cortez:
you need Olinex HardSPL 1.56 to use the ROM you reference above.
[Touch HD Windows Mobile ROM Development] X3mE:
But how to overcome that screen calibration? I can't connect it with ActiveSync.
[Touch HD Windows Mobile ROM Development] masterbrazil:
HELLO Mr. ALLTHEWAY or ANYONE I NEED HELP:eek:

I bought a HTC HD phone used in the Portuguese language. When I go to the official HTC site and entered my serial number appears in a ROM 1:56 DUTCH. Because of this soon realized that this cell had been modified. Making the bootloader (tricolours) found in the bootloader screen doing the following:

BLAC100 32M

SPL - 1.14 OLINEX

MICROP - BLACKSTONE (LED) V6

My doubt is whether to install the original HTC most current version Portuguese (1.56..), I need to do the procedure HSPLWrapper_Blackstone_156OliNex to update again or with the data above I can install directly the 1:56 ORIGINAL PORTUGUESE ROM?

If not I must update to HSPLWrapper_Blackstone_156OliNex from 1.14 Olinex version?? The update to the OLINEX1.56 will be recognized automatically? And then can proceed with the new ROM update for _HTC Touch HD_MR_2009_RUU_BlackStone_HTC_PTG_1.56.410.0_Radio_52.62.25.34_1.13.25.24_Ship? In this way I will get success?

Thank you in advance for your attention

Congratulations for the work!

John from Brazil
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Seeing as you SPL is 1.14.OliNex you will need to use HardSPL 1.56 first before flashing 1.56 based rom.

You should be able to use HSPL 1.56 straight away and then flash rom.

Alternatively you can use USPL 2.5 instead of HSPL. You will need to follow cRaCKwHoRe's guide for this (see my signature).
[Touch HD Windows Mobile ROM Development] Clay123:
I have the same color issue after flashing Miri 21869 v29 ROM using USPL2.5 GUI. It seems that since my SPL is 1.14, this color issue happens. I updated the SPL to 1.54, then the color issue was gone without reflashing the Miri ROM. Just follow this guide on USPL http://xdaforums.com/showthread.php?t=502921&page=3
[Touch HD Windows Mobile ROM Development] fra996:
hi Guys,

i unbranded my Italian 1.13 with HSPL 1.4. Then i updated to custom shipped 1.56 and i got the greenish screen.

I just updated with HSPL 1.56 and everything went fine without reflashing 1.56 ROM.

Hope this help

Best regards
[Touch HD Windows Mobile ROM Development] farukb:
thanks for your effort

i doubt it helped since last post was in october last year....and everything is already described in stuck threads

be more careful,
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Indeed, thought this thread died ages ago......it has now!!

Thread closed
[HTC Excalibur] jorossian:
Weird, huh? I thought this was an interesting issue and that maybe some of you more experienced pda tweakers with some electronics background might have an idea what's going on.

I recently got a "backup" Excalibur on ebay from a girl who said it was "broken". Nonetheless, I figured it was a good deal for parts considering I won it for only $10.50.

When the phone arrived I was surprised to see it looked to be in fairly pristine condition all around (better cosmetically than my own anyway). So I popped in a freshly charged battery and pushed the power button. Nothing. I pushed and prodded for different lengths of time for a while and it actually did manage to power up one time to my surprise (the battery power did show as being fully charged). Thinking this was odd I turned it off again and tried to repeat it again with no luck. After a while I gave up and decided to try with the charging cable attached.

Viola! Started right up no problems. After unplugging from the charger the phone worked flawlessly and it holds a charge just as long as my main phone (I usually have about half to 2/3rds charge left on my OEM battery at the end of the day). The phone charges with no problems as well.

Anyway, I've gone ahead and wiped out the T-Mobile ROM and installed the HTC English-Spanish 6.0 ROM just like my other phone (love this ROM - it's a later build and slimmed down compared to the last T-Mobile .8 Rom plus it's faster, supports HCSD, Voice tags, advanced JOGGR etc.. ) and it works beautifully with this strange exception.... I always need to plug it in if I need to turn it on after a complete shutdown. If the device "soft-resets" via a program such as spb backup it will start up fine without needing to plug it in, however if for whatever reason you power it off via Quick list or long press of the power button, you will need to plug it in to get it to restart. I've had it for about a week and it's a real gem and workhorse aside from that one issue.

Does anyone have any idea what could be the cause of this? I can't complain since I bought the phone for just $10.51 (with free shipping! :) but it's driving me nuts just thinking about what could be the cause. I've scoured the web looking for similar cases but I haven't found anything similar to this.

Is it possible that the phone is supposed to hold a "power up reserve charge" in a capacitor/diode to give it the "umph" to turn on and maybe my diode is bad or damaged? <--- please keep in mind that that sentence came from a guy who knows nothing about electronics but remembers his dad telling him not to touch that broken TV set on his work bench because "it holds a mean charge even though it's been unplugged for a couple hours"... so be kind ;)

Any thoughts or ideas would be greatly appreciated! Thanks guys
[HTC Excalibur] jorossian:
Interesting development...

I've managed a workaround for the problem so I can do a cold start.

1. Remove the Battery

2. Hold in the power button

3. Snap in the battery while holding the power button

4. Release the power button 2 seconds after the battery is popped in.

Works every time.

Still, I'd love to hear some advice from someone who's a bit more electrically inclined.

Now onto my new problem...........
[HTC Excalibur] jorossian:
I've suddenly lost the ability to active sync on this phone and it all started right after I entered the network SIM UNLOCK CODE.

I've done several total resets and even put in old spb backups and a backup from my other Dash running the same rom which activesyncs with no issues. I've uninstalled and reinstalled ActiveSync. Still, this phone no longer connects, while the other does. The one variable I have is that the issue began right after I got my unlock code and SIM unolocked the phone.

I'm fearing that the issue is this...

My other phone was network unlocked while running the T-Mobile stock ROM. I then upgraded to the HTC ROM later with no negative affects. THIS phone was network unlocked AFTER I'd run the HTCunlock program to install the HTC branded Spanish-English 6.0 ROM. I'm wondering if the process of network unlocking doesn't play nice with a ROM designed for a different device ID?

Anyone have any clues what could be going on and whether there's anything I can do to get Activesync back to working on this dash? I really enjoyed using this phone to test out new ROMS and apps before putting them on my everyday phone.

Thanks
[Touch HD General] mkid:
dutty 2.6 rom installed, no problem after reboot

changed the wince.nls, no problem after reboot

but after install chinese ime-only.cab

after reboot showing the rom version, then nothing after that ....

anyones know why, how to fix it ?

====================================

我部 HTC TOUCH black screen

裝左 dutty rom, 換都左中文 wince.nls 無問題,

裝完小熊 ime-only

boot 機之後 , 出左 rom version . 畫面之後 ... 就無野出了.... 黑晒

請問 點解決 ?
[Touch HD General] stepw:
Hard reset
[Touch HD General] mkid:
I was not able to to the Volup + VolDn thing as I thought this function was faulty.

But since it seems there is no other way, then I have to try it again and agian.

I finally got it work, it requires a little trick there.

but anyway, I got it "hard reset".

thanks ............ :D

Now I have to worry another thing is my 1.5TB hard drive is corrupted. ... :(
[Touch HD General] borber:
what else?

I've tried hard reset, but i still can't boot :(. Any suggetions what to do else?:confused:
[Touch HD General] Psygnosis84:
what's with the newbs not explaining anything?

why not start off by saying what you did to cause it not to boot, that way you will get an answer.
[Touch HD General] borber:
newb ;)

woops sry - i did a rom update of my new blackstone, from htc.com/dk website. After the update i got the same problem as this thread: Black bootscreen with rom and radio version text in right bottom. I've tried hardreset with same result (stops at bootscreen). I tried reinstall the rom but got basicly the same result, with one exception: i actually got as far as to the windows loadscreen saying: "...Will install as when u bought it..." (or something very close to that.

Hopes this clarifies my issue :)
[Touch HD General] leobox1:
random thought... y dont u reflash with a lower ver rom first... may help..
[Touch HD General] borber:
Ah yes - but i tried find a lower DK - version; i got a v1.00. But when i try running the RUU it halts at 0%. The version the device came with was v1.19, but i can't find a danish version of that ROM. I tried a WWE, but i got a vender id error.
[Wing, P4350 General] elracing21:
Hey guys, im really new to the whole flashing deal and i spent the whole night reading and messing around with my phone and out of all the ROM's i have tried the only one I really liked was the Touch-it interface. I currently have a Windows mobile 6.0 Touch-it interface that I downloaded somewhere from this site. I have been looking all over for a later version seeing that 6.0 is really old lol.

Anyway here is my current status

ROM version: 4.17.405.2 WWE

ROM date: 06/20/07 (like i said its a really old version =/ )

Please and thank you I will continue my search and see what can I find.
[Wing, P4350 General] ivanmmj:
A new Touch-IT ROM hasn't been made in a long time.

What "Touch-it interface" are you refering to?
[Wing, P4350 General] elracing21:
I see what you mean after more hours of searching i found more touch-it ROM's by itje and they seem to be outdated.

I know this is a silly question but which ROM do you use? I suppose one that you made your self am I right? If so which of your ROM's do you think would go best with a new user?

And I highly thank you for responding to my thread =]
[Wing, P4350 General] ivanmmj:
I don't use my wing as my main device anymore, but it does run JustStable on it. (It's my newest ROM.) It's still a work in progress, I'm still releasing new builds all the time, but it's going to be final soon.
[Upgrading, Modifying and Unlocking] Lonewolf Darkmoon:
Ever since I upgraded my US Cellular HTC 6800 to WM6.1 the camera does not work right. All is good except for the zoom which does not function at all. I can not get it to zoom by using the keys or the touch screen. Does any one know why this way be happening or how to fix it? Thank you for any help.
[G1 Android Development] ampliz:
I have a white G1, with T-mobile RC33 firmware, that I bought unlocked from ebay. So I don't have the unlock code, and I live in Norway..

Can I downgrade and flash the phone to root and dev phone, and the phone will still be unlocked afterwords?

Or does it have to be unlocked again after the procedure? Something I can't do..
[G1 Android Development] jashsu:
It will still be unlocked.
[G1 Android Development] Intergallatic Christ:
I done the same thing with my unlocked phone from ebay, flashed and rooted with no problems.

* I take no responsibility for any problems encountered! *

*edit* I'm too slow
[Touch HD General] eng_asa:
Here is another question/request....

Is there any tweak or registery hack that would show the Quick Menu Button (the little button on the top right corner on the home screen) all the time???
[Touch HD General] eng_asa:
And another question/request...

is there any way to show srt subtitles when playing movies?? I tried TCPMP but it doesn't work on my HD!
[Touch HD General] FileFixer:
http://xdaforums.com/showthread.php?t=484995

Enjoy...
[Touch HD General] eng_asa:
great ... will give it a try .. thank you :)
[Non-Touchscreen Windows Mobile Other] AndrewSpec:
Yesterday I was installing Audigy drivers for Win 7, and everytime it crashed with BSOD. I noticed, that on Windows Mobile I haven't seen a BSOD, so I thought it would be very funny to see it....and finally I wrote this small app :)

Here's a movie that shows how it works http://www.youtube.com/watch?v=hd-VIMarwUU

Changes since last version:

-screens are in better resolution;

-options are in english (for polish options you must set regional settings -> locale -> Polish)

-many bugs are fixed

-support for Windows Mobile Professional devices but I've tested it only on a few emulators

!if your orientation is set to portrait, the BSOD won't launch, but not at all times. Just rotate your screen to landscape.

V.1.0:

*Random mode randomizes the time to show BSOD, the range is from 10 seconds to 1000 seconds (16 minutes).

*When BSOD appears, you can press any letter on the keyboard to close it.

*While BSOD is active, the screen wan't shutdown, when you close it, it restores the power setting to the previous value.

*There are 11 build in blue screens. Program is choosing a random one :)

To run, you need .NET CF 3.5. Program is dedicated for landscape screens so before using it rotate your screen to landscape ;)

To Do:

-Reboot after 3 sec from BSOD
[Non-Touchscreen Windows Mobile Other] bombex:
jaki sens tego jest ??

it will check
[Non-Touchscreen Windows Mobile Other] Nokser:
Sens jest zawsze, we wszystkim, więc nie zadawaj zbędnych pytań.;)
[Non-Touchscreen Windows Mobile Other] AndrewSpec:
Sens jest taki, że można się pośmiać :)

Np kiedy włączysz sobie, pokazujesz coś znajomemu i nagle wywala niebieski ekran. Co taki znajomy pomyśli? Wpadnie w brecht.
[Non-Touchscreen Windows Mobile Other] gnida1:
mam problem, aplikacja się nie uruchamia, tzn. opcje działają ale jak ma się uruchomić program to wyskakuje błąd:

bsod.exe

Error

An unexpected error has occurred in bsod.exe

w Details pisze to:

bsod.exe

NullReferenceException

at

BSOD_for_WM_by_Andrew.Inne.zablokuj_ekran()

at

BSOD_for_WM_by_Anderw.Program.Main()

może da się coś z tym zrobić
[Non-Touchscreen Windows Mobile Other] AndrewSpec:
Z tego co widzę, to nie może zablokować timeouta dla ekranu. Zmiany przechowuje w rejestrze i pewnie nie może tam zapisać...Sprawdź czy masz zdjętą blokadę programową, bo na moje oko wygląda to na zablokowany rejestr :)
[Non-Touchscreen Windows Mobile Other] bombex:
dodam, że mi też nie działa

na SE Xperia 480X800

też jakis błąd, nie pamiętam jaki... na wszystkich modelach to nie śmiga
[Non-Touchscreen Windows Mobile Other] AndrewSpec:
Na i600 musi śmigać ;) A jeśli uruchamiasz to na PPC to jest bardzo prawdopodobne że coś nie styknie, sam tego nie testowałem, ale program jest napisany dla WM Std z użyciem SDK dla WM6 Std.

Sprecyzuj co to jest za błąd.

A tak przy okazji dodam, że screeny są w rozdziałce 320x240 więc na Xperii nawet jeśli byś uruchomił, to będą rozmazane...potrzebowałbym je w dobrej jakości to zrobiłbym wersję dla innych ekranów.

EDIT:

Wersja dla WM Pro już jest w drodze zatem bądźcie cierpliwi (pierwszy build działa i ma screeny w dobrej jakości)
[Non-Touchscreen Windows Mobile Other] AndrewSpec:
Today, I released a new version that supports Windows Mobile Professional!

-screens are in better resolution;

-options are in english (for polish options you must set regional settings -> locale -> Polish)

-many bugs are fixed

-support for Windows Mobile Professional devices but I've tested it only on a few emulators

Rotate your screen to landscape before using it.

Download in 1st post.
[Palm Treo 750] eganzon79:
I have this Palm treo 750 that is on boot loader only (with tri-color)

I don't know why this happendened, just one day I turn it on it just goes to this part and never goes to regular menu at all is just hang to tri-color only!

this is what it look like:

Pal Tr

IPL_0.20

Palm Tr

SPL-0.24.0000

Serial

and it has red color, green, blue, and white at the bottom.

Please kindly help needed badly, thank you
[Palm Treo 750] eganzon79:
Please kindly help, I don't know what to do to make my cellphone work again!:(
[Palm Treo 750] cooler84:
try ti reset phone by pressing reset button with styles, next to card slot...if that don't work try to delete all data from your phone by holding ok button and then with your styles press reset (next to card slot)...and when ask you delete all data...say yes by pressing up button or yes or..you will see instruction on the screen...:) please report results here! ;-)
[Palm Treo 750] cooler84:
or maybe it's media button, lower button from the left side...maybe it's broken or something so it's pressed all the time...maybe that's the reason for enetring in bootloader-mode... try first to delete all data as I told you in previous post ;)
[Palm Treo 750] andheqi:
try to clean the connector port on ur treo (better disassembly it before)......it works!:cool:

good luck!