yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] vdgg:
"Fuzzy" screen problem using Olinex 1.14

Hi All,

This is my first post. I've been doing a lot of reading, and hopefully i'll get all the terminologies right.

Apologies over, here's my problem:

I bought a Blackstone in Thailand 4 months ago.

I'm having problems with my screen, showing green dots over gradients, in all screens including video and while using the camera.

This thing comes and goes (hardly goes anymore, however).

I contacted support, they told me that my device is from Taiwan and that it should've been in Chinese.

Some digging done, apparently it's been cracked with SPL Olinex 1.14 (shown in the tri-color screen), and flashed with WWE ROM 1.19 (region 831).

My initial thought was to restore the original SPL (stock SPL) & send to a support center for repairs - if so, how can i tell which version was there initially?

Second, doing some more searches, i saw some comments about how older Olinex versions can cause screen "fuzziness", but that was a Diamond thread, and mine's Touch HD.

I'm not sure if that describes my problem, anyway, so i'm attaching a picture of the Windows Mobile logo from my phone when the problem occurs.

Has anyone encounter such a problem? Any solutions for it?

Obviously, i'd rather solve the problem myself and not send it over to support.

Any helps would be greatly appreciated!

Thanks.

Asaf.
[Touch HD Windows Mobile ROM Development] Paul203360:
This site is too good, thanks for he hard work people.........:D
[Touch HD Windows Mobile ROM Development] -Satan-666-:
Eh.

Thanks For this :)
[Touch HD Windows Mobile ROM Development] ClydeB1:
If support is saying the device should have been Chinese then that is probably based on the CID/IMEI number on the device. You would therefore possibly need to flash it back to Chinese, but I'm not sure how good your Chinese is LOL :p

Is your screen a bluey/greeny colour, almost like a low res 16k colour screen, or is it green speckles over the screen? If the former, then you can probably rectify it by flashing another rom and upgrading the spl. If the latter however, that almost sounds like a faulty screen and that is going to be rather difficult to correct unless you can get it fixed in Taiwan, but again as the device was sold with a cracked rom, I'm not to sure how legit the supplier was and whether you would have any warranty.

Anyway for what it's worth, you can find links to official roms here

and you can find the steps required to flash back to a stock rom and spl in this very thread at the end of post #1.
[Touch HD Windows Mobile ROM Development] vdgg:
Thanks for your reply.

Obviously, my Chinese isn't very good :)

And green speckles describes the problem very well.

And since my original post, the problem disappeared and reappeared this morning.

Before concluding that it's a hardware problem, i want to make sure that it doesn't have anything to do with the hard-SPL that i have installed.

Because, browsing through the forums i see that i should install a newer version of Olinex than the one i have if ""flash the 1.37 if you experience the fuzzy display issue""

What is the fuzzy display that they're talking about?

It appears on every guide in the forums, but with no explanation.

And now the other way around -

Assuming it is a hardware problem, how can i tell which stock SPL was installed on the device before it was cracked?

How do i safely revert to it?

I assume i must flash the original chinese ROM first, and only then overwrite the SPL.

Will it remove all traces of Olinex?

Sorry to bug you about this, but I must be sure that i know how to do this properly before attempting, as i don't want to be left with a Black Stone.

(ok, lousy pun, but i had to :))

Thanks again

Asaf.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Basically 2 versions of HSPL available for the HD at present

HSPL 1.14 is to be used on all roms based on pre 1.56

HSPL 1.56 is to be used on all roms based on 1.56+

If you used wrong HSPL for your rom, on boot up the screen appears a greenish discolourization/distortion. Once phone has boot up this dsicolourization can be removed by using power on/off simply by putting phone into sleep and then brought out of sleep. However another symptom would be that phone also appears in 'flight mode' i.e. you are unable to get signal and cannot use your phone to make calls, sms etc
[Touch HD Windows Mobile ROM Development] darwon6565:
hd

hey people plz tell me how to donload yes i know its here it says i cant go to the page
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
You can download HSPL 1.56 on first post in this thread. Scroll down to bottom of first post and click on HSPLWrapper_Blackstone_156OliNex.zip
[Touch HD Windows Mobile ROM Development] Skrewku08:
Hey guys. I am having an issue with the 1.56. I keep trying to put it on, but each time i get to the point of flashing it gives me a "202" error and asks if my blackstone is connected through usb (which of course it is and in autosync mode per the directions) or if it is docked. Can anyone help me deal with the error? Thanks.
[Touch HD Windows Mobile ROM Development] ClydeB1:
From the wiki describing error codes and their resolution:
[Touch HD Windows Mobile ROM Development] splopje:
working perfect. thx guys
[Touch HD Windows Mobile ROM Development] Skrewku08:
I appreciate the help. However, I ran the activesync before I ran the RUU just to make sure it was connected. I uninstalled it and re-ran it and received the same error. I also ran it on a different computer but got the same error message. Does anyone have any other ideas? Thanks.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Have you tried uninstalling Activesync and then trying to re-install or looking for an updated version?
[Touch HD Windows Mobile ROM Development] Skrewku08:
Yes. I did. I ran the Activesync 4.5. Thats the most updated version I can find.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Have you tried all of these steps?
[Touch HD Windows Mobile ROM Development] Skrewku08:
The only thing out of those is the Manual HSPL and the different USB. I dont have a different USB. However I will try the manual and see what happens.
[Touch HD Windows Mobile ROM Development] Skrewku08:
Ok. I cant even get the manual to run after i downloaded and extracted it. I am at a loss.
[Touch HD Windows Mobile ROM Development] Digital Outcast:
Are you running Manual SSPL from your device or from your computer? It has to be run from your device when it is in Windows.
[Touch HD Windows Mobile ROM Development] Skrewku08:
I have been running it from my PC. Can you walk me through the process for the device?
[Touch HD Windows Mobile ROM Development] ClydeB1:
From the Dummies guide:
[Touch HD Windows Mobile ROM Development] Skrewku08:
Does it matter that the version of the image on my phone shows 1.59.841.6? I am wondering because of the version of 1.56. I am new to this and just kinda wondering before I run everything.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
HSPL 1.56 is to be used on roms based on 1.56+ (i.e. your rom is 1.59)

HSPL 1.14 is to be used on roms based on pre 1.56 (i.e. roms like 1.14 etc)
[Touch HD Windows Mobile ROM Development] Skrewku08:
Thanks Bro. I appreciate everyones help. I will give this a try and see what happens.
[Touch HD Windows Mobile ROM Development] Skrewku08:
Ok now I ran just like you said in the bootloader and it came up with a different error this time. Error "260", and what do I need to do to not brick my phone in the bootloader? Can I turn it off? Keep it like this? Please help. Thanks
[Touch HD Windows Mobile ROM Development] ClydeB1:
Were you running the manual sspl via your storage card when you got this message or is this after updating spl via sspl and were now trying to flash the hspl? Based on the error message it seems that the sspl update was not succesful. What spl is showing in your bootlaoder screen? From the previous instructions after running sspl you should have spl 1.07.Olinex displayed and you then need to run the hspl 1.56.

Where were you in the process when you got the error - are you in RUU still?You should not brick the device as it is still able to get to bootloader and if you close the error message the process should end - there may be some additional instructions in the RUU app to follow though. You may then also need to need to pull the battery in the bootloader screen as I do not know of another way to exit bootloader (there may be another way though).
[Touch HD Windows Mobile ROM Development] Skrewku08:
Ok so now I got it where I can load the wrapper. But what do I need to do to load the ROM with the wrapper? I know this is a newb question. I am just trying to make sure I do it correctly and not screw up my device. Thanks for the help. This is what I want to load. You help is soooo much appreciated. Could someone walk me through? BTW...I have XP on my computer. Thanks.

http://xdaforums.com/showthread.php?t=542104
[Touch HD Windows Mobile ROM Development] antu_pogroms:
hye.. i'm have a problem here.. i recently bought a blackstone which is from singapore. i found that the sim is not locked because i'm able to use my sim card on my country. the problem is, my phone can't established a connection with my pc. my pc is using windows 7 RC1. i've installed latest version of wmdc 6.1. i've also try to connect my friend blackstone and it works well. but when i connect my phone, it wont work. it is charging when i connect to pc but can't sync with wmdc.. i've try using the manual bootloader and it shows at the bottom that it is "serial" and not usb. i can't install the driver for my phone because it is not shown up at device manager.

is there a way that i can do a HardSPL upgrade using storage card?

how can i flash my rom through storage card?

Thanks in advance.
[Touch HD Windows Mobile ROM Development] netwr:
Thanks for sharing!
[Touch HD Windows Mobile ROM Development] ClydeB1:
Please confirm where you are in the process now. What spl version do you now have showing on your phone?

If you do have 1.56.Olinex already installed, you can just download the rom from miri (it is a rar file). Once you unrar it, put your phone in bootloader mode, connect to your pc and when usb shows up in bootloader you run the BlackstoneRUUWrapper (from the unrar'd file|) and simply follow the steps. (After the flash has finished remember to do at least one hard reset).
[Touch HD Windows Mobile ROM Development] reflag:
hars-spl probleme

Hallo,

habe mir heute hardspl for blackstone_Olinex auf mein Touch HD

geflashtum anschließen Laurentius-Rom zu flashen. Nach dem Re-Start erscheinen die Farben nicht mehr richtig (ich habe ein Moire-Muster im Starbildschirm und auch anschließend bei farbigen Flächen) und vor allem bricht mir active Sync nach ca 30 sekunden die Verbindung zum WindowsMobile Gerätecenter ab. Dadurch ist das Touch HD nicht mehr zugänglich um hardpl rückgängif zu machen oder ein Rom zu flashen. Was kann ich tun???
[Touch HD Windows Mobile ROM Development] ClydeB1:
You would probably get a little better response if you use English here. Even if you use a translator like Google to translate for you.

From this I can see that your spl was not properly updated as the funny screen colours shows. If hspl was correctly installed, in bootloader you will see spl 1.56.Olinex

You need to try to follow the steps in the Dummies guide to flashing (link in my signature) on how to change your spl. From the above, it appears that you tried hspl (so follow all of the steps for hspl in the guide)
[Touch HD Windows Mobile ROM Development] StardustOne:
Hi, I have just installed that hard spl and my phone flashed this version but now I have lost all the colors and it looks like the phone only has 4 bit colors. How can I fix this?
[Touch HD Windows Mobile ROM Development] ClydeB1:
Your spl is most likely wrong (these colours are the typical symptoms of the wrong spl version for the rom). You say you have installed hspl, does your bootloader show 1.56.Olinex? Which rom did you flash?

You need to read the steps in the Dummies Guide to flashing (link in my signature)
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
As already stated by ClydeB1 above it looks like your HSPL installation hasn't been successful or your using wrong version of HSPL.

Check your SPL in bootloader, does it say 1.56.Olinex?

If your using HSPL 1.56, you need to be using a rom based on 1.56+

If your using HSPL 1.14, you need to be using a rom based on pre 1.56

Ta

Rick
[Touch HD Windows Mobile ROM Development] wakigatame:
Phone randomly turns off

Flashed the following ROM about 7 days ago RUU_BlackStone_HTC_Europe_1.14.401.2_Radio_52.49a.25.26_1.09.25.14_Ship and approximately every 12 hours or so the phone stops making/receiving and sending and receiving sms/mms. The phone still says it is on and it will still pick up email. The only way to enable the phone again is by soft reseting. The frustrating thing is that there is no visible indicator to say that the phone has dropped off. Thanks
[Touch HD Windows Mobile ROM Development] Digital Outcast:
The ROM you are currently using is v 1.14. You must have SPL v 1.14.oliNex for this ROM to work properly. Is that what you have loaded? ... Or do you have SPL 1.56.oliNex loaded?
[Touch HD Windows Mobile ROM Development] Ahojky:
I have big problem after flash. I changed HSPL to 1.54 and after I can't flash ROM, old HSPL... Nothing. After flash is on screen "update room code error" I tried put back old HSPL. On phone screen is 0% and on computer connecting error. I tried put roms on card too and nothing. Now is it for repair in service? :(

Sorry for my novice english

edit: I can send some reward for help
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
What does your SPL say in bootloader? Was original HSPL successful? It should state SPL 1.56.Olinex
[Touch HD Windows Mobile ROM Development] Ahojky:
I thing it was complete. After flash restart... and code error. I have on screen only SPL 1.54 without "olinex".
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
If you do not have SPL 1.56.Olinex then it was not completed. Follow this guide and ensure you have correct SPL before you try and flash roms or radio's

Ta

Rick
[Touch HD Windows Mobile ROM Development] torespen:
I have tried this proceedure, but still i have the 1.56.0000 SPL

Have flashed with orginal stock OS WM 6.1 HTC Norwegian, but is there a radio package also to be flashed?

Have tried to flash both 1.14 and 1.15 version, still comes up with 1.56 version.. Tricolor screen comes up, an counter goes to 100% and says successfully flashed.. still 1.56.. :s

Reason i want to flash back is that i hae problems with the reseption.. both calling/receving and recive and send SMS.. sometimes it works sometimes not.. Calls and SMS not getting trough to my phone. Calls i make getting interupted and network signals lost with no apperant reason.

So if Org OS and SPL doesnt work i need to ship for repair..

Any suggestions is appresiated.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Which stock SPL are you trying to get to? 1.13, 1.14, 1.15, 1.54?

When you run HSPL, originally a pop up screen appears. Make sure you do not click anything on this pop up screen, but instead replace .nbh file which was created with stock .nbh file. i.e. go to folder where HSPL is and a number of files should have been created once you ran HSPL including a .nbh file. This is the one you replace with the stock .nbh file.
[Touch HD Windows Mobile ROM Development] torespen:
This is what i'm doing.. just run the HardSPL, wait until everythings been unpacked, replace the .nbh file (with the stock file of choice), and then continue following the on screen instructions.. then the bootloader needs to be confirmed on the phone, and the phone restarts to tricolour screen.. it pauses there for approximately 10-15 seconds, then goes to the white screen with the prosentage counter.. this only takes about 5 seconds to reach 100%. the phone reboots and when the SMART MOBILITY screen comes on, it still says

R 1.3.25.24

G 52.62.25.34U

D 1.56.00.00

MOST probably me that does something wrong, but cant figure out what.

Have tried with 1.14, 1.15 and now 1.54

Not sure what it should be original thou...
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Sounds like your doing everything correctly. Are you putting the HSPL file into its own blank folder or are other files in that folder?

Have you tried running SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen
[Touch HD Windows Mobile ROM Development] torespen:
Jepp, separate folder on the desktop.

Have not tried the manual way..

So run it as You said and then the RUU? what RUU file?

You mean the Stock SPL i want to flash?

is there any other Radio ROM i can use that might get rid of my initial problems with calls beeing disconnected etc..?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Read the restore warranty section at bottom of first post.

You run manual SSPL then run the RUU for the stock SPL (i.e. after you have replaced the HSPL .nbh file with the stock .nbh file)

What radio's have you tried. All official radio's can be found here, latest being 1.14.25.24. You can try alternative radio's including 1.16.25.48, but you need to have your phone security unlocked first using this tool.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Which ROM have you flashed? IS it:

RUU_BlackStone_HTC_NOR_1.56.409.0_Radio_52.62.25.34_1.13.25.24_Ship.exe or RUU_BlackStone_HTC_NOR_1.14.409.1_Radio_52.49a.25.26_1.09.25.14_Ship.exe?

From the information above it would appear that you have flashed the 1.56 version with the 1.13 radio. AFAIK, the D 1.56.00.00 is not the SPL that you have loaded and I believe it is linked to the rom version. To see the spl version installed you need to go into bootloader (tricloour screen) mode. I would imagine that with the 1.56 based official rom, you will need the 1.54 spl. A sure sign of having the wrong spl for the rom will be a funny blue/green screen colour with poor graphics and usually being unable to place a call, so if you don't have any of these issues then you will have the correct spl.
[Touch HD Windows Mobile ROM Development] alegator23:
Have problem to upgrade to 1.56 Olinex

Hi Guys

Currently i got the HTC HD with the next configuration

Rom version: 1.18.707.3 (23358)WWE

ROM date: 12/10/08

Radio version 1.09.25.14

protocol version 52.49a.25.26U

SPL-1.14.0000

BLAC100 32 m

I gone to bootloader and connected cable USB ( i see at the bottom of the device USB).

The ActiveSync is not green (mean it's not connecting), after reading again some posts i understand that the active sync shouldn't be green, as soon as i see USB, the PC and mobile connected.

Then i started with the HSPLWrapper_Blackstone_156OliNex.exe installation, when i press "Update" button then the original version is blank but the future version is 1.56 Olinex which is correct ( I think so) ?

The whole upgrade procedure stuck on 0% on the device and after 2 mins i gets the restore button on the PC (HSPLWrapper_Blackstone_156OliNex.exe installation).

Maybe i am missing something, in addition i saw some flush through SD card, but i think the better wasy if from the PC -> Mobile.

Any assistance will be appreciated.

Thanks for Help.
[Touch HD Windows Mobile ROM Development] jeroen1801:
H-SPL not working

Dear All,

I've trouble with performing the Hard-SPL on my HD. While executing it, the statusbar stays at 0% and, in most cases, I get error code 262 (connecton). I took all necessary pre-actions/pre-cautions for performing H-SPL, but it just won't work. In all cases, the HD enters the boot loadere and recognized a USB connection (port v2.0).

List of what I've already tried:

-Normal H-SPL from bootloader

-SSPL from HD homescreen, followed by H-SPL

-H-SPL (from pc) direct from HD homescreen (it drops auto to boatloader)

-With or without SIM/SD-cards in HD

-Execution on both WinXP as Vista PC

-4 different USB-ports (I have only 1 cable)

-running the unsigned H-SPL

-trying to "re-start/re-continue" the H-SPL when it seems to be paused by

performing a soft reset

-performing a hard reset, followed by the options describe above

Info about my HD

Country: NL

Model: T8282

Operator: Retail

Provider: Hi (KPN telecom)

Sim: Unlocked

CE & build: 5.2.20757 (20757.1.4.0)

Current ROM: 1.14.404.3 (22273) NLD

ROM date: 12/09/08

Radio: 1.09.25.14

Protocol: 52.49a.25.26U

Bluetooth: 2.0/2.0+EDR

If anyone has any suggestions how to deal with this problem, I'm happy to give it a try of course. Myself, I'm thinking of some sort of USB Comm. issue.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
@ alegator23 & jeroen1801 - Do you receive any error code message?

Have you both tried manual SSPL?

Boot up your phone.

Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.

Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.

When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
[Touch HD Windows Mobile ROM Development] jeroen1801:
Tried, but not succesful....

Hi spartan, thanks for your advice,

I've already tried the procedure you describe, before and after a hard reset.

It doesn't seem to work on my HD. Here's what happens:

-I put SSPL-Manual-TouchHD on my phone via USB cable

-I start the program, it brings the HD into the bootloader

-USB comes into screen (bottom), so this is recognized by the HD

-(Active Sync on my pc no active offcourse, because WM is not running)

-I start-up the HSPLWrapper_Blackstone_156OliNex

-I click trough the menu, and pc/hd show a statusbar which stays at 0%

-After a while, it shows ERROR MESSAGE 262.

While being in the bootloader, the HD indicates:

BLAC100 MFG 32M SS-BC

1.07.OliNex XA

MicroP-BlackStone 9LED) v6

USB

Is this correct? What elso could I try??

By the way, when going through the menu of the HSPLwrapper on my pc, it already shows the name of the ROM I want

to flash lateron (= Mikenificent 2.5), perphase because both files are in the same folder?? Is this a problem? Should I keep

both files in a separate folder??
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Make sure you have HSPL in a separate folder and the ruu & .nbh file for a rom in their own folder.

If your SPL is 1.07.OliNex, generally you should be able to run HSPL.

Reboot phone and put it in bootloader. Once in bootloader connect it to pc via usb, watch bottom of bootloader change from 'serial' to 'usb' and then run HSPLWrapper_blackstone_156OilNex.exe file. It should run. I've heard of people doing aeverything right and having to follow this procedure a few times before it works
[Touch HD Windows Mobile ROM Development] ClydeB1:
ERROR [262] : UPDATE ERROR

This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.

Digital Outcast recommends keeping the various components in separate folders ie HSPl and roms separate. Does Mikenificent 2.5 not have it's own RUU?
[Touch HD Windows Mobile ROM Development] jeroen1801:
Solved!!

Problem solved, THE problem seemed to be:

Placing the HSPLwrapper in a separate folder than the ROM + RUUwrapper.

Then, it fully seemed to work.

Furthermore...when flashing, the ROM, 'dragging the file on top of the RUUwrapper, also didnt seem to work, just opening the RUUwrapper and

letting it find the ROM automatically did the job!

Thank you! Another happy man ! :)
[Touch HD Windows Mobile ROM Development] ClydeB1:
Good news - welcome to the club ;)

I would imagine the RUU got confused as to which .nbh file to use.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Nice one ;)
[Touch HD Windows Mobile ROM Development] DaveShaw:
The RUU will attempt to flash the first NBH file it finds. The Hard SPL wrapper self NBH file and attempts to use that, but I'm guessing it find the ROM's file instead.

Dave