Database Info

Dead USB/Stuck on Tri-color screen

Earlier today my ATT Tilt was having trouble synching to my office system; it would charge, but it would not be recognized by Active Sync. I had been planning to flash the new HardSPL tonight anyway, so I thought I'd check different cables on the home system while I looked to update the SPL.
When I got it home, none of the cables or other systems would change the basic problem: the unit would charge, but the device would not be recognized. I tried soft resetting it, but that did not help. I thought I'd try taking the battery out, then try a hard reset.
After taking the battery out, the system went straight to the tricolor boot loader, with "serial" underneath. The micro SD card it had in it wasn't formatted for FAT32 and didn't have an image on it, so it just stuck there.
I removed the microSD card.
I then tried plugging in the USB cable (which does change the screen from serial to USB), but attempting to flash a ROM still fails, as the USB connection still seems to be dead for that. Hard reset does not change this; it goes straight to tricolor.
It didn't seem to be charging on the usb or on the charger (no yellow light), so I also I removed the battery so as not to waste any remaining charge.
My current theory is to get another SD card in the morning, format it with FAT32 and see if it will flash a rom. Any other, better ideas?
Since I had the (v1) HardSPL on it with one of Dutty's ROMs, I am a
bit afraid to send it in for warranty replacement repair, at least until
I can restore it. But if I can't get anything to it, it's going to be a bear
to get through the diagnostic update to restore the original rom.
If I am missing anything obvious to try here, I'll glad take the noob points, but I'm stuck for better ideas.
Thanks for any thoughts.

Mtty doesn't work
Meant to mention that mtty.exe doesn't work through USB.

No Joy with sd card, hmm
So, I re-formatted the SD card, put an image on it, and it was recognized. It loaded the radio and OS, gave a success message and stayed on the white screen. I did a soft-reset, according to the "Flashing with SD cards" instructions, and it returned me to the boot loader and offered to re-run the install. I did that (why not, I guess?), and it did the same thing.
This had been Hard SPL'ed, but I'm trying a return to the stock ATT rom now. Any other thoughts much appreciated.
<edited>Same thing happens with the stock ATT rom. If I load it via SD card, it reports success, but a reset returns to the tri-color screen if the SD card is taken out and to the "loading" screen if it is not.

Hey there,
It seems I have a similar problem as you. A few days ago, I wanted to install this rom:
http://forum.xda-developers.com/showthread.php?t=392245
There was a hardSPL with it. Copied it to my device, ran it (went into tricolor mode, so that's good). From there, I wanted it to flash it, but my laptop didn't recognize my Kaiser anymore. Soft-resetted the thing, went back into windows mobile.. good. Bu from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.

moos said:
Hey there,
But from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
Click to expand...
Click to collapse
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?

I have had some issues with getting usb to recognize in the tricolor screen. In my latest spl flash, it took about five trys to get it to work, you have to be persistent some times.
Anyways the steps to get it recognized are as follows:
1. I plugged the phone in, (with the os booted, you can't do this obviously) and waited for activesync.
2. Went into bootloader mode, in the tricolor screen it said I had USB, but I was never able to flash.
3. Disconnect the usb while in tricolor, and wait about 15 sec and plug it back in.
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.

Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.

Speaking_On said:
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
Click to expand...
Click to collapse
At this point, the tricolor screen is showin the following:
KAIS130
SPL-1.JUMPSPL
CPLD-8
I already got my laptop to recognize my phone, just gave it a reset. I'll update as soon as my phone is over 50% of charge.

i had the same problem with my usb port...
I have just been flashing roms from microSD but I am stuck with radio from hell with no way to change it without usb connection
i also wanted to flash a new spl but have read that it is not recommended to do so from sd card.
not sure if its a hardware or software problem, in either case, it is a problem with the phone, i have tried it on many different computers with many different cables and i also tested my brothers tilt which is detected by each computer immediately.

rcm_rx7 said:
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Click to expand...
Click to collapse
Thanks for your message. The phone is showing olipro (I had flashed it with HardSPL before all this started; I was getting ready to update it to the new HardSPL for WM6.1 ROMs). I've tried a couple of different cables and the usb seems truly gone. I have had problems with it being a bit sensitive in the past, so I think the pins have just shorted at this point.

All else has failed...
GSLEON3 said:
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Click to expand...
Click to collapse
Thanks for the message. There aren't two activesync sessions running on the XP system, and there are none on the phone (as it is stuck in bootloader, there is no way to get to its task manager).
After calling in to ATT and finding a fairly knowledgable tech (Ben, no last name given), it sounds like the original problem was that the mini usb slots has bent pins which caused a short. Somehow, when I removed and re-installed the battery, that short went from preventing a synch to toasting the OS. My first Tilt had a red-light of death on first charge, so I pretty much believe that something in the electronics connecting the usb/charger and battery is delicate on Kaisers.
They're going to send out a warranty replacement tomorrow, and the RMA packaging for returning this unit. I guess I'll just cross my fingers that they don't boot it and notice that it isn't a stock SPL. Given that it's being written up as a hardware issue (as it is), hopefully they won't.

What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!

I think I got it..
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!

Theoretically, yes
rcm_rx7 said:
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
Click to expand...
Click to collapse
I did try flashing the SPL from the microSD, several times and using the stock ATT SPL was one of the choices. It reverted back to tri-color boot mode.
Theoretically, yes, they could demand payment. I've heard of them doing that if a customer said that a unit hadn't been wet, but they found that it had when they did diagnostics. Down from that, they could terminate the warranty or shut off service. Now that T-mobile is getting higher speed, that's not the threat it once was, but still.
The battery is now also empty (since it had no way of charging), so I am hoping they won't even bother.

Glad to hear it!
moos said:
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Click to expand...
Click to collapse
Glad to hear it worked for you! I couldn't get my system even close to that functional to get there, but it's good to know that you were able to get through.

kaiser usb dead
I have the same prblem as your USB is gone cannot move from tricolor screen. Cannot even flash from sd card. Check my signature for the link of my thread it explains everything that happened to it.

hello,
i'm interssested to buy it. can you send me your mail at [email protected]

Here's a tricky problem, need expertise!! Kind of urgent..

I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
The problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it...
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2

By The Way...
I decided to post this in this section as well because it pertains to a problem with Open Touch 5.0 or 5.2 as it is directly related to my problem.

Since you are not hardspl, did you try to go to the bootloader and then flash the original Tmo stock rom from there?

Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10

epicphotoeye said:
Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10
Click to expand...
Click to collapse
Have you tried your regular wing USB?
Sometimes the metal inside the USB varies in number even if they have the same size..

Hi I had the same problem after flashing the phone of a collegue of mine.
After reading forum after forum I found the goldcard method.
It is found here: http://forum.xda-developers.com/showthread.php?t=417930
It is a bit tricky to get it working but eventually it did work. And the phone is up and running again.
good luck..
PM me if you are having problems.

this happened to me.im new at this so i was jus lookin around in the phone and i found that when you install opt 7.5 biggy it changes me from tmobile to at&t and i changed it back and my phone worked with no problems.

Bricked Tornado

Hi. Today as i was flashing my Tornado the power went of.
39% was done when the computer turned off. So now my Tornado only comes to the bootloader and does not connect to the computer.
So am i screwed?

pking said:
Hi. Today as i was flashing my Tornado the power went of.
39% was done when the computer turned off. So now my Tornado only comes to the bootloader and does not connect to the computer.
So am i screwed?
Click to expand...
Click to collapse
It is alright. Don't worry. I had experience similar case earlier. I flash again and it works. So, you try again. I hope, it will be ok. But we better careful not to happen such thing again.

Thanks for calming me down
But the phone doesnt connect to the computer. The small light that shows if the battery is full or not doesnt light up. Termatop or the flashing software doesnt seem to be able to connect to it either.

Charging LED should not be light up,it is normal, but check the screen of handset, when connected to USB it should be in bootloader screen and there should be 'USB' label at left-bottom corner of the screen. In that case you can re-flash the rom. If your battery is bad, you may not be able to enter the bootloader... then you need to find a fully charged battery.
I think there is lots of help arround in this forum for similar situation. So, don't panic there is solution.

thacen said:
... when connected to USB it should be in bootloader screen and there should be 'USB' label at left-bottom corner of the screen. In that case you can re-flash the rom. ...
Click to expand...
Click to collapse
Do you have a link handy for flashing using TeraTerm? I screwed up and didn't fully connect my Cingular 2125 via ActiveSync this evening. I did it with the AudioVox SMT5600 I'm flashing, but got them mixed up and ran the format BINFS command on my Tornado completely forgetting I never let ActiveSync set it up.
All I can find is the guides that refer to using the ROM Update tool via ActiveSync/Windows.
*EDIT*
It worked this morning, not sure how or why... I'm not complaining though!

thacen said:
If your battery is bad, you may not be able to enter the bootloader... then you need to find a fully charged battery.
Click to expand...
Click to collapse
Depends on what you mean by 'battery is bad'. If the battery simply has not enough charge to enter the bootloader and go through all the flashing procedures - there is an alternate way: http://forum.xda-developers.com/showthread.php?t=528258

Help please my Polaris is dead

After installing a new rom ,my polaris died ,no lights not recharging , I removed the battery,the SD and the sim card for > 24hrs and still the usb is not recognised and no lights at all and also not recharging any solution????

Hey.
Im reading u have a problem Polaris not booting up or worse not even working. Well i have the same problem and im also looking for a solution.
My device started to play tricks on me, like shutted down when not needed, freezing, and also when freezing i pressed reset button which did nothing but shut the device down completely (not even charging or booting up again). After many hours later it worked again but still had the same problem.
And well... now... now its totally dead, it stayed off for a day and not even charging nor booting.
Come on guys, some one must have had this problem before and maybe u can tell if its fixable or do i really have a f*cking brick on my table. , and also how can i avoid it if im getting myself another device?

I have the same problem with polaries...
shizny said:
Hey.
Im reading u have a problem Polaris not booting up or worse not even working. Well i have the same problem and im also looking for a solution.
My device started to play tricks on me, like shutted down when not needed, freezing, and also when freezing i pressed reset button which did nothing but shut the device down completely (not even charging or booting up again). After many hours later it worked again but still had the same problem.
And well... now... now its totally dead, it stayed off for a day and not even charging nor booting.
Come on guys, some one must have had this problem before and maybe u can tell if its fixable or do i really have a f*cking brick on my table. , and also how can i avoid it if im getting myself another device?
Click to expand...
Click to collapse
Please anybody help me.. Its pain for me. the phone is not opening. What I do now...

Check if your battery is not dead(voltmeter i guess), also what ROM/radio did you tried to install, also did installation completed successfully?
Don't want to make assumptions, but i think it's terminally dead(mobo fried?)

Thanks for your advice...
I checked my battery with voltmeter, it shows ok..
I installed the Salvy.C.83_Megan_v1.4_WWE_Polaris_EzInput_2.1 ROM and it was successfully installed, but after 1 day it is fully not opening, not responding...
What should I do......
Please help..

retsam88 said:
Check if your battery is not dead(voltmeter i guess), also what ROM/radio did you tried to install, also did installation completed successfully?
Don't want to make assumptions, but i think it's terminally dead(mobo fried?)
Click to expand...
Click to collapse
Thanks for your advice...
I checked my battery with voltmeter, it shows ok..
I installed the Salvy.C.83_Megan_v1.4_WWE_Polaris_EzInput_2.1 ROM and it was successfully installed, but after 1 day it is fully not opening, not responding...
What should I do......
Please help..

Could be the nand failing have a look using mtty to see if you have any bad sectors.
Disable usb connections in wmdc or active sync.
Put the phone into bootloader screen.
open mtty Connect mtty to you usb port.
Type info 8 to check for bad sectors.

meknb said:
Could be the nand failing have a look using mtty to see if you have any bad sectors.
Disable usb connections in wmdc or active sync.
Put the phone into bootloader screen.
open mtty Connect mtty to you usb port.
Type info 8 to check for bad sectors.
Click to expand...
Click to collapse
Thanks for advice..
But my polaries is not powering on
So what I do....???

I have the same issue, my polaris if connected to usb doesn't light orange, can't go in bootloader anymore and mtty seems to not been able to issue any command to the device.
As you know, is there a way to flash an hard spl via mtty? Or another way to flash it on my "seems bricked" device?
As for info, i was using the same rom as you, but mine was working great!
And now seems dead... my invincible polaris...
Please, anyone help us?
Thanks!
Sent from my Liquid using XDA App

Bump....
Anyone can help us?
Sent from my Liquid using XDA App

I have the same problem, my Cruise is dead.
Yesterday was OK, its functions run perfectly.....Today morning it's turned off
Orange light flash, after 20-30 seconds it turned off and Cruise became hot.
I don't know what's happen.....someone has any idea ?
Thanks in advance.

[Q] MAGLDR: Lack of USB battery Charge or Bootloader USB connection Fail?

Hi,
do you have the following problem?
Has your battery stopped charging by usb?
CAN access SD card from MAGLDR via USB to transfer files between computer and phone?
CANNOT access SD card from android via USB to transfer files between computer and phone?
CAN install roms via magldr?
The boot-loader screen only shows serial but Fails to connect via USB? as a consequence you cannot remove magldr or even update it
wondering why only magldr has access to USB?
please join me in a pursuit to find a solution and if you have it please share it with us
I use HTC HD2 LEO 1024, i have been forced to buy an external battery charger, my phone has magldr 1.11, my wive's is magldr 1.13 and both of them cannot charge via usb.

I found something related but didnt offer a solution since the uSB connection problem happened after upgrading to a new magldr
http://forum.xda-developers.com/showthread.php?t=905570

To answer some questions about battery charging whilst flashing in MAGDLR etc...
If you're anything like me, new to Android flashing and got into MAGLDR and CWM like a kid with a new toy... You may have completely knacked out your battery!
I've just bought an HTC HD2 and done just that!
This did my nut for approx 12 hrs lol, yeah it ran plugged in but everytime I took power cord or USB out it popped it's coggs! This concerned me in several ways, as I've been flashing for years and always heard flashing with lower than 50% battery was a VERY bad thing to do, so I was very hesitant in doing this, also there seemed no way to charge as every time I connected the charger it would reboot into MAGDLR 1.13.
With more read up on Hard SPL I thought it more likely it would be OK to screw about as from what I've read it's VERY VERY hard to brick an HD2.... BTW yeah I read all you experts 'READ' posts but none of you actually said it in 'plain English'!!
If your battery runs out whilst screwing about installing different Android builds and/Or playing with MAGLDR and CWM bits and bobs then don't worry.
Connect to comp, then goto the Rainbow screen (reboot with Vol Down button held down)
Find install of MAGDLR 1.10 (http://forum.xda-developers.com/showthread.php?t=893618) - install using RUU in the download.
When your phone reboots it will boot into MAGDLR 1.10, GOTO PowerDown, (last on list.) Power down and your phone will start to charge!! - Hallelujah!!!
Once you have full battery charge, reinstall latest MAGLDR 1.13 atm, and in future be quicker installing your Android OS LOL!! xx
Hope helps some people, if i'd had this post here I would have saved a LOT of time lmao!
D.

Thanks a lot! This saved me having to go and purchase a docking station to charge my HD2.
Thats what i get for attempting to change my ROM with 10% battery!!!!
WONT DO THAT AGAIN!!!!!

ocmtom said:
Thanks a lot! This saved me having to go and purchase a docking station to charge my HD2.
Thats what i get for attempting to change my ROM with 10% battery!!!!
WONT DO THAT AGAIN!!!!!
Click to expand...
Click to collapse
Glad to be of help mate & thanks for saying 'thanks'!

It's Working ..........
:good:
magicianhumphrey said:
If you're anything like me, new to Android flashing and got into MAGLDR and CWM like a kid with a new toy... You may have completely knacked out your battery!
I've just bought an HTC HD2 and done just that!
This did my nut for approx 12 hrs lol, yeah it ran plugged in but everytime I took power cord or USB out it popped it's coggs! This concerned me in several ways, as I've been flashing for years and always heard flashing with lower than 50% battery was a VERY bad thing to do, so I was very hesitant in doing this, also there seemed no way to charge as every time I connected the charger it would reboot into MAGDLR 1.13.
With more read up on Hard SPL I thought it more likely it would be OK to screw about as from what I've read it's VERY VERY hard to brick an HD2.... BTW yeah I read all you experts 'READ' posts but none of you actually said it in 'plain English'!!
If your battery runs out whilst screwing about installing different Android builds and/Or playing with MAGLDR and CWM bits and bobs then don't worry.
Connect to comp, then goto the Rainbow screen (reboot with Vol Down button held down)
Find install of MAGDLR 1.10 (http://forum.xda-developers.com/showthread.php?t=893618) - install using RUU in the download.
When your phone reboots it will boot into MAGDLR 1.10, GOTO PowerDown, (last on list.) Power down and your phone will start to charge!! - Hallelujah!!!
Once you have full battery charge, reinstall latest MAGLDR 1.13 atm, and in future be quicker installing your Android OS LOL!! xx
Hope helps some people, if i'd had this post here I would have saved a LOT of time lmao!
D.
Click to expand...
Click to collapse