Related
Hello,
I believe I have a real 'tough' scenario:
My BA (WM2003) was running normally till yesterday where it simply 'froze'. I tried restarting it, (soft and hard) and it kept stalling on the (IMate) splash screen and didn't proceed to WM. I left it to battery drain completely.
I came to work this morning, and literally tried everything:
Standard Upgrade using the Imate original exe (PDA2k_WWE_14000_176_11200). doesn't recognize the phone anymore.
Tried the MaUpgradeUT_noID with the nbf files (radio, ms and nk). In all cases the upgrade starts and gets interrupted in the middle with a 'weird' error and the BA display fades as the signal led goes RED (constant, no blink). I have to take the battery out, back in.
Tried the mtty set 14 0 / task 28 sequence with no result. (The info commands return a garbled sequence which makes me assume that my bootloader got corrupted).
Any advice would be appreciated.
Thanks a lot.
W.
wzaatar
Read in another post that you got no reply on this one.
Well it seems like nobody can come up with anything that would make more sense than what you have done.
My wording is when everyting else falis go back to the original rom and start from fresh.
If you can't flash an original rom in the ship.exe or the extract form you need to send it in.
Does your device react to hard reset ?? at least you should get a boot screen.
Have you tried Bootloader mode?
I know that this is a really stupid idea.. but have you tried putting it in bootloader mode, and then trying to upgrade? Or maybe throw a WM5 rom on there, and downgrade again! Worth a try until you send it in!
Thanks for the replies guys, I really appreciate the help.
I figured out that I had two distinctive problems:
1. The constant red led light, after a lot of research, it turned out that the battery was defective. Changing it solved the problem.
2. Now, I am able to flash the ROM (Tried it a couple times so far) with the orginal or another one. It flashes correctly, but only if I use the NoID flash program, else it will return a MODEL ID error. And when I reboot it, it stays stuch on the 'Imate' or the bootscreen and I don't get the WM to load (As if it freezes)...
3. I don't think I can upgrade to WM5 as I need to shrink the EXTROM size? Can this be done through some 'task' or other command in mtty for example?
Thanks for your suggestions.
Cheers,
Wadih.
Hi I'm hoping someone can help me with what appears to be a unique problem based on all the searches I've done.
I've been able to install ROM updates with no problem for a long time with my Cingular 8125, however recently I'm getting stuck on the bootloader screen. It's a little strange, but here's what happens:
1) From Windows, if I try to flash ROM using USB it gets as far as rebooting the device and bringing up the bootloader multicolor screen, and it says USB on the bottom as it should. From there I can't get to the device at all and the installer fails with a device connection error. All I can do then is reset and get back into the OS like normal.
2) With the SD card method, I get to the bootloader screen but it never loads anything from there, and again I have to reset and just get back into the OS.
I'm running IPL/SPL 2.26, using Molski's latest ROM, but now can't install any other ROM because of this.
Any ideas?
Thanks in advance
groggrog said:
Hi I'm hoping someone can help me with what appears to be a unique problem based on all the searches I've done.
I've been able to install ROM updates with no problem for a long time with my Cingular 8125, however recently I'm getting stuck on the bootloader screen. It's a little strange, but here's what happens:
1) From Windows, if I try to flash ROM using USB it gets as far as rebooting the device and bringing up the bootloader multicolor screen, and it says USB on the bottom as it should. From there I can't get to the device at all and the installer fails with a device connection error. All I can do then is reset and get back into the OS like normal.
2) With the SD card method, I get to the bootloader screen but it never loads anything from there, and again I have to reset and just get back into the OS.
I'm running IPL/SPL 2.26, using Molski's latest ROM, but now can't install any other ROM because of this.
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
Just for everyone's information: I was able to resolve this by re-running lokiwiz and doing a SuperCID unlock...
Greg.
How did you make to lokiwiz recognize qtek?
My qtek shows:
First (and only) screen shows 4 color (red, green, blue, white), so according to posts on HTC-forum that must be boot loader.
On right upper corner of screen stands RUU
Line bellow, in the upper left corner shows IPL 2.26
Approximately 3 lines bellow still in the left upper corner of the screen shows SPL 2.26
When connect USB cable to qtek on the left down corner shows USB
I can acces to qtek via Multi-port/USB TTY ver. 1.11a, but when I start lokiwiz, even after long period of time nothing happens?
Please give us a precise procedure, nothing else didnt help
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.
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?
Hi!
this is my first post here, so sorry for my bad english or mistakes
i bought a qtek 9100 on ebay, and i'm wondering if it's a brick or not. i received the device 3 days ago. during this time i read through a LOT of threads here, tried a few things and nothing works.
here is some info:
- the phone is a qtek 9100 without branding
- the IPL is now 1.01 (i flashed "CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE" successfully)
- the SPL is 2.18 (because of the missing suffix ".0001" i guess it's a G3)
- GSM is 01.12.10
- OS is 1.5.4.2
- when i start the device (without any button pressed) it stops at the splash screen (which was a qtek logo before flashing, and is now this picture with a beer, that says "some things last forever" )
- i can get into bootloader screen (color screen) by holding camera button while starting
- in bootloader screen a small "USB" appears when i connect cable to usb on pc
- when i press communicate and voice buttons (on the sides) while starting, the "Press send to restore factory default" screen appears, but pressing send prints out "Format FAT Partition Format is Failed"
- the device gets recognized by windows ("Mobile Device" appears on my computer)
- ActiveSync 4.5 does not connect to device, not even as guest.
- when i hit "Connect..." in ActiveSync's connection settings, nothing is found
("Allow USB Connections" is ON)
- the device is CID-locked ("FF" state in Mtty 1.42)
- i can't unlock CID, because i can't get "EnableRapi.cab" onto the device without ActiveSync connection
Ok, these are basically the things i know now. The problem is that i never saw any other screen then the "HTC" boot screen, the "Qtek" splash logo (the one with the clouds) before i flashed with custom ruu wwe, after that i see the new splash logo, and i can get into bootloader (color) screen. I never saw any windows mobile running on this device! I could never establish a connection with ActiveSync!
So i hope that someone here on this nice forum can help me get this device to work (WM5 would even be enough right now) or at least give me a hint!
Thanks in advance!
Put the phone in bootloader mode and flash back to the original ROM.
since i bought it in ebay i don't have the original rom of this device.
but i found "233309-qtek9100_2180707_21807109_20710_qtek_ger_ship.exe" through google, which seems to be an original qtek rom (version 2.18). shall i flash this one?
You can find in the Wiki the latest official roms of every brand for our Wizards .-
ok, thanks.
i found one (Qtek GER 2.18.7) and flashed it. the process was successfull, now the IPL/SPL is both 2.18 . But the device still doesn't start and stops at the splash screen (which is now the original qtek splash again). I can still get into bootloader mode and hard reset results in "Format is failed"! No ActiveSync connection either... how should i proceed now?
i basically narrowed it down to these two problems:
- the splash screen freezes
- hard reset error "Format is failed"
( IPL: 2.18, SPL: 2.18 )
can't anybody help please?
i'm freaking out about this
With everything i’ve read the only people who’ve had any success had CID unlocked devices.
ok, i think that too for what i've read so far...
is there any other way of CID unlocking except lokiwiz (can't copy enablerapi.cab without activesync!)?
would this imei-check service that i've read about work in this case?
meanwhile i've also tried something with mtty (r2sd all) but doesn't work -> "didn't get proper security level"
is this also because of the CID lock? i tried to find out the right password to enter in mtty, but found nothing that worked...
does anybody know the correct password?
I couldent CID unluck my 9100 with lokiwiz so i did it 5min ago with Wizard Service Tool (ha to reboot my computer).
I'm having the exact same problem,
except I can't flash any other ROMS so I'm stuck looking at this incredibly frustrating beer picture, with "some things last forever".
Does anyone have any further ideas?
Look up the orignal rom on the wiki, get into bootloader. And flash it back.
Jodda said:
I'm having the exact same problem,
except I can't flash any other ROMS so I'm stuck looking at this incredibly frustrating beer picture, with "some things last forever".
Does anyone have any further ideas?
Click to expand...
Click to collapse
Jodda said:
I'm having the exact same problem,
except I can't flash any other ROMS so I'm stuck looking at this incredibly frustrating beer picture, with "some things last forever".
Does anyone have any further ideas?
Click to expand...
Click to collapse
Hi Friend!
I have the same problem with my Qtek9100!
Any ideas? have you solved your problem?
I have the frustrating beer picture
Please help me.
Very Thanks
Like I sad before
Get into bootloader, flash back the original rom and try again.
mizobuchi said:
Hi Friend!
I have the same problem with my Qtek9100!
Any ideas? have you solved your problem?
I have the frustrating beer picture
Please help me.
Very Thanks
Click to expand...
Click to collapse
I put the original rom.
But... the problem is the same.
when I started the device (without any button pressed) it stops at the splash screen (which has a qtek logo before flashing)
- i can get into bootloader screen (color screen) by holding camera button while starting, I installed the original and others rom who days before works perfectly... Now... this stopped at splash screen
- when I tryed to format.. = "Format FAT Partition Format is Failed"
Any idea?
I have tried this : http://forum.gsmhosting.com/vbb/showthread.php?t=332143
but... without success.
Could you help me, please?
Very Thanks
i'm still stuck with the same problem with hang up on qtek splash screen, too!
i have IPL 2.18 and SPL 2.18 and i can get in boot loader screen and connect with usb. (but no activesync connection!)
formatting doesn't work either.
does anybody have an idea how to solve this?? it's frustrating... i've tried almost every guide here on the forums.
same proplem here with
ipl 2.16
and spl 2.16
I used this to fix this problem
Hi i had the same problem the other week, installed a dodgy app, went to do a hard reset and wouldn't do a hard reset format failed. Tried updating rom everything worked ok until you booted it up. Wouldn't go past second splash sreen. After a few hours of trawling round i found this thread.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=format+is+failed
worked for me. Hope this helps you out.
Problem in connecting to my PC
Hey ,
I just bought a qtek 9100 a day before ... I tried to connect it with my computer.. instead of connecting my battery gets charging well can u plz help me out !
is there any software that i should install in my pc in order to get it connected to my PC...... please help me fast ! Lot of work is pending !
Thanks
Salman
Ok guys, I finally have this SOLVED.
My QTEK 9100 is working fine now!!!
I'm so happy with it right now
Since nothing I tried worked, I went to imei-check.co.uk and got my phone completly unlocked! It only cost me about 11€ and since it works now I have to admit that it was worth it (no advertising). After the unlocking was done I could do the "r2sd all"-method (Tool: MTTY 1.42) using a miniSD card. You can find a good tutorial on this board somewhere. After that everything was just fine...
-> I never saw it working and Hell Yeah: This baby just kicks a$$ !!! (although it's kinda 'oldschool' these days )