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.
Hello!
I tried to flash my Charmer with the new german Aku 3.3. At first everything seems to be ok, but at 95% it stops and i got the Message: update error- there is an comunication problem! So what can i do? I tried to flash the old rom back but there comes also at 95% a message: invalid command - nfb file cannot be used for your pda!
Please help me !
Greetings Musna!
Ps: can somebody upload a sd image for the mda compact II !
Go to bootloader mode, then try to flash RUU rom (1.x). You can find it on Charmer wiki.
It doesn`t work too, it always stops at 95% has anyone another idea?
did you try hard reset?
Yes i tried hard reset, but it is always in bootloader!
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
nitrane said:
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
Click to expand...
Click to collapse
The aku3.3 is up to date the bootloader version!!!
IPL and ISP version now is 3.00.
http://www.windowsceportal.hu/forum/viewtopic.php?t=1079
Sorry but i do not speak hungarian. What do you want to tell me ?
I´ve got the same: My charmer is in Bootloader IPL 2.06.0001 SPL 3.08.0001
I can´t downgrade to AKU 2: Please order a newer Version.
Every try to upgrade to AKU 3.3 failed at 95% with Error 326.
Is there any help for my charmer???
oh.**** !!!! I got the same problem with them and my first pda uk rom already empty screen and then i try with my scrond pda German rom it the same problem and now just only show in bootloader screen.Have i ask someone who knowage about this he told me that if SLP in you PDA have chang it be hard to repair.So,I think I lose 2 PDA did I try to flash in T-Mobile Official Rom de that i hope to develop it but i hve to kill 2 Charmer.Who take responsibilities,T-Mobile right ???
Ok no problem you can repair it! At first you have to brand your device with the rom you want to! After 95% the Problem will come again! When it stops you have to go with a reset to bootloader again.When your device is in bootloader you have to install the Radio Rom from this thread:
http://forum.xda-developers.com/showthread.php?t=302768
After that your device will be able to boot again and it should work!- But the Problem during the installation will stay,so you have always to use this way to flash your Mda compact II!
In the new rom there must be a problem with the radio rom and this causes the broken device.
I`m sorry for my bad english but i`m not used to talk very much! So i hope you understand what i mean!
Greetings from Austria Musna!
that link is broken
Then try this one:
ftp://xda:[email protected]/Prophet/Radio_Roms/Prophet_G4_RadioRom_v2.47.11.exe
You can find the radio rom also on the ftp server. Prophet> Radio Roms>Prophet_G4_RadioRom_v2.47.11.exe
You can try different Radio Rom versions, i have flashed the v.247.11 and it worked.
Normaly it should work!
Thank u so much !!! My Charmer secrond PDA come back have life again and it can working.So,my Charmer first PDA UK rom still empty screen and notthing working when i press any button.Who can slove this problem !!
Musna do you have any massage such as msn
Hi guys,.. i have been trying to upgrade my P3600 over 2-3 weeks now but i reach the same problem always, and that is simply.... I have managed the RADIO Rom to 1.41.00.111, but when i try to update the operating system.. with... Lvsw 2.0.1.1 / Mary 2.0 / PDAVIET 3.00.07.09 ... everything goes far with the updating.. i can see the progress bar, it reaches 100%, the screen on my mobile goes black... and it says on my computer to follow the info on my mobile and close the update application.
Now at this time my mobile is totally black (shut off i guess)... i have waited for more than 5 minutes but since nothing happens, i have restarted the mobile with a soft rest... but after the rest i still have my OLD operating system....
What am i doing wrong?.... I have read through bunch of threads on the forum, but haven't seen anyone else whom have had this problem.. or is it simply that i should wait even longer time and the mobile should start up by itself?....
Appreciate any help & suggestion...
can anyone help me?...
I've tried to update my HTC3600, by using the "WM6 Official - Any Device" from http://trinityguide.info, and it just doesn't work... I have updated Hard-SPL, and then tried to apply "Official Dopod ROM" ... the only thing it did was to revert my Radio-ROM back to 1.46.xxx (from 1.50.xxx i had before)...
But the OS was never updated to WM6... I have tried a bunch of different WM6 ROMs now during the weekend, nothing has helped... even tried some application to unlock CID (what is it actually ???).
The only thing I've managed is to update my own OS using the official swedish ROM (I've bought my HTC in sweden). And i've been able to update my Radio ROM to 1.46.xxx, 1.50.xxx.. as well as installing different HARD-SPL.
But i've so far not been able to install ANY WM6, or WM5 cooked ROM's .. so pleaaaaaaase help my guides... I'm starting to go nuts over this...
Appreciate any advise & help.. thanks in advance !
Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan
Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.
Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!
try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....
The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.
Hey everyone. I'm tearing my hair out trying to get this sorted but I just don't know what to do!
So, when I got my X1 as everyone on here should do, was flash my X1 with the HardSPL and some custom roms, this was a few months back. Then, shock! Horror! My case went and broke, (cracked near the volume button build W44) so I sent it back to SE for repair. I sent it back reset back to defaults but left the hardspl on there.
SE sent me a brand new phone (I think... This one says under the battery build w50, but the battery says w32..) I received it today. I thought it would be my old one repaired but SE had other ideas. Booted up and have Image Version: 1.03.931.10 and HardSPL 72.000 I think I said that correctly...
Now since sending it for repair and receiving it back, their seems to be quite a few wm6.5 roms floating about, and obviously I can't use the stock software as that wouldn't be right!
Now I have tried flashing the hardspl to the phone through my Vista PC and all it keeps giving me is connection errors. I thought maybe it was already flashed so I tried flashing just a rom, and that just made the phone get stuck on loading (flash by memory card). I thought it might be Vista, so I tried doing it on my other PC (XP) and I get the same issue. This bloody thing won't flash!
I have had "Connection Problems" - "Update Errors" with different numbers. The current one being Error [260] CONNECTION.
Now I have been searching around through the hardspl thread and other places trying to find out what I need to do or how I can fix it, but everything I try doesn't make a difference. I did read some other people with recently repaired phones having the same problem and perhaps SE have put a new spl thingy-ma-jiggy on there. (Please forgive the technical jargon, I have no idea what im on about.) I have also tried the ticking/unticking advanced network functionality, but that hasn't made a difference either.
So by the end of typing this, I have little hair left. Let's hope you can all help, before I have none left!
I would appreciate ANY help! Really.
Just wanted to add, I was at first getting the phone to a loading bar when flashing, but it would stay at 0% then flag up an error on the PC. Now after the tri-colour bars, the phone just sticks on Loading...
Well just to update. I have been trying to sort this since posting. I flashed the rom to an old UK generic one, as I read in another topic people had to do that before HardSPL. Done that, and tried flashing the hardspl. Same thing, just getting connection errors.
I tried going into bootloader and running the hardspl from there. It works and the phone gets to 10% and then gives an UPDATE ERROR. The phone is now bricked, and I have to reflash the original wm rom to get it back.
Though the Tricolour screen now shows 0.52.Olinex
Any ideas?
Shameless bump for help.
very stupid situation.
i have the same situation in puncto of flashing.
i get my phone three month ago.
after hardspl i .... sorry, no hardspl ... the phone says at 0% bla bla bla
i solve the problem by consulting one night absolutly stressing again and again and again .... google ... xda ... google
than 3 thinks at one time was the solution:
0. need activesync - connect !!!!
1. SDA_ApplicationUnlock.exe for desktop pc
2. enterbootloader.exe for pocketpc (please, the right version, it exist for eten too, but we need the xpediaversion ..)
3. changing registry-entries
how to:
activesync-connect, than copy "enterbootloader.exe" to pocketpc. it must be root, not sd-card. use a pocketpc-registry-program to change these values :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies\0000101b = 1
if not exist than add the key.
now, start desktop-program, follow instruction EXCEPT reboot.
start "enterbootloader.exe" on pocketpc. now, you can install hardspl and the device is flashable for ever.
thats works on me, hope it could help you too.
Thanks for the reply. Not had time to try it till this morning. Ok so, after spending about an hour trying to find the correct enterbootloader.exe I finally realized, that the hardspl package includes it. *Duh!* So that was time wasted.
I changes the registry values as you said with Resco registry editor, and follower the unlock then enterbootloader.exe Start HardSPL package. Starts to install. Gets to 10% then I get
ERROR [262] : UPDATE ERROR
The rom update utility has encountered communication errors during the update process.
So im open to suggestions if anyone has any. I just can't understand why it's not working. It's not a problem with my computer or cables. I flashed the phone before I sent it for repair and I have tried doing it on two computers one with XP 32bit and one with Vista 64bit.
hmm. would u like to install a custom rom, or a stock rom?
msg me, and i hope, i can halp u.
I want to have the hardspl on there so I can flash custom roms.
If it's a case of the software/firmware/hardspl whatever you call it, has been updated by SE. How would one go about getting it flashed? Would we have to wait for an update HardSPL to be released?
U read this thread?
My first hardspl was from this thread. New X1 will come tomorrow back from SE (vibration was defect +++ some more problems with case), and i will try it again with this thread.
hope, this will help u mate.
Yeah, I have been through that thread with a fine toothcombe trying everything suggested to see if I can make it work.
When you get yours back, if you have to do anything out of the ordinary to get it to flash or can't do it. Please come and let me know in this thread. If they have updated yours like mine, and yours won't flash, at least I won't be the only one!
k, i will msg u tomorrow around 2pm.
Cheers.
In the meantime. Does anyone have any other suggestions I could try?
Bump, for some help.
now i know, what is exatcly your problem.... <--- SAME Problem
i hope, i will find a solution and msg u then. if u´ll got a solution for this prob, msg me too plz.
Solution found in this Thread!
Download this and unzip it to your device. ++ run it. It will start your X1 in Bootloader menu and say "0.52.OliNex".
Then start hardspl while X1 is in Bootloadermenu....
FINISH =)
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
vwrmic said:
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
Click to expand...
Click to collapse
hmmm... it works fine on my new x1. are u sure, that u start the ssplmanual on your x1 and not on your computer?
Yea, im not sure what the problem was with it. Thankfully I have it done and dusted today! Because I flashed it earlier to an older official version, and you said you got it working. I presumed you had - had yours flashed to the newest version due to it being off for repair. So I reflashed the official update and fully updated it. Then tried hardspl which didn't work. Tried with the advanced USB thing off, tried again with how you said you did it above, and Viola!
Hip hip hoorah! Thanks for the help. Can finally use me bleedin phone now!
no problem mate hf with your x1
hello,
i see smilies and yea's ...
for me to understanding (for next time or other users):
1. complete official update (if exists)
2. flashing (hardspl) without "advanced usb"
thats all?
cool.