Hi,
I have a huge problem.. I just wanted to install a new ROM on my MDA Vario
and during the update process I accidentaly knocked the phone of my desk.
Causing the USB to unplug and crash the update.
The Vario now stops booting @ the red, green and blue screen..
Hard reset didn't work and Windows won't recognize the phone when I plug in the USB cord..
Eerrrr.. HELP!
Can I fix this? If yes; HOW?!
The red/green/blue screen is a good sign, when you plug in your USB cable, you should see a USB icon on the bottom of your Wizard's screen. At this point, run the RUU for the ROM again from your PC. This re-flashing should fix it.
If the icon doesn't appear, check to see that the fall didn't break the phone's USB connector. If it did, send it for repair.
The next step would be to reboot your PC, and remove the battery from your phone for 5 minutes or so. Then try to reconnect again, and see if that works (To display the aforementioned icon).
Good luck!
omg dude..
I could kiss you right now.. Before your reply, I tried the same thing already (without the reboot) but that didn't work..
The USB icon did show up on my Wizard's screen, but Windows didn't recognize a USB device, so there was no
way of re-running the RUU to continue/retry the upgrade..
Obviously Windows had a lot of 'update' programs still running in memory..
And I couldn't 'kill' them.. So I reboot my PC, plug in the USB connector and YES! it's updating!!
The phone didn't fall on the USB connector.. It sort of bungee-jumped of my desk
Phew.. man I'm reliefed You just made my day!
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
So am I gumbydude.. So am I..
I'm sorry to hear your phone is bricked beyond repair..
But isn't it possible for Cingular to fix your bricked one?
They caused the problem in the first place, they didn't inform you in any way that the ROM was for G3 phones..
I wouldn't agree to use a refurbished, sticky G3 phone if it's their fault you bricked your brand new G4b in the first place..
gumbydude said:
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
Click to expand...
Click to collapse
First, if you get the RGB Screen that is the bootloader so your phone IS NOT BRICKED!
Second, the Cingular 2.25 Rom works with both G3 & G4 devices, it contains two complete bootloaders.
Third, you do not need to CID Unlock your device to flash an official Cingular Rom onto a Cingular 8125/8100.
Fourth, you should return the replacement device telling Cingular Returns that it is not in acceptable condition.
Fifth, download the Cingular 2.25 Rom from here: http://www.htcamerica.net/support/8125/software-downloads.html
Well, my problem is kind of similar, so I won't post a new threead, but write in this one instead.
So, what's the story... I upgraded my G3 Wizard to PDAVIET's v4 WM6 ROM and it worked like a charm. Changed the default boot logo with a custom one and after a while I tried to flash again with the same ROM (because I had restored backup from Windows Mobile 5 and had been experiencing a few bugs; however, I had done hard reset before this flashing) - it stuck at 2%; I waited 10 minutes and reset the device, saw the bootloader, pluged the USB and started the flasher - It didn't see my phone is connected to the computer. It turned out that when I plug the USB cable, the device hangs, so if I pull it out, it won't give any indication and the display will still read "USB". So, there is no way to access my phone and reflash it, nevertheless it can go in bootloader mode (however, no LED or keys are flashing) - it will just hang upon connecting the USB cable... Tried to remove the battery for a while and it still hangs just the same way...
Does anyone think there is a way to repair the device and what advice would give me to try to work the problem out?
Related
I have just been trying to upgrade my Wizard, I have done this many times before, I tried but failed with a few ROM's and last I tried Molski's latest, now, it is just dead, after I try a hard reset, I get the red blue green screen for a few seconds, I even see it connecting to the USB and then the screen just goes black.
Pleas help with anything
Sounds to me you're battery could be empty/dead
It was full last night, so I do not think this is the problem
It was full last night, so I do not think this is the problem
Try another battery and see.
And keep us posted
I agree, it sounds like your battery is drained. And since it goes to the boot loader, that means your battery will not charge on your phone. You'll have to borrow a battery that is charged, or get someone to charge your battery.
azmerlin said:
It was full last night, so I do not think this is the problem
Click to expand...
Click to collapse
What state did you leave the phone in over night? Was the battery removed, or was the phone fully off..?
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
lingley said:
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
Click to expand...
Click to collapse
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Bricked
If install IPL 3.08 in G4, exist solution or not
One thing to add : if the battery is really low, then it will likely not charge or respond via USB. It is necessary to use the wall charger in this case. It must have something to do with the amount of charging current that can be delivered to a flat battery.
luisprieto said:
If install IPL 3.08 in G4, exist solution or not
Click to expand...
Click to collapse
I'm not sure if you are asking a question or what. But if you try to install IPL/SPL 3.08 on a G4 device, your device will be bricked (ie: dead). I did see where someone in the Wizard forum said they were able to do a JTAG recovery and get their G4 back.
mfrazzz said:
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Click to expand...
Click to collapse
You are right, sorry.
I used to have Aserg3.12 Rom on my device (G4). It worked well for at least two months. Suddenly the phone crashed in the middle of a call and didnt react anymore. Hard Reset nothing worked.
I got somehow the Boot Loader Screen back and downgraded to the original rom (QTEK novid, 220734, 2207114). Problem was whilst it finished the upload process until 100% and restarted the phone, it got stuck at the OS loading page. After 1 minute the screen started losing its colour and turned white. If I soft or hard reset the same happens, it turns white at the OS loading page.
At some point I got through miraculously, it started up and everything was fine. I charged it, upgraded to smart1 wm6 v2 and everything seemed to work. However again some 10 minutes into a call, the phone crashed and back to square one. Downgrade to old rom, got again stuck at OS loading screen etc.
I then put it over night on the charger. The orange charging LED was blinking in 5-10 sec intervals. In the morning it was red. I started the phone again interestingly got through and got it running. Battery was fully charged. But again: 10 min into a call, the phone crashed. And trying to reboot I get to the OS loading screen, then it turns white. I put it back on the charger LED is blinking, guess I have to wait again for some hours.
Thanks for any help or suggestion,
forgot that:
IPL 2.15.0001
SPL 2.20.0001
Aserg3.12? smart1 wm6? Are you sure you've got a wizard? Aren't those prophet roms?
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
akashastrega said:
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
Click to expand...
Click to collapse
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
peter petrelli said:
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
Click to expand...
Click to collapse
I had at least 80 percent battery. I cannot get into the tri-color screen. Tried holding camera and soft reset, tried comm, camera, power, tried talking sweet to it...it just goes to splash screen each time. HELP!!!
This is a G3 wiza200 IPL/SPL 2.26 and it IS unlocked.
Thanks in advance
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
peter petrelli said:
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
Click to expand...
Click to collapse
Yeah, I know...in theory it SHOULD, it's not, hence the freaking out. I am attempting to charge it on the main plug, but it begins to charge then dies. I did have a loose usb port, which I thought got fixed, as my phone charged fine last night, and sync'd fine today. I'm not a pro, but not a noob either...so I am getting frustrated because trying the things I do know, aren't producing the results they should.
**The splash screen is one I made, independent of an OS...after any rom change, I flash my custom splash screen...it has always worked...however, it is making me think that it is the ONLY thing on the MDA, and any signs of a rom were somehow killed by my kids flashing the phone with a very incomplete kitchen rom.**
I will try again. Any help that can be offered would be MUCH appreciated.
PS---I LOVE Heroes!!
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
peter petrelli said:
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
Click to expand...
Click to collapse
I can get brief and random orange lights (my phone was not 100% but at least 80% when I first began)...it takes a lot of sweet talking though to get it to connect to charge. I tried a backup battery as well. Pushing the camera and soft reset either produces my custom splash, or nothing at all (no boot whatsoever). I am truly stumped.
EDIT
I am not aware of the SD card method. I do have an SD, but if I need a special program, I do not have it.
The fact that no light remains on when you connect usb or mains plug makes me think that the usb socket is loose again. In which case I'm doubtful that you can flash via bootloader mode.
The fact that you cant get into bootoader mode suggests that it was somehow corrupted when the flashing process was interrupted. This could be unrecoverable.
From here I'd suggest you investigate the sd card method. I've never relied on this method so this is uncharted territory for both of us.
Read this thread here and here. I think we're running out of options...
Semi success, I got into the quad colored boot (white bottom)...but cannot get it to recognize the usb. I am getting an error message about an unrecognized device, so I will try to fix active sync first...any suggestions for me now that I am at least in a bootloader screen
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
peter petrelli said:
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
Click to expand...
Click to collapse
it shows usb in the corner, however it is not producing any charging light, nor does my pc recognize the usb. So...I don't know if this will matter, but as I said...I have the RGB + white bootscreen with usb in the corner...is there still a chance????
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
peter petrelli said:
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
Click to expand...
Click to collapse
wcescomm.exe is NOT showing in Task Mgr...I will try to flash anyway. I killed the firewall and the sd had been removed already. Any other suggestions??
EDIT
ruu error 260 update error
It cannot connect, please check to make sure it is cradled blah blah blah
Thats ok. I forgot that the previous flashing attempts would have killed it off anyway.
So I get ruu error 260
I have rebooted my pc, deleted any connections in active sync (leaving only guest)...
UgggH
It is NOT recognizing the usb
the usb port is as tight today as it was last night after my hubby repaired it...I'm backed to stumped
EDIT**
I had to reboot MDA, now I have lost the little corner usb...but I still have the quad bootscreen
This is progress at least, 1 hour ago we didnt even have bootloader mode. Perhaps you could try flashing another rom, but I think if error 260 keeps appearing then something is wrong with the USB socket.
somehow i lost bootloader again...
this is driving me insane!!!
am trying again, will update momentarily.
************EDIT*****************
Finally got it back into bootloader, but it will not read the usb. keep getting that stupid error message that it doesn't recognize the device, and if I try to flash it with a stock rom, I get error 260.
I have closed the wcescomm.exe
I have killed my firewall
I have rebooted my phone, my pc...everything a few times
I have deleted any connections in active sync
I have unticked allow usb in active sync
WHAT AM I MISSING???
The usb port on the phone does not feel loose again...could it have got fried somehow? I feel as if I can get the damned usb to be recognized, I can save my precious MDA.
Please...any other suggestions, brainstorms, whatever???
THANK YOU
I had a little problem with theloons kitchen doing the same thing to me last week where it would give me the 260 error. I'll upload a ROM flashing file for you to try. Probably the best thing to do right now would be to take the nk.nbf file from an official ROM and stick it in this file and then run the RUU in it. After that you should be ok again to try your luck at cooking with theloons kitchen again although you may want to wait 'til the kids are at school or something before you try it.
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
mestrini said:
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
Click to expand...
Click to collapse
absolutely right while in bootloader mode it wont charge,but to charge or verify status of usb connectivity,while in bootloader mode push power off button,it'll go in sleep mode but lights will show charging if usb cable is charging
usb cable might be charging but mini usb port of the phone has many connectors I think 9 connectors,I'm not sure,may be the connector for making connectivity relation with phone and pc is damaged.
try with another usb cable if possible,if the connectivity with usb is established than method in the link provided by 'mestrini' is a good option,good luck
It had been going so well, until 9 months later...today. This morning I noticed my battery low (12%), and I thought I'd charge it when I got to work. However it never made it to work - when I went to charge it the back light was on and it was frozen. Thought nothing of it, plugged in the charger, hit the reset button and... nothing. So battery out, back in - press the power light and all I get is the solid green light, no screen, no activity, nothing.
The charging light isn't on either when it is charging, yet the battery shows good charge (tried it on a friends). I'm guessing it's dead, any other takers? I'll ring Vodafone tomorrow, but I'm running with a Duty rom. Hopefully as it looks terminal it should be ok, fingers crossed??
Same thing happened to me just now. WTF? I didn't even do anything. Just totally dead with green light only on. I've tried everything. Pull battery, connect USB, charger, took out SIM, took out memory card, even tried with another new battery, nothing at all. and I just got this phone as replacement last week.
You are stuck in OEMSBL. I can help, but it will be later or tomorrow.
Tell me your ROM, SPL Version, Radio Version, & device model number as well as typey, i.e. Tilt, TYTNII, etc...
HMMMM seems we have a new problem here
Hi Guys
Guess this is now new problem with tytn ii had my phone repaired a couple of weeks ago. technician said something about 3 bad block in the CE was responsible for the TRI color boot screen i used to get.
He said that he formated the phone and reloaded all "firmware".
Prior to sending it in i had Confused Stu Vista Mobile 1.3 running on the phone. Also had OLIPRO 1.0 as the sspl
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
GSLEO3 you and JockeyW are "GOD'S" when it comes to these issues.
Please grace me with your knowledge.
Running Confused Stu Vista Mobile 1.3
Radio 1.65.14.06
wolffie02 said:
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
Click to expand...
Click to collapse
why did you even try frankenkaiser? you only need to use it if you have no SPL (and only if you have the radio from hell).
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program as frankenkaiser is currently only compiled for specific radio versions.
Sorta Dead with solid green light
I am in the same boat ... I mistakenly flashed a non-Kaiser radio ( 1.65.28.25 ) and then thought I was reading a Kaiser page about ho to fix it and I ran a `2a`. Ooops on me.
I cannot get tricolor bootloader ... tried hard-reset ( two soft keys and reset ), and Camera-reset, but nothing is working.
What does work:
-bong when connected to PC
-mtty connects - but no `CMD>` prompt.
-able to issue `setboot` - and get back "ARM9BootMode:1".
I've read all the posts and it seems like without the bootloader, I am stuck.
This is an ATT Tilt/8925.
Any and ALL suggestions much appreciated.
seems i have such a problem
the kaiser shows only solid green led. nothing else
doesnt enter tricolor
when i plug it to usb, device manager shows first Qualcomm device and then finds several new devices such as Data Interface
device is AT&T Tilt 8925, original rom version, radio and spl are unknown
who can help me?
cmonex said:
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program
Click to expand...
Click to collapse
what program?
Tried to flash button rom with full battery. Comunication error. Only boots to 3 color bars. Every time I retry the flash the phone starts flashing on and off.
Mmmmmm
What is the problem....?
Does your wizard dont begins... so it wont wake up... dont start ?
You cant turn it on?
What do you mean with turn on and off?
is blinking?
If the problem is its blinking and dont stands on... it is a serios problem but if the wizard saty on ... what ipls and spl got?
What did you do?
Men we need to much info..... than it is on bootloader, i cant upgrade etc etc etc.
FUUUUUUU******@@@@@
while flashing the button rom, i got a communication error. At random times after connecting the phone via usb the screen flashes on an off and communication is lost. sometimes the phone gets mostly through the flash, sometimes it wont even start to flash. But here is the f-ing kicker, while trying to recover in the button flasher proggie, my computer locked up and WILL NOT TOUR BACK ON. thats right, i lost my phone and computer in 5 minutes thanks to this flasding sh*t. i am only able to access this forum via a blackjack II smartphone.
OK, Feeling better
Sorry about that.
I got my computer back on.
It wouldnt even go to cmos so I traded out my cpu, still didnt work.
Put the old cpu back in and it booted just fine. Not sure why that happened but at least my computer is back on.
Ok so back to the phone. It boots to the 3 color bar screen and shows IPL/SPL as 2.25. After connecting the USB cable it will sometimes start flashing, not always. If I restart the button rom flasher it will start to flash, after getting to some % the phone starts flashing.
By flashing I mean the screen flashes on and off. Likely the phone is rebooting itself constantly.
Undo?
Is it possible to just undo what ive done? Is the old info still on the phone? IPL/SPL are still the same as before.
No, your old info is not on the phone anymore. The first thing that is done when the flashing process begins is deletion of your flash on your phone. This may seem like a n00b question, but have you tried using a different USB port? DO NOT flash with a port off of a hub, they are usually under powered when compared to direct board connected ports. Try one on the back of your tower(or directly in your notebook whatver.) and see if that works.
It also failed on the back usb port.
All is not lost is it?
I believe that this phone might need a new battery.
I had some problems with the phone turning off when it wasn't supposed to but it hasn't done it in a long time so I though I was ok. Do you think that a new battery might allow this downgrade to complete?
Its possible. The Wizard is kind of a tempermental device....it flashes when it wants to some time. You can try and see if a new battery is what fixes the problem, but in all honesty, it could be anything.
Xtrange
ok
try to get connecte with that cable other device, maybe is broken the cable...
try another usb port...
download again the button rom, maybe is corrupted.
lets wait what happen
Its your battery , replace the battery and it will charge and then you can flash it,you can get two batteries for a tenner on ebay
Battery
OK, so once the new battery comes, it will charge via usb and wall charger just as it would with the OS installed? Im not sure if charging is dependent on the OS at all.
Thanks for all of your help guys.
Does it charge?
It charges??????
in bootloader dont charge men....
if the phone stuckson welcome screen maybe charges, on htc logo dont, neither on splash screen.
All we do is try to help people to upgrade and try to found solutions for those who made a bad upgrade, but i didn't cook, and dont develop anything so my only contribution is for experiences.
Hope your wizard revives.
My wizard does not bootup...only three color bars
I was trying to flush with new ROM and it stopped after 100% and in the mean times, my system rebooted. Now I got this MDA with three color bars, battery is OK but important thing is that it does not connect to computer thru Active Sync............any help>
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know
Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt
Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.
Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.
awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok
Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse
I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.
heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.
hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.