yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
I bought two Tilts the same day and both had 181007(RC01)/US as the date code.

First unit had D 1.56.00.00 and took HardSPL without a problem.

Second unit had D 1.57.00.00 and always white screens.

So date code does not seem to make a difference whereas display version does.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kinggofg:
One more vote:

I vave a brand new tilt.

D 1.57.00.00

+

white screen

I hope somone figures it out soon. Let me know if I can help.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] chippyhawkeye:
No Tech Skills Here! - Paypal Bounty is Best I can do

I'll donate $50 to whoever figures this one out because I don't think I can offer much help otherwise...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jdmspecdc5:
same thing happens here....d 1.57.00.00

guess gotta wait to flash...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rustik:
Same here

181007(RC01)/US

D 1.57.00.00

Just got it today. Luckily WSOD != bricked, had me worried. =P

Keep us updated if someone is working on it. And keep up the good work :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Later today I will post various tweaked SSPLs here. Guys with WHITE SCREEN problems can try them. Please make sure that your Kaiser/Tilt/Tytn2 is application unlocked beforehand. The procedure will be:

- power down phone

- remove sim and sd cards

- power on and copy over SSPL-xxx.exe to "My Documents" on phone

- run file explorer and then run SSPL-xxx.exe

Hint: remove battery cover for easy powerdown when the device hangs :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
I'm sorry, I don't see the SSPL-xxx.exe?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Didn't I mention "later today" :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Sorry, waiting for the coffee to kick in. Was a little tooo excited to get this working. Can't wait to be rid of the Stock AT&T rom and try a new one. Thanks for your efforts!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Sleuth255:
It seems to me that starting with the spl from a 1.57.00.00 Tilt may be a path to try. I'm assuming here that all sspl versions are adapted from original device spl then patched to bypass CID checks and ROM signatures. This was how we originally envisioned cracking the Hermes and for a long while it remained elusive then suddenly Des released it. I never did learn how he did it...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Already tried that :)

subnet99 dumped his spl and it's byte identical to my spl 1.56

Anyway, the coffee is boiling and i fired up my hexeditor :D

Stay tuned ...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
First try: a patched 0.93

Note: these test versions are only to see if they don't crash, not for rom updating
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Just completed a test. The device pretty much locked up after hitting 'continue' - Battery pull worked fine. Phone fine after boot.

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
white screen or not?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Sorry, no white screen. Device froze at today screen.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Test2: same 0.93 but call to displayinit back in
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Same response as above: no white screen and device lockup.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
What seems like a lockup does not really have to be one. When it shows a frozen screen, wait about 30 seconds and then in activesync disallow usb connections, unplug usb cable and plug it back in.

Then try to connect with MTTY. If you don't have MTTY or don't know how to use it, then after reconnecting usb check in device manager if there is a "windows ce usb device". Also, you should hear the typical ding-dong when you plug the usb cable in again.

Do that for both versions I've posted so far and any subsequent.

Do not forget to allow usb connections before trying the next version.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Test1: AS remains connected when screen lockups. After about 30 to 40 secs later I disabled AS USB conn. pulled the cable and reconnected it. I get a 'USB Device Not recognized error'.

Test2: Same as above.

In both case Device manager reports: Unknown Device

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Okay, thanks for testing. In the next minutes I will post two SSPL versions based on 1.56 (which is your native SPL version)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
No problem at all. Thanks for doing this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
One more version based on 0.93. In this case I've reenabled most of the hardware init routines, but displayinit is bypassed. When I run this version on my kaiser I get a white screen but I can connect with MTTY. Please give it a try.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] plirky:
And the samething for me.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Test3: Screen is off/Possibly Device (but AS is still connected). Disabled AS USB connection. Pulled cable and reconnected it. Heard ding for a usb disconnect but nothing on the reconnect. Can't see the device in Device manager.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DoomedTX:
I had similar results with 93-3. After running the device appeared to be off and AS reported that the phone had been disconnected. Unplugged and got the tone; replugged and got no tone. MTTY reported that it couldn't connect to USB, but to be honest it was my first time using MTTY so I'm not sure if I missed something with it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Hmm, not so many options left I'm afraid :(

Here is the last test for today. These are four SPL 1.56 versions:

1) SPL1.56-1 : hw init and displayinit both not patched

2) SPL1.56-2 : hw init not patched and displayinit patched

3) SPL1.56-3 : hw init patched and displayinit not patched

4) SPL1.56-4 : hw init and displayinit both patched

None of them runs on my "D 1.56.00.00" based kaiser, but perhaps you are lucky.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
OK this is looking good, with SPL1.56-4. No white screen, I get the three color bootloader screen......

KAIS1*0

SPL-1.56.000

CPLD-8
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
Where did POF go? I am wondering why he isn't diving into this since it was first he who release the first HardSPL.. I'm sure he must be busy or something but he is the man when it comes to things like this
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DoomedTX:
1) WSOD

2) WSOD

3) Appeared to lockup while redrawing the screen. I still see "KAISER JumpSPL" and part of the notification window at the top, a blank bar where the Ok button was, and the rest is the File Explorer window that was behind the notification. AS disconnected by itself. Unplugged USB, good tone. Replugged, no tone but "USB Device not recognized" balloon.

4) TRICOLOR!!!!!!!!!!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
But what about usb connectivity?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Nope, no USB connectivity, unfortunately not for me anyways. Bummer :mad:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DoomedTX:
Dang, I was so excited that I wanted to post that result...when I saw someone had beat me to it I stopped messing around. I'll remove the SIM/storage and try again...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Don't despair, we need to dig into the init hw function and hit the right GPIO regs to enable USB. But not today, it's party time :D

PS: are u guys sure there is no usb connectivity with 1.56-2 ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Just checked out 1.56-2. No USB.. Thx
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] small9:
4) SPL1.56-4 : hw init and displayinit both patched

Tri color,, seem to have USB but show up "unknow device" on PC.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Sleuth255:
The question I'm not getting by is this:

What is it about the stock 1.57.00.00 spl that allows it to work with all the initialization code intact if it is byte matched to one we already have? SSPL merely copies the spl code to the correct memory location then runs it. Perhaps there's been a change to the IPL on 1.57.00.00 that only allows SPL to run correctly at init time.... some initialization that preps the hardware for spl. This would be a typical spy vs spy response to XDA developed methods that has been tried so often in the past. I'd expect the TyTN II to get this change soon as well.

Maybe a comparison between ipl on 1.56.00.00 and 1.57.00.00 could reveal something that could be done in the sspl exe before jumping to the spl code itself.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
"D 1.57.00.00" is display controller microcode, the SPL version is 1.56 which is byte identical to the SPL on my "D 1.56.00.00" kaiser :)

The SPL configures all hardware via GPIO and more. It's easy to pinpoint the functions but it is time consuming to make the right patch. But we're gettin there eventually. Fogot to mention, there is no IPL. There is QCPBL -> QCSBL -> OEMSBL and controller microcode. None of these code stages can be altered only by sw patching.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Sleuth255:
Precisely. That's exactly what I said. If it is byte identical as my previous post mentioned, then something else allows it to run at device initialization time. The only program that runs before SPL is IPL. My theory is that the hardware has been changed subtly so that IPL must reset something else before display and hardware resets from SPL are allowed to work. If we can determine what IPL does differently using a byte compare on 1.56.00.00 IPL and 1.57.00.00 IPL then perhaps we can find what this is and do it in the loader code for sspl.

Let me elaborate: I'm saying that the display controller microcode isn't the only thing that's changed in 1.57.00.00. It's merely the most obvious way we can ID the change. Logically this must be the case if a byte identical spl won't run on a device that displays "D 1.57.00.00" when it works just fine on a device that displays "D 1.56.00.00".

Sorry if I'm not making any sense here... I'll keep trying :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
I edited my prev post just after yours. Anyway, the problem is in the ucode of some new display controller. which can be bypassed in the SPL and which I did already. Now we "only" have to enable USB and that can also be solved in SPL :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Sleuth255:
Just something to keep in mind should you find that after you've successfully enabled USB you find that sspl still can't actually flash a different SPL (this may very well be your next hurdle btw). My point here is that a compare of the pre SPL initialization (now 3 programs apparently) code in a 1.56 Tilt vs. a 1.57 Tilt to find differences may well yield something that can be done by the sspl loader before it actually jumps into the spl code. I'm willing to bet it would be in OEMSBL too. ;)

edit:

One thing I've noticed about Kaiser is that HTC's initialization architecture has now been segmented into various provider groups. This appears to be carried into ROM initialization routines traditionally handled by autorun.exe (config.txt) and now (based on your above post) hardware initialization routines traditionally handled by IPL. My theory is being supported by your revelation btw. With Kaiser, some OEM initialization routines can now be handed off to Operators too. AT&T may well have used this to disable sspl. The display issue may well be a symptom, not a root problem.

Let me explain this with a thought experiment: Given this segmentation, imagine how easy it would be to tweak the display microcode to check a gp register during initialization for a certain value and hang if it wasn't there. Now an identical SPL would fail unless the OEM initialization set the registry value beforehand. This strategy would explain all the symptoms we have encountered.

What I'm implying here is that while of course none of the IPL code stages can be altered by sw patching, perhaps something they do can be mimicked by the sspl loader.

again, just iterating an option "B" approach in case its needed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
I don't think there will be any issue patching sspl for ordinary flashing. I know all the usual tricks to bypass sec plus a few more. More importantly I found a method to dump qcsbl and oemsbl and *complete* radio. It requires a (illegal) tool from QC ("QPST memory debug") which can download entire radio sdram (32MB SMI and 8MB EBI). This also has the potential to crack sim unlock for MSM7200 based phones. Will start a new thread about this subject soon.

Cheers

JockyW
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Maknificent:
I ran SPL1.56-4, and it took me straight to the tri-color screen. Does this mean I can flash now? I don't get the "usb device not recognized", I did it it the FIRST time I ran it though. MTTY connects fine. Once a rom finish downloading I will try to flash. I appreciate all your hard work. O btw, if no one can get this to work, I will be selling my Tilt...it's brand new not even 2 days old "as of this date". My original "flashable" tilt screen cracked on me!!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
That's quite surprising. You've got a "D 1.57.00.00" ??

Anyway, to answer your question, no you cannot flash with this one. That requires a few more patches.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hellejoep:
Keep up the good work!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Ready to resume testing whenever you have something.

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
I pray the attached version works. It's pof's original jumpSPL (which is based on SPL 0.92). I've patched it such that it bypasses hw and display initialization. It works perfectly on my "D 1.56.00.00", even get tri color screen and after a few secs it shows USB down in the middle. After you see USB, unplug usb cable and plug it back in. Then it should be possible to flash hardSPL and once that is done you can join the hardc*re flasher community :D

Let me know if it works. If it does I will integrate in a easy to use single package similar to the original distribution.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hellejoep:
I will try it on a new Vodafone device and will let U know ;-)

Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
No joy I'm afraid....

powered down phone

removed sim and sd cards

powered on and copied over SSPL0.92-pof-patched.exe to "My Documents" on phone

run from file explorer and device just appears to hang

I have tried with and without the USB cable connected.

Also unit is application unlocked via registry key.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Too bad :(

I'm afraid I have ran out of time and nearly out of options ...

Will provide 2 more variants of this one in the next minutes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Here they are.

SSPL0.92-1-pof-patched: hw init patched and display init not patched (works on my kaiser with tri-color screen)

SSPL0.92-2-pof-patched: hw init not patched and display init patched (works on my kaiser with white screen)

Fingers crossed ...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Sleuth255:
Can we use this method to dump then compare oemsbl on 1.56 Tilt with oemsbl on 1.57 Tilt?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
SSPL0.92-1-pof-patched: hw init patched and display init not patched (works on my kaiser with tri-color screen) = Same as last test.

SSPL0.92-2-pof-patched: hw init not patched and display init patched (works on my kaiser with white screen) = white screen lock up

One question for you, this weekend your successful test results came from SPL ver 1.56 why are these built on 0.92?

At any rate thanks for all your work!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Unfortunately no, it requires a mfg based spl with support for the "rtask" command.

From your questions I can see we're the same species :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Really too bad, I suppose you are absolutely sure about the lockups.

To your question, SPL1.56 looks like a dead end, but I will have a closer look as soon as I have some time. The nice thing about it is that the patched versions behave equivalent on both the old and the new hw platform. I've tried thousand of patches to get usb running but obviously failed so far. I switched over to 0.92 and noticed that after patching both the calls to hw and display init it still works on my kaiser. I was hopeful it would run on your new kaiser too. It's a shame.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
I am sure I did not get a tri-color bootloader screen :)

I did

NOT

try to connect with mtty. Do you want me to retest any of these three version and try to connect with mtty even though i don't get a tri-color screen?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Hell yeah. What the screen shows is of no importance, what matters is USB connectivity :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Maknificent:
I don't know anything about this, but I do know 1.56-4 got me to the tri-color screen, so are there any patches you can apply to that one? I'm truly not worried about it anymore, since I've traded my tilt for another one, which is flashable :P...but maybe it could help the others
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Just cheked out :

Originally Posted by subnet99

SSPL0.92-1-pof-patched: hw init patched and display init not patched (works on my kaiser with tri-color screen) = Same as last test.

SSPL0.92-2-pof-patched: hw init not patched and display init patched (works on my kaiser with white screen) = white screen lock up

#1 - Same results. No USB connectivity - Device not recognized

#2 - Same results. No USB connectivity - Nothing
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
Testing prerequisites:

application unlock phone via registry key

powered down phone

removed sim and sd cards

make sure usb is disabled in activesync

power phone and cable with usb

test usb connectivity with mtty

test 1

powered on and copied over SSPL0.92-pof-patched.exe to "My Documents" on phone

run from file explorer and phone appears to hang

test usb connectivity with mtty = my XP system BSODed here

test 1 continued after restarting XP

powered on and copied over SSPL0.92-pof-patched.exe to "My Documents" on phone

run from file explorer and phone appears to hang

test usb connectivity with mtty = USB port cannot open

test 2

powered on and copied over SSPL0.92-1-pof-patched.exe to "My Documents" on phone

run from file explorer and phone appears to hang

test usb connectivity with mtty = USB port cannot open

test 3

powered on and copied over SSPL0.92-2-pof-patched.exe to "My Documents" on phone

run from file explorer and screen goes to white and phone appears to hang

test usb connectivity with mtty = USB port cannot open
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
There are too many things that can go wrong when testing usb connectivity with MTTY. The best thing is to unplug usb cable, plug it back in and then check in device manager if there is a Usb CE device (I have to look up exact name and will post it later)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
Windows USB CE Devices

HTC USB Sync

Under normal conditions the above is what I see.

I will test all three again shortly and post my results.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] subnet99:
Testing prerequisites:

application unlock phone via registry key

powered down phone

removed sim and sd cards

make sure usb is disabled in activesync

power phone and cable with usb

test usb connectivity looking in device manager for Windows USB CE Devices....HTC USB Sync

test 1

powered on and copied over SSPL0.92-pof-patched.exe to "My Documents" on phone

run from file explorer and phone appears to hang

unplug, wait, replug usb cable and check device manager = no Windows USB CE devices

I do get a popup from the tray stating USB device not recognized

have device manager scan for hardware changes = no Windows USB CE devices

test 2

powered on and copied over SSPL0.92-1-pof-patched.exe to "My Documents" on phone

run from file explorer and phone appears to hang

unplug, wait, replug usb cable and check device manager = no Windows USB CE devices

I do get a popup from the tray stating USB device not recognized

have device manager scan for hardware changes = no Windows USB CE devices

test 3

powered on and copied over SSPL0.92-2-pof-patched.exe to "My Documents" on phone

run from file explorer and screen goes to white and phone appears to hang

FYI, Windows USB CE Devices....HTC USB Sync disappears before unplugging cable

unplug, wait, replug usb cable and check device manager = no Windows USB CE devices

No device not recognized popups

have device manager scan for hardware changes = no Windows USB CE devices
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Ok well done subnet99 and ptukhar.

During the day I got a few ideas which I will implement with SPL1.56.

Please check back t'morrow.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] violato:
thanks for your work jocky. I hope we can get this issue resolved. i hate seeing that white screen!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] vadarius:
I got one of the O2 Stellar yesterday with the SPL1.82 and it got stuck on the white screen as well... any idea?????
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mfrazzz:
Have you even read this thread or are you just posting to post? There are things they are asking people to try so they can figure out whats going on and a solution for it. So you might be able to help by following the posts in here where they are doing testing instead of asking questions and putting a bunch of question marks after it (implying impatience on your part).

So offer assistance, donate to the guys doing the work around this (guys like jockyw2001 and others in here that are looking into this) and don't demand a solution with a bunch of question marks on a lame question. People working on this are volunteering their time to help the community. A solution will come when its found, and won't be sped along by demanding one because someone got a new phone and can't flash it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] unc-newbie:
I am also running the same version other people are talking about and got the white screen.

ROM Version: 1.57.502.2

ROM Date: 08/25/07

Radio Version: 1.27.12.11

Protocol Version: 22.45.88.07H

181007(RC01)/US

I have tried running the kaiser-HardSPL.exe and following all steps as described in one of the threads. Also tried removing my sim card and still a no go. That is the only suggestions that i had read about doing.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ptukhar:
Cool. Many thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hellejoep:
Thanks, will also check this!