There are now a large selection of Kaiser Hard SPL's floating about. I am making this thread as a collection for all of them and the instructions for flashing them.
Explanation
WM Version - Different SPL's perform better depending if you are running WM6.0 or WM6.1. If you are using a WM6.0 ROM, you should be using a WM6.0 Hard SPL (v1 is recommended). If you are using WM6.1 any 3.* SPL is recommended.
Hard SPL Version - Most WM6.1 ROM's are based of a 3.* release by HTC / ATT. The 3.* Hard SPL version should match this the best it can.
MFG - Manufacturing. This SPL supports more commands (such as rtask a)
jockyw2001 - Any Hard SPL made by jockyw2001 (WM6.1 versions)
cmonex - Any Hard SPL made by cmonex.
DaveShaw - Any bootloader patched by me. Will be the same as cmonex's because I copied her changes from previous versions - all credit to her .
Force USB - These SPL's have a fix to force the USB to work if it is not working for some reason.
nostuckinSPL - These SPL's have a fix to prevent you getting stuck at the bootloader as often.
Versions
Windows Mobile 6
-Hard SPL V1 (1.00.OliPof) [MFG] by pof / Olipro - Download and Instructions in the linked thread.
-Hard SPL V1.1 (1.1.JockyW) [MFG] by jockyw2001 - Download and Instructions in the linked thread.
-Hard SPL V1 nostuckinSPL Force USB [MFG] by cmonex - download only.
Windows Mobile 6.1 - All links are to the downloads, instructions to follow.
jockyw2001 (.hard)
3.07 Hard SPL / Force USB
3.28 Hard SPL / Force USB
3.29 Hard SPL / Force USB
3.56 Hard SPL / Force USB
cmonex (.hard2)
3.29 Hard SPL nostuckinSPL / Force USB
3.31 Hard SPL nostuckinSPL Force USB
3.56 Hard SPL nostuckinSPL / Force USB
DaveShaw (.hard)
3.34 Hard SPL nostuckinSPL Force USB
Instructions
If this is your first time flashing an SPL, take some time to read up on the other stickies (mskip's in particular) and wiki pages, this is more of a reference thread.
How to Install A Hard SPL:
Plug the device into your PC
Copy JumpSPL (either 1.56, 1.93 or 1.94) to your device.
Take out your SD card & SIM Card.
Run Jump SPL on your device
Wait for the bootloader screen to appear and "USB" to show.
Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
Run KaiserCustomRUU.exe and flash the SPL
If you have problems with the above process, try this:
Download the attached files from the first instructions
Pull out the battery and reinsert it (this step *is* important)
Connect your PC to phone with a USB cable
REMOVE SIM and SD CARDS !!
Copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe and if you still get a white screen then reset your device and now try JumpSPL1.94-KAIS.exe
After a few seconds "USB" appears on the phone display
Unplug and replug the usb cable
Deselect "Allow USB connections" in Activesync connection settings
Now flash hardSPL (run KaiserCustomRUU.exe on your PC)
Notes:
With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)
Upgrading SPL via SD Guide - Only works if you already have Hard SPL.
Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
Download the SPL you want to flash from the links above.
Rename the NBH file you downloaded to KAISIMG.nbh.
Download KAISDIAG.nbh from here.
Insert the microSD Card into the phone
Hold in the Power and Camera buttons, then press the reset button with the stylus for about 3 seconds until the BootLoader screen appears
It should say Loading / Update in progress and then to a screen saying SPL 1.00.OliNex
It should now say Press Power Button to flash or just flash the KAISIMG.NBH and then reset
At this point it should boot to the OS, if it doesn't then flash an OS (delete the previous KAISDIAG.NBH and KAISIMG.NBH from the SD Card and use Flashing Rom from MicroSD Card method)
After the Operating System loads, DELETE the KAISDIAG.NBH and KAISIMG.NBH files
FOR ANYONE WITH QUESTIONS ABOUT WHAT THIS IS FOR, WHY YOU WOULD NEED IT, OR HOW TO PERFORM SPL PROCEDURES: Read This Wiki page
FAQ (Not 100% applicable to this but a good source).
Thanks (in order of appearance)
pof
Olipro
jockyw2001
cmonex
Kyphur
mskip
I'm off home now I might not be back on for a while.
Post any problems here and I'll update / clean up this thread when I get home.
Ta
Dave
Very nice! Thanks for putting it all in 1 place!
Removed. I flashed 3-4 times and it finally took. Thank you for your help. Anyone else have a preference on a HARD SPL?
Hyden121 said:
Removed. I flashed 3-4 times and it finally took. Thank you for your help. Anyone else have a preference on a HARD SPL?
Click to expand...
Click to collapse
Was just about to reply. Glad you sorted it. I've had problems changing SPL before. The second set of instructions using Jump SPL worked. Also cmonex's KAISDIAG.nbh method works everytime.
I'm using 3.34 Hard SPL for 2 reasons.
1. The ROM I'm using is is based on the 3.34 ROM.
2. I made it (with cmonex's help ).
Dave
I saw that. I am using it as well but was curious if the 3.56 SPL was better in anyway. Either way it is great to finally have a new SPL and it only took me 1 year.
thanks dave! i've flased it and all seems well. my keyboards only have 2 keys you have to press a bit more firmly than the rest rather than 9 with 3.29 so that's much better!
had trouble flashing via customruu so did the microsd card thing. kinda weird though, last night, i couldn't get the microsd approach going with 3.29cmonex. so i flashed via customruu and it worked. now with 3.34, i couldn't get the customruu to work, so i did the microsd approach. anyway, so long as it works!
Thanks DaveShaw, you've really helped new-to-Tytn2 people like me a lot. A good beginning to the ROM experiencing journey
3.34 hardSPL tested ok for my kaiser,thanks to Daveshaw.
nice post, can anyone post his/her experience with the SPLs, meaning if better speed, battery life,....etc
thx dude
Could you explain what is the major advantage of using your 3.34 HardSPL toward to the other Hard SPLs?
I still have no idea about those HardSPLs differences so I'm using latest(? 3.54).
Thank you.
kurobosi said:
Could you explain what is the major advantage of using your 3.34 HardSPL toward to the other Hard SPLs?
I still have no idea about those HardSPLs differences so I'm using latest(? 3.54).
Thank you.
Click to expand...
Click to collapse
All Kaiser ROMs (Cooked or not) are based on a Official release (some cooked roms are based on more than one). Here's a list of the official releases: Kaiser ROMs.
You'll notice the version numbers are all 3.* for the WM6.1 ROM's. People have noticed if you are using the SPL version that matches your ROM version you get less screen freezes.
Sometimes you can't match them perfectly, so a little trial and error can help you find the best match.
Hope this helps.
Dave
DaveShaw said:
All Kaiser ROMs (Cooked or not) are based on a Official release (some cooked roms are based on more than one). Here's a list of the official releases: Kaiser ROMs.
You'll notice the version numbers are all 3.* for the WM6.1 ROM's. People have noticed if you are using the SPL version that matches your ROM version you get less screen freezes.
Sometimes you can't match them perfectly, so a little trial and error can help you find the best match.
Hope this helps.
Dave
Click to expand...
Click to collapse
great work dave but i have to ask something...
is there such a thing as the ultimate spl? meaning it's a bit troublesome to keep changing spl's based on the original builds of our cooked roms...since they keep coming from different sources...
from ur experience, which spl is the stablest with the newer cooked roms..
i've been using cmonex's 3.29 since it came out and to me it seems compatible with any rom i throw at it...
is ur 3.34 the new 3.29 hard2?
mazin13 said:
great work dave but i have to ask something...
is there such a thing as the ultimate spl? meaning it's a bit troublesome to keep changing spl's based on the original builds of our cooked roms...since they keep coming from different sources...
from ur experience, which spl is the stablest with the newer cooked roms..
i've been using cmonex's 3.29 since it came out and to me it seems compatible with any rom i throw at it...
is ur 3.34 the new 3.29 hard2?
Click to expand...
Click to collapse
No idea. I've been using it for a while now but I don't flash cooked ROMs much at the moment
Try it for a bit and it you like it keep it
Only cmonex knows what's going on inside the SPLs.
Ta
Daev
Great work dave, seems you are quite good in organising things, Was missing such a nice piece of thread & must have started had I been so much in to it. Thanks again. Good luck.
DaveShaw said:
There are now a large selection of Kaiser Hard SPL's floating about. I am making this thread as a collection for all of them and the instructions for flashing them.
MOD EDIT Snip...
Click to expand...
Click to collapse
Hi! I have weird problem with HTC Kaiser (or HTC TyTn II).
At the boot of Windows Mobile 6.1 i got the message "the device is clearing storage..." and then the device shutdown, the right led is stuck in blue and when I try to Upgrading SPL via SD my phone stuck at white screen and said loading...
I'm confused so I write this problem here. everything I do fails including mtty process. what can i do, help me please.
Thanks for advice.
Greetings!
neilus said:
Hi! I have weird problem with HTC Kaiser (or HTC TyTn II).
At the boot of Windows Mobile 6.1 i got the message "the device is clearing storage..." and then the device shutdown, the right led is stuck in blue and when I try to Upgrading SPL via SD my phone stuck at white screen and said loading...
I'm confused so I write this problem here. everything I do fails including mtty process. what can i do, help me please.
Thanks for advice.
Greetings!
Click to expand...
Click to collapse
Sound's like the ROM is at fault rather than SPL.
Try a hard reset, if that doesn't work, try flashing a new ROM via the bootloader.
Thanks
Dave
DaveShaw said:
Sound's like the ROM is at fault rather than SPL.
Try a hard reset, if that doesn't work, try flashing a new ROM via the bootloader.
Thanks
Dave
Click to expand...
Click to collapse
Hi Dave, thanks to reply, as I said I think I try everything and everything I do fails including mtty process, I try flashing a new AT&T ROM via usb cable at the BootLoader screen and the process completed 100% and when restart of Windows Mobile 6.1, I got the message "the device is clearing storage..." and then the device make a strange "sound" and shutdown, I was Tried a hard reset, doesn't work, I tried flashing a hardspl via the bootloader but unsuccessful, when I try to Upgrading SPL via SD my phone stuck at white screen and said loading.... when I try to Upgrading SPL via SD with the same SD to another phone its work.
Thanks.
@neilus,
Since Dave mentioned ROM issue, I suggest you re-download again the ROM (just to make sure you got it clean and good) and re-flash. What was your O/S or ROM before flashing? The SPL is important to match the ROM version .. if you're from 6.0, then you need to flash a ROM that comes complete with SPL (such as OEM upgrade ROM)
Otherwise, go back to starting point and read through the newbies guide and this (especially for your stuck on white screen)
anagarika said:
@neilus,
Since Dave mentioned ROM issue, I suggest you re-download again the ROM (just to make sure you got it clean and good) and re-flash. What was your O/S or ROM before flashing? The SPL is important to match the ROM version .. if you're from 6.0, then you need to flash a ROM that comes complete with SPL (such as OEM upgrade ROM)
Otherwise, go back to starting point and read through the newbies guide and this (especially for your stuck on white screen)
Click to expand...
Click to collapse
Hi anagarika, look this:
model : KAIS1*0
SPL-1.93.0000
CPLD-8
I was flashing a new ROM via the bootloader, original AT&T rom, everything work fine at the flashing process and finish 100%, when the unit charge and swich on going to first windows logo screen and with sound switch itself off (the sound is named "LB" I think).
Thanks a lot.
Related
Many of you are eagerly waiting for this: HardSPL v3.07, v3.28, v3.29 and v3.56...
Run a SSPL (aka JumpSPL) and then flash the HardSPL.
Practically all questions are answered in kyphur's excellent F.A.Q. in the next post
Brought to you by JockyW
Have fun !
EDIT:
* The "force USB" versions are only for a tiny minority who have USB connectivity issues.
* SPL3.56 is part of the latest AT&T Rom which is dated June 6. 2008
* SPL3.07 was included in a recent Vodafone RUU.
F.A.Q.
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
If you have problems with the above process, try this:
1a. download the attached files
1b. pull out the battery and reinsert it (this step *is* important)
1c. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe or JumpSPL1.94-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
Notes:
With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)
FOR ANYONE WITH QUESTIONS ABOUT WHAT THIS IS FOR, WHY YOU WOULD NEED IT, OR HOW TO PERFORM SPL PROCEDURES: Read This Wiki page
Q: Can I use with with Wizard/Hermes/"Insert other device here"?
A: No, this is only for Kaiser/TyTN2/Tilts.
Q: Do I have to use Jump/Soft SPL?
A: Yes.
Q: Do I have to install HardSPL v1.x before installing HardSPL 3.x?
A: No, you can follow this process to install HardSPL 3.x on a factory device without ever installing HardSPL 1.x.
Q: Will I have to reflash my OS/Radio or set-up my software again after flashing this?
A: No, changing SPL doesn't touch either the Radio or OS.
Q: Do I have to use this BEFORE I flash a WM 6.1 Rom?
A: Not really, you can flash it before or after upgrading the OS/Radio to WM 6.1 but you may experience "Screen-Freeze" until you upgrade your HardSPL.
Q: Since this is SPL for HTC Branded Devices will it work with AT&T's Tilt?
A: Yes.
Q: Does this SPL support AT Command Mode?
A: No.
Q: Does the 3.2x HardSPL support "Task 2a" via MTTY?
A: No, HTC took it out.
Q: What is the difference between this & HardSPL v1.x?
A: HardSPL 3.x should be used with WM 6.1 Roms, HardSPL 1.x should be used with WM 6.0 Roms. Both HardSPL prevent you from accidently flashing a new SPL (you must use Jump/Soft SPL for this) and SuperCID your phone.
Q: What is the difference between 3.28 & 3.29 SPL?
A: Just speculation at the moment but there appears to be a minor change, possibly a hotfix. Both SPLs seem to work fine with all models & WM 6.1 Roms but 3.29 is included in the AT&T Rom and a few of the HTC Roms.
Q: Should I install 3.28 or 3.29?
A: Honestly it probably makes little difference but you can always check the SPL that shipped with the rom (or BaseRom if using a cooked Rom) you are running. I have AT&T Tilt running my Rom (using AT&T 3.51 Base) with 3.28 and have no problems including screen-freeze. Note: some members recommend 3.28 for HTC Roms & 3.29 for AT&T Roms.
Q: Does this HardSPL fix the "Screen-Freeze" in WM 6.1 Roms.
A: Yes, everyone using the new HardSPLs has reported it resolved the issue.
Q: What about WM 6.0 Roms?
A: Some users have reported having the "Screen-Freeze" issue on WM 6.0 Roms and fixing it with the New HardSPL. It's worth a try but definately recommended to use the same generation SPL & ROM in most cases.
Q: What about "Diamond" Roms?
A: As the Diamond Ports are WM 6.1 Roms and the SPL has the same effect, eliminates "Screen-Freeze".
Q: What was the cause of the freezings with the older hard-spl and what did you do to fix this
A: SPL initializes a lot of subsystems (power management, touch screen, lcd, etc). The newer SPL probably has contidional code that would handle variations in hardware (if they exist). I'd also think that the 3rd gen SPL would be geared more towards the 3rd gen OS & Radio needs which would explain the fix working as well as it does. Reminds me of the Wizards days when we were running 2nd & 3rd gen OS but had to stick to lower radios because we were intentionally not upgrading SPL (due to HTC Locks & such in the 2nd gen SPL).
Q: Can I flash this via SDCard?
A: Technically, you should be able to BUT flashing SPL is a "dangerous" process for your phone so you really should use KaiserCustomRUU.
Q: Where can I get Jump/Soft SPL?
A: http://forum.xda-developers.com/showthread.php?t=354061
Q: I can't flash a cooked Rom after installing 3.x.Hard SPL, help.
A: See the next question, if you didn't successfully change to SPL03.2x.Hard then try again.
Q: How can I be sure that I've successfully changed to SPL-3.x.Hard?
A: Get into your Bootloader (hold down camera+power buttons while inserting stylus for approximately 3-5 seconds). It should show SPL-3.28.Hard or SPL-3.29.Hard on the second line of text on your screen. If not then you didn't flash the new HardSPL, try again.
Q: Using Jump/Soft SPL shows "unknown device" when hooked up to usb.
A: Try the SSPL attached to the first post.
Q: Could you clarify what the "Force USB" does?
A: Some users managed to nuke configuration parameters which determine the default connection mode. They are stuck in serial mode. The "force usb" version of SPL corrects this. Of course it would be better to figure out which parameter(s) are at fault and correct these, but that would take time and experiments and more over a higher risk to really brick a device.
Q: I'm stuck in the Bootloader (Tri-Color) Screen with "ruunbh" text in the upper right corner.
A: To get rid of the RUNNBH error:
Download an ORIGINAL (not cooked ROM) for your device from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs
Choose one appropriate for your device (AT&T tilt / HTC TyTnII). 6.0 or 6.1 shouldn't matter.
Download that and flash it...it should work and get you back to a working phone. Then you will have to try the HardSPL procedure again.
Q: Does this "Security Unlock" my Phone?
A: No, Security Unlocked is something different from HardSPL.
Check here on how to do a security unlock: http://forum.xda-developers.com/showthread.php?t=361236
Here are the files that you will need to do the process:
http://www.4shared.com/file/46447471/7ae96b57/Jockyw2001_HardSPL_-_SuperCID.html
Just follow the steps in the supercid. I have included the .txt file that Jockyw2001 included.
Be sure to flash the "SPL-1.1.JockyW" as the process won't work while SPL-3.2x.Hard is installed.
Q: Where did my post in this thread go?
A: All useful information was consilidated into this single post. Everything else was deleted.
Troubleshooting:
When all else fails, try these...
Use a Windows XP Machine (not VISTA).
Delete all USB peripherals and root hubs from Device Manager, reboot, let everything be re-detected, reboot again and then plug your Tilt in again.
Make sure you have removed both the SDCard and your SIM Card.
HardSPL v3.29.0000 added
HardSPL v3.29.0000 added.
I don't know which one is better. The version number tells me that they prolly hotfixed an error in 3.28.
Enjoy!
hey Jocky! I kinda miss the SPL-1.1.JockyW tag in your SPL, lol.. donation coming in as promised!
Confirmation number: 6CM53141XF789163M
pfcsabre said:
hey Jocky! I kinda miss the SPL-1.1.JockyW tag in your SPL, lol.. donation coming in as promised!
Confirmation number: 6CM53141XF789163M
Click to expand...
Click to collapse
Thanks! First donation from 'old europe'
Work worthy of donation!!
New SPL has done the trick and eliminated the laggy freezes in L26 v3 for me!
Many thanks jocky......worthy of the small donation (Paypal Confirmation number: 99A446736N006110A) that I can afford and great stuff!
FAQ Updated, thread cleaned...
I'll be leaving Kudos, Donation notices & such after this but all Question/ Answers will get cleaned & integrated into the FAQ.
BTW, Jocky had mentioned that North America as consistantly been the lion's share of support for his work . I do encourage everyone who uses this to send a little something his way as it does take both time & skill to provide these tools. Even a couple of bucks goes a long way to show your appreciation.
kyphur said:
I'll be leaving Kudos, Donation notices & such after this but all Question/ Answers will get cleaned & integrated into the FAQ.
BTW, Jocky had mentioned that North America as consistantly been the lion's share of support for his work . I do encourage everyone who uses this to send a little something his way as it does take both time & skill to provide these tools. Even a couple of bucks goes a long way to show your appreciation.
Click to expand...
Click to collapse
Chaulk another one up for North America, donation sent, thanks Jocky!!!
Confirmation number: 7YH40824J6586891R
Donations
Just making sure N. America stay on top!
Nightly Thread Maintenance.
FAQ Updated....
Posts removed....
it worked!
worked without any issues...i did the 3.29 on dutty rom even doh i should do htc but reviews show little difference and i have att phone ... reponse is slight better i know for sure...but not AMAZING like people saying...will keep u updated!
Seems like Kyphur is a bit fast on the delete button
Anywhoo, just wanted to re-post that I've sent a small donation off to JockyW.
Unique Transaction ID #56B84509V76451713
Thanks for everything and keep up the great work!
_Alex_ said:
Seems like Kyphur is a bit fast on the delete button
Anywhoo, just wanted to re-post that I've sent a small donation off to JockyW.
Unique Transaction ID #56B84509V76451713
Thanks for everything and keep up the great work!
Click to expand...
Click to collapse
Hehe...Kypher would it be better to just lock this thread?
Mass deleting posts just doesn't sit well with me either.
probably less work for you too.
your call
Thanks, worked well as well. Now no freezes.
Kudos to kyphur for perfect moderation and orchestration of this thread and to all who donated of course. The fact that nearly all donations are from north-america is prolly because these SPLs are solving the AT&T rom issues.
Whatever, I appreciate it!
Yeah great work!! sure to donate..
It works like a charm. Happy to donate.
From the Netherlands 4M744925453729221
gqstatus0685 said:
Ok what I show is:
KAIS*0 MFG
SPL-1.0.0liPof
CPLD-8
I installed this L26 diamond V5 onto my device and it says includes newest version 3.29. Freezes like crazy and very annoying. I know it's fixable.
Click to expand...
Click to collapse
You didn't successfully install 3.2x.Hard SPL, you're still on the 1.0 version.
Try again, read the FAQ carefully, everything you need is (should) be there.
gqstatus0685 said:
Ok what I show is:
KAIS*0 MFG
SPL-1.0.0liPof
CPLD-8
I installed this L26 diamond V5 onto my device and it says includes newest version 3.29. Freezes like crazy and very annoying. I know it's fixable.
Click to expand...
Click to collapse
Your bootloader screen should show:
KAIS100
SPL-3.28.Hard
CPLD-8
or SPL-3.29.Hard if you've used 3.29.
Donation made!
confirmation nr. 9A097724M3643491F
Has anyone successfully flashed via microsd? My USB port has been dead for awhile now.
I'd like to fix my freezing problems.
Friends,
I read through the faqs, instructions, and did my research. Still, there are a few questions.
I have been successful in upgrading to Gullum's diamond rom which is awesome btw. Now, I am on the prowl checking out other roms from the other authors.
Each time I perform the hardspl which successfully goes through w/no glitches . At the bootloaded screen (tri-color) it shows KAIS1*0 MFG SPL-1.0.OliPOF.
Shouldn't it read HARDSPL Version 3.? after the spl update?
Basically, in a nutshell this is what I did:
1. CID unlock program "kaiser- CID Unlocked
SPL01.0 OLIPOF
2. HardSPL Version (per authors instruction)
3. ROM Upgrade.
Please advise for the advance instruction,
Tvos
Did you jumpSPL before you upgrade to HardSpl 3.xx?
If not, search for JumpSPL!
Also, you dont need to CID unlock everytime. just once is enough.
I agree, it must be the jumpSPL. Jocky's thread is stick in the ROM development.
ditto this happened to me and jumpspl was the answer
no, i didn't use jumpspl before hardspl..
I actually used hardspl 3.56 with Laurentius26 and everything works beautiful!
w/o jumpspl..
All the steps are pretty basic, but question on the following:
1b. pull out the battery, REMOVE SIM and SD CARDS !! and reinsert battery (this step *is* important)
2. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
** When I copy the .exe to my device, is it to the storage card? Previous step states to remove sim,sd card, and battery.
** If I install JumpSPL1.56 successfully, I don't need to install 1.93 correct?
6. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
7. After I run KaiserCustomRUU.exe, then I should be able to run
HardSPL v3.07, v3.28, v3.29 and v3.56 - per authors instruction.
8. Reload the authors ROM.
Is this correct?
please advise and thank you!
tvos
You copy the JumpSPL onto your device memory!(becuase you have already removed your SD card)
When you install JumpSPL 1.56 without anyproblems then you dnt need 1.93, correct.
Then run HARDSPL 3.xx...
Flash your rom.
tried JumpSPL1.93-KAIS.exe, then SDA application lock still nothing..
okay - did all that and KAIS1*0 MFG SPL-1.0.OliPOF still shows.
any ideas?
tvos
tvos said:
tried JumpSPL1.93-KAIS.exe, then SDA application lock still nothing..
okay - did all that and KAIS1*0 MFG SPL-1.0.OliPOF still shows.
any ideas?
tvos
Click to expand...
Click to collapse
let me ask .. when you first tried to hardspl did you run into whitescreen? if so you probably need to use the same version of jumpspl 1.56 or 1.93 that you used to get past whitescreen. Secondly once you have copied the jumpspl file to your device you have to run it from there.
Hope this helps.
p.s. glad to see you got the rom flashed .. sorry couldn't respond sooner
Hello...
I own the AT&T Tilt and first used app to unlock the device,sid, cid etc.
HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)
Everything ran fine when updating the rom.
After that, I then ran hardspl thinking that it updated the spl but didn't. After that, moved on to Gullums, Laurentias, and Dutty's rom (testing each one). No problems flashing, however it's not the correct hardspl installed.
So I decided to post and see what could be done to get the correct hardspl on there.. I have tried everything with jumpspl (both versions) and didn't take. I tried this about 4-5 times - nada.
I noticed that HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free) stated for Kaiser, but I own the tilt. Does that matter?
ANy ideas would be appreciative.
Tvos
tvos said:
Hello...
v1 - CID Unlock & Flash any ROM to your device (4 free) stated for Kaiser, but I own the tilt. Does that matter?
ANy ideas would be appreciative.
Tvos
Click to expand...
Click to collapse
no it doesn't as they are the samething except the tilt lacks the front camera. i don't know why u are having problems. using jumpspl i have switched between all of these newer spls provided by jockyw... hmm
tvos said:
no, i didn't use jumpspl before hardspl..
I actually used hardspl 3.56 with Laurentius26 and everything works beautiful!
w/o jumpspl..
All the steps are pretty basic, but question on the following:
1b. pull out the battery, REMOVE SIM and SD CARDS !! and reinsert battery (this step *is* important)
2. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
** When I copy the .exe to my device, is it to the storage card? Previous step states to remove sim,sd card, and battery.
** If I install JumpSPL1.56 successfully, I don't need to install 1.93 correct?
6. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
7. After I run KaiserCustomRUU.exe, then I should be able to run
HardSPL v3.07, v3.28, v3.29 and v3.56 - per authors instruction.
8. Reload the authors ROM.
Is this correct?
please advise and thank you!
tvos
Click to expand...
Click to collapse
OK. First off, if your bootloader shows you as having an SPL or **Olipof then you have a HardSPL installed. You can then flash to your hearts content. Second, you don't need to flash HardSPL ever again, unless uprading the HardSPL that is. All you need to do is download the ROM and then flash it.
JumpSPL is only used when uprading SPL number that is all. If you install a HardSPL and bootloader says **Olipof or whatever then HardSPL is installed. After this only update the ROM by downloading a new one and flashing........
Hmm,
if it's any consulation, so far I like Laurentius rom...
I will keep trying - just to refresh the steps.
1. remove battery, sim, storage card,
2. insert battery, usb
3. install JumpSPL1.56-KAIS.exe
4. remove usb, re-insert and then run flash hardspl
5. install hardspl version 3.x
correct?
tvos
The steps you have mentioned are correct FOR UPDATING THE SPL VERSION. you dont need to go through this every time. Once HardSPL is installed it stays installed, even after a ROM flash........
If you use the original HardSPL, bootloader shows SPL as 1.0Olipof or something. If you install a newer HardSPL it shows as SPL: 3.28, 3.29 etc Hard.
If you are unsure, go into bootloader and see what SPL version your phone is at. If it shows 1.0 Olipof, 3.28 Hard, 3.29 Hard or [anything else] Hard then you have a HardSPL installed and can flash ANY rom you like. Only one exception to this. DO NOT flash an HTC ROM after HardSPL or you MAY need to re-flash HardSPL before changing it to a cooked one at a later date.
I thought after running "HTC Hard SPL V1 CID Unlock - POF" I then needed to run HardSPL 3.xx.xx . After that, I could upgrade to what ever rom I choose?
If so, I guess that I'm done...
tvos
tvos said:
I thought after running "HTC Hard SPL V1 CID Unlock - POF" I then needed to run HardSPL 3.xx.xx . After that, I could upgrade to what ever rom I choose?
If so, I guess that I'm done...
tvos
Click to expand...
Click to collapse
If you run V1 CID Unlock - POF, check the bootloader for the SPL version. If it says 1.0 Olipof, i think it is anyway. If Olipof is showing in the SPL field of the bootloader then you have version 1 of the HardSPL installed and can flash any ROM. The updated HardSPL's ie 3.28, 3.29 etc are only to try to help with a few minor bugs that some ROM's have. I currently have 3.29 installed on my Kaiser and the Diamond ROM installed and all works like a charm. Any bother give me a shout.
going offline to get some food. Back on later. Good luck. If your bootloader shows Olipof, get a ROM flashed for god sake........lol
DO NOT flash an HTC ROM after HardSPL or you MAY need to re-flash HardSPL before changing it to a cooked one at a later date.[/QUOTE said:
are you talking about a HTC rom released from the HTC for a release update?
right now, i have been using Laurentias rom and I like it a lot! only thing I hate is when the backlight goes dim.. I know there is a hack for that..
I'd like to find a rom that is bare bones, at&t, outlook, office, bluetooth, gps all included then I can start working my way in building it.
I think someone said Rotohammer's rom was built this way?
THank You for all the help!!!
Tvos
Click to expand...
Click to collapse
OK, I am not sure if this is your problem after this long of a thread...
It looks like you are trying to jumpspl 1.56 over hardspl. Instead, run sspl-kais.exe on your tilt after you have removed your cards. Then on your computer, run the customruu with the desired hardspl version.
in kyphurs words:
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
You may have tried this, but it might be that you are just using the wrong jump spl. I have not used the 1.56 version since I don't need it but I think it is for people that can't hard spl. Hope this helps.
thanx dude.. I did all that already, no luck...
I have 1.0 Olipof which is fine. I was able to flash different roms w/no problems and as stated above, I am set ready to go rom upgrading..
so far I really like: L26_Kaiser_DIAMONDV9 rom which works beautifully!
a few little quirks here and there, but these can be tweaked..
thank you all!
tvos
ok, I guess I just don't understand why your phone won't flash the .nbh file to change your hardspl. If 1.0 is working, then who cares, right?
so, I had some people contact me about the above problem. apparently some kaisers have this for some reason: they for no reason enter bootloader screen and won't boot OS.
the usual mtty commands ("set 16 0", "set 14 0") do not seem to help, and the whole thing is intermittent, sometimes you can still get the OS to boot. (NickCollision mentioned shorting the battery terminals after removing the battery helps for a while)
I patched the 3.29.Hard HardSPL (and the 3.56 too) to remove all enterbootloader reasons other than the usual stuff, keyboard combination and ruunbh tag.
both 3.29 and 3.56 will now say .Hard2 where the 2 means it is patched version =) so it will be less confusing to users.
UPDATE: you can try using force-usb SPL versions now, see new attachments!
UPDATE2: you can try 1.0.olipof-nostuckinspl-force-usb version and 3.31 hardspl (new hardspl, asked for by some users, of course with all these features)
3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29.
download from attachment and flash with SSPL to fix problem if you can get the OS booting at least once. also strongly recommended to flash this for prevention even if you have no problems yet!
what to do if you are still stuck in SPL - in that case, the spl overwrite protection will not let you flash. you should try to get the OS booting at least once. try with USB in, or after battery removal-reinsertion, those help increase chances.
if that doesn't work out, then see below what to do in that case:
the kaisdiagtest1.zip or the kaisdiagSD.zip in attachments may help solving the problem of reflashing the SPL to the patched version, if you absolutely can't get the OS to boot at least once.
the one of these allows you to reflash SPL via USB connection, the other one allows you to reflash from microSD card. this SD one is strongly recommended especially if you have problems with USB connection in SPL. it is also much more automatic.
usage STEP BY STEP (only if you cannot get the OS to boot not even one time!).
for diag and flash via microSD:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the KAISDIAGSD.zip in attachment (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS and then it will autoflash my hardspl again from SD.
2. put one of my hardspl's on the card too (in attachment, 3.29.Hard2 or 3.56.Hard2, 3.29 recommended). name this file as KAISIMG.NBH!!!
3. insert the microSD in the kaiser, then reset kaiser.
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
for diag and flash via USB:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the kaisdiagtest1.zip (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS.
2. insert the microSD in the kaiser, then reset kaiser.
3. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
4. it should then work with RUU over USB (has USB force patch). but test with mtty first, make sure to disable usb connection in Activesync/WMDC! if PC doesn't see the device, try a USB replug. also, the USB should be plugged in all the time (except for when you replug)!
5. if it seems to have a good connection, then please now flash one of the SPL's posted in this post. after that you will be able to boot OS (of course reflash OS if you need to but the *first* flash *must be* SPL).
6. if this doesn't work (i.e. USB connection won't go), then go and check the SD version of the diag image, if you haven't already.
Wow Great work.
Thank you very much for your hard work! Going to sticky this for the time being.
Damnn,m nice work.
Thanks for this.
I have added it to my Wiki page on what to do if you get stuck at the bootloader. (Kaiser_Stuck_at_bootloader).
Anything you spot wrong with it feel free to modify (I asked GSLEON to take a look, but I don't know if he's had time).
Thanks
Dave
I can tell you that it does work and it did fix my kaiser!
Great work!
Nice!
I don't use the SPL, other than the one that came with my phone.
(Warranty....don't want to take a chance). Come October, when the warranty expires, I'll probably start flashing some of the cooked ones, plus, the Raphael
will probably be around by then.
I love you cmonex, let me know if you broke up with olipro
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
----Thank you cmonex, once again you show that your one of the amazing forces behind Xda! I hope there are little girls out there that want to be just like you when they grow up! That would be so cool a bunch of mini cmonex's running around we would have no issues with are WM devices then!
sakajati said:
I love you cmonex, let me know if you broke up with olipro
Click to expand...
Click to collapse
lol, sorry, no chance
austinsnyc said:
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
Click to expand...
Click to collapse
most probably that was because the older SPL's formatted nand too aggressively, so the end of the OS might get erased, which is no good. wasn't a problem before but the new OS's are bigger, so it affects them more likely.
as for the SPL versions, I don't really recommend 3.56 SPL, 3.29 seems much better in terms of available commands (though neither has task 2a for frankenkaiser fun ). did someone have any good experience with the 3.56 over 3.29? - I wonder why it is an option.
cmonex can u post the patch for the 3.56 it would be greatly appreciated, thanx
Get a new battery. The reason for this problem is the power manager keeps reseting the watchdog timer. Depending on when that happens the unit will either constantly reboot or enter bootload.
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
htcfan2008 said:
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
Click to expand...
Click to collapse
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely. As cmonex indicated shorting the terminals did have a positive effect, so you may be on to somthing re: the batsense line. Just that swapping batteries had no effect in my experience.
oOoOo my batsense is tingling hehe
Where the two batteries...
Nick Collision said:
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely.
Click to expand...
Click to collapse
...Samsung brand made in China, and both more than six month old? Then quite possibly they're both bad. (I forgot to mention in my other post that I replaced the battery with a non-HTC brand.) One way to tell is look at the battery edge on: if it has a bulge in the middle or looks "swollen" all around then it surely is bad.
I have found that using a non-HTC car or wall charger almost always and rather quickly kills the battery. It's not the charger voltage but the charging current profile that's the problem.
Anyway, good luck.
the bootloader can enter tricolour screen for a couple reasons other than the usual key combination or nbhload / enterbootloader tags in flash:
- if CPLD function returns 0xF
- or if debugboard is detected for whatever reason
- other configdata in flash tells it to do so
the last one can be excluded, because the problem is intermittent, and flash contents should be permanent.
then, I had Nick Collision run info 7 (which calls the same function), and it doesn't return 0xF, so maybe the second one.
I don't know what would cause that though, this battsense line sounds interesting.
to ofcourseimnaked: OK, i will do that soon.
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
stepw said:
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
Click to expand...
Click to collapse
yes, those mainly, and some flags.
but the issue is not them.
stepw said:
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
Click to expand...
Click to collapse
you mean task 37? btw, reset wasn't an issue here, but if someone shows up with a device constantly rebooting, we can look into that too..
note, CID is not really accessible directly from SPL anymore, MSM7xxx. (though right now I'm having fun finally dumping the protected radio nand)
Please explain me what it exacly is.
Is it better, most recent and fixed for Bootloader mode stuck version of HardSPL 3.29 which we can found on 'jockyw2001' thread?
Is it still HardSPL which let me flash any ROM for HTC Kaiser?
Thanks for all explains. Best regards.
I've always fancied flashing my Kaiser (V1615) with a new ROM, but was always nervous because I wasn't sure of the process and didn't want to risk bricking the phone as well as all the effort needed to get everything back on it I needed. Well, a few days ago my old Kaiser met the floor and an untimely end. So I decided to take the risk and put a new ROM on it and decided on the latest Dutty WM6.1 ROM.
I read all about flashing on here and made as much sense of it as I could. Thing is, I'm very technical in general, but not very familiar with Windows Mobile or flashing. I found there was lots to read, but it was all written with an assumed level of knowledge and understanding of terminology. As a result I found it quite hard to understand. I took the plunge anyway and started, but things didn't work out as expected and I didn't understand why.
I'm not trying to be critical of all the work a lot of people have put into the documentation that is available online, it's just that when I originally approached this with zero flashing experience I found it difficult and confusing to understand. What I really needed was a concise and basic introduction to flashing. I've now been through the process and after re-reading the documentation it makes a lot more sense.
I worked out you need to run something called HardSPL before you could flash a new ROM. I'm still not sure what HardSPL does apart from CID unlock the device, but what does CID unlock mean?
I ran HardSPL v1 and it started ok, but then I ended up with a white screen. At this point I already wished I hadn't started, but no going back now. Is it known why some phones white screen? Turns out it's a common problem, so followed the instructions to recover. All was well again, but still with the original ROM.
I thought I'd be brave and stuck with it and this time tried JumpSPL1.56-KAIS instead of HardSPL as recommended on one of the tutorials. This went better and I ended up with the Tri-Color screen. I plugged my USB cable in and USB showed on screen.
Next step I thought was to flash a ROM onto the device. I ran the Dutty updater on my PC and all started ok, but when the update got to 18% I received a communication error. I tried to recover using the updater, but the same thing happened. At this point the phone wouldn't boot, so I was more than a little worried and wishing I hadn't started!
Found something that described several options for recovering from this problem. I decided to try and flash the device back to the original ROM from Vodafone. When I eventually found that ROM I ran JumpSPL again, got to the Tri-Color screen and ran the updater. This time the update completed successfully and the phone rebooted and was all working again.
I decided to leave the device as it was and started customising it myself. I'd still love to put a cooked ROM on there, especially if it helps with performance, but after the experience above I'm not very confident.
Can anyone tell me where or what went wrong? I'm going to get my old Kaiser repaired and want to try again on that phone.
My flashing routene (not ideal but it works for me)
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
2) after device reboots, hold camera button and restart to check SPL
3) Flash rom/radio of choice
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Sam
Wow, I need a cuppa now
I'll go through 1 at a time... (and Sam has answered some questions already)
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Thanks for the advice, but this is what I normally encounter when I read something on here, which is advice which no doubt makes perfect sense to the author or others experienced in flashing, but usually raises more questions than it answers in my head.
For example;
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
Click to expand...
Click to collapse
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
2) after device reboots, hold camera button and restart to check SPL
Click to expand...
Click to collapse
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
3) Flash rom/radio of choice
Click to expand...
Click to collapse
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Click to expand...
Click to collapse
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
BTW, not trying to moan about everything, just posting my experiences to find out where I went wrong, but also highlight some issues hopefully other flashing newbies can relate to and authors of tutorials can draw some useful feedback from.
Only one question, do I need to CID Unlock before using Jump and HardSpl or, the Hardspl does the Supercid ?
I'm not referring about SIM since I don't care, for now
With WM6.1 - Oficiall HTC ROM
Thanks
Thanks for that one dave, on reflection i kinda missed the whole point of the thread, and as for the majority of the stuff you posted i didnt undertand that to begin with.
Also, DaveTME, if you are wanting to flash a custom rom to youre kaiser. from my experiance and from the number of times ive seen this happen. i advise against asking for reccomendations(sp?) (not saying you will but its worth saying) try a few roms out and decide from there.
Also another thing to note. if you flash to WM6.1 remember to use a 3.xx spl otherwise you'll encounter a few problems with youre device.
Sam
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
Click to expand...
Click to collapse
download the Kaiser unlocker and run the first stage of it, the program is in the linked thread.
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
Click to expand...
Click to collapse
No, after the device reboots, youre given youre Rom, Protocol and Radio. if you hold the camera button and reset you'll get youre SPL displayed, youre looking for 1.01 olinex to be shown
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
Click to expand...
Click to collapse
1) Yes, just run the RUU with youre chosen rom and thats it
2) its not a minefield, just make a decision on what rom you like and flash it. theres nothing to stop you flashing another one.
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
Reply With Quote
Click to expand...
Click to collapse
The 1.01 SPL will allow you to flash a cutom rom. following that you need a 3.xx SPL as they are designed for windows mobile 6.1. as for yure decision. i use 3.29, yet other users have had better sucess with 3.56. Most rom chefs will say which SPL they reccomend anyway with their rom.
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
Click to expand...
Click to collapse
Great. Thanks for that. Makes perfect sense now
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Click to expand...
Click to collapse
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Click to expand...
Click to collapse
Thanks, will have a read
DaveTME said:
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
Click to expand...
Click to collapse
Read the "SPL Questions" Wiki Page, it is all there and fairly clear.
Ta
Dave
I downloaded Several Roms but can't intall them completely my hard spl is 3.29 and rom version is 3.34 and os is wm6.1 wwe so whenever is tried wm6.5 Rom it stucks on 0%
any one can help me out thanks in advance
Are you using the .exe file provided to flash?, in that case, try by flash a new ROM from your SD card. Rename the .nbh to KAISIMG.nbh, in your SD card (1 Gb is the best) and power on your phone by pressing and hold camera button and reset, then follow the instructions.
If you are going to WM6.5, flash first an original 6.1 ROM from your provider or HTC to cleanup the storage, and after the flash, hard reset your device.
Happy Flashing !!!
Good Luck
yes that is a good sugestion..flash from SD card and place flash file to be on the root of you SD disk..i don't use PC for anywhere to flash Kaiser because can download from WiFi that files birect to SD card.Good luck!
MY device go still at Color screen when i press three buttons
and only the word appears is ( serial)
nothing go forward
what should i do know
zeeshan9211 said:
MY device go still at Color screen when i press three buttons
and only the word appears is ( serial)
nothing go forward
what should i do know
Click to expand...
Click to collapse
Read the stickies!!!!!!! Then follow the flashing for noobs bit. It explains it all in perfect detail in there. Force it into usb mode or if that doesnt work, flash via sd.
Dear Senior members
whenever i wants to upgrade Rom wm6.1 to wm6.5 it stucks on 0%
and if i use storage card method it stucks at loading ...
plz guide me better what should i do whether i change hard spl to 3.56
and radio rom to 1.71.09.01
and then should try or what to do??????
zeeshan9211 said:
whenever i wants to upgrade Rom wm6.1 to wm6.5 it stucks on 0%
and if i use storage card method it stucks at loading ...
plz guide me better what should i do whether i change hard spl to 3.56
and radio rom to 1.71.09.01
and then should try or what to do??????
Click to expand...
Click to collapse
Which 6.1 rom are you using to upgrade from?
Send Me Help Back
original HTC wm 6.1 wwe
rom version 3.31.415.1
radio 1.70.18.02
protocol 25.83.40.02H
What other HardSPL versions have you tried? Does it say USB on the screen when you are on the tri colour screen after changing HardSPL?
I've had problems doing it the sd card way in the past so I always use USB now and it's not failed once. Just try different hardSpl versions, that seems to be where you troubles lie.
Stuntdouble is right, remember when you search and flash different roms the cookers always post in their threads recommended hardspl and radio so you won't have any problems running their roms.
Also, please follow in detail every step in the flashing for noobs thread for hardspl flashing
Having that, I think nobody should have any problems since you only need to follow intructions in detail.
Have you un-locked the Kaiser?
I got the same problem when I got my TYTN II back from repair, I had to un-lockit again.
http://forum.xda-developers.com/showthread.php?t=375583
//T