yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ApexPredatorBoids:
At step 12 I ran SSPL.KAIS.exe and the bootloader screen came up like it should. But after that I"m not sure if I have an activesync connection or not when it comes time to run KaiserCustomRUU. I unplugged and replugged the USB cord but the AS icon never went green. According to activesync the phone isn't connected but it does say USB accross the bootloader screen. I continued anyway on to step 13 anyway and ran the KaiserCustomRUU and it went thru the motions like it was properly installed. But now that it's finished I can't get into the bootloader mode to see if it worked. I tried about a dozen times by holding the power and camera buttons while doing a soft reset but all it does it the soft reset..no bootloader. Any ideas?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sl_uk2:
boot loader

there i knack to it hold camera and power buttons together soft reset but keep hold of the other two buttons after you remove the stylus from soft reset bool loader should appear

steven
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ApexPredatorBoids:
No luck so far. No matter what I do it just does a soft reset still.

**Ok I'm an idiot. Apparently you have to hold the camera and power buttons in for like 5 seconds before bootloader shows up. I don't remember having to hold them in that long with my Hermes. Thanks ALOT for your help.**
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] benfica88:
Downgrade Rom?

Ok, so I put the 1.60 at&t from on the device. Tilt came factory with 1.57. It won't let me install the rom without cid unlock...won't this void the warranty?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I'm confused... are you saying you installed 1.60 or are TRYING to install 1.60? If the ROM wasn't supplied by HTC (for AT&T) or by AT&T themselves, you're warranty will be void.

Of course you can always CID unlock your phone (as you allude to) with HardSPL, but that will also void your warranty. Doing anything with "unsupported" ROMs puts you in jeopardy of breaking your phone which is why every cook here has the boiler plate disclaimer about your doing all of this at your own risk.

All of that being said, if you do decide to muck with your phone with these cooked ROMs and HardSPL you can use the process outlined in the first post of this tread to put you back to the AT&T ROM and SPL.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
For you first concern... you do not want an ActiveSync connection after running SSPL on your phone, just unplug and re-plug. ActiveSync should not reconnect (and this is by design).

As for your second question, if your phone boots you have a bootloader, so either you don't have the camera button pressed enough or something else is wrong.

Just something else to try, you don't actually have to do the reset on your phone to get to the BL. Turn off your phone, either by taking out the battery or by holding the power button and selecting 'yes' when prompted. When the phone is off, press and firmly hold the camera button (keep it held). Now while keeping the camera button FIRMLY pressed, press and HOLD the power button. The phone should power on and go directly to the boot loader.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] benfica88:
I wasn't very clear on this. I had to exchange my phone. The problem is I put the 1.60 rom over the 1.57 rom witch isn't yet released or supported. This changed the SPL from 1.08 to 1.93 or something of that nature. Now I can't downgrade to 1.57 rom to return the phone. It says the update is unsoprted... Im getting the feeling that I have to CID unlock it now. I was hoping there was a way around this....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Emblema:
HI,

unfortunately I cannot execute step 7 why to my device does not work the touchscreen, as I can make?

Tanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Same problem, though I don't have to return mine, ran the 1.60 ROM on phone, but trying to revert back to 1.57 as the current binaries for MS Voice Command do not support the new RIL for BT, but the RUU says invalid vendor ID...

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
OK for you guys I think you'll have to install HardSPL, and then follow the directions from the first post in this thread which will revert you back to the shipping ROM and should enable you to revert back to the stock SPL as well.

Let me know how it goes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I'm not sure I understand your question... I assume you're talking about running SSPL-KAIS.exe on your phone. Are you getting any errors, if so, what are they?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Yes, confirmed working, had to HardSPL it in order to take the previous ROM, then had to restore the OEM SPL as explained in post 1, then applied the older ROM, still came up with invalid vendor ID, so something is still wrong... [edit] device reports no service... Must be something to do with the RBL not dropping back down, corrected with a hard reset...

The bootloader is reporting the device is "Kaiser1*0"...

At least I am back to the previous ROM and can run MS Voice Command, the RIL in the 1.60 ROM produced issues when trying to execute from BT headset...

All the use of the USB has caused there to be a problem with the mini USB port (cable not seating correctly), have returned to at&t as this unit was originally an open box, so I have no idea what took place with this unit before I got it...

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Emblema:
Is not possible run SSPL-KAIS.exe, pda is blocked to welcome screen, (toucscreen not respond).

It's possible one solution whit mtty.exe for disable welcome screen or disable overwrite bootloader ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cjmedina:
ok here is my problem, my usb isnt working or charging for that matter.(phone) i manged to flash the phone back to att rom,( the first one) via the transflash card method. my next problem is putting back the orginal spl on the phone instead of the hard spl.

i download the att spl , my question is can i flash it via memory card like i did with the orginal rom? could i drop the att spl on the card and boot it from there? or am i screwed?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Based on previous experience with the Wizard (8125), Hermes (8525), and now the Kaiser (8925), yep, been w/ at&t for a while and still perplexed as to why at&t buggers their ROMS, my guess is POF has only been able to deconstuct the SPL as for now, so he created the bootstrap that will allow write to the device via the SSPL-Kaiser.exe bootstrap... I don't think that your outa luck in the long term, but I think there is some issue regarding dumping or pulling apart the systems IPL, and experience might say that the carriers along with HTC, might not like POF pulling this stuff apart and actually might be a bit embarrassed as to discovery of the olipro IPL on previous devices that included anti-brick utilities. Too bad they take it the wrong way and decide against building the idea into their stuff... :(

For now I think you might be outa luck regarding w/r to your device IPL/SPL without the presence of the bootstrap, which unfortunately is only at the SPL level, and for now requires another machine to execute code for w/r via the USB port...

[edit]Furthermore, it is my opinion that POF has displayed characteristics in programming and ethics that HTC should grant him his own .cer as an asset to the community in favor of the end user. No reason someone should have to hack it to fix it with only limited prospective of just the hex, this has been one of my issues with developers since the start of the Win32 side of network engineering.

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ko0ky:
hey thanks for putting this together. it worked great. Now how exactly do I verify?

thanks again, nicely done.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gf_gollum:
OK - Got a small problem in that the reason I'm returning my TyTNII is that the USB port doesn't want to connect anymore. The USB charge / connect cable doesn't do anything anymore - I've tried 3. I got one to charge - but none of them connect to the PC.

So - How do I do this from a storage card??

Graham
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rock4mayo:
Hello

I just revert back my spl according to instruction on page 1.and i did it

my spl is

KAIS130

SPL-1.56.0000

CPLD-8

I'm using HTC Tytn II

but this evening i saw my friend's HTC Tytn II and his spl shown

KAIS130

SPL-1.81.0000

CPLD-6

So which one is correct for HTC Tytn II users.......

thanks

cheers
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] weinson:
OK -- I am about to try this to go back to the AT&T Stock ROM ... just to confirm, this will bring my Radio back to normal too, correct?

Also, after all is said and done and I verify my SPL, what should I see on the screen?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I don't believe there is a way to flash the SPL from the card. There is a method to flash a ROM but if you've done the HardSPL it will bypass the SPL portion of a complete ROM. I think you might be outta luck. You might try copying the NBH over to your SD (following the instructions available in another post... search is your best bet). But instead of doing the hard reset you would have to run the SSPL-KAIS.exe and hope it starts the flashing process.

Good Luck.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
Correct, if you flash the original ATT ROM it will flash your radio and your OS. Follow the instructions to get the SPL back to ATT OEM status. After you finish the SPL, the bootloader shouldn't mention anything about HardSPL, if it does you did something wrong. I can't remember the exact syntax of what it does say...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
Well, I don't have an HTC version of the phone, I assume that is what you have and what your friend has. If so then it sounds like there's a new SPL in the wild (no big surprise). Until we get an official release of that full ROM (including OS, Radio and SPL) then you can't get back to the version your friend has. If it's coming out on new phones though chances are it should be released eventually.

Cheers,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rock4mayo:
Thanks for your reply...

My friend use ruu_kaiser_dopodasia_wwe_1.81.707.0_radio_sign_22.45.88.07_1.27.12.11_ship

and i just extracted RUU_signed.nbh successfully from that files

and here is the file..

http://rapidshare.com/files/71156279/HTC_SPL1.81.0000.rar.html

cheers.....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
There has to be some kinda glitch with this HardSPL thing or somethin because, I just reverted back to my old OEM ATT Rom & SPL, and now when I tried re-flashing the OEM Rom, I get an "Invalid Vendor ID" error! I've already tried reflashing the oem spl twice to make sure I did it correctly and still no progress! Now its seems the only way I can flash a rom is if I have HardSPL installed. Also in bootloader the information displayed is:

KAIS1*0

SPL-1.56.0000

CPLD-8

a solution anyone?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I think I know what you're getting at but the directions indicate that you need to flash the original ATT ROM (while you are still running HardSPL) BEFORE you revert back to the stock SPL.

So reflash HardSPL, flash the ATT ROM then reflash the ATT SPL using the instructions in the first post.

Cheers,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
Thanks... updating the first post with your link.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Yes thats exactly what i did both times, and i still get the same results!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I'm not sure I understand what the problem is then...

Sounds like you're running the stock ATT ROM and SPL (SPL info you posted matches the version in the "shipped" ROM).

And the only way you're going to be able to flash other ROMs is to use HardSPL, but I think you know this, so again I guess I'm not clear on what the problem is.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
OK this what ive done. I flashed hardspl and a cooked rom onto my device. The rom didnt work well enough for me so I decided to go back stock. I read your guide thoroughly and proceeded with the steps mentioned to reflash the OEM spl. After successfully flsahing the spl from the att stock rom, I attempted to reflash my phone again with the stock rom(not using the customRUU) and in the process, I now get a "Invalid Vendor ID" from the stock ATT kasier rom, and this is file im trying to flash from "RUU_Kaiser_CINGULAR_WWE_.exe"
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
ok... you need to reflash HardSPL.

After that flash the FULL ATT ROM (should be 72MB or so). Boot the phone... let it customize and all that stuff just to make sure you get all the ATT stuff.

Now flash the stock ATT SPL... this has to be done AFTER you flash the ATT ROM and you must use the SSPL-KAIS.exe for it to work.

For good measure, hard reset the device by holding both soft keys and doing a soft reset, and follow the onscreen prompts.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Yep I have done exactly that 3 times, and still no luck!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
its seems like something corrupted my bootloader, so in order for me to flash an upgrade roms from att, i will need hardspl on it!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Yes, I made that observation earlier in the thread.

1 Flash HardSPL

2 Flash AT&T ROM 1.57

3 Replace SPL from 1.57 ROM using SSPL-KAIS.exe

4 Hard Reset

5 Flash AT&T ROM produces 'invalid vendor ID'

Since the SPL is from the 1.57 ROM, I believe the vendor ID is stored in IPL, and flashing the latest ROM modifies or writes a newer IPL and/or AT&T has modified their vendor ID with the Cingular / AT&T merger.

I have looked through the entire kaiser forums in search of version information regarding the IPL, and have come up empty handed, beyond that, the multi color screen in bootloader mode of the kaiser does not show any presense of an IPL, but I know it is there.

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
So actually, if someone was to do a warranty exchange with there phone in this state, then its possible that data tamperment would surface once att run there diagnostics on it! Becareful members!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Yes, this is true, but the Tilt I got was out of an open box with additional ringtones that survived a hard reset when I got it, so, ya just don't know what your getting when you go into a store, you can't 'expect' to get a device that hasn't been tampered with...

It is my belief that the official release of the Tilt ROM will not produce the invalid vendor message...

Beyond that, it would be better for them if they release a radio that is better than the one in the current release, they would probably save themselves a lot of headache flashing devices to put them back out on the shelf...

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
ok thats makes sense! I thought This rom was thee official! and you do have a point, My phone was already setup when i bought mine too! and that would make a good argument if att was to question about tamperment!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Most files available on this site are not official, though current official release files for pretty much all devices are tucked away and linked to somewhere. What you flashed is a leaked rom provided to carriers for testing and debugging purposes, granted the site should have a cookie based opening page disclaimer noting that you take full responsibility for anything you do to your device, on the other hand, I question how many folks have been helped here by a bad flash of an official rom in effect preventing a warranty return, beyond that, the carriers can refer here at any time for a list of bugs in their test roms, in all, I think it is a wash for the carriers in terms of warranty exchange costs, because they can't get accurate results from a heavily controlled test group, they need to know how the ROM will perform in the wild with installed app diversity and minor hardware revisions before they can agree with HTC on a final release, what makes the file official is when you see the updated information on HTC's download page. Now you should understand why it is important to read, read some more, and then some before you attempt the procedures on the site, this is intended to provide you the knowledge to understand what you are doing and prevent you from bricking a device by your own err.

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Just for confirmation, can someone tell me if they have successfully flash this "RUU_Kaiser_CINGULAR_WWE_.exe" ATT tilt stock rom without hardspl?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Thx for that information ?Glitch! Thats definitely something I didnt know!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] davenash:
Would these steps work for an athena (using the relevant rom)?

Cheers,

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I just got a friend's stock (BONE stock) Tilt. First thing I tried to do was flash the "RUU_Kaiser_CINGULAR_WWE_.exe". This failed saying it was not compatible with this phone. I then tried to flash the "unreleased Tilt ROM AKU v.0.4.4" and it is currently flashing fine on the unmodified device (no SPL or ROM changes, prior to this).

So based on this logic, if you remove HardSPL and revert back to the ATT SPL I have linked and you can then flash the NEW Tilt ROM then it could be reasonably assumed that the device's SPL is back to stock.

Again, because you can't flash the "original" ATT ROM after reverting back to the Stock SPL does not mean it's evidence of tampering.

I'll do some more testing before and after I flash HardSPL on this guy to confirm.

Cheers!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
OK after flashing v0.4.4 the SPL reports:

KAIS1*0

SPL-1.93.0000

CPLD-8

I tried flashing back to the "released" ATT ROM and get the same "Invalid Vendor ID" error...

Flashing HardSPL now and will try reverting back to the stock SPL and doing the same install of v0.4.4.

Cheers!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ?Glitch:
Even if you flash back to the 1.57 ROM using HardSPL, and restore SPL included with the 1.57 ROM, when you use the carrier RUU to flash the 1.57 ROM, it will report invalid vendor ID.

Couple possibilities here, either the new RUU updates IPL and/or new vendor id on the AT&T/Cingular merger in IPL, or the vendor ID is stored in SPL and RUU will hexedit upon reading either a valid Cingy or AT&T vendor ID and replace with their new vendor ID, I do not believe they would do the latter, too many ways for things to go wrong with an edit on the fly situation.

Either case, old RUU will not pass the phone after the test ROM has been applied, even if forced back to 1.57 ROM using HardSPL.

?Glitch
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
Alrighty... Flashed HardSPL then reflashed the ATT SPL. As noted by others, the original ATT ROM fails with "Invalid Vendor ID".

However, I can flash the v0.4.4 ROM... so this seems to match the behavior of an unmodified Tilt. I'd call the method described in my first post as pretty much as good as it gets for making your hacked phone "STOCK" again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JasjarMan:
I downloaded this rom listed in the first page: RUU_Tilt_XDA-Live-v1.1_WWE_1.60.502.XDA_No_Radio

But now when I start the camera I only get a black screen. Is there a cab that I can re-install the camera software? This rom is so fast I love it.

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
JasjarMan... I think you posted to the wrong thread. I too love Kyphur's ROMs but I'm not the guy to ask.

However, on your topic, I had that issue once before and just redownloaded and reflashed the ROM and it works perfect. And for the record you want his ROM WITH the Radio ROM, his ROM is based on the AKU v0.4.4 ROM which require the radio be updated with it. The downloaded file should have the filename: "RUU_Tilt_XDA-Live-v1.1_WWE_1.60.502.XDA_With_Radio.exe"

Good Luck!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
one more thing, did your tilt say "KAIS1*0 MFG" on the bootloader screen before ever flasing hardspl? or did it say KAIS130 or 120 or so on?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
I have pics of the screen (no screenshot util)... one sec... Pic below is of a stock Tilt.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Thank you for verifying this with me! but you know what, I think when i flash back to the stock spl, "mfg" is still listed right after KAIS1*0"!

ok I just reflashed again to very if "mfg" was still there, and its not, so nevermind!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
no worries... I took several pictures (with my Tilt :)) during all my testing so I have shots of SPL and "About" screens of the two ATT ROMs and the stock Tilt ROM prior to any tampering.

Let me know if you're curious about any of them and I'll see what I can do to post em.

Cheers.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Thanks once again, and your help is appreciated!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] matrixis2day:
invalid vender id

hi there,

i can not install any ROM. With same I get the error invalid vender id, same just hang with 0%.

I can not install the Hard SPL, because the boodloader mode is the only mode who is working.

thanks in advance for help
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] margatenj:
I just got mine over the Thanksgivings weekend for $149.00 with the $100 rebate ... the premier for me if for the government ...did they expect government employees to be around on the holiday weekend to buy a cell phone!?? and yes the price is back up to where it was before the holiday.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
are you trying to flash a Tilt or TYTN II or MDA? If you are trying to flash a tilt, download the AKU v0.4.4, you can extract the downloaded EXE file with WinRAR... do that and you should have a several files including a "ROMUpdateUtility.exe" and an "RUU_signed.nbh" file.

Put your phone in bootloader mode.

Plug in your USB cable.

Run the ROMUpdateUtility.exe and follow the onscreen prompts.

If this doesn't work, please post the following:

Your Phone Model

The text from your SPL screen

What you did to get it stuck at this point.

Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] BKsFinest:
OK i would go through this whole process if my screen did not go black. It's some type of hardware malfunction and I'm within my 30 days, but I'm wondering when they fix the screen and check the device will it void my warranty and in turn forfeit my refund.

I'm not sure how this process works, Do I have to revert back to att rom and spl before sending my phone back? If so, how can I achieve this without a functional screen?