Related
Dear Gurus ...
I need help. During the upgrading process, the connection was disconnected and my XDAII is currently not showing any sign of life.
I ran through the forum, and tries a lot of stuff:
1) try to reset it to bootloader (pwr+joy+reset) - nothing
2) change USB port - nothing
3) setting in MsActiveSync - nothing
There is no display on the screen right now. Even if I put it in to charge there is nothing, no flashing blue led etc ... just dead ....
One thing I noticed is that after removing the battery, and putting it into the cradle, there is a red led light up.
Currently I ran out of options and can only think off taking out the battery for the XDAII to drain completely (not sure if this could help me get into the bootloader mode).
Any one out there who has any bright ideas? Pls help as I am desperate to fix my XDAII .... thanks ....
alvinlim28 said:
Dear Gurus ...
I need help. During the upgrading process, the connection was disconnected and my XDAII is currently not showing any sign of life.
I ran through the forum, and tries a lot of stuff:
1) try to reset it to bootloader (pwr+joy+reset) - nothing
2) change USB port - nothing
3) setting in MsActiveSync - nothing
There is no display on the screen right now. Even if I put it in to charge there is nothing, no flashing blue led etc ... just dead ....
One thing I noticed is that after removing the battery, and putting it into the cradle, there is a red led light up.
Currently I ran out of options and can only think off taking out the battery for the XDAII to drain completely (not sure if this could help me get into the bootloader mode).
Any one out there who has any bright ideas? Pls help as I am desperate to fix my XDAII .... thanks ....
Click to expand...
Click to collapse
I had the same problem but I didn't loose hope. I kept on resetting it until I was able to get into the bootloader mode. It was black with some writings "SERIAL 1.06". When I put it back on cradle, Serial changed into USB 1.06. Tried to do the upgrade over and over again but didn't work. I put AC Adapter to my cradle and hard reset my unit, put back to the cradle, started the upgrade again and it worked. :wink:
twinkle said:
I had the same problem but I didn't loose hope. I kept on resetting it until I was able to get into the bootloader mode. It was black with some writings "SERIAL 1.06". When I put it back on cradle, Serial changed into USB 1.06. Tried to do the upgrade over and over again but didn't work. I put AC Adapter to my cradle and hard reset my unit, put back to the cradle, started the upgrade again and it worked. :wink:
Click to expand...
Click to collapse
Thanks!! I tried hard reset after 30mins with the battery out, nothing works. After I out in the AC adapter for 5 mins and tried a couple of times of hard reset, the screen came out with "Serial" !!!
YAHOOooo ... now I'm in the middle of uploading the ROM back ... thanks twinkle .... that just saved my day ..
alvinlim28 said:
twinkle said:
Thanks!! I tried hard reset after 30mins with the battery out, nothing works. After I out in the AC adapter for 5 mins and tried a couple of times of hard reset, the screen came out with "Serial" !!!
YAHOOooo ... now I'm in the middle of uploading the ROM back ... thanks twinkle .... that just saved my day ..
Click to expand...
Click to collapse
No problem... have fun! 8)
Click to expand...
Click to collapse
plz give me te steps coz i had the same problem, what do i have to do???!!
red LED when plug it to carger without battery........... plz
Same problem
@NightmarE
I have exactly the same problem!
If you find solution please PM
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
adad said:
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
Click to expand...
Click to collapse
There are several Golden Rules when upgrading - not just to SE, but any upgrade.
Always make sure the cradle is attached directly to a USB port on the PC and not through a hub.
Always make sure the power supply is connected to the cradle.
Disable USB in Activesync connection settings.
Disable any screensavers
If an error does occur, putting your device into bootloader mode and restarting the upgrade often proceeds OK.
Bootloader mode can be a little tricky to obtain as the multi-directional button has to be pressed directly down in the middle - not tilted up, tilted down, tilted left or tilted right, at the same time as pressing the power button and the reset switch.
It is very easy to assume bootloader is not working when it may just take several attempts before you get it right.
adad said:
So many people have their XDA II gone dead while upgrading to the second edition rom. What went wrong during the process ?
Click to expand...
Click to collapse
My qtek2020 dead because it's my mistake I upgrade it to SE correctly but with Chinese Version and before DCS post his ROM when I saw it's working better than my PDA2K I try to flash my qtek2020 with the PDA2K ROM ( I make some HEX editing ) but with no luck my qtek2020 is totally dead
Any body have solution !
How I recover from my dead XDA II ..
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
How to upgrade my BOOOTLOADER VERSION (it shows USB 1.01)
Is there a way to change my bootloader version from USB 1.01 to 1.06? I'm currently using T-Mobile MDA-II.
Thanks beforehand!
I have a big problem: this summer i dropped my MDA2 on a concrete floor and i broke the power button so I cant make anything but soft reset, or to remove the battery for 30 min for hard reset.
Re: How I recover from my dead XDA II ..
alvinlim28 said:
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
Click to expand...
Click to collapse
I'm trying and trying to hard reset it I can't see the bootloader, I discharged the backup batt already. Can you help here or is there any other suggestion?
Ps: If I remove the battery and plug the Ac.Adpt I can see here the red light , but if I put back the battery there won't be red light , is that normal ?
Bum pp
Sanity saved
Thanx to dcs i was able to get my device working again.
During upgrade (wich was also possible due to time and effort by DCS) my laptop went into standby for unknown reason.
So my xda got stuck in T-Mobile bootscreen
It was this thread and especially the posting by dcs wich saved my ass (and xda)
for i did not know about the reset with third button to get into bootloader.
Now i finally upgraded to 2003SE.
Thanx DCS!!
hello ,
i have the same problem.. somebody can help me or us??
thanks !!
qtek 2020 dead
i tried upgrading the 2020 to the diamond v1.2 but in the middle of it, the pc based application said that it isn't designed for my version of the phone and now i cant get out of the bootloader mode can any1 help me with it i have the original 1.66 rom from the qtek site but the problem is that it too requires activesync to be started initially ... how do i get outta this mess cuz the hemaupdate and the update utility i got from the qtek site requires the phone to be synchronized using activesync first... can any1 help me with it i need help urgently ....
upup... if somebody can help us ..
Re: How I recover from my dead XDA II ..
alvinlim28 said:
I have to agree with DCS that those are the rules and you need to follow them properly. It's not the ROM that's having the problem but the procedure needs to be followed.
In my case I didn't have the Sync cable properly connected (I bought a new sync cable & I didn't use the cradle) to upgrade the XDAII (duh!).. and I paid the price of having my heart droped on the floor ..
My nightmare started when the cable came loose halfway through the upgrade, so the XDA kind of "hung" and when I tried to reset it, it refuse to show any signs. Do a small test. My guess is as long as you take out the battery, put the XDA II into the charger (without a battery), and the red light comes on, that's a good sign.
For those who is stuck in this situation try this steps:
1) Remove the main battery
2) Leave it out for at least 30mins (to drain the backup battery)
3) Go make your self a coffee or watch TV (time flies faster than staring at your XDAII)
4) Put the battery back (at this stage it still won't work)
5) Put the XDAII into the AC Charger (give it a good 5mins charge)
6) Then keep doing the hard reset (just don't give up, it's like doing CPR, your XDAII will show "Serial 1.06" after a good hard resets ...)
Those steps above did work for my XDAII .... and it should work for most cases as I believe when we upgrade (the ROM) we don't touch the bootloader. Sometimes when we screw up, the XDAII got "hung" and it needs a good "cold boot". Taking the battery out won't help because the backup battery is still in. After a good "cold boot" the XDAII will boot into the bootloader and you can resume your upgrade ;-)
NOTE : Do keep your fingers cross through out the entire process.
PS: Thanks to DCS, Twinkle, mamaich and many others who contributed to this fine forum ... Long live the XDA I, II, IIs, III .... beyond ....
Click to expand...
Click to collapse
Just searching through the old threads and I found this post by alvinlim28. I have the same simptoms, white screen, won't start, I get the red light when I remove the battery and place the hima in the craddle, so I guess I'll be up all night trying to get into bootloader and reflash. Thanks all for the contribution in this forum, and thank God for the search option
J.
No luck tonight, I'll keep trying tomorrow gtg to sleep now.
cheers,
J
damm*t still nothing
I've been tryin' all day, and I'm unable to enter bootloader mode
My brother brought me his O2 Prophet a couple of weeks ago because he said it randomly turned off. I assumed, obviusly, a faulty battery, and replaced it with a new one, fully charging it with an independant desktop charger before putting it in. Still the problem persisted.
I hence came here, and trawled through the xda bible, concluding that since the thing would turn off even by leaving it on a table and looking at it, it could very well be a software problem, as so many before me have had. No biggie, methinks - it's flashing time!
And here's where the phone decided it wanted to be a cute white paperweight: before it could finish flashing pdaviet, it turned off, voiding the process. Since, it's stuck in bootloader, and every time I try to flash (and I'm positive I'm doing it right), it will turn off, normally even before it reaches 50%. What could be the problem?
I've checked the connectors to see it they were dirty, and connectors 3 and 4 seemed slightly recessed, but I don't know if this is normal (they're very neatly recessed).
So, finally (I'm a long typer, sorry!) if anybody has any ideas, even maybe apparrently stupid ones, please post - my computer wiz reputation is at stake.
Try a different computer if you can, or even just a different USB port.
If that fails, re install active sync, get a different WM5 NVID ROM, Manually put the device into bootloader, disable connect through USB in active sync and then connect the device. Then run the RUU from the ROM you downloaded.
Thank for your reply l3v5y.
I tried all of your suggestions, but it still turns off all the time - I'm starting to think it really is a harware problem, but I can't figure out where.
Any other ideas come to mind?
Does it start up (and run WM5) properly? If yes, and it persists to reset, I would assume there is a faulty connection between the battery and the device. Check the battery connectors on the device to see if any are further depressed than others.
WM5 doesn't start at all - it's stuck in bootloader. The two middle connectors are slightly depressed compared to the other two - should I pull them out a bit?
I would suggest pulling the pins out slightly, but do not overdo it. Try a different WM5 ROM (an official one is probably best).
I know it may be silly but check if the soft reset button didn't stuck, maybe someone was pressing it too hard and that is causing problems
I have an 8125, IPL / SPL 2.25.0001 that has been working fine for over a year with the factory WM5 ROM. Recently, it started behaving badly, and thinking it was an OS problem, I restored a backup that I took using Sprite Mobile Backup. It worked for about 5 minutes, then started buzzing loudly, and the screen went dark. Now, if I try to boot normally, I get the blue splash screen, but after that the screen goes dark, and the bluetooth and wi-fi lights blink, but nothing else happens. I can get to the striped bootloader screen, and when I plug in the USB cable it says USB in the corner, but I can't get the Wizard tool or Hard SPL or any other tool to recognize it. It's not recognized by ActiveSync or WMDC, but Windows does realize that it is plugged in and adds it as a device to device manager. Am I suffering a hardware failure here? Is there anything I can try?
Thanks!
Nevermind, I figured it out. I found the information in the Wiki and got the Wizard Love ROM working. Seems a lot faster than it ever was before, might just stick with this instead of going to WM6. Or maybe not
There is so much information on here, and it can be overwhelming, no matter how much you try. But, I kept reading and reading and finally it all clicked.
THANKS!
so u figuered it out???
that's cool. i have similar problems. my os works but neither active sync nor wmdc can find the device.
at the time, the loading station is recognized by my pc.
how did u get them connected?
greetz tears
I have flashed the latest HTC update with Windows mobile 6.1 onto my T-mobile MDA touch plus. But I have a problem and I don't know if this is about the firmware, the phone or the battery.
I bought this phone recently (secondhand) and actually flashed this update directly, so I don't have experience with the phone how it came.
Right now, the battery doesn't last for a day without actually using it (even without a simcard inserted). It is clean of software, only flashed the firmware and that's all.
After a day, when battery is empty, the device won't turn on with the charger connected. Even when I keep the charger connected for a whole day. Then I try some things like unplugging the charger, remove/insert the battery, press reset button, connect/disconnect usb and it eventually turns on (I don't know what the real trick is). Battery is empty then, so it didn't charge at all...
Current firmware is Nike_HTC_NLD_2.09.404.1 with its default radio (1.65.28.25). Camera works.
Does this have to do with the software, hardware or do I have a 'almost-dead' battery?
I also like to try to flash the stock firmware, but it won't flash when I have run the sspl 1.16.jump executable on my mda. Or can I just flash the phone with the new stock 1.22 spl ?(fixed)
you need hardspl first ... try again!
I did try that preciously, but the problem was that the 1.16.jump executable booted up the bootflash menu without showing usb. But I did a second try now, and it worked
I am now running the default t-mobile firmware (but I don't get a t-mobile bootscreen.. so it's not a real shipped rom I think).
Battery is 95% now, let's see how long it takes to get empty again...
Battery is empty now, so this had nothing to do with the firmware.
I try to charge the mda with a different charger, because the one that I had was an aftermarket type.
I have another question. When I charge the phone, should the orange light in the speaker turn on? It stays off here...
When in charging mode, via charger or USB cable, the light will be orange, turning yellow once fully charged.
rling said:
When in charging mode, via charger or USB cable, the light will be orange, turning yellow once fully charged.
Click to expand...
Click to collapse
That doesn't happen.. It charges, but it doesn't show any light
Is there a way to check the battery instead of buying a new one ?
I have bought a new battery, but the problem persists
The last thing I want to try is flashing another or original radio. I have read that battery drain can be the result of having the wrong radio version. I hope this is the case.
My device is a niki200 and it is currently running Nike_HTC_NLD_2.09.404.1 with its default radio (1.65.28.25).
I'm unsure if a niki200 device needs a different radio than niki100's. Therefore I like to get a original T-Mobile MDA Touch Plus rom (Dutch/NLD) or a radio that is 100% compatible with the phone. Which radio do I need? And where can I get an original T-Mobile rom, or do I have to request it?
I hope the problem is in the radio, otherwise the hardware itself is faulty
Problem is fixed. It was a hardware issue. The keyboard lights and gsm/charge status leds didn't work at all. Only when I moved the display housing a little bit, I sometimes got these lights working. I have disassembled the phone, reconnected everything.. and it all works fine again . Battery is 95% after 16 hours standby! I'm happy again!
all nike can use the same radios ... only japan nikes use different radios!
I want to say thanks to tuti fruiti, I had the same problem with my touch dual, followed instructions as give, and everything is fine now.
Cheers
Tutti-frutti said:
Problem is fixed. It was a hardware issue. The keyboard lights and gsm/charge status leds didn't work at all. Only when I moved the display housing a little bit, I sometimes got these lights working. I have disassembled the phone, reconnected everything.. and it all works fine again . Battery is 95% after 16 hours standby! I'm happy again!
Click to expand...
Click to collapse
I have an old 8525 that I want to bring back to life... tired of the iPhone. It has Mobile 5 on it. Haven't used it in... oh, close to 2 years. Still powers up fine and all so I decided to try upgrading. I used Hard-SPL first and it errored out after the tricolor screen came up, saying it couldn't find the phone. So I popped the battery and went back in, and tried Auto Unlock v3a. Script failed, as did the manual method of copying up. Every time I get to the tricolor screen and it displayes HERM100 IPL-SSPL by Des and HERM100 SPL-1.09.ds. If I leave USB plugged in it says USB, otherwise it says serial. I do NOT have a SIM card in it right now. Am I missing something? It seems like I should have an option on the phone to do the upgrade, but I just have the colors I'd really like to get up to 6.5!
Thanks,
MP