well, Hard-SPL is released now! sorry for delay, I got distracted elsewhere
[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]
[size=+2]Donations are always appreciated to the big link in our signature ("elite project"). You can also donate via the link offered in the new Hard-SPL program. Thank you!![/size]
Preparations:
first an important note, if you want to flash more than one Iolite, contact cmonex for additional licenses via http://support.htc-unlocks.com. (the first license is transparently granted and free, so normal users do not need to worry.)
0) this package is for Iolite (Touch Cruise II/2009) devices. for any IOLI***** so far (SSPL loader checks this and gives a warning if needed), afaik there is no CDMA version so all the model variations should be fine.
1) if you have vista, WMDC update is recommended: http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center.mspx
Instructions:
read this if unsure how to install Hard-SPL...
1) download latest Hard-SPL package (currently v1.10) from attachment, extract to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!!
3) NEW: internet access is required as the program checks online for updates and license.
4) run Iolite-Hard-SPL EXE on PC, make sure it's launched from a local drive (not through network drive, etc.). if you are on vista, launching as Administrator is strongly recommended, on XP administrator login is required. important: if your AV (norton/symantec mainly) warns about a virus, ignore it, it just doesn't like the packer I used to pack the program.
5) if possible, always use Automatic flash mode (for uses of Manual mode, see troubleshooting section)
6) it will ask you to wait while it prepares for the flashing, press OK. follow steps in the program and then in the RUU.
7) some notes: 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).
more 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.
8) device should go to a tricolour screen now that says 1.09.C-SSPL, this is the SSPL version, which is temporary.
9) SPL flashes, device automatically reboots, job done.
10) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.09.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, fully power the device off by long press of power key, then power on 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 or radio packages. 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 will soon be posted in this post as well. 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: 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 customRUU if you need to flash cooked ROM.
Troubleshooting:
- read the instructions above.
- read the instructions above.
- read the instructions above.
Manual flash mode for USB issues: you should usually go for Automatic flash mode; you must only attempt the Manual mode option if Automatic flash mode or SSPL-Manual.exe already put device in SSPL tricolour screen and you got USB issues. any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
ModelID checking:
- afaik no CDMA model, so doesn't matter but let me know if you got any problems.
nothing happens on the device, does not enter tricolour screen mode:
- anyone having problems with the device entering SSPL automatically, please make sure you watch the device screen if it asks about running files. also try unchecking advanced usb functionality in settings.
- if it crashes instead of entering SSPL, you need to use Automatic mode.
general usb connection error problems if you get connection error in RUU after the device goes to 1.09.C-SSPL screen:
- try manual SSPL: copy SSPL-Manual-Iolite exe to the device and run it, then when it went to 1.09.C-SSPL tricolour screen and shows "USB" at the bottom in this screen, use Manual option in the Hard-SPL program on the PC.
- make sure device was still synced via USB to the PC at the point of it entering SSPL (the 1.09.C-SSPL screen)!
- 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.
- also you can try unticking advanced network functionality in start menu / settings / connections / usbtopc applet.
- 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 RUU when driver installation finishes.
- finally, you can try disabling antivirus or firewall programs on the PC.
other issues:
- if Enterbootloader.exe fails to run (says missing component or similar), try a hard reset of the device.
- if device reboots instead of going to SSPL screen (1.09.C-SSPL), contact us by PM'ing cmonex. do not PM OliNex user, that is not monitored frequently.
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. take the SPL relocker attachment, and run the EXE - this will flash 1.09.0000 stock SPL. simple as that!
2. flash
3. verify if it flashed by checking version in tricolour screen, it should say 1.09.0000.
credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> EXE program concept that runs on the PC, Hard-SPL concept, server code, maintaining licenses
cmonex -> new PC EXE & SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code)
---reserved post---
---reserved---
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Let me see see!
chenjun_conan said:
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Click to expand...
Click to collapse
yes, I've sent it to several people. I'm posting it here too in a sec.
edit: posted
Dan
OK
you are great.
Thank you so much.
Fantastish!
THANK U VERY VERY MUCH!!!
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Great job, big thanks!
@ cmonex was send you a PM, please answer me. Thanks!
Greetings
Baga12 said:
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Click to expand...
Click to collapse
try to flash WWE|Eng and post result here
Nice work as usual guys.
Thread stuck
Dave
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Thank you
Thank you so much for your hard work.
My Iolite can do do just about anything right now.
Baga12 said:
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Click to expand...
Click to collapse
You tell us? It what way doesn't it work?
Dave
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
So? what about WWE Roms? Does anybody flash them at new HSPL?
thanks very much . it's great'
Baga12 said:
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
Click to expand...
Click to collapse
Please help!
max_nya said:
So? what about WWE Roms? Does anybody flash them at new HSPL?
Click to expand...
Click to collapse
Once you have Hard SPL, you can flash any ROM's (Cooked or Shipped) to your device. So put on Hard SPL, find a WWE ROM and flash it .
Baga12 said:
Please help!
Click to expand...
Click to collapse
I've just checked the re-locked and it does contain the correct SPL.
Connect your phone to you PC using AS, and then run the re-locked, once done your SPL should be 1.09 (with the .OliNex) again
Dave
Related
Apparently, I'm pretty stupid.
I just got the Cingular 8525; I have spent two hours on this site.
Things I've noticed:
One page says go into bootloader; one page says not to allow usb connections.
I do not know if I am supposed to have my non-Cingular SIM card already in the phone when attempting to do anything.
I have seen connect via USB and use mtty (with what settings do I use when I click on USB from the dropdown menu (if any) and do I connect with mtty via USB in bootloader or when the phone has booted into Windows 5.0 and again what about the non-Cingular SIM card?).
I have flashed my computers BIOS several times but I do not understand how to flash this phone based on the myriad of instructions all over this site (and RFTW did not help which is why I am here with 40000000 questions).
The steps to go from SPL 1.06 to an unlocked SIM/CID phone are?
Things I do understand:
I have SPL 1.06 (I know this from bootloader).
I must downgrade to 1.04 from 1.06 then run the upgrade to 1.06 from the Hermes Upgrade wiki page (I already downloaded all of the Cingular files).
Thanks in advance for any clarification.
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
I assume the activesync connection via usb is okay? I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone? Note: after I unplugged the device, setting allow USB connections on the device in the ActiveSync settings, then plugging it back in, it connected via USB in ActiveSync (4.2). However, I just got a box saying the version of ActiveSync is not compatible with this mobile device. This occured after I started the installer and it showing Verifying the information on your PDA phone.
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
I went to check the M$ page to see if there is a later download; there is not. Then, the AS icon return (trying to update outlook, install nero mobile) so I decided to run the installer again and now sees my current version 1.34.502.1 and I have the option to upgrade ROM
MilanoRex said:
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
Click to expand...
Click to collapse
crazyut said:
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
Click to expand...
Click to collapse
right
crazyut said:
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
Click to expand...
Click to collapse
doesn't matter
crazyut said:
I assume the activesync connection via usb is okay?
Click to expand...
Click to collapse
It is ok, but generally it causes more problems than it helps. Best is to disable the checkbox that says "enable usb connections" on activesync settings and you'll see the icon on the system tray turn gray with a red "X". Then you need to start the RUU when the device is in bootloader mode (tri-color screen). After you have upgrded the rom (or radio rom) you can reenable activesync again if you want.
crazyut said:
I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone?
Click to expand...
Click to collapse
SIM card and activesync have nothing to do.
crazyut said:
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
Click to expand...
Click to collapse
Icon was gone because RUU checks your current rom version using activesync and then kills it an put device in bootloaer mode. If RUU cannot kill activesync correctly errors happen:
You will avoid the 260 error if you disable usb connections on desktop activesync as I told you, and start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Hey. I left the RUU software running (the 25+ minute variety) while I went to buy a case and care charger. I came back and evidently, the phone had rebooted because, it is at the Windows Mobile screen to setup the Windows Mobile device. I assume it is safe to do the 2a software. After that, am I able to update the RUU back to 1.06?
Thanks for your help, Milan and pof!
I rebooted into bootloader to confirm successful downgrade to 1.04 from 1.06 and it was. The RUU software from the upgrade page for Cingular appears to have been successful.
I am now going to attempt the 2a software.
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
pof said:
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
Click to expand...
Click to collapse
It's now on the upgrade screen to Radio 1.16.00.69 but it does not show the previous version. Is this normal? I have not pressed upgrade yet. I have the splitter with the AC and USB cables into the phone (currently in bootloader mode at SPL-1.04).
yes, it is normal... i told you before:
pof said:
RUU checks your current rom version using activesync
[...]
start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Click to expand...
Click to collapse
pof said:
yes, it is normal... i told you before:
Click to expand...
Click to collapse
I got the 114 error as promised in the readme. I exited the program using the EXIT button.
The next step:
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
On the phone display, it still shows Upgrade Radio Stack Please Wait..
The soft reset is the simultaneous OK and Power?
I just took the battery out and reset; it appeared to go okay. I copied the exe file to the phone and was able to run the file as in the readme. I then reset the phone, put in the t-mobile sim and it works.
Thanks much to POF and Milan for their straightforward approach. You can use this thread as a tutorial!
Is there any reason I should add the 1.06 file back to the unlocked 8525?
SPL 1.06 to SPL 1.04 back to SPL 1.06?
Hi:
I followed pof's (with pof's help) tutorial on how to unlock the Cingular 8525. I am currently at SPL 1.04 (downgraded form SPL 1.06) and had run the v2a software to unlock. It works great with T-mobile (I was a Cingular customer but made the switch).
My questions are:
Is there any reason to go back SPL 1.06?
If I do go back to SPL 1.06, it does not affect the unlock status of the SIM or CID?
I still am confused about the Radio and what that does in relation to the CID, SIM, or phone. I assume the Radio is affected the SPL version that you have?
I have tried to peruse through various pages regarding downgrading (the 13 page thread for example) to see if that question is answered.
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Sleuth255 said:
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Click to expand...
Click to collapse
Oh okay, that clears up yet something else I did not understand
Thanks for the tip on the bootloader version; I will leave it at SPL 1.04.
That being said, I am currently in the middle of the Radio 1.20 thread; I have not finished reading it yet (I can only do so much at work before people wonder what I am doing). Have you upgraded to Radio 1.20? If not, what radio are you running and what do you think of its stability and/or functionality?
Thanks!
I'm running the 1.20 radio. It and the 1.35 TyTN ROM are the best combination I've used so far.
Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Update - I just tried this:
http://forum.xda-developers.com/showthread.php?t=326953
but without success. I get an Error [260] and the entire process stops.
Anubis1965 said:
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=405814
lakeman said:
look here
http://forum.xda-developers.com/showthread.php?t=405814
Click to expand...
Click to collapse
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Anubis1965 said:
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Click to expand...
Click to collapse
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
If you see in bootloader mode ID showing somenting different than ATHE100 the solution is HERE http://forum.xda-developers.com/showthread.php?t=405814
I had the same problem! whell restart your pc and then connect the device to it. now start flashin an spl 1.20 rom. i did it and it worked! I hope i works for you too.
Cheers, Hirad
lakeman said:
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
Click to expand...
Click to collapse
Thanks - already tried!
When I reset/hard-reset the phone (tried many ways) I see a garbled boot image (with random pixels here and there)... It is definitively not the usual bootloader with the information about the various ROM components and the "USB" text at the bottom.
Anubis
Solution!
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
You are right and this is what sergiopi and I were referring to , specifically this post
http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
We were refering to the whole thread so you could learn the background.
However you are incorrect in your advice about how to enter bootloader
All you need to do is hold in the camera button and reset
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
Thanks - you are giving me some hope! I am on a business trip now and my Athena is at home, but I will try that as soon as I am back
Anubis
Before you start, backup anything on your phone you might want to keep after the new Rom has been flashed as all contacts, emails, texts, notes, Internet BookMarks/ ect. WILL be lost!!
PimBackup is good and free (copy any mms attachments to your storage card or computer seperately)
[FONT="]***THIS TUTORIAL IS FOR THE GSM RAPHAEL'S ONLY!!! DO NOT USE WITH CDMA VERSIONS***[/FONT]
[FONT="]If your phone has a SIM Card Slot then its a GSM Model. Carry on reading.[/FONT]
[FONT="]If it has no SIM Card then its CDMA and you should not use this procedure.[/FONT]
[FONT="]**USE THE WIKI FOR EVERYTHING YOU WANT TO KNOW ABOUT YOUR RAPHAEL**[/FONT]
[FONT="]*ONCE YOU HAVE FLASHED A HARDSPL ITS PERMANENT. YOU DONT NEED TO DO IT AGAIN WHEN FLASHING NEW ROMS OR RADIOS*[/FONT]
[FONT="]*DO NOT start another process while the flashing process is taking place*[/FONT]
[FONT="]*DO NOT click off of the status bar... Let it stay in the foreground* [/FONT]
[FONT="]*DO NOT let the Screensaver activate*[/FONT]
[FONT="](any of these can lead to a bad flash and possibly brick your phone)[/FONT]
*FLASH HARDSPL BEFORE FLASHING ANY CUSTOM ROMS*
[FONT="]1. YOUR DEVICE MUST HAVE AT LEAST 50% BATTERY POWER FIRST BEFORE ATTEMPTING EACH STAGE[/FONT]
[FONT="]2. FLASH HARDSPL[/FONT]
Before flashing make sure you have installed Microsoft .NET Framework 3.5 on your PC
[FONT="]Flashing via ActiveSync with USB Lead (thanks to [/FONT][FONT="]OliNex)[/FONT]
1. Download Hard-SPL package and unzip it to your Hard Drive. Make sure it's launched from a local drive (not through network drive, etc.)
2. REMOVE SIM and SD CARDS!!
3. Turn phone back on and let it boot back into your operating system
4. Connect your phone to PC with a USB cable and wait until it syncs with your PC
5. Run RaphaelHardSPL-Unsigned_190_1_3.exe
6. Follow steps in the RUU (Rom Update Utility), check device for prompts after PC shows loading bar
7. It should go to a black screen now
8. SPL flashes, device automatically reboots, job done
9. To confirm you installed it correctly, go into bootloader mode (tricolour screen!) and verify the screen shows 1.90.OliNex
[FONT="]**To enter Bootloader and check HardSPL version; with the device turned OFF, press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears**[/FONT]
[FONT="]NOTE 1: You will not see the SPL version during normal boot, that is the OS version, not SPL![/FONT]
[FONT="]NOTE 2: Anyone having problems with the device entering SSPL automatically, please copy SSPLManual.exe from the download to the device and run it. Once the screen is black, run RUU manually from the PC.[/FONT]
[FONT="]NOTE 3: This is an unsigned Hard-SPL. no limitations on flashing ROMs or radio packages. Also, this has overwrite protection, if someone needs to revert to stock SPL for warranty reasons, go *HERE*[/FONT]
[FONT="]NOTE 4: DO NOT use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! If you want to flash some other rom, then use customruu from *HERE* [/FONT]
[FONT="]3. SIM AND CID UNLOCK [/FONT][FONT="](OPTIONAL)[/FONT][FONT="].[/FONT]
[FONT="]Note: You do not need to SIM or CID Unlock your phone to flash a new Rom.[/FONT]
[FONT="]If, however you want to flash Diamond/ Blacksone Radios OR use your phone on a different Network then you MUST Unlock your phone.[/FONT]
[FONT="]To Unlock your phone go *HERE*[/FONT]
[FONT="]4. DOWNLOAD AND FLASH YOUR PREFERED ROM.[/FONT]
[FONT="]Flashing Via ActiveSync[/FONT]
[FONT="]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer[/FONT]
[FONT="]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT="]3. Turn phone back on and wait until it syncs with your PC[/FONT]
[FONT="]4. Run the Raphael_RUU.exe (or [/FONT]RaphaelWrapper.exe if thats included instead) [FONT="]from the Roms Folder[/FONT]
[FONT="]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]6. Follow onscreen instructions to set up your New Rom[/FONT]
[FONT="]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards[/FONT]
[FONT="]8. Turn phone back on and set up as required[/FONT]
[FONT="]Flashing Via MicroSD Card[/FONT]
[FONT="]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do)[/FONT]
[FONT="]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer[/FONT]
[FONT="]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT="]4. Copy the RAPHIMG.nbh file to the root of your microSD Card[/FONT]
[FONT="]5. Remove Sim Card and Restart phone
6. Plug the microSD Card into the phone[/FONT]
[FONT="]7. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears[/FONT]
[FONT="]8. Follow the onscreen instructions to start flashing[/FONT]
9. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT="]10. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]11. Follow onscreen instructions to set up your New Rom[/FONT]
[FONT="]5. FLASH PREFERED RADIO IF DESIRED (OPTIONAL).[/FONT]
[FONT="]For more information about different compatible Radios that you can use go *HERE*[/FONT]
[FONT="]**If you want to Flash a Non Raphael Radio then your phone MUST be Security Unlocked** [/FONT]
[FONT="]Flashing Via ActiveSync[/FONT]
[FONT="]Sync your phone with the PC, Run the Raphael_RUU.exe from the Radio's Folder and follow the instructions.[/FONT]
[FONT="]Flashing via MicroSD Card[/FONT]
[FONT="]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do)[/FONT]
[FONT="]2. Download your prefered Radio from the Raphael Rom Develpoment Page and unzip/unrar it to your computer[/FONT]
[FONT="]3. Goto the Radios Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT="]4. Copy the RAPHIMG.nbh file to the root of your microSD Card[/FONT]
[FONT="]5. Plug the microSD Card into the phone[/FONT]
[FONT="]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears[/FONT]
[FONT="]7. Follow the onscreen instructions to start flashing[/FONT]
[FONT="]8. After the flash finishes press the reset button with the stylus to reset the device[/FONT]
[FONT="]6. JOB DONE[/FONT][FONT="]. Well Done YOU DID IT!![/FONT]
[FONT="]I have attached all the files needed so you dont need to hunt around for anything. Good Luck.[/FONT]
[FONT="]*DISCLAIMER*[/FONT]
[FONT="]I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.[/FONT]
** FREQUENTLY ASKED QUESTIONS AND HELP WHEN FLASHING **
1. What the benifits are of flashing a new rom?
Flashing a New Rom basically gets rid of all the garbage thats included on Stock Roms and Flashes a Clean, Optimized, Fully loaded Rom that will squeeze every ounce of speed and stability from your phone. Chefs usually include all the programs you are ever likely to need and because the Rom has been cleaned out you are left with more memory to play around with.
2. What are the different types of Unlock? (answer by DaveShaw)
The three stages of unlock are:
SIM: Allows you to use SIM's from another carrier. Can be done using codes or unlocker programs on xda-devs.
Security: Allows you to flash radios from another device (i.e. Raphael) - It does other stuff, but this is all the casual user will use it for
CID: CID unlocking is an old concept, nowadays you flash Hard SPL instead. This lets you flash any ROM, Splash or Radio (depending on sec unlock) to your device. N.B. the CID is the carrier ID (e.g. HTC__001). The stock SPL's only let you flash ROM's that match the CID in the ROM image with the CID on your device.
Also, SuperCID is an even older concept no longer valid on newer devices.
Wow, Great job Mskip!
Just wat i was looking for.
A couple questions though...
1. These instructions will also work on the Fuze, right?
2. Once the phone is done flashing and it is booting up, we are sopposed to HARD RESET when we get to the Stylus Config part?...I didnt know that...ive read some other tutorials, and this step isnt included? ?
Fuze, yes. Sprint, no. There's no Hard-SPL for CDMA phones yet I believe.
Thanks a lot! just what I was looking for (the bit about not needing CID unlock to flash roms.. just hardspl).
gj, mskip, but shouldn't you be clear that your instructions and links are only for GSM Raphaels???? As of the past few weeks the flood gates are now open among 5 North American carriers for the CDMA version of the Raphael. No sense in encouraging confusion and hassles from those less in the know.
There is a release for an unlocker for the CDMA phones, but after a quick search some may mistakenly find themselves to your links and info here.
Keystone said:
gj, mskip, but shouldn't you be clear that your instructions and links are only for GSM Raphaels???? As of the past few weeks the flood gates are now open among 5 North American carriers for the CDMA version of the Raphael. No sense in encouraging confusion and hassles from those less in the know.
There is a release for an unlocker for the CDMA phones, but after a quick search some may mistakenly find themselves to your links and info here.
Click to expand...
Click to collapse
Thanks for the info its been noted in the tutorial. I was only asked to write it last night so any information or changes needed are welcomed
Which button is the "action button"?
mhumphrey said:
Which button is the "action button"?
Click to expand...
Click to collapse
Its the ENTER (center) Button. I have amended the instructions to make that part easier to understand.
might sound stupid, but I think you should say what RUU means and what it is...
first time I flashed hardSPL I couldnt find what this RUU means (while reading steps before flashing).
I started flashing without knowing what it was, when I opened the .exe its title was self-explaining, but its hard to know before starting... because the .exe name is not RUU or something like that
Sorry for bad english!
respider said:
might sound stupid, but I think you should say what RUU means and what it is...
first time I flashed hardSPL I couldnt find what this RUU means (while reading steps before flashing).
I started flashing without knowing what it was, when I opened the .exe its title was self-explaining, but its hard to know before starting... because the .exe name is not RUU or something like that
Sorry for bad english!
Click to expand...
Click to collapse
Done. Thanks for the input
Thanks great guide!
Wish i had this my 1st time flashing i was confused as ever
Thanks for taking the time to write this guide for all of the noobs (like me ). I'm still unsure whether I'm willing to gamble right away with my Fuze next month, but I've made sure this thread is bookmarked in case I decide to take the plunge!
What should one do if using the MicroSD card method and the Olinex HardSPL says Loading... No Image File!
Coromoto said:
What should one do if using the MicroSD card method and the Olinex HardSPL says Loading... No Image File!
Click to expand...
Click to collapse
you cant flash HardSPL via microSD Card
Bricked Fuze?
I was using OliPro Rapheal Unlocker and seemed to have bricked myself. (my fault, I understand the risk) I'm not a total newbee, but first time I ran into this. Any ideas how to get past a Upgrade ROM code error? Updated from 8525 to Fuze.
lmeyers said:
I was using OliPro Rapheal Unlocker and seemed to have bricked myself. (my fault, I understand the risk) I'm not a total newbee, but first time I ran into this. Any ideas how to get past a Upgrade ROM code error? Updated from 8525 to Fuze.
Click to expand...
Click to collapse
I dont recognize the SPL version in your signature is it from Oli's Sim/CID Unlocker?
Can you explain exactly what you have done to your phone and when you bricked it please. Also can you load your Rom up or does it get stuck.
Have you tried flashing the HardSPL from Step1?
lmeyers said:
I was using OliPro Rapheal Unlocker and seemed to have bricked myself. (my fault, I understand the risk) I'm not a total newbee, but first time I ran into this. Any ideas how to get past a Upgrade ROM code error? Updated from 8525 to Fuze.
Click to expand...
Click to collapse
If you flashed the hardspl, then you should be fine and should not have done any lasting damage. You didn't read the part of the instructions that tell you that you must first flash a 1.01 version of the att radio. You can get that here:
http://www.rapidspread.com/file.jsp?id=v3q7csfizy
If you don't then you get the rom upgrade error. Just put your phone into bootloader (tri-color screen), and flash that radio. Also, as always, questions about specific roms, apps, etc should be posted in the thread they came from. That is where all the people most knowledgable about the subject are most likely to read it.
@Mskip, i think that SPL is for his 8525 not his fuze.
scotchua said:
If you flashed the hardspl, then you should be fine and should not have done any lasting damage. You didn't read the part of the instructions that tell you that you must first flash a 1.01 version of the att radio. You can get that here:
http://www.rapidspread.com/file.jsp?id=v3q7csfizy
If you don't then you get the rom upgrade error. Just put your phone into bootloader (tri-color screen), and flash that radio. Also, as always, questions about specific roms, apps, etc should be posted in the thread they came from. That is where all the people most knowledgable about the subject are most likely to read it.
@Mskip, i think that SPL is for his 8525 not his fuze.
Click to expand...
Click to collapse
oh ok lol thanks for the input scot
mskip said:
you cant flash HardSPL via microSD Card
Click to expand...
Click to collapse
I did know and realize that, and your walkthrough doesn't give instructions for that either, but rather for flashing a ROM using the mSD method.
I was referring to flashing a new ROM from the MicroSD card and getting this error message in the HardSPL Bootloader screen. The ROM image has the proper name (RAPHIMG.nbh) but isn't seen by the OliNex bootloader.
[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?