Database Develop

Forcing Bootloader Mode

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.

oh my...did i brick my phone?

I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!

what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..

I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...

Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..

wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail

I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?

Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...

tnx for the explanation..
have fun!!..

thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >

Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..

What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.

How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).

G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).

ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.

brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....

Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck

mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!

brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help

entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!

Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!

New HTC Trinity issues

Got my Trinity in the mail today and started the process of pimping it up to xda-developers' standards.
1. Ran SSPL-TRIN.exe without problems from "HTC Trinity SIM & CID Unlock - v1")
2. Ran ROMUpdateUtility.exe. Dialog on PC said upgrade was successful, but screen was black on device
3. Soft reset device. Windows Mobile (green screen) shows, but never goes away. Repeated this procedure 3 times (waited over 5 min each time)
4. Hard reset device. HTC logo shows with numbers "M 05, B 05, D 1.16" showing for 5 seconds. The text "No GSM" appears for 1 second and disappears with the numbers. Only the HTC logo on white is on the screen, forever.
Any ideas? Would hate to have bricked my phone after only a couple of hours.

I can get into the three color screen. I attempted to run ROMUpdateUtility, as I wrote before, again, but I get an error message on the PC saying that the ROM is corrupted, after which my device resets. (To HTC screen, forever, like I wrote above)

Sounds like a bricked device already.
There is a lot of information on this problem in the Hermes Wiki and forum. You may find some useful information there to help unbrick.
Sorry mate.
S.K.

Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.

lazaron said:
Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.
Click to expand...
Click to collapse
Check the Wiki, you will find links to some standard ROMs.

lazaron said:
Is there a way I can obtain a rom that will be accepted by my bootloader? I checked on the FTP, but there's nothing there (anymore?)
If so, perhaps I could flash over to a standard one, then start over.
Click to expand...
Click to collapse
Chek here:
http://wiki.xda-developers.com/index.php?pagename=Trinity_Upgrades

Will try them all now. Results with all roms thus far have been:
Progress bar on both PC and phone moves to 1%, then:
a) Phone reboots & PC displays error "invalid vender ID" or b) Phone reboots & PC displays error about image being corrupt

Good news!
I went to a HTC service center where I live (Oslo, Norway). They said they could fix it in 15 min. (flash the device with an original ROM using more advanced equipment than a USB cable)
After about 10 min. the guy comes back with the phone, which now has the exact same screen I was stuck on and concludes that the motherboard is broken. I told them how I had only owned the phone for a day and they offered to replace the motherboard for free (took a few hours).
Once I got back home with the repaired phone, I was pretty nervous about flashing it again, but everything went perfectly.

Congrats friend... let me tell you that you got balls to re-flash your new device after the repair .

lazaron said:
...
2. Ran ROMUpdateUtility.exe...
Click to expand...
Click to collapse
Can you tell us exactly what ROM you used to update and is your Trinity HTC made ?

Always flash from the SD card!
Cr7pt0r said:
Congrats friend... let me tell you that you got balls to re-flash your new device after the repair .
Click to expand...
Click to collapse
Actually, I'd suggest adding to the Wiki that any flash should always be done directly from the SD card (as per instructions in the wiki) to avoid PC/USB problems. After bricking my Hermes because of a USB comm problem, I always flash from the card directly. Much faster and safer.
/politby

help mda messed up

after i used button's 1.05 ROM i cant get no usb and its very slow not i cant install HTC Wizard Unlocker UPDATE Version 0.2b

Do you mean no activesync by no USB? Try flashing it again through bootloader screen or try flashing the official rom of your provider through the bootloader.

how to get to the bootloader screen

cesarrri12 said:
how to get to the bootloader screen
Click to expand...
Click to collapse
when you soft reset hold the camera button

so just press the power then hold the cam key

Just use teh soft reset on the side then hold the cam-key

ivanwinkel said:
Just use teh soft reset on the side then hold the cam-key
Click to expand...
Click to collapse
Once at the bootloader screen, what do you do next? I've been stuck here for a little while now and can't figure out what to do while in this mode.

itburnout said:
Once at the bootloader screen, what do you do next? I've been stuck here for a little while now and can't figure out what to do while in this mode.
Click to expand...
Click to collapse
Read all the stickies (also in WM6 forum)! It's all explained there.
http://forum.xda-developers.com/showthread.php?t=298613

vippie said:
Read all the stickies (also in WM6 forum)! It's all explained there.
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
Yes, I've been over that, and some of the related links from that thread, but so far I still can't find the missing piece. All of the tips point to using an updater to load Wizard Love, but I still get a communication error. I can't figure out what I'm doing wrong.

I'd also point out that while this may be my third 4th post, I'm not really new at this. I am new at having problems. I've flashed this phone probably a dozen times in the past year and have never had a problem. I've going over the sticky threads and tutorials, but what I'm missing is how I actually get wizard love to load. So far, it still does a check for the phone through activesync, then tries to run RUUGetinfo.exe and EnterBootloader.exe to which copies nk.nbf. So far the central issue seems to be establishing a connection. Since I am already in the boot loader (the red, green, blue, white screen) I need to be able to copy nk.nbf, which is what I cannot figure out. So far, I haven't found anything useful on this.

I'd also point out that while this may be my third 4th post, I'm not really new at this. I am new at having problems. I've flashed this phone probably a dozen times in the past year and have never had a problem. I've going over the sticky threads and tutorials, but what I'm missing is how I actually get wizard love to load. So far, it still does a check for the phone through activesync, then tries to run RUUGetinfo.exe and EnterBootloader.exe to which copies nk.nbf. So far the central issue seems to be establishing a connection. Since I am already in the boot loader (the red, green, blue, white screen) I need to be able to copy nk.nbf, which is what I cannot figure out. So far, I haven't found anything useful on this.

When you just plugin USB cable. Does it say USB on the left bottom of your screen? After this you should just use the RUU. Maybe it helps to uncheck allow USB connections in activesync.
Most people having problems flashing from bootloader (communication error) can succesfully flash from another XP machine. Have you tried that?

HELP ME! My Tilt Is Bricked.

Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.

Just re start the ruu and let it sit for a minute when that happens, it will start again by itself. Almost shat myself when it happened to me.

First of all, relax. Your phone is not bricked. Do a little looking around the forums and you will resolve this.
I am too lazy to search for him but is the 3.02 SPL compatible with the 6.1 ROM?

I can't restart the Ruu because I can't get a usb connection to my phone. The bootloader goes into usb mode but my computer does not see the phone. The Ruu says it cannot detect the phone either.

Isn't there a way this guy can re-flash using a MicroSD card?

MineralGray02K said:
Isn't there a way this guy can re-flash using a MicroSD card?
Click to expand...
Click to collapse
I'm not sure if the OEM SPL has the ability to flash from card like the Hard SPLs.
To test put the Carrier ROM (Download from the Wiki) on to the root of the MicroSD Card and call it KAISIMG.NBH. Turn on the Phone with the Camera Button Held Down. It should try and flash the ROM then. If that doesn't work, I have a thread and wiki page all about getting stuck on the bootloader, check my Sig for more info.
Hope this helps.
Dave

rodavery said:
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Click to expand...
Click to collapse
run this while phone is hooked up to computer stuck in bootloader.

Sweet Jesus
Ok, I tried the tri-color fix from nufsaid. It didn't work b/c it couldn't open a usb port or didn't see the phone or something. Then I tried putting the rom on my microSD card.
And *SHAZAM* there it was. DaveShaw you are a god to me now. It said the update was successful but I'm still stuck in the bootloader. It used to work if I would plug it into the wasll charger and reset it but that isn't working now. My computer still doesn't recognize it so Mtty or anything still doesn't work.

Ok, I left my tilt on the tri-color screen all night long to run down the battery. When I woke up I tried to power it on and I got the familiar ATT flash screen but when I plugged it into the AC power it went straight into the bootloader.

I don't know what's worse, bootloader or red light of death, I just experienced the red light, called att and got a new phone sent out in 12 hours! What SPL does your phone show? they might exchange if it's not 'voided'

ok, I finally got it to load the windows. If the battery has a high charge or is charging resetting won't get out of the bootloader. If I let the battery run down to almost nothing, wait a little while with it out, then try it again it will turn on. my spl is now 3.56.0000.

Finally
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.

rodavery said:
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
Click to expand...
Click to collapse
Glad your back up and running. There are two new hard SPL's be cmonex (they are mentioned in the link in my sig) that make it less likley for you to get stuck at the bootloader. You could try those?
Ta
Dave