Related
Hi Folks
Well, here it is, ported from what I did for the Polaris basically... I find it's a nice solution as it works by flashing your device with a patched radio and changing stuff properly, anyway...
download and run the EXE, follow the instructions.
bear in mind if you already have Hard-SPL on your device you can skip *straight* to Step 2.
and remember the golden rule:
YOUR DEVICE MUST BE IN CE AND SYNCED BEFORE RUNNING EACH STEP.
Download Here or Download Here
UPDATE: now version v2.0 - Model ID error fixed, it WORKS.
if and when you get success, POST!
PS: If you try to sell this, I will find you, kill you, and sell your ****ing testicles on eBay
Yes, apologies, my error, new version uploaded
So what is the status now?
I found this solution does not work on all of devices. But my solution is as follows.
Run KaiserUnlocker.exe
1. I started with the Step 1. The upper button of total 3.
2. Go through the menus and accept everything.
3. You get TRI-COLOR screen on your device and a few seconds later you get the USB label.
4. After some time you get a communication error Message. DON'T RESET YOUR MOBILE DEVICE. DON'T TOUCH IT.
5. Press Exit to quit KaiserUnlocker.exe on your Desktop machine.
6. Unplug and replug the USB cable.
7. Start the KaiserUnlocker.exe again and wait a little bit.
8. Your mobile device (AT&T Tilt) suddenly alive again. The progressbar shows up and you're from 0% to 100% in a few seconds. Wait a little bit and then you get the message the process is finished.
Now I don't know what to do with step 2 and 3. Should I perform them or not. Hmm?
What I would like to do is just to update from AT&T Tilt ROM to original HTC TyTN II ROM
AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one
Oh I see you changed the version now. At the time I downloaded it and wrote my first message it was just V1. There was no V2. But I can't test it now because I already have the ROM patched.
And I didn't get the ModelID error. It was a connection error 260.
I think it's just some guys of you are lucky to have a device that doesn't get the white screen when using hardspl and it doesn't stop on tri-colors or the progressbar at 0%.
actually, it's steps 2 and 3 that I care about, having a patched ROM is irrelevant.
step 2 and 3 allow you to sim/CID unlock
Mirror:
Kaiser Unlocker v2.0
FTP Problems!
Hi everybody,
Our provider has notified us of the fact that our ftp server has appeared in a list of compromised FTP servers which are known to host malware associated with attacks on banks and banking infrastructure. We have been requested to secure our systems. Since we realize it would cause serious problems to some if not most of our users if we we're to close it down immediately or change the password in the next 5 minutes we hope you can all live with the following arrangement:
We will close down the ftp server Monday the 9th of march on 09.00 CET. You have until then to download anything from our ftp server you (urgently) need, especially if you host software of which you don't have a back-up on our ftp it's important to download it asap. After closing down our server upcoming Monday we will remove all malware and start restructuring our server, implementing a new user structure, this does mean our server will be offline for a while and we cannot assure you no data will be lost.
If you have space available to host your own software please do so, if you have space available for those who do not have their own space please let it be known by posting a reply to this post. Our apologies for any inconvenience this will cause, but we hope to be able to serve you with a better ftp server as soon as possible.
Best regards,
Flar
Site admin.
Click to expand...
Click to collapse
Just to be safe!
Thanx Olipro
Sorry for asking, what do you mean by "your device must be in CE"?
Olipro said:
AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one
Click to expand...
Click to collapse
I did re-download after you said it didn't work. I must have downloaded it before it was fully uploaded. I did see the V2.0 NOw...this time no errors.
Thanks again Works perfect now. Thank again.
It Works!
This is awesome. I was trying with Jocky's unlocker for couple of hours. No luck.
Gave a try to this tool. Unlocked first time. Now, I got to check my phone with a different provider SIM.
Thank you so much!
Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?
Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?
Penske MB said:
Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?
Click to expand...
Click to collapse
it's 1.58.something, i forget the rest
FTP will close today.!!!!!!!!!!!!!!!!
I try to download and uploade to mediafire
Midget Edit: Mirror removed, new version.
doesn't matter, I'm updating the FTP link in a second or two with the new one
Active sysnc
Hi Olipro,
Thanks for all the hard work.
When I try to run the step 1, it keeps on disconneting the active sysnc. Am I doing something incorrectly?
Cheers
Shan
elmoono said:
Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?
Click to expand...
Click to collapse
These were my steps,
1. Identified my AT&T radio ROM & downloaded that from XDA website as a backup. Pick from here
2. Ran Pof's HardSPL Link
3. Ran Jocky's SuperCID & Security Unlocker Link
4. Installed Dutty's Official WM6.1.2.19199 Full Version Link
5. Installed Radio ROM 1.64.06.04 Download
6. Installed .NET Framework 2.0 on my Windows XP SP2 from Microsoft website.
7. Ran OliPro's Kaiser SIM/CID Unlocker. Followed just step 2 & 3 since I had already installed HardSPL.
8. Installed Radio ROM 1.64.06.04 to get my ringtone & HSDPA connection.
May be my steps 3 ~ 5 were over kill but that was just me. If you would like to skip 3 ~5 make sure you have WM 6.1 installed also remember to patch your original radio on step 8.
All the above steps does not need a strange SIM. I am yet to pop in a different carrier SIM to confirm about my Tilt Unlock Status. However, after the above steps, I found "Kaiser Unlock.exe" under my Tilt root folder. I ran that from phone, clicked on check SIM Status, came up as "You are already SIM Unlocked"
Hope this helps.
when you run step 3, just query what simlocks are active
Worked on my AT&T Tilt!
Not sure about step one already had SPL done with Whitescreen Fix
I will try it monday when my friend brings his tilt over to get it unlocked.
I did have to install a 6.1 ROM (I used Dutty's Official) between steps 2 and 3, had a blank screen, using the att rom -bloatware.
Not exactly a newbie, but I am not about to brick my phone because the wiki won't load on either of my machines and am too man to ask.
Steps to flash a cooked rom seem to be...
1) HardSPL (directions in the hardspl thread)
2) Flash radio of my liking (should the ROM not have one)
3) Flash the rom
4) ???
5) Profit!
Is that how it works? Seems like I went through a similar process with my Wizard.
ps - on a tilt, if it matters.
4) Hard reset (press both softkey's and stylus during boot until message appears)
Thanks!
Flashing now.
I waited a whole week after I got my phone.
So proud.
... when do I hard?
I pooped while it was flashing the rom, and now it is sitting here gleefully waiting on my input...
Set up my exchange server and it is running flawlessly... ps - mail2web.com is free. saves me from installing outlook on my windows machine
rule of thumb is when ever u flash a new rom hard reset at the windows mobile screen (where it says tap screen to setup ur device). this way all the files of the previous rom, if exist, r deleted.
Credit goes to the creator of the HardSPL files V3.28/3.29; JockyW
Simple Step-By-Step Installation of 3.28 Hard SPL:
I have decided to expand on what has already been posted for those noobeees that are having hard time understanding the HardSPL procedures and are hesitant to flash new cooked ROMs fearing the process was not really explained in details.
You only need two files; SSPL-KAIS.zip and Kaiser-HardSPL-3.28.zip. Save both files on your PC in their own folder for easy access later. Follow these steps to the tee, Do this only if you have your device CID unlocked already ( OliPoff method ):
1. Save then unzip SSPL-KAIS.zip inside a folder on your PC, then copy the unzipped “SSPL-KAIS.exe” onto your device. To do this, connect your device to ActiveSync, After Syncing, Click on Tools from the ActiveSync window, and then click on Explore Pocket PC. “Mobile Device” window appears, Copy SSPL-KAIS.exe by dragging it inside the “Mobile Device” window.
2. Unzip “Kaiser-HardSPL-3.28.zip” in its own folder on your desk top. It will unzip into two files; KaiserCustomRUU.exe and Kaiser-HardSPL-3.28.nbh.
3. Remove your SIM card and your SD card from device. Your device will power off when your SIM card is removed. Power up your device. You are still connected to your PC via USB at this point. Your phone will sync again since it is still connected.
4. On your device, go to “File Explorer” and locate SSPL-KAIS.exe that you copied earlier on your device main memory and click it.
5. Wait for the Bootloader Tri-Color screen to appear and "USB" to show.
6. On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
7. Unplug your device from the USB port, wait 5 seconds, plug it back in.
8. Go to the folder on your PC that has “KaiserCustomRUU.exe” and click it. This will flash the HardSPL on your device.
9. When done flashing, do a soft reset, and you should be good to go.
10. You can use the above steps to flash Kaiser-HardSPL-3.29 if you so desire.
Good luck
Tilt will not receive ROM
I tried flashing the below upgraded Kaiser Rom on my ATT Tilt but now I have the tri-color screen:
KAISI*0
SPL-1.93.000
CPLD-8
The first time it stopped loading at 15%, recovered and now I am getting vendor ID error (294 invalid vendor ID).
I tried others ROMs (including this one) but it just does nothing 0%, errors out, recovery and repeat (update error 262).
After removing battery the tri-color screen says "serial", once I plug in the USB it says USB, but no firmware can be loaded on it.
Does someone have basic firmware that will load when an ATT Tilt gets in this state?
Any help is really appreciated. I just got this thing too. Below was the update I tried that kill my Tilt.
'RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe' that you can find
did u hardspl?
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
TiltedHTC said:
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
Click to expand...
Click to collapse
Sounds like your phone is still CID LOCKED. Unlock it using the software posted somewhere else on XDA but NOT in this thread, and try to upgrade the SPL after unlocking.
One way to find out if your device locked or unlocked is that you can try to revert back to the AT&T OEM ROM and flash it. You would then be certain that the CID is locked if your device accepts the OEM ROM.
I wish you posted your troubles in the ROM post where you downloaded the ROM where it belongs; My instructions have nothing to do with your device ROM issues.
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
TiltedHTC said:
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
Click to expand...
Click to collapse
The following link is to Pof's full and clear post on unlocking your device CID. Use it carefully.
http://forum.xda-developers.com/showthread.php?t=334679
Search the forum for RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom, download and then flash. you will be set.
Cingular/AT&T OEM ROM
Download the AT&T OEM ROM from the following link:
http://rapidshare.com/files/55298724...GULAR_WWE_.exe
This is just because I feel good today... Otherwise I would ask you to take the time and do the search yourself. Noobee Spoon-feeding Time...
I found this link to put OEM ROM back:
http://forum.xda-developers.com/showthread.php?t=335568
but the RUU ROM for the AT&T link would not load on my tilt (step 2 of idiots guide). I also did a search for the RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom but no hits.
At least I know what went wrong, now I need to recover the original Rom.
update:
This newbee still won't eat. I got the file (your link is to the same file) but I am getting the same 294 invalid vendor error (after 1%).
I rebooted computer and tried it again with same 294 error.
did you just use jumpspl and used that to load a rom?? why oh why.......
Tilted newbie, did not read enough. Any solutions?
A question.
On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
Do you have to do this ?
I never did that.In my settings USB connections is enabled and it seems to work
/Linus
thaaaanx
i must admit this is the best and clearest step by step guide i have come acrooss thanks a lot mate
just a quick thought..... maybe you should give some credit to jocky
Also,
It wouldn't hurt to mention the "white screen" issues people get when running SSPL.
In such a case they need to use Jump SPL 1.56 or 1.93.
Link Here
Ta
Dave
Thnks man for tutorial. I think it usefull and simple for newbies.
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
kpcz said:
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
Click to expand...
Click to collapse
Correct.
Hard SPL's allow you to flash custom ROM's no matter what version.
Ta
Dave
ok, thanks - will give it a try!
It appears there is no way to recover.
Any great excuse that should be used when I take it back for repairs?
I am a newbie but slowly learning from everyone on here. I just have a couple of questions before I start. First, I found the step by step directions on how to do the flash from 6.1 to 6.5 but it is for a Diamond and I have a Fuze. Will I be able to use the exact same steps or will I run into something different. Second, I have vista on my pc and my sync doesn't work. I have searched and tried everything. My cd from the phone doesn't load any software onto my pc because it says it has problems with vista. Anytime I put a new cab on my phone I have to put my sd card into the pc directly and load onto it. Will I be able to use my sd card the same to flash the ROM with the things like hardspl and the rest of the programs I need?
Thanks for the help
Your answer is here my friend.
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael
There are some great roms for HTC Fuze/Raphael.
Good luck.
You have to flash hard spl off of a pc, but once you do that, you can (and should, imo) flash radios and roms off an sd card. The pc needs to have net framework 3.5 installed-that seems to trap a lot of noobs. And make sure that the anti-virus protection is turned off, when flashing and when downloading and extracting the hard spl package. If you put your fuze into bootloader before connecting it to the pc, it won't matter if active sync is installed or not (I'm pretty sure on that). It should say 'usb' or something like that on the screen when you connect to the pc in bootloader mode. I'll let you look up how to go into bootloader, it's in the noob flashing thread (also check fuzemobility).
As for the sync issues, Vista stock WMDC has issues with Windows Mobile 6.1. You need an update. Grab it from here: http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center-download.mspx
Attached you find all you need to flash cooked ROMs on your Ozone (Cedar).
The sspl/hardspl are confirmed to work fine on the HTC Cedar platform (Ozone).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. For the Dash3G I have already developed a sspl/hardspl. Users of the S511 have to wait until I feel motivated ..
The packages contains a SSPL, HardSPL, patched ROM updater and the original Ozone SPL. The package is based on SPL v0.39
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Ozone HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
5. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Ozone cooked or original ROM.
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Awesome work JockyW.
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
Click to expand...
Click to collapse
Um... so most of this worked fine, and the screen is dark, and a generic htc driver got auto installed... and the Rom Utility popped up on my screen... But how do I get it to connect to activesync like this?
After my phone rebooted completely (following the ROM utility completing), I just re-enabled Allow USB connections and it seems to work fine.
No, so the rom update tool doesnt complete because ActiveSync doesnt work after the screen turns black...
Edit: and Im using XP (noticed ur not from the thumbnail...) idk if that matters or anything
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
forgot to remove my SIM card! Gonna try again, give me a few minutes
no, same problems. :sigh:
The bootloader is still locked in 0.39.0000, confirmed.
EDIT: I'm pretty sure all my problems are coming from x64 drivers. I'm going to try this again in Windows XP Mode. Congrads everyone who's succesfully flashed! Good work guys!
businesschild said:
forgot to remove my SIM card! Gonna try again, give me a few minutes
Click to expand...
Click to collapse
businesschild said:
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
Click to expand...
Click to collapse
businesschild said:
no, same problems. :sigh:
Click to expand...
Click to collapse
businesschild said:
The bootloader is still locked in 0.39.0000, confirmed.
Click to expand...
Click to collapse
Instead of replying to yourself, please use the edit button next time.
Anyways, if you run auto.bat, disable USB Connections after the screen turns black via ActiveSync. In your device manager (with the screen still black) look at your USB Devices. You should see a entry called HTC USB Sync. If you see that continue to flash. Seeing HTC USB Sync is a key step in this whole process.
Please read the testing/development thread for some good solid help. A bunch of us ran into the same issue you did. If you read all 4 pages you should be able to troubleshoot your problem: http://forum.xda-developers.com/showthread.php?t=550628
computerpro3 said:
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
Click to expand...
Click to collapse
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
ookba said:
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
Click to expand...
Click to collapse
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
computerpro3 said:
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
Click to expand...
Click to collapse
HERE HERE!
The stock ozone rom is crap, I would love to cook my own ROM!
BTW hardspl successfully flashed first try on my device. Totally painless. Excellent job.
Anyone with a Telus SNAP try this?
ariesq said:
Anyone with a Telus SNAP try this?
Click to expand...
Click to collapse
I think the Telus SNAP is a CEDAR as well. Uses the same CDMA network as Verizon. Dump your SPL and post it for JockyW to examine and give the tumbs up.
Also, dump your RAW files, upload and post in this thread if you can.
http://forum.xda-developers.com/showthread.php?t=540586
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
ookba said:
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
Click to expand...
Click to collapse
I agree. Just sent him a small donation. You're next ookba, but will have to wait until next paycheck.
Update: Small donation sent to you as well ookba. I'll just have to skip lunch tomorrow
P
How sure are you that Ozone is Cedar?
RUU_Chief_W_WM65_VERIZON_WWE_2.10.605.1T_Radio_612522_1.71.00WV_NV_MFG_VZW
looks like a chief to me, but I could be wrong, I would like to release a 6.5 kernal, but dont want to have wrong device.