Database Info

Stuck at 3 color bar

I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!

alan1974us said:
I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!
Click to expand...
Click to collapse
What phone you got... G3, G4 ... CID Locked/Unlocked ?

G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!

alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
Turn the phone off (pull the battery if you have to) and unplug the USB cable. Then turn it back on so its back at the bootloader screen (rainbow color bars screen you saw). Now plug in the USB cable. ActiveSync will NOT connect, but thats fine. You will see USB above the left soft key. Now flash an offical rom (either the Cingular 2.25 found on the HTC website, or T-Mobile 2.26).
Read this thread for details, steps and links:
http://forum.xda-developers.com/showthread.php?t=298613
Once you get back on an official rom, then you can reinstall whatever custom rom you want (but you need to get back to an official one first at this point).

alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
OK then...
Plug it into the usb, and when the bootloader appears, start flashing whatever rom you like...
Easy, right ?

hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?

alan1974us said:
hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?
Click to expand...
Click to collapse
Please forgive me for stating the obvious but you do know that it is normal to stall at 99% for a few minutes sometimes longer.... What do you mean by "Died at 99%"?

To be honest. You didn't said anything but typical wrong flash case...RUU from custom ROMs to another custom ROM(or having CIDlock probs) is good method for having 3bars relax time.
it's question of the day: what do You mean by "died @ 99%". when i am flashing anything, stalls up to 5 minutes @ ANY percent arent reason to PLUG CABLE OFF,or ANY manipulation on pc, or ppc. if it just stuck forever, its time to turn back to old ROM image, or just any rescue ROM, SO:
revert to old rom with ruu, then install 2 cabs from shelltool, wait 30 secs, reset, turn radio off, plug usb on, and after adding nk.nbf into shelltools directory, and spectacular launching earlier mentioned shelltool, and rtfm od its docs, you may start to do what you've just read.
while flashing DO NOT DO ANYTHING with machines.
After finished operation you will see end so it IS END.
Hard reset.
100% positive flashes, if net is turned off, firewall killed and antivirus turned off. also, remove sd card before flash.
btw, what's your IPL/SPL...

Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.

I had this problem as well...
I ended up just flashing a stock rom multiple times until it finally took.
I think I had to do it at least 2, if not 3 times before I was finally able to boot the phone.

alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
So, you are experiencing this when trying to flash a stock rom.
Check if the RUU is not corupted. If you downloaded it now, it may also cause this.
Also...restart your PC and don't run anything in the bacground while flashing. Just to make sure.

alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
Also make sure you remove the SD card in your phone if you have one. I've seen flashes fail when SD cards are installed.

Ok, I reloaded the rom. I can't figure out the button rom, there is a screen with a bunch of ???? that come up and none of the buttons do anything. :\ I loaded the wizard love one, which loaded ok. I tried the crossbow reloaded but it hung at 99% again and the application went back into error recovery mode. Maybe I'm just not meant to have it! lol. I don't have the sim or sd card installed atm.

Oh ya, this is probably the most responsive/helpful forum I think I have ever seen.

..removed..

I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?

alan1974us said:
I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?
Click to expand...
Click to collapse
All the roms will hang at some point towards the end of the flash (official ones tend to hang around 85% or so. The cooked ones hang closer to 99%). This is the point where the final part of the flashing is occuring and I think there is verification that what was written checks out as being valid.
If you can get a rom on and the phone working, and then do a hardreset and that works, then I would say you do not have a hardware issue with your phone (at least not from the flashing side).
BTW: Crossbow Reloaded v1.5 is out now. Please try downloading it and flashing that one (just to see if it makes a difference for you). It is very odd that multiple roms stop at 99% on your like this (hard to say its a bad download).
Sorry, I haven't reread this entire thread, but have you tried this from a different computer? ALso try to turn off any firewall, VPN, or even antivirus software on your computer while you flash to see if that corrects the issue. I think I remember someone trying to go into Safemode one time to do a flash.
Then there is also stand on your head or wave a dead chicken over your head while the flash is happening.... (yeah, I'm grasping at straws on this one )

Lol, thanks. I downloaded the 1.5 and going to give that a wing.

People... pleas read throught the forums!!!
Its so annoying that people asks the same question again and again and again. Dont be so lazy, do your research, search the forum and dont post ST$#"D questions!!!

Gah, error 302 every time. I loaded buttons ROM, unlocked again, tried reloading rom, then BOOM 302! Maybe WM6 isn't meant for this phone.. lol I can load any WM5 or lower and have zero issues.

Have I bricked my 8125?

I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.

Splooshie said:
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Click to expand...
Click to collapse
Some G4's can't be flashed with the ROM on the HTC site, but can be flashed with the Wizard Love ROM. I'd try that. It's saved me several times.

Or try a hard reset before flashing another rom. See if it fixes the problem

If your phone makes it to the boot screen it isn't bricked.

It isn't bricked. It shouldn't be. If he flashed the Core 2.0n it's impossible that a OS only ROM would brick it because it doesn't touch the bootloader or the extended rom. Plus, from what i understand the ShellTool flashes OS only and that means even if the ROM he was trying to flash contained an IPL/SPL , then only OS would be flashed.

The fact that it even gets to the bootloader screen is proof enough it isnt bricked.... reinstall the carrier update and try something else.

Oh Sorry, he tried to reinstall the carrier ROM .. disregard.

I tried the love rom, but it errors out with error 300, invalid argument ( I think it looks like italian) =/
I've rebooted my pc, did a couple hard resets on the phone and verified the phone is being detected. The USB sync driver is loading. Seems every flash utility cant see the phone even when in the boot loader.
BTW it fails at the point where it tries to verifiy the information on my phone. if that helps.

Is your PC XP or Vista? If its Vista, it can't talk to a phone in bootloader mode. If you are XP then you should be fine but then I'm not sure why you can't flash the Wizard Love rom...

I'm using xp.

When you put it into boot loader mode, is USB in the lower left corner?

Splooshie said:
I'm using xp.
Click to expand...
Click to collapse
Have you tryed a hard reset ?

yes twice the second time when it rebooted I forced it to boot the boot loader before it tried to boot the OS.

And you have tryed taking out your SD card, and flashing the Wizard Love rom directly from the RUU (not with ShellTool) ?
You have enough battery ?

I have been using the flash utility, I don't know how to use shell tool without the scripts, and I can't install any of the cabs since it wont boot into the OS. I just tried on another xp machine and both the cingular rom utility and the love rom failed to communicate with the phone.
any other ideas?
edit: oh and I should have near if not 100% battery ( been plugged into a pc since the problem started and it was 100% when I started this mess. =) SD card has always been removed.

FYI, even though it has been plugged into the computer, it may not have enough battery. From my experiences, it drains the battery even if it is plugged in. Luckily, I have a second wizard so when my first battery drained (and wouldnt recharge even when plugged into the wall) I just popped the second battery in and i could flash it again. See if you can find a charger or something for the battery, and then once it is charged, let me know and I will give you a ROM i have that saved my other wizard (which is a G4 and no it isnt wizard love)
-Nstefanelli-

it seems to be charging, the orange light is on and the phone is off.

ok in a few i'll PM u a link to the ROM.. i havent used it in a while so i might have to gather it up..
-Nstefanelli-

well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)

Splooshie said:
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Click to expand...
Click to collapse
Are you sure you don't have a G3 ? Hmm, I think you have a G3 and that's why it doesn't work. Try and flash the Tmobile 2.26
If your ipl 2.25, spl 2.25, then you defenively have a G3 CID UNLOCKED
Go back to Button's 1.05 ROM, CID UNLOCK it and then flash the Tmobile 2.26 and then flash Core 2.0n
Don't use ShellTool !

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBH​KAIS 1*0
SPL-1.56.0000
CPLD-8
USB​
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people

I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/

I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!

I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.

Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen

Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.

http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...

i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!

Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061

Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?

like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results

The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.

I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.

Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.

Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse

Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.

pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....

Please Help! TYTN II from WM6.0 To WM6.1

I have read through endless posts and stickies.. I still can't figure out what the correct procedure is for updating my TYTN II from WM6.0 to WM6.1
I would greatly appreciate it, if someone would lay it out step my step
I tried to flash with the WM6.1 update, it said there was a vender error.
I tried flashing with HardSPL 3.28 and it stops at 0% and says there is there is a communication error, and to click next to perform the recovery. I perform the recovery, after removing the battery and putting it back in, the phone starts up normal.
I tried the white screen solution.. it reaches the three coloured display with USB and just sits there.. i eventually reboot the phone.. and it starts back up normally..
but none of the flashing procedures have worked yet..
I used the files found Here for the white screen problem.
I don't know what else to try..
Direct update - Invalid Vendor ID
HardSPL 3.28 - Communication Error
JumpSPL - Does nothing...
What am i missing?

Puff1911 said:
What am i missing?
Click to expand...
Click to collapse
Interpreation and sense of what you are reading.

http://hpcmonex.net/olipro/KaiserUnlocker.zip
That is the link to the Kaiser Unlocker by Olipro. It Hard-SPL's and SIM Unlocks. If you do not need the sim unlock simply flash to a different ROM after the first step.

Thanks socalkevin21 for providing a usable response

Not a problem, let me know if you have any issues.

The software says to unplug the USB connection as soon as the screen turns to the three coloured screen.
when i plug back in, the progress bar waits a couple seconds then jumps directly to 100%.. is that correct?
The phone reboots, and starts back up as normal.. but the same version ROM is still there..

Puff1911 said:
The software says to unplug the USB connection as soon as the screen turns to the three coloured screen.
when i plug back in, the progress bar waits a couple seconds then jumps directly to 100%.. is that correct?
The phone reboots, and starts back up as normal.. but the same version ROM is still there..
Click to expand...
Click to collapse
enter bootloader (press and hold the camera button all the way while pushing the stylus into the reset hole)
you should now be at a tri-color screen
what does this screen say?

KAIS130 MFG
SPL-1.0.OliPof
CPLD-8
when I click on Unlock Radio, it says "incompatible device"
Is that also normal?
Do i need to patch the radio as well?

wooooo!!! got it! i eventually got it to update the radio by clicking the button over and over..
I didn't get to unlock the phone (step 3).. but after i tried to update to windows mobile 6.1.. and it worked!
Thanks socalkevin21 and mbarvian!!

Well my device runs a lot faster.. but also sticks a helluva lot more!
Also my camera doesn't show anything, it takes pictures fine.. but there is no live display.. anyone having that problem?
And i also lost Voice Commander.. anyone have the install files for that?
**Fixed the camera problem. I had installed the HTC camera patch... Problem solved after removing it.**

Puff1911 said:
Well my device runs a lot faster.. but also sticks a helluva lot more!
Also my camera doesn't show anything, it takes pictures fine.. but there is no live display.. anyone having that problem?
And i also lost Voice Commander.. anyone have the install files for that?
**Fixed the camera problem. I had installed the HTC camera patch... Problem solved after removing it.**
Click to expand...
Click to collapse
Try a new HardSPL.
WM6.1 freezes sometimes with the OliPof 1.0 Hard SPL.
All the latest Hard SPL's are here: http://forum.xda-developers.com/showthread.php?t=396922
There are no other differences between 1 and 3.* other than the version number - they both work the same (oh and no MFG in 3.*, but you won't notice that)
Ta
Dave

Kaiser stuck on green WM6.1 clear memory screen

I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?

bsgbelg said:
I have a Kaiser which I updated a while ago with WM6.1 official Belgian dutch. Since it became way to slow, I wanted to hard reset the device. Since a couple of hours, it has been stuck on the green WM screen saying The device is erasing the memory, Please wait...
I have been looking through the forum, but have not found the same issue.
It does not come up in acctive sync, so a normal relaod is not possible. Any ideas?
Click to expand...
Click to collapse
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!

Not possible to flash anything
what I've tried so far:
- activate active sync to install hardSPL. Not working
- install HardSPL through microSD. Not working
- install ROM through SD. Not working
I tried a non HCSD for a change, and then I see the loading scree flashing up, but quickly says No rom found and returns to the bootloader screen.
The only thing that works is load the bootloader (red green blue white) into a screen that says:
KAIS130
SPL-3.29.0000
CPLD-8
Serial
When connected to USB, it says USB, but no disk is showing in Explorer or any connection is made to AS
The only thing I've done in the past is flash the 6.1 rom through the system provided by HTC with a file called RUU_Kaiser_HTC_NLD_3.29.404.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe
Please help, I really like this phone and hate to loose it

put it into bootloader, connect it to the computer and then flash one of the htc roms. make sure its an htc rom, you cant flash a custom rom cause you dont have hardspl

I have not been able to find the original rom, only the exe from htc which says Connect with active sync. Do I have to set it in bootloader and then execute the program?

Solved
Just want to let you know I sorted it out!
Flashing the original rom does not need active sync, the bootloader USB connection is sufficient.
After this, the phone restarted in 'Erasing memory' mode, but was able to finish it and reinstall the whole rom.
I believe I got the taste of it and will start testing some other roms...

msd24200 said:
manually go into bootloader if you want to reflash the rom, if phone is powered on hold camera button in and the softreset button at the same time! it sounds like you possibly have had a bad flash, OR you had a bad download!!!
Click to expand...
Click to collapse
Thanks, worked fine

majedaly said:
Thanks, worked fine
Click to expand...
Click to collapse
good to know