Related
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
Got my Trinity in the mail today and started the process of pimping it up to xda-developers' standards.
1. Ran SSPL-TRIN.exe without problems from "HTC Trinity SIM & CID Unlock - v1")
2. Ran ROMUpdateUtility.exe. Dialog on PC said upgrade was successful, but screen was black on device
3. Soft reset device. Windows Mobile (green screen) shows, but never goes away. Repeated this procedure 3 times (waited over 5 min each time)
4. Hard reset device. HTC logo shows with numbers "M 05, B 05, D 1.16" showing for 5 seconds. The text "No GSM" appears for 1 second and disappears with the numbers. Only the HTC logo on white is on the screen, forever.
Any ideas? Would hate to have bricked my phone after only a couple of hours.
I can get into the three color screen. I attempted to run ROMUpdateUtility, as I wrote before, again, but I get an error message on the PC saying that the ROM is corrupted, after which my device resets. (To HTC screen, forever, like I wrote above)
Sounds like a bricked device already.
There is a lot of information on this problem in the Hermes Wiki and forum. You may find some useful information there to help unbrick.
Sorry mate.
S.K.
Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.
lazaron said:
Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.
Click to expand...
Click to collapse
Check the Wiki, you will find links to some standard ROMs.
lazaron said:
Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.
Click to expand...
Click to collapse
Chek here:
http://wiki.xda-developers.com/index.php?pagename=Trinity_Upgrades
Will try them all now. Results with all roms thus far have been:
Progress bar on both PC and phone moves to 1%, then:
a) Phone reboots & PC displays error "invalid vender ID" or b) Phone reboots & PC displays error about image being corrupt
Good news!
I went to a HTC service center where I live (Oslo, Norway). They said they could fix it in 15 min. (flash the device with an original ROM using more advanced equipment than a USB cable)
After about 10 min. the guy comes back with the phone, which now has the exact same screen I was stuck on and concludes that the motherboard is broken. I told them how I had only owned the phone for a day and they offered to replace the motherboard for free (took a few hours).
Once I got back home with the repaired phone, I was pretty nervous about flashing it again, but everything went perfectly.
Congrats friend... let me tell you that you got balls to re-flash your new device after the repair .
lazaron said:
...
2. Ran ROMUpdateUtility.exe...
Click to expand...
Click to collapse
Can you tell us exactly what ROM you used to update and is your Trinity HTC made ?
Always flash from the SD card!
Cr7pt0r said:
Congrats friend... let me tell you that you got balls to re-flash your new device after the repair .
Click to expand...
Click to collapse
Actually, I'd suggest adding to the Wiki that any flash should always be done directly from the SD card (as per instructions in the wiki) to avoid PC/USB problems. After bricking my Hermes because of a USB comm problem, I always flash from the card directly. Much faster and safer.
/politby
Hello,
I have this rom : RUU_Trinity_LVSW_WWE_1.25.0.8_GPS (AKU 3.5.2)
from http://forum.xda-developers.com/showthread.php?t=302198
I wanted to test the new WM6 roms, unfortunately, my trin doesn't update with any rom I tried (Orange, HTC, LVSW Wm6, Mun_Rus Wm6, ...)
It tells me : "ERROR 262 : UPDATE ERROR
... communication error during the process"
I'm stuck on LVSW Wm5 rom :'(
Not sure if Des SPPL is causing this problem... anyway, I tried to update it from Bootloader or synched, on XP and Vista, 5 differents roms... no luck.
I would really appreciate some help, thanks
can you list the steps of what happened, in order?
also, just to make sure i understand, have you already tried to manually enter the bootloader and THEN run the RUU? *edit* one last question, have you tried this.. after the error, leave your device connected and in bootloader, then restart the RUU.. can you give me your device details too?
Well, when I run the update with normal step (connect AS, then launch update...) when the update is ready to be started (progress bar appears), phone have to switch to bootloader, which it does. However, it seems that the RUU is waiting for that since it return me this error:
ERROR 246 : Device not responding
And I have to exit. I don't understand ?
Progress bar didn't even appear on the phone.
At this time boot loader shows
IPL-SSPL by Des
SPL-1.07.ds
So since I'm already in Bootloader mode, i try to launch RUU again. Here is the error I get when the progress bar appears on both phone and PC :
ERROR 262 : Update Error
And it offer me to recover the device, which I don't need as the current rom has been left untouched and is still functionning after the error.
Then I reset the device to enter bootloader this time:
IPL-0.50
SPL-1.06.0000
same error : ERROR 262 : Update Error
I'm kinda out of option, thanks a lot for your help !
well, it's been a pretty common thing for the RUU to give an error when the device goes in to bootloader (can't detect it for some reason). Most times, simply running the RUU again while the device is still in bootloader works fine.
Why don't you put hard-spl on just in case, manually enter bootloader (which will then be hard-spl) and run the RUU again. You shouldn't enter the bootloader manually unless you've loaded hard-spl or sspl on to your device. From what i understand you won't be successful from what you did after the hard reset. When your phone went in to bootloader the first time, it was with SSPL pushed to your device by the updater program to enable you to update safely. After resetting, you're back to your normal bootloader which won't help anything.
I know one time it did this to me, and wouldn't connect to my device. I started the RUU about 3 times in a row with my device on bootloader, and for some reason after the 3rd time it suddenly worked.. weird, i know.
anyway, hard-spl will make the whole process safer.. let me know if it connects or not, i'll see if i can help you troubleshoot
I wanted to install hard-spl, but it runs as a normal RUU and give me exactly the same errors as a normal run update (error stated above).
So I don't see how I could install it
Another thing weird, when I run a official HTC rom update, when the udpdate should start (device enter in boot loader, progress bar appear in bot PC an device), the Trin reset itself and boot as normal... of course the RUU gives an error due to this reboot ...
Same weird behavior with an official Orange rom...
Now I'll try with SSPL...
Oh and thanks a lot for your help
simply try to run twice ROMUpdateUtility.exe after error
Please read carefully what I have posted (and the steps I ran into)...
Already launched again RUU, it gives me an Update Error and the device is stuck on the screen that show the progress bar.
Need to soft reset... I can't launch again the RUU after that since the device is no longer recognised as connected on PC.
I confirm I can't manage to install the Hard SPL, even after laoding Des sspl from the device...
Defintly blocked
At last I have succeeded in upgrading the device. Seems like my bootloader was somehow corrupted or something... after doing another Hard Reset it have installed hard spl succesfully...
I had already done a hard reset before, so I don't understand what happened.
Nevermind, at last i can try wm6
thanks a lot for your help racerx_ anyway
hey no problem.. not sure that i actually helped haha.. but i'm glad you sorted it out. happy flashing!
Might it have been the USB driver on the desktopside ?
Did you see XP recognize and install HTC USB device again, after device disconnecting from AS and going into bootloadermode for first time ?...
Just a thought...
Not sure what it is, but it's happening again, can't update anything as the bootloader seems somehow corrupted.
When i enter bootloader it briefly display the 3 color, then grey screen with "loading" and then the hard spl screen from Olimpo... the only problem I see is that it does no longer display TRIN100, but only little dots (like if it was corrupted)...
Very annoying situation, and I have already done some hard reset, but nothing
So more exactly, where I start DES SSPL or when I enter Olipro Hard SPL (that I installed before WM6), it shows the good infos like :
TRIN100
xxxx
TRIN100
SPL-
But after 1/4 of second, it start loading for a very short moment
and display again the RGB screen with the infos except the "TRIN100" parts are like this ':':':':':':
Anyone has seen this before ???
@cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again.
If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case.
pof said:
@cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again.
If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case.
Click to expand...
Click to collapse
...... well well, that was simple hahaha (and I feel stupid lol).
yes I had my SD inserted (and I remember only now that the last time it worked I had indeed removed the mini-SD).
So, thanks to you I have understood this issue at last !
Muchisimas gracias por tu gran ayuda pof
Now the question is, wtf do u have on this SD card? LOL
Errr that's a good question... maybe it is time to clean those 4go of things (which most of those come from the SD I had on my Prophet, in the top of that)
Anyway, it's a rare specimen indeed... want a copy to play with heh ?
There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)
Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?
i need some serious help im desperate at this stage.
ive basically got a htc tytn ii on uk orange
i update the rom to htc standard one which sim locked it
i followed the instruction on how to get it like i got it from orange
which i believe was sucessful. but because it was still sim locked i
thought the hardspl was relocked so i ran that again which failed and ended up on the tri colour screen after which i tought it may still be hardspl locked
so i tried to flash it with the rom again it got to 17% then crashed
now my phone will only boot to the tricolour screen it wont load activesync and if i try a flash it with anyrom it either stays at 0% gets stuck or gets to 1% then the phone restarts.
ive buggered the phone up proper i need some help if there is any for this mess
when i try a rom upload it says error [294]: invalid vender id
this update utility cannot be used for your pda phoe please check your update utility
Did you install Hard SPL?
http://forum.xda-developers.com/showthread.php?t=334679
See if you can install that and then try to reinstall your rom.
this required activesync to be green mine will respond to usb but not activesynce so i cant go any further with the hardspl unlock im stuck on the tricolour screen. and flashing will only go to 1% then restart and the message come up again.
same problem
i have the same problem and i can only get to 1% . i have tried to flash it with several roms using diferent utilities and none seem to work i used hard spl the first time when it failed. HELP PLEASE !!!!!!!
found solution
got mine working here is what i did
run mtty select usb after disabling it in activesync
press enter and you should see cmd>
type boot and when your device restarts it should start in your old rom
run hardspl again
then you need to reinstall your rom
although a word of warning my phone became sim locked after this
worked a treat many thanks it is sim locked just have to wait for the sim unlock for it now
willbyrne said:
got mine working here is what i did
run mtty select usb after disabling it in activesync
press enter and you should see cmd>
type boot and when your device restarts it should start in your old rom
run hardspl again
then you need to reinstall your rom
although a word of warning my phone became sim locked after this
Click to expand...
Click to collapse
no worries
yeah no worries, i was affraid when i locked mine i might have to return it and get anothe orange version but i used some company online and got my code in about 3 days.
oh yeah you will probably need to enter the code in twice, mine said simlocked and then network locked but it was the same code