Related
Hello,
I recently acquired an i-mate and before doing anything, decided to perform a ROM upgrade. It started with ROM version 1.66.00WWE and Radio version 1.10.00. I followed all the instructions on the clubimate website. The ROM upgrade (Step 1) went well, until I started the English Language customization (step 2). That program froze on my computer and left the i-mate in bootloader mode, even before starting the Extended ROM upgrade for the customizations. When trying to upgrade the main 1.72 ROM again, it gets stuck at the Radio Stack Upgrade (to version 1.14) at 14%, then either exits with no message (Win XP), or gives a Radio Stack Upgrade error message (Win 98 ME). The phone meanwhile says that it is perfuming the radio stack upgrade and to please wait. Waiting for an hour yielded no change. The following is the log file entries of the part for the Radio Stack upgrade:
03:06:42 Connection with USB
03:07:52 Begin Stage 4
03:08:22 Radio Erase retry 1
03:08:59 Radio Erase retry 2
03:09:15 Stage 4 Complete
03:09:15 Begin Stage 5
03:09:15 Write block1
03:09:26 Write block2
03:09:32 Write block3
03:10:08 Radio Update data retry 1
03:10:16 Write block4
03:10:24 Write block5
03:10:32 Write block6
03:10:40 Write block7
03:10:49 Write block8
03:11:25 Radio Update data retry 2
03:12:01 Radio Update data retry 3
I tried many times, but get the same result. I followed all advice on this forum and searched all over for solutions, from getting the device into bootloader mode (power button + action button + reset), making sure that my PC does not have any other USB device connected, that the only programs running are the upgrade utility and ActiveSync 3.7.1, etc.
I also notice it takes approx 1 hour from start of upgrade until the Radio Stack Upgrade, instead of the advertised 30 minutes. Someone mentioned that this Radio Stack Upgrade problem may be caused by a security feature on the Radio Stack ROM preventing the installation of older versions. However, I am installing the newest (ver 1.14), so this should not be a problem. With a hunch, I decided to try the English Language Customization (1.72.800) upgrade again, and the extended ROM upgrade worked, but still no Radio Stack. So now I ave everything upgraded, but a blank Radio Stack.
Now when performing a hard reset, I get the blue screen with "i-mate" written on it. In the bottom right only the version of the ROM "D 1.72.00 WWE" is shown, but it says "No GSM" right above it. It takes approx. 15 minutes to boot (with blue Bluetooth LED flashing), then goes through the screen alignment and intro procedure. After that, it installs customization and boots again. It takes another 15 minutes to boot and the phone functions only as a PDA. Even a soft reset takes 15 minutes (with Bluetooth LED flashing). I tried upgrading again after that, but no use. Going to "Device Information", I see the versions of ROM and Extended ROM, but the Radio and Protocol are blank.
I tried phased upgrading, where I would include the main ROM upgrade file into to the directory where the archive was extracted, then extended ROM, then radio stack. Everytime the radio stack upgrade failed (i.e. stuck at 14%), I would try to upgrade that part only, since all others upgraded successfully.
I am really out of options. Any help would be highly appreciated.
Thanks!
I asked Carrier Devices (clubimate) about this step 2 because on the official download page all I saw was the step 1, no step 2 and no link to download.
The answer I got was there is no english customization 800, only a beta. The customization or step2 would be presented for arabic or telstar etc based on your IMEI # not for english it is contained in the first .exe
So you MUST have got this 800 customization and maybe the main upgrade from on here because it was never on the offical download page. Only the BETA from the FTP which some hacked into on clubimate and posted on here.
Go to the official download page on clubimate (register if you havn't) and dowload the official .exe upgrade (one file) and see if it will run. Don't get it from here.
RUU172126WWE_imate.exe
Hard reset a couple times and that should be it. The upgrade does take a LONG time to do.
If that does not work, you might have to do a warranty repair, I would use the online chat support on clubimate, just watch for when they are online and ask. I don't think you can just flash the radio portion.
I find 1.72 VERY stable and fast. Good luck!
Hmm.. All files were downloaded from the official clubimate website (I had to register in order to download). Talking to customer support, they were aware of the Step 2 customization file on their site (they recommended it, too). I doubt I downloaded hacked ones.
Still a loss on what to do, other than take it to a service center, that is (anybody do that? was it expensive? took too long?).
I tried a suggestion where I extracted the Radio Stack ROM upgrade file from version 1.66 and installing it separately. Still stops at 14%. I also tried a full reflash back to 1.66, but also same result. Took it to an i-mate service center nearby, was surprised that they didn't even know how to put the i-mate into bootloader mode (I had to show them)! All they could do was try reflashing using the same utilities we use (still no luck). They said that anything more elaborate would require sending it to Dubai. So much for "service" center. So, no luck there, either.
Also tried to reflash to the orginal 1.00 ROM with 1.05 Radio: The upgrade utilitiy that came with that version won't go past the small "please wait...." screen. Just sits there.
Really sad. I didn't even use this phone (figured that the best start is to perform a ROM upgrade). I'm not that impressed with how fragile ROM upgrading is (and I am careful with using only official releases). I thought after the Wallaby, things would be more robust. Maybe I shold dump this thing and get an HP h6300 series.
Note that I managed to successfully upgrade to 1.72 at least once. It was only when trying the 1.72.800 customization did things start to go south.
Also, does it matter whether the SIM card is in the phone or not while upgrading? Instructions are not clear, although they did mention that the phone will behave as if it is out of area.
Another question (desperate and a long shot, maybe stupid), Do SIM cards from say T-Mobile have an effect on i-mate phone Radio Stack ROM (i.e. lock it, etc.?)
ANY help would be appreciated!
i-mate and bootloader
I just got to see the problem as I am going through the same search for answer. How to get to the stage of bootloader? Somehow I feel that the device has crashed: While I was trying to install the upgrade RUU172126WWE_imate, my laptop, and for some odd reason, shut itself down, then auto restarted. The i-mate from that point on did not respond and in fact all lights on the device went blackout. I tried soft and hard resets but to no avail. I even removed the battery for several hours and when I re-installed it, all what it gave me was the word i-mate (but no backlight). Any advise on how I can get the device functional again.
Thank you.
Put your device in bootloader (press the Jog button and the Power button at same time and press the reset switch). Place it in the cradle and re-run the upgrade. That should work OK.
Jog
Thanks for the quick reply.
Power and reset button I know, but I am not familiar with the Jog button on the i-mate (Pocket PC PE). Appreicate your help.
Its the multi-directional button in the middle at the bottom. Press it straight down.
WM6 Essentials project DISCONTINUED due to lack of patience with idiots
ROM you have been waiting for. Clean, stable and fast.
This ROM was the reason for ending my previous project with Vlodeck. I started to make it few weaks ago, the day I notticed that clean WM6 has leaked MS labs. I grabbed it and started cooking, throwing all previous progress away. And now, I do not regret.
ROM you have here is the most clean thing you have seen on Charmer. I hope it's also the fastest and the most stable one. All packages that were added to privode aditional functions as camera, mms and others were doublechecked for unnecessary files and registry entries before they were gently inserted inside, tuned and approved.
I tried to remove all possible bugs, but there are few of them that I wasn't able to solve yet:
v. 000.5b WM6 Essentials known bugs
- for the first time after startup, it's sometimes impossible to activate HTC Black theme correctly, switch to Windows Mobile Green, then HTC Black applies correctly (probably tsk file issue)
- power patch correct application is still necessary
- system does not remember word completition set by user - it remembers default settings after reset (defaultly switched off)
Download
v. 000.5b WM6 Essentials
http://www.megaupload.com/?d=WPI87C3I
http://www.filefactory.com/file/691aed/
http://rapidshare.com/files/59969691/000.5b.zip.html
aWizard complete update package - v. 000.5b WM6 Essentials
This archive contains full dump of really smoothly operating device - my device. It contains Radio 02.19.21, custom bootscreans, absolutely empty extrom and 000.5b ROM. Use it only on unlocked devices and if you know what are you doing. Flashing this is easy, but it cannot be done from bootloader. No more comments needed...
http://rapidshare.com/files/61181560/essentials000.5b_aWizard.7z.html
Old versions:
v. 000.4 WM6 Essentials
http://rapidshare.com/files/51447784/Essentials000.4.zip.html
http://www.megaupload.com/?d=HSF6TKRX
http://www.filefactory.com/file/83724f/
v. 000.2 WM6 Essentials
http://rapidshare.com/files/40428170/Essentials_000.2_distrib_1.zip.html
Changelogs:
000.5b WM6 Essentials
This is just a minor build, just with some settings and details I want to have set up right after each HR. It brings just a little performance bonus due to larger filesystem cache
- removed windows live and its today plugins
- removed original tray application, permanently replaced by traylauncher
- replaced back original wm6 wallpapers
- clock set to "Display clock on the title bar in all programs" by default
- clock set to display date and time in title bar
- today plugins disabled by default
- cleartype used by default
- increased filesystem cache
- GPRS connection bubble includes "Disconnect" button and timer now
000.4 WM6 Essentials
- HTC Touch Dialed added (modded key font)
- HTC Black theme added
- HTC Touch CommManager added (necessary registry only)
- small registry cleanups
000.3 WM6 Essentials (unreleased)
- removed camera mode "theme"
- removed obsolete camera registry entries
- removed Windows update
- repaired IE to work with PIE Plus 2.2
000.2 WM6 Essentials
- first release
Unlock your device, you will avoid problems with flashing and it makes flashing much safer and easier
Unlocking your device brings more comfort and safety. You will never more need to download aditional files - files I'm providing will be enough. It's also almost impossible to totally brick unlocked device - there's allways a way back (if bootloader is not damaged, of course). Locked devices has problems with some common recovery procedures like SD card image flash. If you have locked device, you have a great chance to spend your money to a service company for such simple thing like unlocking is...do it yourself NOW.
Here is the working guide:
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=437&PN=1
Excellent flashing guide for czech users is available here: http://mda.force17.net, made by Trash. Czech translation of unlocking procedure is here: http://www.ce4you.cz/forums/view_topic.asp?t=24991
This ROM is provided AS IS, with no warranties from me, xda-developers server or other parties. Use it at your own risk. Use it only if you know what are you doing.
If you do not like it, don't use it. Use another one, freely modify this one, do anything you want - but do not bother me with stupid begging like "can you add total commander in this rom" - I can, but I will never do it. The same with HTC X-button, backup apps and other useless but popular junk.
Post non-technical suggestions and ideas here:
http://forum.xda-developers.com/showthread.php?t=314776
Let's keep this thread clean with the stuff that's only technically relevant.
PROBLEMS
If somebody has problem others never seen, he:
1) uses some 3rd party software. if I'm asking for this, report ALL 3RD PARTY SOFTWARE, not just one you thing has something to do with error. report all
2) his obscure extrom was executed and some untested cabs, often for other systems, were installed. PREVENT EXTROM EXECUTION even if you think it's harmless.
3) he is using smoe uncommon accessories (gps, handsfree, a2dp.....). Report this
4) his device is damaged. throw it away.
We, charmer owners, are in a big advantage: all devices are the same. No MB revisions, no G3/4 problems.
Common debug procedures if you have an error:
1) try to look if others has the same issue.
2) if not, hardreset device and try if error is still present BEFORE YOU INSTALL ANY OTHER APP
3) if this issue seems to be application sdpecific, install JUST THIS ONE APP and try it. be sure you are installing latest build of your app
4) flash latest official ROM and try your app
5) flash WM6 ROM again and repeat procedures 1 - 3
Previous steps are leading to discover if this is clear system error or is related to any 3rd party app. You will clearly see if it's ROM or application issue. If it's hardware problem, it's harder to say...
If it's ok after HR or new flash, perform following steps to check:
1) leave all settings as they are in defaults (including local settings, timezone etc)
2) if it's app specific, install this app. if not, skip this step.
3) perform step-by-step check: change one thing you usualy do, softreset device and check behaviour (eg. change timezone, softreset and try)
So you will discover hidden error dependencies. Sometimes you will get really surprised what can cause errors...
Hope this simple guide will help you to analyze your charmer errors and will help me to get rid of strange questions...
Error [222]: Device Not Responding
Hi, first of all, many thanks for your job.
I have a problem as soon as I star.
I run ROMUpdateUtility_NoID.exe and when trying to connect to my PDA I get the following error message: ERROR [222]: DEVICE NOT RESPONDING.
My Charmer is connect through the USB connection and activesync is connected.
Anyone has any idea on how I can solve this problem (I´ve tried with other USB ports but nothing... :-( )
Thanks in advance for your help.
For activesync troubleshooting, see http://www.htcamerica.net/support/8525/troubleshooting-guide.html
First, hardreset your charmer. During the meantime, reset your computer - do not connect charmer untill your pc is restarted...hope it helps. You may also try to reinstall activesync - or try it from another computer (it's not necessary to setup activesync partnership to perform rom upgrade)
No booting after update !!
Hello,
i have one question :
I had the wm6 rom : ver 004.4 -=- CHARMER WM6 WWE ROM by vlodeck & nocturne installed on my charmer.. worked fine. No Problems. Today i saw that there is this new one "WM6 Essentials". I flashed my charmer with this new rom and flash method 2 (i also used method 2 for the old wm6 rom). Everythink was ok but after hard reset my charmer stuck at the very first splash screen ( This one where the IPL, SPL and OS Number is beeing displayed). The Phone just did not go on. After another hard reset -> same problem.
I then had lots of problems to get my charmer working again... all the old (even official) rom updates didnt work. But at last i downloaded an obviously newer (than mine) AKKU 3.3 from t-mobile site and was able to flash the device with that one. Now the question : Is it possible that it didnt work because i did not downgrade to an official wm5 rom before upgrading to that new wm6 or do you think that i should not give it a new try because it seems to be another problem ?
many thanks for your answer(s)
If you want flash other WM6 and you have WM6 you *MUST* first downgrade to WM5 and finally flash WM6.
The most successful method has always been to install an official wm5 rom before trying another wm6 rom.
pjam
many thanks for your fast answers.
i tryed it again after downgrading to the official wm5 and now it works fine.
After the flash and saying "Congratulation you flashed it" it died. There goes my charmer to waranty again....
WM5
ZoNki said:
many thanks for your fast answers.
i tryed it again after downgrading to the official wm5 and now it works fine.
Click to expand...
Click to collapse
I don't have official WM5. please
Official WM5 Rom
I do only have a link to the GERMAN Version of the official wm5 rom but if you want to upgrade to wm 6 it doesnt matter i assume.
Use this link :
http://www.t-mobile.de/privat/0,1788,13082-_,00.html
Click on "mehr.."
Then "Software / Konfigurationen"
-> "Gerätesoftware"
Then you can download "Software-Update AKU 3.3
ZoNki said:
I do only have a link to the GERMAN Version of the official wm5 rom but if you want to upgrade to wm 6 it doesnt matter i assume.
Use this link :
http://www.t-mobile.de/privat/0,1788,13082-_,00.html
Click on "mehr.."
Then "Software / Konfigurationen"
-> "Gerätesoftware"
Then you can download "Software-Update AKU 3.3
Click to expand...
Click to collapse
U.S. Downloads are here: http://www.tm-phonedownloads.com/index.html
user989 said:
U.S. Downloads are here: http://www.tm-phonedownloads.com/index.html
Click to expand...
Click to collapse
Wery Thanks
NEW version is out, released 21:22 GMT+1
New ROM version is out...
Hello Mr. Nocturne.op.15. IS IT REALLY WORK ON MY QTEK S100?
No, this ROM is working only on charmer and also on microwave ovens. Put charmer inside oven, turn it on to max power and wait until image download from charmer to oven is completed (this is indicated by battery explosion). Enjoy nice pieces of hardware all around your kitchen, they are WM6 powered.
Wrong
This didn't work on my microwave oven at all. I have a Daewoo microwave oven and it is white. All that happens when I try to flash the rom (on full power) is that there is a strange smell and my Charmer stops working. There are sometimes some sparks.
The microwave now won't get past inital boot loading - there is a big while light and I have a TMobile screen and there are pink squares all over the microwave.
Thanks a lot nocturne and vlodeck - I now have a WM6 microwave but the softbuttons don't work properly and they are very hot to touch. And can I have a German version please?
nocturne.op.15!!!! you bastardo! me charmer no work! it smell not good.
littld: I doubt it, there will be a german translation unless someone from germany wants to do it, go ahead
Isn't it possible to use an original German O2 XDA Orbit WM6 and add the charmer drivers / reg entries to it?
Is there anything else to do?
members.htc.com ->
RUU_Hermes_O2_DE_3.54.207.2_6275_1.47.00.00_108_Ship.exe
Well over a year ago I bought the MDA-Vario and back then promptly flashed the rom to remove T-Mobile default. I installed MR.Clean Rom, after a few months of medium usage I completely forgot about the device and never used it.
Found it again the other day and came back here so I could upgrade/flash it so I can use the device as SatNav on the latest rom/build.
I can confirm that my device is G4:
WIZARD SERVICE TOOL REPORT
Wizard Service Tool v4.2.2
13/07/08 18:24:16
CPU: Texas Instruments - OMAP850
MODEL: Wizard
IMEI: *************
=> Bootloaders:
IPL: 2.21.0001 (G4 device)
SPL: 2.21.0001 (G4 device)
Built on Mar 9 2006 at 13:52:14
Copyright (c) 2003 High Tech Computer Corporation
=> Firmware:
OS: 5.1.xxx (Build 14955.2.3.0)
ROM: 2.24
Registry AKU: .2.3.0
Radio: 02.25.11
Protocol: 4.1.13.12
=>Extended_ROM:
Version: 2.24a Mr. Clean
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
0e9e4332 - 9.99M (0x9fd800)
aea9c13a - 43.24M (0x2b3e000)
cfb25f96 - 50.95M (0x32f4000)
4fb25f42 - 2.94M (0x2f0000)
0fb25fba - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000f23102052b35008f13050698
Key Index: 57
Now, I am having great difficulty searching these forums because after not being around here for so long I don't even know what I'm searching for.
I have been reading different posts/guides since last night pretty thoroughly and I haven't gotten any closer to figuring out what I need to do etc.
I would like a fast/simple/clean G4 WM6 Rom, so far I have been unable to find one on these forums aswell (Why? Read the 2 previous paragraphs.. I honestly do not know what I'm looking for regarding compatibility with my device etc)
I understand I probably have to revert my rom to the T-Mobile original and start from there.
Please can somebody link me to the files I need, including roms/programs/guides.
Better still add me to MSN cr0sis at hot*mail d0t c0 d0t uk *(Not bothered about having this email listed publically, I never use it as email at all)*
Well,its not that hard to find what you are looking for,To upgrade read and follow either 'SoftSPL' or 'HardSPL' posted as stickies on the top of this thread.
To get a rom of your choice,look in the 'Wizard Mobile6' forum,all the latest custom build wm6 or 6.1 roms are safe for flashing a G4 phone.
I managed to figure out Shelltool (despite a ton of broken download links etc)
and successfully flashed TNT 19213. I was getting too many errors (on first boot "Timesomething not working" blah blah, then a lot of programs it claimed to have installed simply did not work (No icons in program viewer or anything).
Anyway, not here to complain about a specific rom not working, so I'll just get on with trying another. Shelltool seems to be the only working flash tool out there, and since last night I have tried a lot of different methods to the exact guide instructions.
I need to go through a list of the roms I can find which ARE successfully linked to still (Again, so many broken links on here it's unreal!). I'll report back when I've cracked it and got a rom I can actually use.
----
Ok, I ****ed up during a flash. Won't go into detail of how/what I did but basically, I need the original MDA-Vario Rom for T-Mobile or I can't continue, Anyone know a working link please??
SoftSPL works. You do need a ROM that boots tho - if whatever you try to load DOESN'T boot you're screwed and left on the tricolor screen, and need an ORIGINAL load for that device (with the proper CID) to recover.
DO NOT screw around with loading things on a G4 unit without a proper CARRIER ORIGINAL firmware file you can use to recover with if something goes wrong.
Guess why I know this.....
Hehe Hmm, I wonder.
Well, yeah, I know this too now. But I wasn't screwing around I just had really bad luck because less than 20 seconds after starting shelltools I had a power surge followed by a brief power cut, effectively "Removing the USB cable during this operation" which of course we all know full well not to do
So I can use SoftSPL even when stuck in bootloader/RGB screen? I'll need a little help on how because I get "unable to copy files, try again?" dialogue. Gone into Activesync, told it not to accept USB connections, Killed activesyncs exe file in running processes in task manager and still no joy. Then again, do I really need to use SoftSPL if what I'm doing now is only putting on my carriers original rom (Yes, I found it.. Eventually! The rapishite links weren't working for me at the time, strange that suddenly they all started to late last night)
No, you need to get a copy of a valid firmware file for the unit and carrier you have, and flash that - then, once you've done that and its running again, use SoftSPL again.
SoftSPL will NOT work from the tricolor screen.
Ok this is going to sound really dumb but:
Stuck in bootloader completely
I have my devices original rom
Extracted the nk.bf file
Ran shelltools, it froze
Ran RUU, Errors (Possibly wrong .dll version, I'm not sure?)
I am following all the wrong guides because not one is telling me how to flash when stuck in bootloader, with what program or version.
My head is fried
If you have an ORIGINAL carrier ROM (which is an EXE, self-extracts and then runs the RUU that is in it) you can run that from the tri-color screen and it will flash successfully.
Don't try to extract anything or get cute with the carrier ROM - just run the loader (the EXE) and it should self-extract and execute.
You CANNOT flash a cooked rom from the tricolor screen on a G4 phone. It won't work - the loader will complain about being an invalid file or device and quit.
You need an ORIGINAL carrier ROM load for that phone - not a cooked one. Load it, go through the startup (screen cal, etc) and then use SoftSPL again.
Ok well I thought I had the correct original Rom for this device, but after 3 times trying to flash it to my device by just running the .exe I get
Error[294] Invalid Vender ID
This update cannot be used for your PDA phone. Please check your update utility
----
Nevermind, seems I was linked to the G3 version in a G4 thread. Goddamnit.
I can't find the G4 version so I'm going to try and flash Wizard_Love rom.
In the days of SoftSpl and HardSPL, messing with RAPI tools like Shelltool is really risky. You should have taken more time with the wikis and guides.
Now you must use an official RUU (from your provider) or you won't be able to recover your phone (since it's G4 and it's CID locked)
Ok Brightrom installed, no panic anymore
Easier than I was first led to believe after spending a little more time figuring out the guides.
gazman86 said:
Ok Brightrom installed, no panic anymore
Easier than I was first led to believe after spending a little more time figuring out the guides.
Click to expand...
Click to collapse
THUMBS UP
And today after a greatly anticipated arrival of my new miniSD card, my device completely destroyed it! I switched off the wizard, plugged the card in, switched on, noticed the card was really hot within a matter of seconds.. card wasn't readable in the Wizard/PC/Card reader/Digital Camera/Second phone...
I already stuck it in my Card reader after unpacking it just to be sure it was working...
Anyway, I'll buy two more lol. Could just be that I bought a ****ty card.
Anyone know where to get the latest TomTom + UK map?
Hello everyone,
After few weeks of lurking of this and some other forums related on PDA, I decided to upgrade my qutek9100 (MDA Vario 1, wizard 200) to win 6.1, however i know there are some risks about that.
1st i checked some info about device and it reported that it is SIM unlocked but it's CID locked.. (to qtek).
2nd as some guy from our local news groups gave me program called ShellTool, I started the procedure, downloaded ROM i liked (TNT.20273 Professional Wizard -from this form) and whole procedure took cca 5min of loading the new rom (program reported that it would take over 15mins) and after that i reset the device (pressed small key in spot on the side with a stylus) and from then when i turn on the device it starts to load but it stops on screen where are IPL /SPL /GSM / OS info and some clouds (there is also qtek logo on screen)
after that windows mobile logo should appear but it doesn't. nothing happens after that.
3th I know maybe i should try with tips from (http://forum.xda-developers.com/showthread.php?t=329147) but i didn't
I tried to format rom with mtty 1.42 (i put device in bootloader mode > selected USB in mtty > typed cmd task 28 55aa)
also 'wake up' device with cmd set 14 0 > task 28 > taks 0 (i followed instructions from one our local forum)
but after all of that i did nothing changed.
what should i do now ?
I think i described every step i did good enough so you know at which stage i am, and what possibly can be done now.
I will be very thankful for any help
Thanks for reading.
heh this was fast, I tried one more thing which worked.
I put device in bootloader mode and started original ROM instalation (RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship) and now there is win again but 05 ofc. I thought on that day ago but i could not find that ROM on qtek website (i think they have some problems).
Ok this thread is kinda pointless now. So if there is nothing new mod should delete it coz i can't
[UPG]Hard-SPL Unlocker for Topaz (AT&T Pure) - Released! Now New Update to HSPL 2.51!
[SIZE=+3]Hard-SPL Release Time!!!![/SIZE]
[size=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/size]
NEWER UPDATE: Hard-SPL 2.51.OliNex! you can update to this if you already have Hard-SPL (1.33.OliNex or 1.83.OliNex). to do the update to 2.51, download attachment update_to_251.zip and simply use customruu or do an SD flash (TOPAIMG.NBH).
UPDATE: Hard-SPL 1.83.OliNex! if you have 1.33.OliNex, strongly recommended to update to this, better compatibility with WM6.5 ROMs. you can update to this in 2 ways:
- simply download new HardSPL package and run it in Automatic mode
- or you can download the attachment "update_to_183.zip" and flash it using CustomRUU. this only works if you already have 1.33.OliNex
preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
important: again, don't forget, each user gets 1 license, or perhaps 2-3 on request if needed (which is valid forever and all this works as transparently as possible, so won't be a problem at all), while businesses who need to unlock more devices than that, need to purchase it.
contact us via http://support.htc-unlocks.com (do not PM on XDA!) for requesting 1-2 more devices for private user (free), and if you want to discuss bulk unlocking also contact via http://support.htc-unlocks.com or contact cmonex.
Preparations
0) this package is for Topaz (Touch Diamond2, not the original Diamond1) devices. any TOPA***** accepted currently, as long as we don't see a CDMA or other special release.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended: http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center.mspx
Instructions
read this if unsure how to install Hard-SPL... if you are an experienced user and you just downloaded the HardSPL package and it worked, then cool. but if you run into an issue, then you should read the following!
1) download newest Hard-SPL package from Topaz-HardSPL_V5_00R5.zip attachment, extract to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! and it must not be in Flight mode (i.e. radio should be on).
3) NEW: internet access is required as the program checks online for updates and license.
4) run Topaz-HardSPL_V5_09R6.exe on PC, make sure it's launched from a local drive (not through network drive, etc.). XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, allow it please. if the exe fails to run or throws an exception (i.e. crashes), report this in the thread with exact error message/code. if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it).
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below (in NOTE 3 and in troubleshooting section) and you must only attempt the Manual mode if Automatic flash mode or SSPL-Manual.exe already put device in tricolour screen. any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the thread, but this should not ever occur (as this means a really fatal error occurred).
8) at this point the device did hopefully went to tricolour screen reporting version as 5.09.C-SSPL, this is the SSPL version, which is temporary. then RUU will instantly launch.
9) some notes: when RUU says it will hard reset, do not worry, it is not going to do that. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.83.OliNex, which is the Hard-SPL version.
NOTE: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, do a soft reset while holding the "volume down" key on the left side of the device. keep holding the volume down key until you see tricolour screen which is the bootloader mode, then release it.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs. also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted here below. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps at the end of this post about how to reflash stock SPL.
NOTE 3: anyone having problems with the device entering SSPL automatically, please copy SSPL-Manual-Topaz.exe from SSPL-Manual-Topaz.zip attachment in this post, copy it to the device and run it. then once the screen is showing SSPL, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team (using OliNex custom cert, which is not public) will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or topaz customRUU if you need to flash cooked ROM.
NOTE 5: for developers asking: Hard-SPL is not based on MFG SPL, as it can strictly be used for development and hacking, contact cmonex in PM if you need that one.
NOTE 6: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. win2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS softwares. also, version verify: if Hard-SPL package says V509R in first Welcome dialog title (and version 5.09 in About box), it is the latest version, not some crappy beta/old version.
Troubleshooting and Step by Step on reflashing stock SPL are in next post below!
credits
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
finally,
[SIZE=+2]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you!![/SIZE] - and enjoy!!
Hard-SPL for Topaz - Released!
-continued from first post-
Troubleshooting
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
you've donated and it still doesn't work: if you donated in Manual mode, you didn't enter an IMEI or it was mistyped. if you donate in Automatic mode, that will always work as long as the error message was about the commercial usage. to fix this, please contact us at the support ticket system link and use HardSPL - Paying category!
nothing happens on the device, does not enter tricolour screen mode:
- anyone having problems with the device entering SSPL automatically, you can get SSPL-Manual-Topaz.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing SSPL, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes.
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems
- if you get connection error in RUU after the device goes to x.xx.C-SSPL tricolour screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the tricolour x.xx.C-SSPL screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the "USB" text on the tricolour screen shows up, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time and perhaps if you are on vista), then if RUU times out, but device still says "USB" on the tricolour screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please contact cmonex in PM for testing SPL on that too. check modelid by entering SPL tricolour screen manually and note what it says (TOPA100, or something else). note: currently SSPL accepts any TOPA*****, but if we get notified of an incompatible (CDMA) topaz version, we will instantly modify it to deny those models.
other issues
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (x.xx.C-SSPL), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
- a new note about Hard-SPL versions: if for some reason you intend to use a stock rom, the Hard-SPL version should match the rom. (for example old 1.8x rom with old Hard-SPL, not 2.51, and so on.) cooked roms shouldn't be an issue.
how to reflash Stock/Shipped SPL - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker attachment, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary, the included one is the 1.33.0000 stock SPL. you can also use 1.83 in attachment to this post (Topaz-StockSPL183_NBH.zip)
3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 1.33.0000 (or 1.83.0000), not 1.33.OliNex.
About UPDATES:
-the last release (V5.09) added:
1. SSPL update supports more devices (especially more recent devices that would not update the SPL to Hard-SPL).
2. HardSPL binary is still 1.83.OliNex, should be fully compatible with HTC's WM6.5 RUU's.
NOTE: v5.00 will tell you to update to v5.09! and older than v5.00 will not work, so don't bother with the old versions.
-previous release 1 (V5.00) added:
1. new HardSPL binary, 1.83.OliNex, should be fully compatible with HTC's WM6.5 RUU's.
2. new SSPL binary, supporting more devices
3. fixes; this version will also tell you in future if you need an update for HardSPL.
-previous release 2 (V3.01) fixed the following 2 issues:
1. if you get this error message: "Please make sure the device is still plugged in and synchronized to the PC"
2. if the SPL version did not change to 1.33.OliNex, but stays on 1.33.0000
PS: if you still get any of these problems let us know in the thread! thank you.
Finally, it does come true, and now i may flash any rom that i want.
Great great great thanks to cmonex and olipro, you guys did a great thing to us all.
Just flashed my device with this Official HSPL without any problems (as usual). Thanks Oli/cmonex.
Ohh, Happy day...
Congratulations for your work and Thank you very much!
Just installed HSPL, everything worked fine (Windows Vista x64 SP2). Thank you very much!
Good Job!
Your guys are the best, THX a 1000000000000000000000000000000
Cheerz
Many thx to your both!
Here my first question:
...bootloader mode (tricolour screen!) and verify the screen shows 1.33.OliNex
Click to expand...
Click to collapse
My screen shows only "SPL 1.33.0000" is that right? I believe not . I tried to re flash it but i couldn't do that cause of the 1 license/person "prevention".
Grats on the release! but why no release party?
KyBO said:
Many thx to your both!
Here my first question:
My screen shows only "SPL 1.33.0000" is that right? I believe not . I tried to re flash it but i couldn't do that cause of the 1 license/person "prevention".
Click to expand...
Click to collapse
nah, the license won't be a problem, if you only have 1 device, did you run the Hard-SPL package at all? any errors?
Got it and it worked
Its like making a fancy dinner, so many hours spent designing it, planning it, preparing then 'cooking' it. Only to be eaten in 5 minutes.
HardSPL installed seamlessly and now I can flash on my D2.
Thanks guys/gals.
I have left you a small donation for your hard work.
Aussie
Thanks a lot
I'll try it again
p.s. now its time to get to cooking!
Congratulations for all especially Olinex
good job.
Great！Congratulation！
Thankyou very much！
Good Job!
Thinks!!!!!!!!!!!!!!!!!!!!!!!!
Awesome Job
News came ture.
Say thanks.
Is the _Topaz-HardSPL_V1_01R1.zip infected?
I get the message from Symantec Antivirus of Bloodhound.W32.EP virus.
Anyone else having the issue?