Database Develop

[Walkthrough] How to fix your bricked phone

So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.

WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse

papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...

Too bad it'll be stated a million more times afterwards too.

falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol

ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!

ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?

ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.

falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider

Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.

The instructions to do this are actually in my newbie thread. Which is a sticky.

TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...

help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang

gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......

Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.

And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec

If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.

Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!

foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.

ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.

I Think I just Bricked my AT&T Tilt

Uhh......yea......I was trying to upgrade my Rom to Dutty's Diamond V1 Build 19588. I was using the instructions from Flash-Your-Tilt . I got to Step 4 CID-Unlock it installed 100% rebooted and then nothing. Now the phone will only play the intro with no sound, then go black. It shows in the lower right hand R 1.70.02iNex, G25.65.30, D1.62.00.00. The phone will allow me to do a hard reset but after it it goes through the intro with screen alignment and installs the extra apps, it reboots and then goes black. I did a ton of reading through the wiki's if someone could point me in the right direction or tell me if its toast, it would be much appreciated.
Thanks

Be strong. I think it's only bricked when you can't power it on.
I have a poor net connection and not time atm. So a suggestion if you haven't already, search the forum for the word bricked. I'm sure this has happened before..
There are several tricks that people know so you might be ok. good luck.

Calihoe said:
Uhh......yea......I was trying to upgrade my Rom to Dutty's Diamond V1 Build 19588. I was using the instructions from Flash-Your-Tilt . I got to Step 4 CID-Unlock it installed 100% rebooted and then nothing. Now the phone will only play the intro with no sound, then go black. It shows in the lower right hand R 1.70.02iNex, G25.65.30, D1.62.00.00. The phone will allow me to do a hard reset but after it it goes through the intro with screen alignment and installs the extra apps, it reboots and then goes black. I did a ton of reading through the wiki's if someone could point me in the right direction or tell me if its toast, it would be much appreciated.
Thanks
Click to expand...
Click to collapse
Flash an OEM Rom/Radio Combo. Also it wont hurt if you already CID unlocked to to go ahead and flash a new SPL to it. Should fix any and all issues as your phone is still actually booting and Not bricked

Installing windows the 6.1 ROM from HTC's site worked. Thank you very much for the great advice. If I wanted to now put Dutty's ROM on my phone can I go straight to that, or do I need to restart the whole ROM flashing process(installing Jump SPL, Hard SPL and CID) ?

If you have unlocked it, just put duttys onto the SD card and rename the .nbh to KAISIMG.nbh
Put the phone into bootloader and install Its the fastest most successful method. No worry about a data cable coming out mid flash ( happened once to me....not fun )
Shouldnt have to install hardspl again ( or use JumpSPL )
Just make sure that if you are installing a WM6.0 rom that you have a WM6.0 radio. If not, the flashing process for the radio is the same ( rename to KAISIMG.nbh )

Is there a way to see if I the hard SPL install and CID unlock worked ? Can I just restart the whole process regardless. Sorry for the noob questions.

Calihoe said:
Is there a way to see if I the hard SPL install and CID unlock worked ? Can I just restart the whole process regardless. Sorry for the noob questions.
Click to expand...
Click to collapse
Go into bootloader. If your screen says hardspl somewhere near the top then you're good to go. Check which version because you can have radio problems if you use a WM6.0 spl with a WM6.1 rom. Most recent roms are WM6.1 so try HardSPL 3.29 or higher.
If you don't have hardspl, get it here for wm6.0 roms or here for wm6.1 roms.

many thanks, your advice with the links were invaluable. I read and read and read, but i guess i did not read enough. This site rocks.

Potentially Broken T.HD - Need help!

Hi All,
I have used the search function - but ended up getting confused.
I have a Touch HD that I bought in January of this year (2009) from Mobiles.co.uk (Carphone Warehouse) and is on the O2 network (UK).
I have been using Dutty's ROMs (both 6.1 and 6.5) for months now - and have always used USPL when flashing, using the SD card method.
Over the past 3 days, my HD has been playing up.
When it started, I was using Dutty's R7. The radio was 1.14.something.something. The device was working perfectly, and I was really happy with the ROM and the way the phone was working. I had installed NO other applications with the exception of a different taskbar and obviously SDKCerts.cab
First of all, HTC Sense stopped working - it would cycle between "Loading HTC Sense" and "Tap here to launch HTC Sense"
Then, when rebooting the device, it just hung on the "Smart Mobility" screen. I left it in case it just needed a while to boot, but nothing.
I had no other option than to hard reset.
It worked OK for a few hours, but then HTC Sense started to crash again. So I flashed a new ROM - Lost in Asia or whatever it is called.
Same symptoms.
I flashed Dutty's R7 back and also the new 1.17 radio.
No joy.
The phone also hangs for ages on the Smart Mobility screen - perhaps a full minute where as before, it used to be no more than 15 seconds or so.
The following is displayed on the "Smart Mobility Screen"
1.17.25.09
52.69.25.37H
1.59.Dutty
The bootloader screen (before running USPL) shows the following:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) V6
So the question I'm asking - is... Is my phone suffering some kind of hardware malfunction, or is this a known and fixable fault that I somehow have caused?
If the phone looks like it is malfunctioning, how would I go about returning it to stock so that the CPWH repair centre do not know it's had an unofficial ROM installed?
I'd like to add that whilst I'm very PC literate, I'm no programmer and a lot of the stuff here is alien to me hence my confusion - I just know how to flash a new ROM etc.
Thanks to anyone that takes the time to help me - I'd be really thankful to anyone that helps me sort this - be it tell me how to fix the device, or tells me to take it back!
Thanks in advance & Regards,
Chris.

Will D/L and flash Dutty's R0 Holy Grail ROM and see if that makes a difference...

If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.

a1gp said:
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
Click to expand...
Click to collapse
Thanks for the quick reply.
So is it perhaps better to revert to the original ROM before flashing a cooked ROM? I always Hard Reset twice after flashing as understand this helps.
OK - so the 1.56+ situation - I was under the impression that using the latest USPL (2.5) when flashing was OK? I have never had the colour problem... but perhaps if I'm flashing wrong then these problems could be to do with this?
Thanks again...
Chris

The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.

Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.

mcdull said:
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Click to expand...
Click to collapse
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?

a1gp said:
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
Click to expand...
Click to collapse
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris

constablechris said:
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
Click to expand...
Click to collapse
what do you mean hang for age?
1 minute is nothing if it turns out boot up.
There are chances that the nand flash needs to refresh and wasted some times. But it won't be forever.

constablechris said:
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
Click to expand...
Click to collapse
there's an original rom on htc.com for blackstone just use that one.
hope it will turn out right for you

I thought I'm the only one who had this problem. Last Sunday my blackstone started to freeze on the smart mobility screen too. I flash 3 different roms because I thought its an rom issue with no luck. On Monday it even managed to hardreset itself after I waited for about 15 min in the smart mobility screen.
After that I flashed a stock rom and it seem to be fine by now.
But now I will flash a custom again, the stock one is so 6.1

Bad Flash?

Ok, here's what i did:
I'm sending my xperia back to vodafone, so i need to restore stock rom and spl. I flashed a NL Vodafone R3AA rom (found here) to my phone yesterday, which worked perfectly. Did a hard reset, and went on with restoring stock spl.I tried using the special RUU with a replaced stock spl .nbh (the method described in one of the topics here), but the RUU couldnt find my phone. Since i didnt have another PC here, i tried to flash the .nbh to my phone via the micro SD method.
This went well, the progress bar filled up and disappeared, followed by 10+ minutes of "loading". Advised by a friend, i pulled out the battery, put it back in the device and powered it on. The phone instantly booted, showing the bootloader-screen and saying it's going to resume flashing the device. Followed by another endless "loading" screen.
But, since i got a chance to look in the bootloader-screen, I saw the SPL version was now 0.72.000 (or something like that, at least the OliNex text was gone). Afaik, this means the stock spl is back. I tried replacing the stock spl Kovsimg.nbh with the default one provided with the custom RUU (which is OliNex HardSPL, right?), but it showed the same "loading" screen. I havent tried flashing the rom again, since the bootloader says it's on stock spl at the moment...
What can i do? I guess they dont accept bricks over at vodafone...
Thanks in Advance,
Sorbo

using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!

You also need to flash the radio back to stock (not sure what version it is, but it's around here somewhere) otherwise you'll face flash issues. This means flashing HardSPL flashing the radio, flashing StockSPL again and return. Also, best flash R2A. Not sure if R3A was ever properly released.

Ok guys, thanks for the replies
Jonny4911 said:
using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!
Click to expand...
Click to collapse
The phone is back on stock spl, is it possible to flash a rom? Or only stock roms? (Sorry for my dumb question, havent been into flashing for a few months now)
aethelbert said:
You also need to flash the radio back to stock (not sure what version it is, but it's around here somewhere) otherwise you'll face flash issues. This means flashing HardSPL flashing the radio, flashing StockSPL again and return. Also, best flash R2A. Not sure if R3A was ever properly released.
Click to expand...
Click to collapse
Ok, thanks for the tip R2AA it is!
When flashing the rom the radio was also updated, but i'll try this

R3AA was properly released!
if you want to be cure of complete stock why not just use SEUS?
and there is no need to flash radio with stock ROMs as they're included, all your doing is flashing a radio extracted from a stock rom anyway! this means you don't have to hardspl

Jonny4911 said:
using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!
Click to expand...
Click to collapse
And this was the winning tip. Just flashed back the R3AA rom (vfone NL), even though i doubted if it would work (since the bootloader said it was back on stock spl), but it did.
Phone works again. Bootloader now says 0.78.000 (or something like that, no OliNex), so i guess it's ok now. RUU still isnt able to flash the phone, tried on 3 different pc's ( win7 x64, vista x86, xp x86), but i cant flash the phone...
Ah well, i'll try to send it back, see what they come up with. Thanks a bunch!

Remove Hard-SPL

Hi, can you help me with how to remove the Hard-SPL to upgrade to the original ROM for HTC Touch Pro 2. I'm from Bulgaria, the phone is not locked to an operator (AT & T Orange), etc. What files will I need and how. I also want to download the original Rom from the site of HTC. Thanks in advance!

http://forum.xda-developers.com/showthread.php?t=550131
All info you need is here.
One note from my experience: first downgrade to original rom then install original spl. I had an issue, it was bricked, but all it needed was to one more time upgrade original rom.

You mean that you must first install the original Rom (I could not download it from HTC's site can help you). And then correct me if I'm wrong:
First you say to install the original ROM.
2nd to download RhodiumSPLRelocker_079SPL.zip unzip it and run. Exe
3rd Stock_SPL_Restore_084.zip to download and in the same way as putting a new ROM to choose it (unzip it first)
Do I need to do Hard Reset at any time? And maybe a little help otkade to download original ROM.

I did this from the link you gave me in boot loadera get out this Oninex, then I load again ROM-a which had previously tried to put my original and gave me an error

The instructions say to flash the stock ROM before you re-lock SPL.

I have failed to: (i already made a re-lock SPL ... now what to do: (
I am still with Energy ROM, which I had to do before re-spl .. in boot loadera now I do not go Olinex 0,85 as before ... what to do?
Sorry for my bad English!

ivailo0 said:
I have failed to: (i already made a re-lock SPL ... now what to do: (
I am still with Energy ROM, which I had to do before re-spl .. in boot loadera now I do not go Olinex 0,85 as before ... what to do?
Sorry for my bad English!
Click to expand...
Click to collapse
i don't think you can re-lock your phone with custom rom on your phone but what you do is hard_spl it (if spl re-locked) then
task 29 ----> install stock rom ----> re-lock spl
good to go

Isteglih his RUU_Rhodium_S2_HTC_Europe_2.07.401.1_Radio_Rhodium _4.49.25.91_Signed_Ship
this is the right Stock Rom correct me if I'm wrong. Inastaliram it and to 0% gave me an error. - 294 Invalid Vender ID.
But it's not e what I need.
I'm not too far into things ...

Please help, now I can not get no ROM, and this olinex do not write anymore. and gives me an error any attempt to put the new ROM. Now when I work under the Energy ROM ...

Hi
Before flashing another rom, please use the tool called task29. get it here http://forum.xda-developers.com/showthread.php?t=649191
Check here for another rom for your device http://rapidshare.com/#!download|33...dio_Rhodium_4.49.25.17_Signed_Ship.exe|180171
or here http://shipped-roms.com/index.php?category=windows mobile&model=Rhodium
use the SPL relocker tool LAST
Good luck!

Hello, thank you for the help you gave me, but I think we still have a problem (task29). Do the following:
1 - http://forum.xda-developers.com/showthread.php?t=649191 here I lost my task29.zip.
2 - unzip it, inside there was task29, had ROMUpdateUtility.exe. ROMUpdateUtility.exe and opened as follows next .. next .. me and sticks to 0%.
In the above post I mentioned that yesterday I did relock SPL before I know that I need to do this first (I do not write now in olinex boot loadera). I think from there

:-( you're in bad way. look for some help here http://forum.xda-developers.com/showthread.php?t=550540

The solutions mentioned above will NOT work, because you don't have hardspl installed.
Flash Hardspl again and then restore to stock rom and spl.

Guessed for it, but waited for someone to tell me. I will use this thread http://forum.xda-developers.com/showthread.php?t=550131 and you will get new and will write what happened. Thanks!

I made myself a new Hard-SPL. After I did task29. After you've installed the new ROM. After I did Relock-SPL. Now everything is OK.
Many thanks to all who helped me!

ivailo0 said:
I made myself a new Hard-SPL. After I did task29. After you've installed the new ROM. After I did Relock-SPL. Now everything is OK.
Many thanks to all who helped me!
Click to expand...
Click to collapse
This is what i told you to do in Post #7 ..... i guess you didn't read it at that time but anyways glad to know your problem is solved

You are right. Thanks again

ivailo0 said:
I made myself a new Hard-SPL. After I did task29. After you've installed the new ROM. After I did Relock-SPL. Now everything is OK.
Many thanks to all who helped me!
Click to expand...
Click to collapse
Bravo! so you how many of your fingers still have finger nails? lol
Baptism by fire, eh? Nice time.

ivailo0 said:
I made myself a new Hard-SPL. After I did task29. After you've installed the new ROM. After I did Relock-SPL. Now everything is OK.
Many thanks to all who helped me!
Click to expand...
Click to collapse
How did you MAKE a new HardSPL ? When I did this mistake, I had to buy another HardSPL to unlock it because the license I had for the first time was already used up.

jfandl said:
How did you MAKE a new HardSPL ? When I did this mistake, I had to buy another HardSPL to unlock it because the license I had for the first time was already used up.
Click to expand...
Click to collapse
he already had the same phone Hard-SPLed. the license works for the same phone forever. a different phone is different.