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.
i need some serious help im desperate at this stage.
ive basically got a htc tytn ii on uk orange
i update the rom to htc standard one which sim locked it
i followed the instruction on how to get it like i got it from orange
which i believe was sucessful. but because it was still sim locked i
thought the hardspl was relocked so i ran that again which failed and ended up on the tri colour screen after which i tought it may still be hardspl locked
so i tried to flash it with the rom again it got to 17% then crashed
now my phone will only boot to the tricolour screen it wont load activesync and if i try a flash it with anyrom it either stays at 0% gets stuck or gets to 1% then the phone restarts.
ive buggered the phone up proper i need some help if there is any for this mess
when i try a rom upload it says error [294]: invalid vender id
this update utility cannot be used for your pda phoe please check your update utility
Did you install Hard SPL?
http://forum.xda-developers.com/showthread.php?t=334679
See if you can install that and then try to reinstall your rom.
this required activesync to be green mine will respond to usb but not activesynce so i cant go any further with the hardspl unlock im stuck on the tricolour screen. and flashing will only go to 1% then restart and the message come up again.
same problem
i have the same problem and i can only get to 1% . i have tried to flash it with several roms using diferent utilities and none seem to work i used hard spl the first time when it failed. HELP PLEASE !!!!!!!
found solution
got mine working here is what i did
run mtty select usb after disabling it in activesync
press enter and you should see cmd>
type boot and when your device restarts it should start in your old rom
run hardspl again
then you need to reinstall your rom
although a word of warning my phone became sim locked after this
worked a treat many thanks it is sim locked just have to wait for the sim unlock for it now
willbyrne said:
got mine working here is what i did
run mtty select usb after disabling it in activesync
press enter and you should see cmd>
type boot and when your device restarts it should start in your old rom
run hardspl again
then you need to reinstall your rom
although a word of warning my phone became sim locked after this
Click to expand...
Click to collapse
no worries
yeah no worries, i was affraid when i locked mine i might have to return it and get anothe orange version but i used some company online and got my code in about 3 days.
oh yeah you will probably need to enter the code in twice, mine said simlocked and then network locked but it was the same code
Hey quick question. I've looked in all the threads but can't quite seem to find the answer. Just wondering if when I go to update to the official htc wm6.1 if I can just remove my sim card during the update process without having to back all my crap up. I just can't find out if the sim card needs to be in the phone during the process or not. thanks for the help.
Your SIM card stays in the phone for the update.
Remove your Micro card prior to the update process and install your new ROM. I think the install directions say to remove the Micro card prior to the install.
Boot Loader
Alright. Im slowly getting there. Just succesfully loaded the wm 6.1 update to my device. But theres a problem. My computer says it's 100% done and the click to finish button comes up, thats not the problem. the problem is after my phone hits 100% it goes back to the bootloader screen. the new SPL is displayed as SPL-3.02.0000 and than it says CPLD-8 and im getting a reaction from the usb, but it wont load the os? ive tried to reinstall from the ruu like 4 times now and nothing.
Hello! I got a problem a couple of days ago with my Xperia. Whenever I try to load it i get the "Alien battery" dialog. I searched and found that reflashing it would probably fix it. I am not sure if flashing the phone means putting a new rom on it, but that is what I did. The rom worked but the problem was not fixed. I didn't know what to do so I accidently put a stock SPL rom file on my phone and installed it. I realized what I had just done when the progress bar had reached about half way through. When i start the phone with any Kovsimg.nbh file on my memory card the phone boots up with the "rainbow screen" and goes to a gray screen with blue text saying "Loading . . .". If I boot without Kovsimg.nbh or without memorycard it says something like "Loading . . .
Image file not found " and then it goes back to the "rainbow screen" except that it says "Serial" at the bottom of it. Have I destroyed my phone or is there any way to fix this?
Edit:
This is what the "rainbow screen" says, without sd card:
RUUNBH
KOVS110
SPL-0.072.0000
MicroP1-787
MicroP2-707
Continye to Upgrade ROM
Please wait...
Serial
Click to expand...
Click to collapse
Bump (The number of viewers stopped increasing.)
Bump.
Any Replies are appreciated.
I fixed it. I updated it with SEUS.
how u fixed fred; cuz i'm facing same problem but my configuration on the rainbow screen are different; do write briefly so novice like me can understand....thanx in advance