Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
SuperDodge said:
Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
Click to expand...
Click to collapse
i had this very proglem... TURN OFF THE PHONE ASAP.. as the bootloader screen will drain your battery very quickly.... reset computer and phone... plus in the USB cord.. and in the booth loader screen in the lower left corner.. you should see USB!!! just flash workin room.. and you should be set to go.. i believe>.
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
SuperDodge said:
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
Click to expand...
Click to collapse
hmmm i dont know... try restarting both devices.. other then that i cant hlep ya.. im still new to this...
USB means it is connected.
Again, keep the battery out when you aren't doing the flash. Reboot the PC in case the link is down.
Try flashing a stable ROM, like the Mr. Clean one you used before. Activesync doesn't need to operate, the ROM will see the wizard if the wizard says USB.
Zonealarm actually interferes with my ROM flashes, although it prompts me to see if it is ok; you might turn off your firewall prior to doing the ROM flash. If you do so, disconnect from the web.
I have also the same problem with my XDA 2 mini or the other called this the HTC Magician. I try to UPgrade my Radio 1.03 to 1.12. and when im applying the upgrade procedure the Upgrading stops and error. What happen now is my XDA 2 mini or HTC magician doesnt open now. only the word "SERIAL" and when i plug the USB, the word "USB" show on the screen................... Is there some one can help me pleasssse with my problem....
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.
Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan
Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.
Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!
try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....
The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.
Hi there, I've been reading your forums since I got my diamond. You have done a great job here.
Until now, I have been able to learn almost everything I now from here. (I'm new to ppc). Nevertheless, I have come up with something I cannot resolve.
I had installed hard spl signed from olinex (1.30). And also upgraded my rom to 1.93 without any problem. But when I tried to do the same with the radio (I want to go from .05 to .08) I get 260 errors over and over.
I use Windows Vista x64 which seems to be problematic but for me worked at first. Anyway I also tried to run it on Xp and go 262 errors instead so no luck with that.
I have tried several things I've already read. Switching USB port, starting the flashing on bootloader, disabling advanced network functionalities from Usb to Pc, ...
The issue seems to be with my PC not dealing with the device when the tricolor screen appears. USB is written in the white band, and Vista seems to recognize an HTC usb device. But when I try to run the CustomRUU when already in the bootloader mode, the app doesn't even recognize the diamond.
Otherwise it recognises it, but when it changes to tricolor screen and the progress bar appears it gets stuck at 0% until the 260 appears.
I think I have run out of ideas right now. Could any of you lend a hand, please?
im pretty sure you need unsigned spl for flashing radios. i dont think radios are signed. i could be wrong, so maybe wait for some more replys before flashing. btw welcome
Thanks. I suppose I'll wait as you said but you are probably right about that. Anyway I suspect that sadly that's not the main problem. I have tried to reflash my rom, just for testing if it worked and ... 260 . Trying to reflash HardSpl or trying to install an unsigned version didn't work either. I've downloaded from different sources to make sure that the file being corrupted was not the problem. I don't know if I'm doing something wrong or I was just extremely lucky the first time it worked
I have been trying for almost 2 days straight to flash a new HardSPL then ROM to my Touch Diamond. I have done everything I can possibly think of but nothing works. I think the problem may be that I am using VMWare Fusion (on a MacBook Pro) running Windows 7. I can establish a connection with WMDevice Center perfectly fine, the RUU puts my Diamond into BootLoader and it says USB in the white area. However, after this step the status bar shows up on the computer for about a minute then I get error 26x (260, 266, 264....) cannot connect to device. I don't know how to work around this. I would just boot from the Internal Storage but I need to be able to flash a HardSPL before I can do this. I somehow was able to flash a new SoftSPL (I'm running SPL-0.64.000 right now). If anyone has any ideas about what I can do please let me know. I've searched the forum, done hard resets, tried JumpSPL v1, tried to boot a ROM from Internal (can't without updated HSPL), everything. I'm out of ideas.....
Im having the same problem i almost slammed mines. At first the activesync use to come out now it doesnt even do that some choose what to open with box comes out. This phone does things random i have no idea why. Everytime it connects i press the update to install the new windows 6.5 on it and the the sound of it disconnecting shows up then it sounds again and then the screen says usb and then on my computer it says theres no htc connected so i wait to see and i get a error after 3minutes of waiting then i got to reset. Its getting me real frustraded.