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.
At 56%, the desktop went to a blue screen and said an error had occurred and the system must be restarted. The screen asked if I had installed any new programs, check with the adminstrator, etc. The only program recently installed is the program for this ROM revision. When it crashed, the phone had a completion bar in the top 1/3rd, showing 56% completion. The rest of the screen was white. I restarted the desktop and was unable to establish a sync connection. I then preformed a hard reset on the phone. When it restarted, it showed 4 color bars, red on top, green, blue and white at the bottom. Since I cannot restablish a sync connection, how do I finish the modification. I am now concerned that I have "bricked" the phone. I am reluctant to try this mod on another phone until I can determine what went wrong.
Adding additional info
My phone is a G3, CID and SIM are unlocked, desktop is using Windows XP, SP2 and ActiveSync is Ver. 4.5.0
phone isnt bricked, your getting into bootloader fine. you need to turn it on, get it into bootloader i mean. if needbe press camera and soft reset (power button) then plug it in USB. You then need to flash your phone with the operator ROM, or the ROM you want to flash it with. Your phone is by far bricked, G3 ones are really difficult to ruin. I learnt that first hand
http://forum.xda-developers.com/showthread.php?p=1560272#post1560272
Think I may have done just that...bricked my phone. G3 wiza200, IPL/SPL 2.26
Cannot get it to read a usb connection at all. Help please?? Thanks in advance
jphuffs said:
At 56%, the desktop went to a blue screen and said an error had occurred and the system must be restarted. The screen asked if I had installed any new programs, check with the adminstrator, etc. The only program recently installed is the program for this ROM revision. When it crashed, the phone had a completion bar in the top 1/3rd, showing 56% completion. The rest of the screen was white. I restarted the desktop and was unable to establish a sync connection. I then preformed a hard reset on the phone. When it restarted, it showed 4 color bars, red on top, green, blue and white at the bottom. Since I cannot restablish a sync connection, how do I finish the modification. I am now concerned that I have "bricked" the phone. I am reluctant to try this mod on another phone until I can determine what went wrong.
Click to expand...
Click to collapse
hi
ur phone is certainly not bricked,cuz ur desktop crashed therefore the phone upgrade cudn't be completed,nothing to worry as long u can get to bootloader mode(Tricolor Screen)
Ok,listen, u do not require active sync connection,to flash a rom,do as I say and it'll be working fine,follow these steps to complete ur upgrade:-
1.Switch on,go to bootloader mode (Tri colored screen).
2.Connect usb cable to the phone and PC
3. After connecting usb cable,u will notice small 'usb' showing on the corner at the bottom of the bootloader screen of ur phone,if it shows,ur r ready to flash and upgrade
4.start the upgrade RUU_ rom u want the to upgrade with
5. complete the flash,let it reboot
let me tell u,u dont need active sync connection to upgrade
cheers
akashastrega said:
http://forum.xda-developers.com/showthread.php?p=1560272#post1560272
Think I may have done just that...bricked my phone. G3 wiza200, IPL/SPL 2.26
Cannot get it to read a usb connection at all. Help please?? Thanks in advance
Click to expand...
Click to collapse
hi
i have read ur situation at thread u have mentioned here,well i can assure u it's not bricked,cuz as sometimes it's able to go to bootloader mode.
The only problem to me seems the usb connectivety problem.
does it charge ?,if not then clearly it' a usb connectivity,if u can manage to get another usb cable and check out,hope it wud clear this doubt
zabardast_1 said:
hi
ur phone is certainly not bricked,cuz ur desktop crashed therefore the phone upgrade cudn't be completed,nothing to worry as long u can get to bootloader mode(Tricolor Screen)
Ok,listen, u do not require active sync connection,to flash a rom,do as I say and it'll be working fine,follow these steps to complete ur upgrade:-
1.Switch on,go to bootloader mode (Tri colored screen).
2.Connect usb cable to the phone and PC
3. After connecting usb cable,u will notice small 'usb' showing on the corner at the bottom of the bootloader screen of ur phone,if it shows,ur r ready to flash and upgrade
4.start the upgrade RUU_ rom u want the to upgrade with
5. complete the flash,let it reboot
let me tell u,u dont need active sync connection to upgrade
cheers
Click to expand...
Click to collapse
I just had this happen to me as well, I got stuck a 29%
Now when I get to bootloader it shows the IPL 2.26 and SPL 2.26 and also a RUU in the top right hand corner. Plug in USB and I get USB at the bottom left but then when I try to launch the RUU with the rom I want to flash I Invalid update tool, download new tool... It wont "Verify information on the device"
**EDIT
Nevermind, I just got Titanium to take... I may be ok... I think the RUU in the vanilla download I got is messed up or something...
Currently ripping through the rom update now. Damn I just got this phone yesterday I was gonna be pissed if I killed it.
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
jphuffs said:
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
Click to expand...
Click to collapse
ok when u swith on the phone what happens ?
does it go to bootloader mood ? or u force it to go bootloader by keeping camera button pressed and doing soft reset ?
well,after geting to bootloader mode,don't reset again just establish usb connectivity and when it show usb in the lower part of the bootloader screen launch ruu and start the flash.if it still stops with an error,post that error,then it means u had a bad flash or no flash at all.are you pretty sure you got it CID unlocked ?
tell you what you do,go to this link download WST tool and apply it,than post the data info it gives here,this will give the present status of your phone,ok
http://forum.xda-developers.com/showthread.php?t=329170
read this sticky:http://forum.xda-developers.com/showthread.php?t=298613
jphuffs said:
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
Click to expand...
Click to collapse
download the wizar-love rom
flash it using the ruu provided..
ftp://xda:[email protected]_Novii+CF2.rar
it should work.....
read this sticky
http://forum.xda-developers.com/showthread.php?t=298613
G4.1 Does you're device start normally (yes) or is it stuck on the three-colored bootloader screen (no)? YES... go to step G4.4, NO go to step G4.2
G4.2 Turn off you're device totaly. Remove the SD card and disconnect the USB cable from you're device. Turn on the device while holding the camera button. You will get into bootloader mode (3 colored screen). Connect the USB cable to the computer and you will see USB at the bottom of your screen above the left softkey (Activesync will not connect in bootloader mode, but you can flash from this screen!). go to G4.3
G4.3 Download wizard_love rom and flash it to your device. Your device should startup again after doing this. Go to G4.4.
G4.4 Is your device CID-unlocked (note: it's not the same as SIM-unlocked!)? YES... go to step G4.7, NO OR DON'T KNOW go to step G4.5. (note: CID-unlocking a G4 is only possible by paying for it at imei-check!)
G4.5 Download enable-rapi.zip. Transfer Cert_SPCS.cab and EnableRapi.cab to your phone. Run Cert_SPCS.cab FIRST and EnableRapi.cab SECOND. Turn your device off and on or wait 5 minutes before soft resetting. Done? Go to G4.6.
G4.6 Follow this great thread by the-equinoxe: [solution] G4 SoftSPL Flash any ROM to CID locked G4 [UPDATED] and load the softSPL on your device using his method. Make sure you take a G4 safe rom (see the thread for details). After the steps you'll have the rom of your choise on your device!
G4.7 You're reade to flash the AKU2, AKU3, WM6 rom of you're choise IF the rom DOESN'T contain IPL/SPL. AKU3 and WM6 roms normally don't contain IPL/SPL. If you want to flash an AKU2 rom, make sure you take the G4 version. If you get an error 300 (invalid update tool) while trying to flash your device look at this thread!
NOTE: If you tried to flash a G3 rom with IPL/SPL in the rom on a G4 you probably will have a bricked device! DON'T flash the new 3.08 and 3.09 IPL/SPL to your G4!
NOTE2: If you got problems flashing with softSPL: Follow this great thread by mun_rus: Solutuion found: how to flash any rom to CIDLOCKED DEVICE. If your device won't start after flashing you can use step G4.2 and G4.3 and try again. Also look at this thread by eddieitman: Faria G4 Step by step installer with instructions to make sure you did all the necessary steps!
Crashed during flash
It has been suggested that I download Wizard Service Tool. OK, I did that. The Wizard Service Tool says to connect to ActiveSync. Can't do that. Phone is locked in Bootloader. It boots up into Bootloader. Any action requiring ActiveSync won't work as long as the phone is locked in Bootloader. Any suggestions as to procedures at this point. Remember, that trying to flash the ROM at this point, I get a message 300 that says I need to get a newer update utility.
Crashed during update
It has been suggested that I flash with wizar-love rom. Did that. Got a message 300, my phone need a newer update utility.
jphuffs said:
It has been suggested that I flash with wizar-love rom. Did that. Got a message 300, my phone need a newer update utility.
Click to expand...
Click to collapse
go to the G4 section and look for the HardSPL thread. Once there get the MUNRUU file from first post and use it with the ROM you wish to flash as it might do the trick of the ERROR 300
crashed during flash
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
jphuffs said:
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
Click to expand...
Click to collapse
this is the thread. and the link is there......
http://forum.xda-developers.com/showthread.php?t=332320
or another thread with link...
http://forum.xda-developers.com/showthread.php?t=334796
jphuffs said:
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
Click to expand...
Click to collapse
download latest Official Rom from carrier official site, establish usb connection while in bootloader flash,it will start working,after that follow the procedure of unlocking and upgrade
or if you have put in Sdcard,remove it and then switch on the device,it might get ok.It's seen in many cases that some Sdcards create problem while upgrade and bootloader screen gets stuck,by removing it,it starts to work fine
good luck
(mestrini;1565518]this is the thread. and the link is there......
http://forum.xda-developers.com/showthread.php?t=332320
or another thread with link...
http://forum.xda-developers.com/showthread.php?t=334796)
My phone is a G3. These links are pretty adamant about being for G4 only
jphuffs said:
My phone is a G3. These links are pretty adamant about being for G4 only
Click to expand...
Click to collapse
I'm talking about the, so called, 'MUN RUU' which are the files used to upload the nk.nbf. You just have to replace those for the ones you're using now; NOT THE nk.nbf, just the others...
zabardast_1 said:
download latest Official Rom from carrier official site, establish usb connection while in bootloader flash,it will start working,after that follow the procedure of unlocking and upgrade
or if you have put in Sdcard,remove it and then switch on the device,it might get ok.It's seen in many cases that some Sdcards create problem while upgrade and bootloader screen gets stuck,by removing it,it starts to work fine
good luck
Click to expand...
Click to collapse
What is "Official Rom from carrier official site"?
The SIM card was removed.
Hope this helps
jphuffs said:
What is "Official Rom from carrier official site"?
The SIM card was removed.
Click to expand...
Click to collapse
For instance, if you are (like me) with TmobileUS, go to the Tmo site and go to the page that gives you the download to rom 2.26. I have that rom, if you are with Tmo, but won't be able to upload it until later...
http://tmobile.infospace.com/tmweb/...wnloadCenter/DeviceDownloads.aspx?deviceID=24
THAT^^^ is for TMOUSA...it is the official Tmo rom. If you are with cingular/att, you need to access their website and download their official rom, etc.
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08
licensedtoquill said:
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
Click to expand...
Click to collapse
What was the ipl/spl...? before you flashed button's rom 1.05 ? and which carrier's Rom was loaded ?
you got ipl 1.01 due to flashing button's rom but your spl remained 2.26,try to flash button's rom a couple of times more,sometimes it takes a lot more than one flash to load up button's rom,or try a hard reset.
secondly,download official carrier's rom and as you say you can get into bootloaders,flash it.
Disconnect your phone from the usb cable,disable any Firewall and Anti virus and reboot your Pc.
1. Make sure your phone 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 phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t Bluetooth for the Upgrade)
4. When you see usb appear at the bottom of bootloader screen
5. 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.
What do you mean by 'I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08',did you upgraded to ipl/spl 3.08 before flashing button's rom 1.05 ?
good luck
I've tried some of that: Now I'll do it properly
OK I will follow your instructions: Just a few points. Firstly I didnt realise that when it says Button's ROM has loaded properly, you might still have to try loading it again a few times.
Secondly I did try loading the manufacturer's ROM and it gave the same result: Loaded fully, went to FINISH. After 100%, wouldn't get past initial splash screen on reset.
Thirdly the reason I was doing the upgrade which failed with that error message was because I just didn't recognise the IPL of 1.anything. So as I had heard that the SPL/IPL was some type of bootloader, I thought that the reason it wouldnt in effect boot was because I was trying to load an advanced ROM with a dinosaur boot loader. So I was trying to load IPL/SPL 3.08 to try the ROM flash again. This seems to have been a red herring. I am reasonably sure that the IPL/SPLs were the same as they are at present before I loaded Button's ROM
Lastly I can do all of this with a vanilla computer I have lying around somewhere onto which I can load ActiveSync 4.5 so I will try that.
I hope this is of some use to users who have this problem
Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!
Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)
Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).
So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.
With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.
Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/
licensedtoquill said:
Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!
Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)
Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).
So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.
With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.
Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/
Click to expand...
Click to collapse
First of all,let me advise you that lokiwiz02b tool never works in bootloader mode (tri color screen),to work it has to have a working OS on your phone,therefore using lokiwiz again and again will not work and is of no use,untill and unless your able to flash button's rom 1.05 successfully and it loads up correctly and the phone is in working condition,also downgrading to IPL/SPL 1.xx,lokiwiz will not operate.
Vippe said to rerun the lokiwiz in this sense that if you ever again downgrade to IPL/SPL 1.xx by flashing button's rom.as if you have upgraded to a wm6 Rom with ipl/spl 2.xx or 3.xx and you flash back again button's rom 1.05,than only to rerun the lokiwiz.but if you are able to flash button's rom 1.05 and load up sucessfully to OS and get the device unlocked,than there's no need to go back to ipl/spl 1.05 as your phone will be permanently unlocked.
regarding Error 'Formating FAT32 partition Formatting failed'
well to my understanding and knowledge,it does not pertain to any Rom flashing errors,it's mostly related to sdcard/mini-sd problems,Are you having any sdcard/mini-sd card in your phone,then remove it before flashing cuz it has been seen that sdcard/mini-sd card create problems while flashing.If the sdcard/mini-sd card requires format,it usually get splash screen stuck up or won't let bootloader mode stuck.
So, try to flash button's rom a couple of more times or as sometimes it gives problems then download and try xda_minis_Launch Rom :- http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe
and the third option is of course try to flash the official carrier's rom,good luck
Not sure I have simplified enough
Many thanks for the note: To restate the problem, no ROM I flash can get me past the initial splash screen and I am not using any SD card at all.
Every ROM flashes successfully. It always then gives me it's SPL/IPL report on the initial splash screen but none of them get past that first splash screen. All they do is to load the splash screen (whether it is the beer mug or the T-Mobile one) and then tell me what versions I am running in red and then all stop.
Actually I thought that there wasnt much point in re-running the unlock program of whatever type if it was unlocked already but that was how I interpreted Vippie's advice if you had somehow got back to a 1.xx IPL. Now I see that was incorrect. I have tried so many times to reflash Button ROM and seen it complete fully and even close the utility that I am beginning to wonder whether it IS worthwhile trying numerous times again. So I will now try to flash the http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe as you suggest.
By the way, I don't ever seem to be able to get the computer to see the device so as to flash it when any OS is loaded (obviously because none of them load after the soft resets after their flashes). it SEEMS to me that I can only get ROMs to re-flash from the three colour screen? But even trying to get a stable T-Mobile ROM onto the machine seems to work this way and as I say usually completes to 'FINISH' and then doesn't get me past the splash screen again. Curiously this device doesn't seem to mind being flashed in tri-colour mode!!
In first splash screen mode with the Button beer mug showing, and with the red text showing an IPL of 1.01,, an SPL of 2.26, GSM or 01.12.10 and an OS of 1.5.4.2 all I get now when I try to flash the T-Mobile ROM is an error 274 or error 260 telling me that although I can see the green light lit on the Wizard telling me that the device IS connected to the computer and the battery IS fully charged, there is no connection between the computer and the Wizard! Actually flashing Xda_MiniS_LaunchROM_v154102 now does the same thing: I should try rebooting and possibly [grasping at straws here] moving the flash directory from the desktop to the root of C:
update
Just to update this, I did flash the mini-ROM Xda_MiniS_LaunchROM_v154102 and it did complete successfully from the tricolour screen (going red at 85% and then at 98% as well) and then completing and closing the utility
And now stops yet again at the Button beer mug after reading the parameters (which are the same)
Sorry to repost yet again
I have now flashed the manufacturers ROM and it took successfully from the tricolour screen and the unit now boots to the T-Mobile initial splash screen where it yet again stops completely after telling me that it is now at spl/ipl 2.26
licensedtoquill said:
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
Click to expand...
Click to collapse
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
Pity no one seems to know the answer to this judging by the number of page views!
lou2ser said:
I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.
Any ideas?
EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.
Click to expand...
Click to collapse
At the moment the Consumer Product Safety Commission is looking into the general question of battery malfunction on these Wizards: T-Mobile seem to know all about it as they have instructions to try to sell customers new units when problems with batteries or battery overheating are reported; if customers don't respond positively, they are instructed to read endless scripts to you and keep you on the phone for as long as possible and hope that sooner or later you will go away.
Did yours overheat before dying? Some element of reseting the device may be called for: I found that with a working unit I have, (not the one with the frozen screen problem) if you simply put another charged battery in it, the Wizard may spring to life. But don't expect T-Mobile to assist you with this, they are in denial about this problem. One suspects Cingular may react the same way, I have never had any experience with them.
Nevertheless this does appear to be a real problem here judging by the number of page views and the lack of suggestions by any moderators?
lou2ser said:
I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.
Any ideas?
EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.
Click to expand...
Click to collapse
what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?
secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.
There may be another problem, - People dont like answering hardware problems here?
No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.
Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.
But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.
Can you still flash your device?
licensedtoquill said:
No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.
Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.
But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.
Can you still flash your device?
Click to expand...
Click to collapse
As long as your phone gets into bootloaders(tri color screen),it's not 'Bricked',be rest assured of this,ok
Secondly until and unless you have working OS on your phone,it'll not be recognized by the computer,as it cannot establish connectivity through Activesync.Activesync will only detect your phone in a normal working status,so in present status,your phone doesn't bootup normally into working OS and it only goes into bootloaders,it will never be detected by the Activesync and thus your computer.
The only test to verify the connectivity of your phone with computer at present is that when you attach your phone with the USB cable to the PC and there appears small usb at the bottom of the bootloader screen,that means your phone has established connectivity with PC.
It's a 'catch 22' situation,where your bootloaders are not accepting any Rom flash and the only way is to get your phone start working normal and unlock it ,for that it's required to downgrade to ipl/spl 1.xx,or the other option is to flash the official rom to bring it back to it's default status and then try to downgrade to ipl/spl 1.xx and unlock it.
Well,as you say it's not charging that cud be a major hindrance in flashing,cuz it's recommended to have atleast 70% charged battery before starting any flash,if it does not retain charge during a flash and does not have enough juice left to complete the flash then the flash will not complete,it's a bad flash and phone usually stuck up at the bootloader screen,this cud also be the problem ,you are not getting a full proper flash.
Try to fully charge your battery and then try to flash,if it's not charging,than check your charger or the usb plug of the charger,it might not be having a good connection with the mini usb port of your phone,wiggle it a bit and see if it starts to charge,secondly,it cud also be the mini usb port of your phone which might be malfunctioning,anyway verify and rectify the problem.if it's the usb plug of the charger,get a new charger,but if it's the mini usb port,than I'm afraid you'll have to get it repaired or replaced,
good luck
zabardast_1 said:
what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?
secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.
Click to expand...
Click to collapse
Here's my updated post:
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
lou2ser said:
Here's my updated post:
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
Click to expand...
Click to collapse
hmmm,are you sure it's IPL/SPL 2.25.001 (two '0') and not 2.25.0001(three'0') ?
well if it's 2.25.001,it'a G3 device and I find no reason that it cud brick like this,but if it has 2.25.0001,than it's a G4 device,than it's pretty well known that by flashing a G3 Rom will definitely Brick it.
secondly,First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"
I'm pretty sure. I wrote it down before staring the update process.
Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1
Am I describing what a bricked phone looks like? Any other ideas on how to revive it?
This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.
lou2ser said:
I'm pretty sure. I wrote it down before staring the update process.
Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1
Am I describing what a bricked phone looks like? Any other ideas on how to revive it?
This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.
Click to expand...
Click to collapse
GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.
well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement
zabardast_1 said:
GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.
well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement
Click to expand...
Click to collapse
The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.
Again, thanks for your help.
lou2ser said:
The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.
Again, thanks for your help.
Click to expand...
Click to collapse
wee.this you know yourself that they are the manufacturers,technicians and have all the gadgets,knowledge and means to find out.lol
why don't you atleast try the 'Force bootloader' once,let's check it out.huh !
Try this.First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"
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 )
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Before I flashed my first rom, I read wiki.xda-developers.com to make sure I understood what I was doing, and used the search button, instead of risking turning my phone into a paper weight.
Since then, Crackwhore has written a very helpful post at the top of this forum about how to use HSPL and USPL to allow you to flash roms.
yeah i know all that. not my first time flashing a phone but the first time it got stuck loading the bootloader. and specially when i´ve only used the HTC update.
darfor said:
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Click to expand...
Click to collapse
you mean you couldn't get to boot loader page?
So you already have HSPL 1.56 installed (or have SPL1.54 and used USPL)?
If you have HSPL you could try renaming the .nbh file to blacimg.nbh and copying it to the SD card and entering bootloader
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
AFW said:
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
Click to expand...
Click to collapse
try dnloading the rom again amd try.
the file might be corrupt
Have tried that many times. File is not corrupt. I'm getting really worried this is now a brick...
OK, if you can get phone into bootloader, it is not bricked
What does your SPL say in bootloader? Do you get any errors when trying to flash rom? Are you using USPL or HSPL? If USPL, you have to use it before every flash to new rom or radio. If HSPL, are you using correct version?
Was on Dutty's 3.9 XT, but decided to revert to standard WWE 1.56. I flashed the Std 1.56 ROM successfuly, and then tried to restore the ship SPL 1.54 using the card flash method. This failed, and now I'm stuck on the bootlader screen forever.
No matter what I do the THD always goes to bootloader (red-green-blue-white screen), with following text:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
Upgrade ROM code error
Please try again
USB
Click to expand...
Click to collapse
When I start blac_uspl.exe (USPL 2.5), a window flashes (Vista64) for a split second and then nothing else happens. The Vista64 system's USBs work with THD and have been used to sync over past few months.
When I try to run HSPLWrapper_Blackstone_156OliNex.exe and step through the preliminary screens, the Verify that you want to update ROM version screen has the From Image Version as blank and the To Image Version as 1.56.Olinex. When I click to commit the flash the THD screen switches to white with a progress indicator that always stays at 0% until it times out. Recovery does nothing and the same thing always happens. Using Vista64. .Net installed and fine. I can't use the card method (BLACIMG.NBH) - the system also stays on "Loading .... 0%" and nothing else happens.
When I try to flash anything (have tried HSPL1.56, Dutty's 3.9 ROM, stock 1.54 spl) using the card method, the system says "Loading . . ." and hangs there forever without a progress indicator showing.
Your SPL says 1.54.0000. When you try and run USPL.exe have you remembered to disable your antivirus?
Have you tried usb method instead of card for flashing rom?
I know you have said that youi have used usb for syncing, but when in bootloader does it change from 'serial' to 'usb' when you connect HD to PC?
Fallen Spartan - I want to thank you for taking the time to help me resolve this problem. Very much appreciated!
1. Yes, anti-virus disabled and indeed removed from the PC.
2. Yes, have tried the USB method at least 20 times.
3. Yes, the bootloader changes from Serial to USB. It then goes to the progress indicator screen and hangs on 0%. The progress indicator on the RUU on PC also stays at 0% and eventually times out. I've gone through the Recovery routine at least 20 times, with no luck.
When I try to run SSPL-Manual-TouchHD.exe it says "not a valid Win32 application".
I'm a bit perplexed by this.
You have obviously successfully flashed Duttys V3.9 so drivers are fine, you know how to use USPL, both flashing methods (SD card and usb/pc), disabled anti-virus, phone in bootloader.
Have you tried to reflash 1.56 rom or possibly performing a hard reset before trying to use USPL or HSPL. I doubt this would make a difference though.
Have you tried cRaCKwHoRe's USPL GUI v 2.5 Application?
You don't get any code errors?? I'm struggling to find a solution here.
Yes, this is most vexing. I've flashed innumerable times before and never had an issue. I suspect the SPL is fine, but somehow the actual WM ROM image is corrupted. Will now try to load Std 1.56 ROM image again...
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa (though I'm a rugby fan).
AFW said:
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa.
Click to expand...
Click to collapse
No accomodation required, just glad you got it sorted
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
can anybody help me at all
Adamsville: perhaps you're stuck in bootloader mode because the WM ROM image flashed on your system has become corrupted or disabled, ie the only thing the system can boot into is the bootloader.
Try flashing a new compatible WM ROM image and see if that works.
AdamsvillE said:
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
Click to expand...
Click to collapse
a hardreset followed by a 1.54 base rom will solve all ur probs.
or lower spl to 1.14 cos ur stock rom is a 1.14 base as suggested by th name..
cheers