Related
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Will this work?
I saw this on said thread, but I presume it applies for a Herald phone, will it work?
The tricolor mode is "bootloader mode"?
Isn't there some sort of restart that can fix it?
Can someone elaborate on this? I'm really a super-noob!!!
"Try a SD card flash to unbrick your device
This is how:
MAKE SURE THE HERALD IS FULLY CHARGED BEFORE STARTING THE PROCES
#01 Download your original RUU
#02 Download (if not yet installed) WinRar and install
#03 Copy your full sd micro card to your harddisk and format your card with FAT 32
#04 Rightclick the downloaded exe file with your original RUU, click Unpack here
#05 In the map the will be created you will find a file (or similar) called RUU_signed.nbh. Copy this file to your formated sd microcard.
#06 Rename the file to Heraimg.nbh
#07 Get your Herald into bootloader modus by pressing the comm manager button and the camera button and pressing the reset button at the same time. Do not release both buttons until your in bootloader.
#08 Once in bootloader pop in your sd micro card.
#09 As soon as your card is popped in the screen will say something like "Reading SD card". Wait it out till it says "Push button to start" and slide the indicated volume slider down.
#10 The Herald will start the flashing proces. Wait it out till it says "Press any button" and hit the send button.
#11 Perform a hard reset
#12 Voila! Your back in business"
velascoperroni said:
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Click to expand...
Click to collapse
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
timothyjok said:
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
Click to expand...
Click to collapse
Already did that... still on "brick" mode...
Question: is my warranty still valid? I bought it 3 days ago.
you can solve simply to launch original upgrade to wm6 rom
glenbo said:
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Click to expand...
Click to collapse
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Yes, You Are Correct!
pfunkside said:
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Click to expand...
Click to collapse
Yes, that is the correct path for him to take, install a 6.0 ROM first, before installing a 6.1 ROM. I suggest he install the T-Mo official wm6, just to get things started in the right direction again.
(1) If the device is still in the tri color mode (bootloader mode), that's a very good sign, it's not bricked. Connect the device to your PC via active sync in the tri color mode, you may think that the device is not connected to Your PC but it is, it may not look like it's connected, run the official T-Mo wm6 ROM RUU WWE, it will install on your device as long as your device is in the tri color mode.
(2)Once you get the wm6 ROM installed on your device, you must first SDA_ApplicationUnlock your device, next you want to Certificate AppUnlock and SurrealApplication Unlock your phone. Now, the reason you are doing all these unlocks are because you coming off the T-Mo wm6 ROM.
(3)After all this have been done, it now ok to try to install the 6.1 ROM on your device.......!
Great support!!! But now comes the obvious question from the n00b of the n00bs!!!
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
T-Mo Wm6
velascoperroni said:
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
Click to expand...
Click to collapse
Is your mobile device still in the tri color mode, if so just connect it back to your PC via active sync, It will accept the download! OK you can get the T-Mo wm6 at T-Mo's website, if not I will send you a link with the T-Mo wm6 RUU. Don't panic, you are still in the game.......!
Update!! Phone unbricked but still on WM5!
Ok... I used this ROM: HTC_S620_WWE_1.27.405.1_4.1.13.44_02.94.90_Ship.exe
It went thru the upgrading process but got stuck at 3%, anyway, it finished with a message like "this ROM cannot be used for your phone" or something and restored WM5.
Now I will follow instructions on the thread: "The Full Guide To Upgrading From Windows Mobile 5 to 6" and I'll be posting my acomplishments on this thread.
Question: The reasons for me not being still able to upgrade may be:
1. I haven't unlocked phone,
2. My phone is for Mexico and cellphone co. "Movistar", or
3. I'm running Windows XP as a virtual machine (via parallels) on an intel Macintosh and somehow there's a problem with the USB drivers.
I'm rooting for option 1 (but kavana's upgrade was supposed to already unlocked it). Option 3 maybe but then, why do I get Activesync to run? Option 2 would be a bummer!
T-Mobile WM6 RUU WWE ROM
Get the T-Mobile official Wm6 RUU WWE Rom here http://www.mediafire.com/?0vtw32zmuz3 ......!Oh! I throught you had a Excalibur.....!
Just can't seem to upgrade WM5 to WM6!
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Your Answer Is In jockyw2001 Thread
velascoperroni said:
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Click to expand...
Click to collapse
A easy frix, but read the instructions very carefully, jockyw2001 thread is located in the sticky section. What you are looking for will be in post #1.........!
New Instructions
Run the Excalibur Uspl-CID ByPass.zip, extraxt on your PC and open it there, you will see several file folders. Open the one that say (uspl) MS-Dos batch File, follow on screen instructions by pressing any key. This time when you see the white screen on your device do not panic! Run the HTC WM 6 ROM, this is done while the screen is still white on your device. Just follow the on screen instructions on your PC.............!
Now I definitively bricked it!
I ran the CID unbloker, screen went blank, ran the ROM, it got to 16% and made me do a recovery, after the recovery it gave me the same "invalid vendor id" message and it automatically restarted the phone, but...
The restart stopped at the HTC intro screen!! I've restarted it several times and it just stops on the first HTC logo screen... even a hard reset won't fix it!!!
HEEEEEEEEEEEEEEEEEELP!!!
Here is a visual aid.
You are not reading into detail. Use the Tmobile rom instead of the HTC Rom.
http://forum.xda-developers.com/showthread.php?t=368998&highlight=Jamerican
Still Bricked!!!
Yeah!!! superb visual aid!!!
I just wish I had seen it before I bricked it!!!!
This is the current state of my phone: I press power, I see a white screen with the HTC logo in the middle, the phone vibrates, still the same HTC logo... and it is stuck that way! I can't turn it off, I have to take out the battery!!
I've tried a hard reset, same thing happens! It stays stuck on the HTC logo screen and I'm forced to pull the battery out for the phone to shut down.
It is obviously not recognized in any way when I plug it to the PC's USB.
What made this happen? HTC Generic ROM got stuck on 16% before telling me "invalid vendor id", restarted the phone and voila: brick!!
Boy, I wish I was back in the tricolor mode!!!
IS THERE NOTHING I CAN DO?
I'm seriously thinking about going back to the vendor on monday and saying: It was like this when I woke up (I just bought it three days ago!!!)
If it gets that far, it doesnt seem totally bricked, ima PC man, so this may be off, but it seems like some kinda bootloader error on the phone itself....IE, the HTC screen is all that the bootloader tells the phone to load. Have you tried forcing the phone into bootloader mode?
I Looooooove Google!!!
OK... I found a turnaround for the problem... got it to go to bootloader mode!!!
Whenever something like these happens to you this is the hard way to put your excalibur/dash in bootloader mode:
1. Take out battery and sd card;
2. Plug your USB cable to your PC (not yet to the phone)
3. Press and keep holding the SIMB. key (the one with the camera next to the space bar)
4. Plug your USB cable to your phone (while still pressing the SIMB. key)
5. Voila: You are in bootloader mode!!
This was gotten for a 15 min. search in google!!
Now... I'll keep going with my WM5 to WM6 upgrade...
Hello Experts,
i have read a lot of the Threads here, but i can't find a good information
about my O2 Cosmo. My Dash is Simlook free and SuperCID enabeld.
I found this instructions:
Tools you need:
===============
- HexWorkshop from http://www.bpsoft.com/downloads/-
the ROM of your choice
- Winzip or Winrar
- a valid UNL file for YOUR phone
Preparation:
============
a) install HexWorkshop and Winzip or Winrar on your pc
b) in explorer on pc, RIGHT click on the ROM of your choice and use: "Extract files to folder ..." from conext menu Now it will unpack all the files
c) in the new folder you will have ONE file like "HRUU_signed.NBH" (*.NBH) RIGHT click on the .NBH file and use: "Hex Edit with Hex Workshop" from context menu
d) You'll see on the 5th row EXCA20000 ==> !!! make it EXCA***** (5 stars) and save the file
e) Now RIGHT click on ROMUpdateUtility.exe and use: "Hex Edit with Hex Workshop" from conext menu
Search for word "BsaD5SeoA" (without quotes, case sensitive)
You'll find it around address 0x3FC6C ==> !!! replace "BsaD5SeoA" with "IMEICHECK" (without quotes) and save the file
ROM-Update:
===========
1) take SIM card and SD card OUT of the phone
2) Connect the phone running windows ce to the pc (normal way).
3) Completely Unlock your phone using our unlocker <== REALLY IMPORTANT
4) After phone is unlocked run unlocker (again) BUT when the unlocker ask for UNL file, remove the USB cable from the phone THEN press "Cancel" on the unlocker select file window (unlocker will close on PC). NOTE: The screen on the device will not show something usefull when in this mode. Most probably it is complete WHITE. !!THIS IS NORMAL!! Don't touch phone, let it like it is!
5) After you closed the unlocker, attach usb cable again (phone has still white screen)
6) start (the modified) ROMUpdateUtility.exe
7) when update finished and device started you will get a message: "Data Crashed, contact service provider" (!NO PANIC!) ==> Simply fix this problem by running the unlocker again and this time select the key file normal way (full unlock process again). In case you have problems please indicate the step letter/number which is not clear/not working for you. If you REALLY do it STEP by STEP exact like described you will have no problem.
Click to expand...
Click to collapse
When i edit the .NBH file, i get a "ERROR 270" message!
When i dont edit the .NBH file, i get a "Invalid Ventor - Error Message"
I try to install this ROM:
"RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.90_Ship.exe"
So my Dash is a German Device, and i want a German ROM, if it is possible!?
OK, i try to go manually in the Bootloader modus, disable ActiveSync for
USB Transfer...and run the RUU Rom...but it allways break down the flash
process at 4% !
...mmh...have i forget any info, that you can help me...i dont know?
Ah Yes...i read in the Thread:
"How to flash a new ROM to your Wizard... a little tutorial!"
Here the link to:http://forum.xda-developers.com/showthread.php?t=298613
But i can see anything on the starting screen, if my dash ist a G3 or G4,
on my start screen ist "ABSOLUTLY - NO - Information" about it!
In the "System Information" i found a RIL Nr. 2.0002 ...
So i think my dash is a IPL/SPL G3...but i dont know it really!
I dont know what i can do anymore, to update my device to WM6.0 or 6.1
Plz, if anyone know what i can do, to fix my problem, plz then tell it to me,
thank you very much, and forgive me about my bad english!
Ok, i test many times this tool "Excalibur USPL- CID BYPASS" ...and yesterday
it works suddenly...i dont know "why" it works, i have done the same, like
every time i try it, but yesterday my dash move to the needed "WHITE
Screen"! And so i able to run the Rom Update, and it works fine!
Ah yes, my Phone tell me i'm in "SuperCID" Mode...so "WHY" i must use
this "CID Bypass Tool" ....crazy??? Or is my Phone a Liar...?
I have now installed this Rom, it Works a bit faster i mean:
RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.90_Ship.exe
But it is the same Rom Vers, like my old O2-Cosmo Rom, WM5.0 (1) with
Future Pack. But i have now the HTC Splash Screen!
So i want now to install this Rom (with WM6.1) :
"NoThrills_WM61_GER_V3.exe"
This is a "Kaiser" Rom... "Warum eigentlich Kaiser, hat der Beckenbauer damit
was zu tun...*g*
But when i try to run again the "Excalibur USPL- CID BYPASS" tool, my
dash show me only the "Linux Monkey" (Pinguin) Screen and hang up the
Phone, so that i must remove the battery....
The "White Screen" (that is the Screnn you must have to flash your Rom),
will dont come anymore....i dont know how...??? I start this batch file,
"Uspl.bat" ... and follow the instructions....mmh....allways i get the Linux
Monkey Screen...and not the white screen, "WHY" ?
Anybody a hint, how i can move into the "White Screen" Modus?
And a Question, is this Kaiser Rom compatible to my HTC S620 ?
Please belive me, i read a lot here...but i cant figure out this..., this Forum
here is a bit confusing, on many Threads you can read other informations!
Plz anyone, tell me (who know it) how i move exactly in the White Boot Screen?
Thank you!
If I understand you right you flashed a rom from the HTC Kaiser on your Dash. That's Windows Mobile 6.1 Professional for Touch Screen Devices. You need a rom from this thread for your Dash, not the Kaiser thread. Those ROM's are specifically for that phone. I doubt they'd even work on other Touch Screen phones because of it has the radio (I believe Radio is like Drivers in Windows, I may be wrong.) for that phone. As to fix your problem. I have no clue. Maybe you can get lucky and reflash it with an Official Dash ROM for your phone, but better getting advice on that from one of the more experienced people here. I'm a bit of a newby when it comes to this phone stuff. Good luck...
drkfngthdragnlrd said:
If I understand you right you flashed a rom from the HTC Kaiser on your Dash. That's Windows Mobile 6.1 Professional for Touch Screen Devices. You need a rom from this thread for your Dash, not the Kaiser thread. Those ROM's are specifically for that phone. I doubt they'd even work on other Touch Screen phones because of it has the radio (I believe Radio is like Drivers in Windows, I may be wrong.) for that phone. As to fix your problem. I have no clue. Maybe you can get lucky and reflash it with an Official Dash ROM for your phone, but better getting advice on that from one of the more experienced people here. I'm a bit of a newby when it comes to this phone stuff. Good luck...
Click to expand...
Click to collapse
Thank you!
But "NO" i don't flash my HTC S620 wit a Kaiser Rom..."What a Luck" ...i try
to do it...and now im Happy that this have not work for me!
I actually install this Rom:
RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.9 0_Ship.exe
I have now understand, what is a Kaiser ROM, it is the Device Name, oh
Man...i'm so a dummy....haha...
But i have a success, i change my O2 Rom to a HTC Rom
The Question now is, how i move in the "WHITE BOOT SCREEN" ?
That i'm able to Update my Rom to a WM6.1, if posible, a German 6.1 Rom.
Is here a German WM6.1 Rom?
Is a WWE a Multilingual Rom, is in such ROMs German Language included?
And how i can remove the CID forever, so that im able to update a ROM
without a CID Bypass Bootloader?
Any ideas?
The thing is, ...this CID Bypass Bootloader work "ONCE" and now that
Bootloader dont work anymore...i dont know why...i get only the Linux
Pinguin Screen...and this is a "Hang up Screen" so that i must remove
the Battery, for a new start.
But i get nevermore the "White Boot Screen" ...how is this posible?
I do the same, like before i do...mmh...???
If I understand what's been said. You need to re-run the CID-Bypass anytime you reflash you phone. As for a German ROM. I am not sure. Ypu'd need to look around through the furom. You could try the "Seach" feature and see what you come up with.
drkfngthdragnlrd said:
If I understand what's been said. You need to re-run the CID-Bypass anytime you reflash you phone. As for a German ROM. I am not sure. Ypu'd need to look around through the furom. You could try the "Seach" feature and see what you come up with.
Click to expand...
Click to collapse
Thank you,
but i try to run the "CID Bypass" but the "CID Bypass" run every time
into the "Linux Pinguin Screen" ...(i think it is programed in Linux?)
But the same "CID Bypass Bootloader" - work - for me "once" !
But now, not ! I dont know why?
With this CID Bypass Bootloader, i flash my Q2 Rom into a HTC Rom !
But that was only possible, as my dash move with this "CID Bypass Bootloader"
INTO a "White Boot Screen"...!
But "HOW" this was possible...i dont know...now this CID Bypass Bootl.,
wont work anymore....
You know what i mean?
The same tool (CID Bypass) wont work anymore, it work one time only.
When i now try to run this CID Bypass, i get a "Linux Pinguin Screen" in
Black. So there is a little Linux Pinguin "Preloader" ...and then the Phone
have a SOD..."Stand of Death" you Guys call that so, i think so!?
To search here, is very strange for me....i get results of all Forums here!
That was the reason why i want to try the Kaiser Rom, while i search
here in the Excalibur Forum...so i had think so, that was wrong, you know!?
Sorry, my english is not good enough to tell exactly my expirience!
But Thank you for Advice!
Hum, does it still look like windows mobile? If so they may have just changed the load screen. Either way when you run the bypass program, there' one step that'll show a screen on the phone when in windows mobile itself and you must press the center soft button to "continue" and then it'll enter the white screen mode. Sometimes I forget this step and bounce through the steps missing that. If you can't get into windows mobile, try reflashing with your phones official ROM first. They don't require the white screen. There's also a way to enter the bootloader screen by holding down a button, I forget which, while you press power to turn the phone on.
drkfngthdragnlrd said:
Hum, does it still look like windows mobile? If so they may have just changed the load screen. Either way when you run the bypass program, there' one step that'll show a screen on the phone when in windows mobile itself and you must press the center soft button to "continue" and then it'll enter the white screen mode. Sometimes I forget this step and bounce through the steps missing that. If you can't get into windows mobile, try reflashing with your phones official ROM first. They don't require the white screen. There's also a way to enter the bootloader screen by holding down a button, I forget which, while you press power to turn the phone on.
Click to expand...
Click to collapse
...no no, this ROM runs great! I have no Problem with this Rom!
But i have found a Solution "Yeah" !
For all who want to flash a O2 Cosmo!
Try this Link: Click
Thanks to the Uploader, found it by searching!
The last in line: "Unlock_phone_files.zip" !
Follow the steps in the text document!
Work fine for me!
But when you want to flash, and you get a connection ERROR, remove
the USB cabel, and put it back on your Dash, and run then only the
"ROMUpdateUtility.exe" again and it will work.
(Your srceen are allways WHITE!!!)
I had flash for 10min the "RUU_Excalibur_SPL-1.11_UpgradeOnly.exe"
You must extract the exe file, and copy the *.nbh file to folder 3!
After you run the "Auto.bat" and the Connection Error, click finish,
remove the USB cabel, put it back on the dash and run again and only
the "ROMUpdateUtility.exe" !
All work fine!
Thank you Developers!
Hi there, I'm Italian I'm here because your'e the only one on this planet who can help me.....so sorry for my english.....
I had some trouble with my diamond, the touch screen is no longer working so I have to send it back to htc, now I have to restore original rom and spl.....
I installed olinex 1.40 and the last original italian rom 2.03....
Now I downloaded my former rom (1.93.772) from italian server, I installed it and everything seemed to be right, (I can't check it because the diamond blocks me at the aligning screen, the touch screen is broken and I can't start the phone...the aligning screen appears to me forever and there's no way to bypass it)...
Then I downloaded the original spl 1.93 from your server...I cant use active sync because I can't start the phone so I have to work in boot mode.....I followed carefully the procedure, that is quite easy, but there is no way to remove the olinex 1.40, the process starts, it reachs 100%, but when i check the spl is always the 1.40 olinex....and restore original spl...I try also the usb trigger mode, with the spl putted as dimndimg.nbh...
Please help me!!!!!!!!! I' going crazy!!!!!
Thank you very much for the attention...
DAVID
do you hear me?
hi
hi, did you check out this? http://forum.xda-developers.com/showpost.php?p=2324837&postcount=20 see if that helps you.
I read everithing and now I'm a sort of diamond technician, but I cannot solve this problem, I can only flash in bootloader mode cause the telephone cant initialize windows, it' blocks in the aligniment screen and can't go on, so maybe the bootloader mode isn't strong enough to by pass the write protection of the 1.40 olinex and overwrite the hardspl...HELP HELP HELP
I'got the same issue, you have to install a rom !! and use ActiveSync in order to get the SPL1.93 ! I think in bootloader mode, you can't change the SPL!
Good luck
Freaky, I have the same issue it will not remove no matter what.
HTC have sent mine back, they say the HardSPL 1.40 OliNex damages the mainboard and causes touch screen failure! They want £230 for a new one
If you find out how to remove let me know, I've flashed all sorts and no luck it still says it.
Andrew
PS) I have activesync working with a failed touch screen (stuck on the align screen window), copying and running stock 193 in /internal doesn't change it. When I try:
http://forum.xda-developers.com/show...7&postcount=20
it sits at 0% then fails. The other program they mention to force it uinto bootloader I can' run obviously because the touch screen is broke.
miscioidi said:
Hi there, I'm Italian I'm here because your'e the only one on this planet who can help me.....so sorry for my english.....
I had some trouble with my diamond, the touch screen is no longer working so I have to send it back to htc, now I have to restore original rom and spl.....
I installed olinex 1.40 and the last original italian rom 2.03....
Now I downloaded my former rom (1.93.772) from italian server, I installed it and everything seemed to be right, (I can't check it because the diamond blocks me at the aligning screen, the touch screen is broken and I can't start the phone...the aligning screen appears to me forever and there's no way to bypass it)...
Then I downloaded the original spl 1.93 from your server...I cant use active sync because I can't start the phone so I have to work in boot mode.....I followed carefully the procedure, that is quite easy, but there is no way to remove the olinex 1.40, the process starts, it reachs 100%, but when i check the spl is always the 1.40 olinex....and restore original spl...I try also the usb trigger mode, with the spl putted as dimndimg.nbh...
Please help me!!!!!!!!! I' going crazy!!!!!
Thank you very much for the attention...
DAVID
Click to expand...
Click to collapse
In order to switch from 1.40 to 1.93 HARD SPL, you must you the jump spl program. It's in my signature. Also read the txt included for the instructions.
Let me know how it goes...
band27 said:
In order to switch from 1.40 to 1.93 HARD SPL, you must you the jump spl program. It's in my signature. Also read the txt included for the instructions.
Let me know how it goes...
Click to expand...
Click to collapse
>> prun JumpSPL.exe ...
ERROR: CreateProcess failed with errorcode = 30123
- UNKNOWNERROR: 0x000075ab
snoopy20 said:
>> prun JumpSPL.exe ...
ERROR: CreateProcess failed with errorcode = 30123
- UNKNOWNERROR: 0x000075ab
Click to expand...
Click to collapse
First plug phone into computer via active sync....
Then:
Copy the following files to the Diamond root directory
"Copy JumpSPL.exe & "copy SSPL"& sspl-1.01-reloc-mod.nb
Then: "execute Diamond SPL now - screen may trun black"
Then: "run DiamondCustomRUU.exe to flash any HardSPL
What is "copy SSPL" ??
snoopy20 said:
What is "copy SSPL" ??
Click to expand...
Click to collapse
Copy means either to right click and select copy to then past it to the root of the diamond directory or you can choose to drag this file to the diamond directory. Then continue to copy the other files.
Another way is to just start with the Diamond-SSPL.exe file and it will tell u to copy these files one by one. Make sure that you are activesynced prior to started this.
What I mean is WHAT IS sspl.exe
It's not in your magic zip file.
And when I find it, how can (I / We) execute it with failed touchscreens?
Still getting ...
>> prun JumpSPL.exe ...
ERROR: CreateProcess failed with errorcode = 30123
- UNKNOWNERROR: 0x000075ab
I'm having the same problem tryng this stuff...does't work at all....I sent 2 private message to olipro but no response....Is there someone out there who can hepl me??????
is there any absurd rom using just the button of the pda excluding the touch screen??????
You must flash in bootloader mode and run ROMUpdateUtility.exe in "C:\ROM" with file "RUU_Signed.nbh" 1.93 version in his directory (C:\ROM).
Use Windows XP and cable miniUSB original and Activesync of course.
1)Use Activesync conected.
2)Copy ROMUpdateUtility.exe and RUU_Signed.nbh (HardSPL 1.93)
3)Enter in bootloader mode
4)From "C:\ROM" run ROMUpdateUtility.exe
Leoarg....I can't activesync the diamond in bootloader mode....I can activesync only if I start the diamond in normal mode....when it reaches the aligniment screen it stops and sinconize
miscioidi said:
Leoarg....I can't activesync the diamond in bootloader mode....I can activesync only if I start the diamond in normal mode....when it reaches the aligniment screen it stops and sinconize
Click to expand...
Click to collapse
mmmm, Ok. What problem!
Why remove the 1.40 is so hard?????.....why flashing in bootloader mode doesn't bypass the overwriting protection?? why olipro is not answering my private message?
Upgrade to Hard-SPL Olipro 1.20 - USB or SD Just Added SD Card Method at Bottom of this Post
10 Step Program
Pulled from Website dated: Monday August 06, 2007 by ??? if someone knows, I'll give credit.
Recovered and Updated Monday October 27, 2009 by SuperSport
because the WiKi has vanished
Hard SPL will allow you to flash cooked ROMs without SuperCID’ing your device and also will protect your device from being bricked in a bad flash. If a bad flash occurs it should remain in bootloader, and you can re-flash another ROM.
Caution!!! Flashing Hard-SPL will Probably Hard Reset your device!!!! Backup all data FIRST!!!
Before you proceed, check which SPL is on your device:
*** Enter Tri Color Screen ***
--Unplug your phone from USB - Helps to avoid freezing USB Ports
--Hold down the Power & Camera Buttons
--While still holding them down, press the Reset Button using the Stylus
--Release the Reset Button, but continue to hold the Power/Camera buttons until you see the Tri Color Screen
*** Enter Tri Color Screen ***
If your SPL is 1.30.Olipro, 1.20.Olipro, or 9.99 CP, then you already have Hard-SPL on your device and can skip flashing HardSPL, although, I recommend using Olipro 1.20 to avoid problems.
If you want to continue flashing Olipro HardSPL 1.20:
Press the Reset Button using your Stylus. Wait for your phone to start back into Windows. Plug the USB Cable into your phone and PC. Verify ActiveSync or WMDC is connected properly. Now you can Flash.
1. Download "Olipro HardSPL 1.20.zip" in attachment below
2. Unzip the Files, and Run the Program "Olipro HardSPL 1.20.exe" This is a small AutoFlash file I created using Olipro 1.20
3. Windows Vista and Windows 7 may confirm you want to run the program. Choose YES.
4. Check the check box, click ‘Next’
5. Also Check this check box, click ‘Next’
6. In the next window, click the ‘Update’ button
This will show the version number of the ROM, radio, or in this case bootloader that you are about to flash.
7. After the version number has appeared, click 'Next'
8. In the following window, click ‘Next’, your phone may ask if it's ok to run the program, Tap 'Yes'.
(After you click this, the flash will begin, so do not disconnect your device or do anything on your computer)
9. A Progress bar will appear on your computer screen, and your trinity will display a grey screen with progress bar. Be patient while your device is being updated. This will only take a moment.
10. Once your device is finished updating, if it did not automatically soft reset, Press the Reset Button with the Stylus. Click the ‘Finish’ button to exit the RUU program.
To confirm Hard-SPL is on your device, re-enter Tri Color Screen following directions above. You should see the following:
Hard SPL 1.20.Olipro
TRIN100
IPL-0.50 (your device may show IPL-1.00)
TRIN100 MFG
SPL-1.20.Olipro
CONGRATULATIONS!! You have now installed Olipro's Hard-SPL 1.20 on your device using USB Method!! Press the Reset Button with your Stylus to restart.
**********************************
Alternate SD Card Method
**********************************
For those who would rather use their SD Card for this (Maybe your USB Port is not functioning). For this method, the way I'm describing, your phone must be running a version of Windows Mobile. Can be any Version, 5-7. If your phone does not currently run, flash back the OEM ROM that came with it Originally. You can find some in my signature.
Caution!!! Flashing Hard-SPL may Hard Reset your device!!!! Backup all data FIRST!!!
1. Be sure you have a, Non-SDHC, SD Memory Card.
2. Be sure the card is formatted Fat32 and Without a Label.
3. Download the attached HardSPL SD.zip file and extract it's contents. Copy both files, SSPL-TRIN.exe and TRINIMG.nbh, to the Root of your SD Card.
4. On your phone, use File Explorer to browse to the Root of your SD Card.
5. Tap the SSPL-TRIN.exe file. This should run the file.
6. On some phones, you will see a security message come up. Select 'Yes' to run the program.
7. You should now see a Grey screen with Blue Lettering. It will be asking you to Press power button. Go ahead and press the power button.
8. You will see the update progress for a short moment, it will restart, and update again, then show "Update Complete - UPDATE SUCCESS" If you see this message, it has worked.
9. Press the Reset Button with your Stylus to Restart
10. Delete the two files from your SD Card (TRINIMG.nbh, SSPL_TRIN.exe). To confirm Hard-SPL is on your device, Enter Tri Color Screen following directions above. You should see the following:
Hard SPL 1.20.Olipro
TRIN100
IPL-0.50 (your device may show IPL-1.00)
TRIN100 MFG
SPL-1.20.Olipro
CONGRATULATIONS!! You have now installed Olipro's Hard-SPL 1.20 on your device using SD Method!! Press the Reset Button with your Stylus to restart.
Maybe if this could be Stickied?
Thanks, it's a very nice guide for Trinty users, clean and detailed, I also recommand using Olipro 1.20 and not 1.30 to avoid problems, especially with 6.5 roms the annoying "WLAN ERRROR" sometimes seen in bootloader mode ...
Yes, make this "Sticky"
Brds,
nAr
Thanks narshorn! Someone else posted this a long time ago on a WiKi I believe, and I just recovered what I could of the original web page and then rewrote it to work with my files. The original page was removed from it's server, so I grabbed as much of the cached version of it as I could, thus, I don't know who did the original.
Also, thank you for the confirmation of using Olipro 1.20 and not 1.30. That was my belief, and I've heard others, but I'm glad you confirmed.
noob here, need help on flash HardSPL.
i encounter error when trying to update my hardSPL. when i try to flash when my phone is tri color screen mode, this error pop out.
ERROR [270]:UPDATE ERROR
The image file is corrupted. please check your update utility.
info update:
at last i manage to flash my phone to hardspl 1.20, i boot my d810 in normal mode, establish active connection with window, then the flash carry on without any error. but the phone hard reset
but, i wonder y i cant flash to hardspl in tri color screen ???
update to 1.20 spl Olipro true sd card not USB
hi and Thanks for so nice explanation. there is a way to update spl with sd card? my USB connection is faulty. if s/o know please let me know how.
tzuki1 said:
hi and Thanks for so nice explanation. there is a way to update spl with sd card? my USB connection is faulty. if s/o know please let me know how.
Click to expand...
Click to collapse
Just added SD Method to bottom of post #1. Good Luck!
thongkh said:
noob here, need help on flash HardSPL.
i encounter error when trying to update my hardSPL. when i try to flash when my phone is tri color screen mode, this error pop out.
ERROR [270]:UPDATE ERROR
The image file is corrupted. please check your update utility.
info update:
at last i manage to flash my phone to hardspl 1.20, i boot my d810 in normal mode, establish active connection with window, then the flash carry on without any error. but the phone hard reset
but, i wonder y i cant flash to hardspl in tri color screen ???
Click to expand...
Click to collapse
Because stupid me forgot that if you don't have HardSPL on your phone, then TRI COLOR SCREEN flashing is not possible. Doh! FIXED above.
Thank you for bringing this to my attention. When I physically went through the steps, I forgot I still had HardSPL on my phone from previous.
I just went through the steps AGAIN after removing HardSPL, and verifed it works correctly as listed in Post #1.
thankz for promptly reply
btw, what d diff between HardSPL 1.20 and 1.30?
thongkh said:
thankz for promptly reply
btw, what d diff between HardSPL 1.20 and 1.30?
Click to expand...
Click to collapse
I've seen many reports that 1.30 caused issues. Olipro, 'the guy who made our Trinity's safe for Flashing', stopped updating the thread, but if you read it, you will find many users reporting problems and asking for the thread to be updated to go back to 1.20.
I've been using 1.20 since it was released, and have NEVER had a problem with it. And believe me, I Flash a LOT!!! I'm expecting my poor Trinity to catch fire any day now.
Oh... Thx for the tutor...that what i need now...
Good job someone remembered howto
Thanks for the reminder - managed to forget how to enter tri-colour screen in the three months since I last reflashed.
I need help here
I have tried each of the methods.
though your explanation and step by step instructins are very clear, istill can't seem to get Olipro's HSPL on my phone. in the case of using active sync, after it enters the tri color screen nothing happens again and the i get an error message (ERROR 260).
When i tried using the SD method, when i tapped the SSPL_TRIN file, it goes stright to the tri color screen ths is the information i have there
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
and for this reason i can seem to flash any rom with success each time it only gets to the tri colou screen and i get the ERROR 260 message.
Anyone with any idea on how i can fix this.
thanks in advance
redoxy said:
I need help here
I have tried each of the methods.
though your explanation and step by step instructins are very clear, istill can't seem to get Olipro's HSPL on my phone. in the case of using active sync, after it enters the tri color screen nothing happens again and the i get an error message (ERROR 260).
When i tried using the SD method, when i tapped the SSPL_TRIN file, it goes stright to the tri color screen ths is the information i have there
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
and for this reason i can seem to flash any rom with success each time it only gets to the tri colou screen and i get the ERROR 260 message.
Anyone with any idea on how i can fix this.
thanks in advance
Click to expand...
Click to collapse
Did you copy the TRINIMG.nbh file to your SD Card also? Was your SD Card formatted FAT32 and No Label?
Using the SD Method, you do not need to be connected to your Computer. Copy both files to SD and do all work from phone.
Let me know if that works or not.
Remove the HARDSPL...
Hi,
How can I remove the HARDSPL from my Trinity and go back to the original?! Thanks!
sergiopedro said:
Hi,
How can I remove the HARDSPL from my Trinity and go back to the original?! Thanks!
Click to expand...
Click to collapse
Only do this if you do not plan to flash any more Custom ROMs, and would like to stick with the OEM ROM (You may Brick your Phone if you flash from the Stock SPL):
Download the "HardSPL SD.zip " file from the first post.
Extract the files
Copy ONLY the "SSPL_TRIN.exe" file to your SD Card.
Run the "SSPL_TRIN.exe" file from your SD Card (This puts your phone into a special mode that will allow the HardSPL to be overwritten)
Now, your phone should be in bootloader mode with:
TRIN100
IPL_SSPL by Des
TRIN100
SPL_1.07.ds
At this point, you can flash your OEM ROM that includes the Original SPL and IPL.
I use this one: http://www.mediafire.com/?v5yjt1zvgjm
Hi all
I have tried to flash with usb but i'm having a problem
i'm using active sync and after i click 'execute' at the mobile screen it enters the tri color screen and it disconnects the usb port. I get an error message (ERROR 246) that says the device is not responding.
I've tryed several times and it has the same behavior...
The tricolor screen shows this message:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
i havent try the sd method because i dont have a sd card right now...
Thank you
rcpamr said:
Hi all
I have tried to flash with usb but i'm having a problem
i'm using active sync and after i click 'execute' at the mobile screen it enters the tri color screen and it disconnects the usb port. I get an error message (ERROR 246) that says the device is not responding.
I've tryed several times and it has the same behavior...
The tricolor screen shows this message:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
i havent try the sd method because i dont have a sd card right now...
Thank you
Click to expand...
Click to collapse
Your mobile screen is showing the correct information, with the exception of USB not showing. As soon as you get to the Tri Color Screen, try removing then reconnecting the USB connection and see if that makes any difference.
Also, when the Tri Color Screen comes up, does your computer ask to install a driver? If it does, be sure to allow that.
SuperSport said:
Your mobile screen is showing the correct information, with the exception of USB not showing. As soon as you get to the Tri Color Screen, try removing then reconnecting the USB connection and see if that makes any difference.
Also, when the Tri Color Screen comes up, does your computer ask to install a driver? If it does, be sure to allow that.
Click to expand...
Click to collapse
Well i just trying all steps again and it worked just fine...go figure!
Thank u anyway
rcpamr said:
Well i just trying all steps again and it worked just fine...go figure!
Thank u anyway
Click to expand...
Click to collapse
Glad to hear you are going. Now you are safe to flash custom ROMs.
Also, remember that each time you flash back to the OEM ROM for any reason, it replaces the HardSPL with the stock one. You will then need to flash the HardSPL back again. At least this is the case for the OEM that I use.
SuperSport said:
Glad to hear you are going. Now you are safe to flash custom ROMs.
Also, remember that each time you flash back to the OEM ROM for any reason, it replaces the HardSPL with the stock one. You will then need to flash the HardSPL back again. At least this is the case for the OEM that I use.
Click to expand...
Click to collapse
ok. thank u so much!