ATT Tilt Dropped on Floor, Dead ? - Tilt, TyTN II, MDA Vario III General

Hi,
I dropped my ATT tilt on floor 3 days back. Initially I was able to start-up mobile, but it used to reboot again giving me pop sound before rebooting. I also observed a '?' on battery status and noticed me of low battery before rebooting.
I recharged my battery using my bro's HTC. I also tried recharging with AA batteries. Yesterday the phone was completely dead. I was only able to see bootloader.
With the help of info available from different posts I tried to flash my mobile(-ATT_Tilt-RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship). I was successful to upgrade my ROM.
However, once the mobile boots...it shows me Windows Mobile 6.1 with a notice " The device is clearing storage please wait..." and the red light blinking...then after few seconds it gives a pop sound and starts rebooting.
Here are the weird things I noticed.
-I was able to flash my mobile without HSPL.
-WDMC doesn't recognize my device.
-Whenever I connect my mobile to charge/USB it gets stuck at the ATT start up screen with orange light indicating battery is charging. I'm able to see my start up screen only if I disconnect from charger/USB and power on.
Now I'm not able to flash again. Help needed !
My device Info on boot loader :
KAIS1*0
SPL-3.56.0000
CPLD-8
I'm able to see USB on bootloader when I connect to USB.
Thanks in Advance !

Help Please

Hardware damage calls for a hardware solution
If the problem started since you dropped it on the floor then that indicates some physical damage to the device (perhaps internally where you cant see). No amount of ROM flashing or hard resetting will cure this, whats required is a visit to the HTC repair centre/knowledgable phone repair shop. They'll be able to inspect/test the device, come up with a solution and quote to fix it. There are many possibilities as to whats gone wrong and the only way to be sure is to have an expert check it out in person.

Related

Holy shizznits, cannot enter bootloader, HELP

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

Dead with solid green light

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?

Color Bars Help Please

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>

[PROMBLEM] Diamond stuck in restart loop.

I believe my battery ran dead and i didnt notice, now my when you press the power button the blue o2 loading screen comes on then about 2 seconds later the device restarts and same thing over and over.
If i plug a an ac adpater in (i've tried 2 and an incar charger) the light ring goes up twice then then phone triggers a start up and gets stuck in the loop. I've tried leaving it in this loop for 10mins see if it would charge the battery but no luck.
I have tried doing a hard-reset 3 times now it says its done ok soon as i press vol up to boot it goes into the loop.
Is there anyway i can charge the battery if this is the case or is there another problem thats causing this?
Any help would be appreciated.
Are you sure the battery is dead?
If you left it in the loop for 10 mins I would have thought that it would flatten it such that it doesn't light up at all.
I know the battery was very low before it started doing this and i hadnt installed anything new in months.
Usualy on the o2 screen it shows red writing at the top and bottom, its not showing that right now if that means anything.
Its a stock o2 uk rom with no changes to the radio and official battery.
I've just installed the latest rom from the o2 website (keeping it stock incase i need to send it off to them) and still doing the reboot on startup thing.
Contacted o2 see what they say but if anyone else has any ideas im open to suggestions
i've got the same issue and the battery won't charge ...i suppose it could be a battery issue, but i'd be sure about it prior to buy a new battery..
Battery was fine, i sent the phone to the o2 repair centre got it back week later fixed
SMeK said:
Battery was fine, i sent the phone to the o2 repair centre got it back week later fixed
Click to expand...
Click to collapse
did you use a modified rom? ..i was told htc repairs only unmodified products, could you gimme more information about it?
No it was not a modified rom, default o2 xda ignito rom.
Me too!
I had the same issue. I tried soft-resets, hard-reset, swapping batteries with another phone (even tried warming the battery in my hands which was suggested somewhere!), reflashing a couple of different ROM's, including Shaks 4.30 and the latest Telstra ROM (2.07.841.2 WWE). I tried using MTTY to reflash the ROM, and reflashing using the DiamonCustomRUU.exe from the PC. (OliNex 1.40 SPL). All of the reflashes were in Bootloader mode (hold pwr and vol down) because I couldn't get it to the point of ActiveSync connection.
Nothing would work.
The winning step that bought me the joy (and relief) I was looking for was downgrading the radio from 1.09.25.23 to 1.00.25.05.
Also, I'm not sure if it is related, but I think the reset button under the stylus is stuffed because pressing it doesn't do anything.
Now I've escaped the reboot loop from hell, I'll run it for a few days before giving it back to my boss! If anyone's interested, I'll update you in a few days.
HD.
could you please tell me how you installed the radio, because when I use diamoncotumruu it stays at 0% and the finaly gives an error
yves_the_man said:
could you please tell me how you installed the radio, because when I use diamoncotumruu it stays at 0% and the finaly gives an error
Click to expand...
Click to collapse
I had to install the radio in Bootloader mode (hold pwr and vol down), but there was no issue with the install after doing this. Have you checked this thread? I don't know if that thread will help you fix your issue but it might be worth a look.
What exactly was the error message? Perhaps a search on that error message will help you.
HD.
I've tried it in bootloader mode, but it won't install...
the error number is 262. but that should be an active sync problem but I can't sync so I don't know what the problemm is
Not really on topic, but...
yves_the_man said:
I've tried it in bootloader mode, but it won't install...
the error number is 262. but that should be an active sync problem but I can't sync so I don't know what the problemm is
Click to expand...
Click to collapse
262 isn't an necessarily an ActiveSync problem, more of a connection problem. Try post 9 here. Or try uninstalling Active Sync altogether and installing radio and ROM via MTTY. Since it is a connection problem, you could even try a different USB cable.
But I suggest you post 262 queries here, here, here or here.
BTW, Are you using XP?
HD.

O2 XdaIIS Dead while Upgrading

Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT
Milesht said:
Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT
Click to expand...
Click to collapse
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")
No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help
in that case you should remove the battery and charge it in the back of the cradle (needs AC power supply, usb alone doesn't work). it might also show red at first, meaning the battery is completely dead now, but shortly after that, it will turn orange. if, during the charging process, it should turn red again, your battery is probably broken. maybe the battery dying was the reason your upgrade failed in the first place. i had a similar issue when i first tried upgrading in vista several years ago (before i came here). i removed the device from the cradle and it was still in bootloader mode. normally you should let the device stay in bootloader mode and just start flashing again. i didn't do it and neither did you, so all you can do is try everything to get it into bootloader mode again.
try everything you can do with the device at the moment:
- insert the battery, try bootloader
- reset, try bootloader
- power+reset, try bootloader
- battery out, battery in again...
eventually you will get the device back into bootloader mode and can try flashing it again. but before the next attempt to flash it, you should find out, what caused the error in your last upgrade to make sure, it does not happen again.
Milesht said:
No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help
Click to expand...
Click to collapse
Chef is correct. The battery will not charge if it is on the device. Luckily for us, the BA cradle has the charging slot in the back for the "extra" battery. I would (regardless if it is dead or not) just buy a new battery on e-bay (they are dirt cheap nowadays) simply to rule out the possibility of the battery being dead, which as chef suggested might be the reason for the failure (especially if you cannot turn on the device).
Tony,
It worked lot of thanks.
1.Removed battery charged it.
2.Done hard reset(power+softreset)
3.Tried bootloader.IT WORKED .....
4.Flashed it with old stable wm6.1 rom.
IInd case.Finding the root cause.
After flashing I put that back again to the cradle.Then problem began BA went OFF.
Then I softreset and put again to the cradle before OS boots up Tried 3 times same result to make sure its cradle prob.
I take out frm the cradle
softreset the BA to boot.Now another problem.ITS not booting it reaches the FOUR COLOR SCREEN WITH RoM DETAILS then it FADES OUT with some markings(horizintal lines) here and there.
I waited for few minutes removed battery.Put it again then pressed power button got same results.
On the second attempt while locking the battery switch (pressing it up) That old RED LIGHT glows up.Then I pressed it down to unlock and removed battery.Then I tried again
This time it boots up and everything came to normal.(My HEART BEAT WENT DOWN) Thanked GOD.. And ofcourse you Tony.
Meanwhile I had given a small blow at the cradle and put my sweet Angel to cradle its working fine Now.
SO AM NOT SURE WHO IS THE real CULPRIT.. Battery,battery switch,or cradle?..
egzthunder,
I think battery is ok because I am getting the same backup just it was before..
So big THANKS to u two of you.
( I write this post frm my BA ) ;-)
Regards
Milesh James
egzthunder1 said:
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")
Click to expand...
Click to collapse
Hello,
I am facing the same problem on my xda iis showed on the screen only " Serial/USB v2.06"
I am really appreciated if you and someone can help me to solve the problem.
Many thanks for your kindness.
please don't double post, there was really no need to bump the other thread, since it is incredibly outdated and not helpful at all. being stuck at the serial v2.07 screen, the bootloader, you should try starting over from the very beginning, using the guide in my signature (if you are a windows xp user).

Categories

Resources