Database Users

BIG Problem after Upgrade to WM6

I make a ROM upgrade for WM6(1st versions) three week past.
Works for 2 days and after this, when i reset or turn ON, show the Rom versions numbers normaly and when it should enter in Mobile Windows, the screen distorts and they show some vertical lines.
I try reinstall the others ROM, but nothing.
What i do.
Thanks,
Fersoft

Wish I could help
Sounds like its been dropped or knocked. I've never heard of anything like this previously. I've been upgrading for years on all types of htc phones. I may be corrected but I do not see how a ROM can ruin your model in this way.
Have you got the original back up of the ROM that you started with?

I can olny enter in USB mode.
What ROM to RESERT completly my Pocketpc ?
Thanks any help.

Have you tried to flash an original ROM from the three color screen?

WM6 is the problem...
I got the same problem as you dude.... sounds like crossbow version isn't really suited for prophet. And I guess we'll get more and more of these troubles while more and more users are tested it (at least the first versions). I guess it has something to do with power management, and the way WM6 handles the battery. Mine got better after I flashed it back to WM5, but it still had the problem, and I had to send it back to warranty...
While you find a "solution", you can get it to work again for a few hours by letting it turned off for a few hours, battery out. That way I could flash it back to another rom. But still, after a few hours it would crash or reset itself, and you'll have to let it off without battery for a moment...
If an admin read this, I guess it could be VERY usefull to stick it to let people know they can arm their device that way.
Good luck

Amazing. I got exactly the same problem.
I am back to WM5, however, I still cant use the phone properly. After ten minutes into a phone call it crashes. When I reset I get until the OS loading screen (sometimes it even omits the radio rom number which usually comes between the SPL and OS). Then the screen distorts and thats it.
If I get the battery out for a short while and then connect it to the charger, I can restart the phone after 1-2 hours and it will load properly. However, again after 10 minutes into a phone call it crashes.
Any idea if a new battery would help, because I get more and more the feeling that something is actually wrong with the power/battery system.

Is WM6 even a final version?
I don't see any equipment running WM6 as of now, that's why i asked.

really? I don't think so.
However, every MS software still has a lot of a bug....

I have the same problem, but now even a bigger problem !
I have NO backup!
I don't know how to get it back to the original rom because mine freezes with the screen when the os version is in screen!
Damn, I only got the phone back for 4 hours because is was getting repared for a speaker failure.
and isn't that ironic..

What the BRICK!?!

So I went out and got a TMOUS HD2. Fantastic. Love it more than the Iphone for the typical reasons. So I'm at the point where its time to really make it mine, custom rom, a few tweaks, a few preferred apps, etc...
Here's what goes down.
1. I try to install HSPL. I fail, not yet knowing there is a difference between the TMOUS and typical flavor machine. Luckily I don't brick, learn my lesson, find the right HSPL.
2. Install a TMOUS friendly HSPL. Cotulla shows in the boot loader and all that jazz. Radio is of the 2.08 flavor which should be compatible with sutom roms, so with that 100% successful I should be good to go.
3. Huh. Rom page says I should TASK29 before I install. Ok. TASK29 seems like a cleanout and reformat of the room, so that makes sense, though I only seem to half understand it. What's the least hassle way to handle that? Well, since I don't want to change my radio it looks like the "ShaDrac repack" is the way to go. I follow the download link, watch the youtube video, and set to do the deed.
4. This is where I should be saying "and then I went into the bootloader and installed the TMOUS friendly custom rom." I didn't get this far. TASK29 went to 100% and rebooted the phone, only it hung on the T-Mobile splash screen (that part that says "stick together!" in obnoxious pink). I figure it just needs a good old fashioned reset like in the instructions. I pull the battery and put it back in, getting the same result. I'm a bit worried, but I have my rom ready on an SD card, toss that in and proceed to try to go to the boot loader (which should always come up since HSPL is installed, right?) Well, that time when I tried to boot up I got nothing, not even the ill fated splash screen. This thing looks bricked, doesn't respond AT ALL, even after I let it sit for 24 hours to let the internal battery die and hope it'll go to at least the bootloader. Tried hard reset, tried linking it up to the computer (WMDC says there is no device there), tried volume down+power. Nothing it just sits there like a rock.
I went over my steps carefully, read numerous posts, and as far as I can see I did nothing wrong. (I completely avoided anything involving the radio and the dreaded number "51") Please correct me if I'm effed up somewhere. I've flashed devices before and never bricked, even though this was my first HD2 attempt, so I'm not completely unknowing in the subject.
If anyone has a solution I'd love to hear it. If anyone has any idea WTF happened, I'd love to hear that as well, even if it means I just made a $300 mistake. At this point I am officially stumped like a chump.

darkekun said:
So I went out and got a TMOUS HD2. Fantastic. Love it more than the Iphone for the typical reasons. So I'm at the point where its time to really make it mine, custom rom, a few tweaks, a few preferred apps, etc...
Here's what goes down.
1. I try to install HSPL. I fail, not yet knowing there is a difference between the TMOUS and typical flavor machine. Luckily I don't brick, learn my lesson, find the right HSPL.
2. Install a TMOUS friendly HSPL. Cotulla shows in the boot loader and all that jazz. Radio is of the 2.08 flavor which should be compatible with sutom roms, so with that 100% successful I should be good to go.
3. Huh. Rom page says I should TASK29 before I install. Ok. TASK29 seems like a cleanout and reformat of the room, so that makes sense, though I only seem to half understand it. What's the least hassle way to handle that? Well, since I don't want to change my radio it looks like the "ShaDrac repack" is the way to go. I follow the download link, watch the youtube video, and set to do the deed.
4. This is where I should be saying "and then I went into the bootloader and installed the TMOUS friendly custom rom." I didn't get this far. TASK29 went to 100% and rebooted the phone, only it hung on the T-Mobile splash screen (that part that says "stick together!" in obnoxious pink). I figure it just needs a good old fashioned reset like in the instructions. I pull the battery and put it back in, getting the same result. I'm a bit worried, but I have my rom ready on an SD card, toss that in and proceed to try to go to the boot loader (which should always come up since HSPL is installed, right?) Well, that time when I tried to boot up I got nothing, not even the ill fated splash screen. This thing looks bricked, doesn't respond AT ALL, even after I let it sit for 24 hours to let the internal battery die and hope it'll go to at least the bootloader. Tried hard reset, tried linking it up to the computer (WMDC says there is no device there), tried volume down+power. Nothing it just sits there like a rock.
I went over my steps carefully, read numerous posts, and as far as I can see I did nothing wrong. (I completely avoided anything involving the radio and the dreaded number "51") Please correct me if I'm effed up somewhere. I've flashed devices before and never bricked, even though this was my first HD2 attempt, so I'm not completely unknowing in the subject.
If anyone has a solution I'd love to hear it. If anyone has any idea WTF happened, I'd love to hear that as well, even if it means I just made a $300 mistake. At this point I am officially stumped like a chump.
Click to expand...
Click to collapse
If I'm following you then what you need to do is put the phone in bootloader manually. Pull the battery and hold down the "down volumn" button. This should bring up the tri-colored screen(bootloader). Connect your USB cable wait for it to show "USB" then Flash away...I hope this helps
Im sorry...Just read your whole post and it seems you've already done what I suggested..

well if the battery is dead, it isnt going to turn on. now that the battery has depleted completely, let the phone charge again. once it does try to go into bootloader and flash ROM from sdcard or via USB.

One more thing...
Oh, one thing I forgot to mention before.
I've set the thing charging for about 3 hours and still no response. Furthermore, when I have the charge cable in I don't get the LED that lights up during a charge does not turn on. It just sits there unresponsive.

check your battery pins. plus you haven't said what rom was on your sd card.
oh and in step four, after task 29, it's supposed to hang at the boot screen, there's no rom on the phone, task 29 just erased it.
you should have held vol down as soon as it hit 100% and gone into boot loader. if you mis time it, pop the battery, hold vol down and tap power to manually enter boot loader then connect to usb and flash your rom.

The rom I was trying to flash to was the latest OZrom for the 1024. Seems like the most stable cooked rom that I've been able to find for the TMOUS HD2.
Mostly I just want a WM 6.5.5 rom with CHT and the full functionality of the HD2. WM 6.5 stock just isn't quite finger friendly enough for me (though HTC Sense helps a LOT) and I want to have some more of the customization that CHT offers.

Holy crab in a burning biodegradable bag on my doorstep.
It was the battery pins not lining up properly. Why is it always the dumbest most simple things that defeat me when I'm handling something high tech?

did you get it flashed okay? I'm gonna attempt my first flash tomorrow for my hd2 and I was gonna do the task 29 also, pretty much with the same steps you listed. When I saw your post it worried me for a sec

SUCCESS!!!
I have successfully flashed OZrom onto my HD2 and have saved myself from having to spend another $300 in shame.
Had to flash from SD card since for some reason WMDC 6.1 was not detecting the HD2 on bootload screen, but it still worked.
Hopefully that'll take some of the fear out of this process.
Do your research right and things go (almost) according to plan.

dont worry
Do not worry man same **** happen to me.... I had gunk on the batt pins felt like an idiot lol

If you have any other issues with the phone not charging check out my post on the pins for the battery.
http://forum.xda-developers.com/showthread.php?t=701939
There has been an issue with the contacts being bent and then they don't contact the battery and wouldn't charge it.

Well, I'd like to thank you all for your help with my issue. My HD2 seems to be rocking nicely. Battery life seems to be shortened a bit, but I've also probably been tooling around with it too much, else it might just be I chose a power hungry rom. I'll also keep my eye on that batter contact issue.
Once again. Thank you.

darkekun said:
Well, I'd like to thank you all for your help with my issue. My HD2 seems to be rocking nicely. Battery life seems to be shortened a bit, but I've also probably been tooling around with it too much, else it might just be I chose a power hungry rom. I'll also keep my eye on that batter contact issue.
Once again. Thank you.
Click to expand...
Click to collapse
Do this test with different radios.
Flash a radio and let it charge all the way and write the time you unplug it and let it die by it self and then write the time.
Flash another radio and do the same thing.
While doing these test try to use the phone with the same settings as the previous tests and close to the same usage.
This way you can find the best radio for the area you live in which helps battery life overall.

darkekun said:
Had to flash from SD card since for some reason WMDC 6.1 was not detecting the HD2 on bootload screen, but it still worked.
Click to expand...
Click to collapse
no it won't recognize it.it doesn't need to.
when the phone is in boot loader connect usb and watch the phone screen for the word serial to change to usb. when it says usb you can flash. wmdc will never see a phone in boot loader.
when instructions say "connect to active sync " they don't mean connect to the active sync/wmdc software they just mean connect to usb. its an added confusion that there is no need for.

Phone Keep restarting

Hi, I'm having a big problem with my device, I've bought the European version and didn't touch the ROM or radio for a cool 3 months, but I often update to the latest Cookie HT, and lots of different apps. Then it got a weird behavior that if I use the device and it got a little hot it would restart by itself and after the restart got stuck on the white logo screen. It would happen often when plugged and Activesynced to my computer.
I lived with this situation for the past month but now I had enough, I've updated the radio to the latest I could find, and the ROM to Energy with Cookie HT.
Now it's worse, I can't get it to stable on the Home screen, I can see it but can't play with anything, stuck...
And BTW when it get stuck the bottom of the phone is quite hot, even if I left it for quite some time.
Edit : The Sense UI isn't loading and it actually a good bug, cause the device is running smoothly even on ActiveSync. It feels like the CHT is to blame, at least the latest one to date.
Edit 2 : Sorry, I was wrong, now it got stuck during SPB backup restoring connected to ActiveSync.
Edit 3, Sorry 2 : I've let it cool, turned it on and somehow the CHT is back and working wonderfully, this is weirder then I thought.
Edit 4 : I've managed to run Android 2.1 Desire and it was running good until it got a little warm and then froze. I'm beginning to suspect this is a hardware issue.

I realy need help feaguring this one out.
I've replaced a couple of Radio versions and this device keep jamming up, it's now unusable. I need to get it relaxed and cold before I try to turn it on again.
Can it be that the ROM is responsible ? should I go back to the stock with no mod at all (it would KILL me though).
I'm frastrated and thinking of selling the phone if anyone would buy this piece of crap.

i am in the same boat mate.
mine is going back to htc tomorrow.
In the end i removed everything and took the rom/radio back to stock still the 'heat' issue exists.
It has been like this on test for nearly two weeks if i try to run the youtube app the phone switches off anything more intense and it hard resets itself.
I have learnt that if you leave it too cool down battery out etc it will switch back on and if you do nothing but make phone calls it will be ok?
Having read alot it appears this issue happens if the device goes over a certain temp. For example folks have been moaning about the phone switching off if used in a car whilst charging running sat nav.
I advise you to contact htc as i have done.

you may have already done this, but did you do a task 29 before flashing the rom (task 29 wipes the phone and gives you a clean base to start from). Also delete the application data on your mem card(important). If your phone wont boot you can enter the bootloader by removing batt and holding vol down as soon as you you put the batt back in,This will put you onto bootloader screen ( if you have hspl installed?) from here you can do task 29 and reflash your chosen rom. Oh and make sure you have required radio for the rom you choose. hope this is of some help thought id try

Just wanted to update that HTC took an effort and accepted my unwarranted device for fixing. They replaced the board and sent it back on their expense. The device now is working flawlessly !
Thanks to HTC for a GREAT customer service and support !!!

[Q] HTC Magic bricked(?) after radio flash

Hi there,
your first thought might be: Ah jeez another one posting the same **** 2000 people posted before ^^. But anyways i think my problem is a special case:
yesterday i wanted to flash another radio to my htc magic via clockwork recovery. However something must have gone wrong. After the recovery rebooted my phone i got stuck at the "htc magic" splash screen. Pressing the home or the back or vol-down button or home and back button at the same time doesnt change the situation. still stuck at splash screen. fastboot and recovery dont seem to work.
After some really bad panicking minutes, i pulled the batery out of the phone and let it rest, while googling and searching the **** out of every forum on the net. Some minutes later i reassembled the battery and started the htc magic without pressing any other buttons, hoping it would juts boot and say "kidding ))" on the display. but yeah ... it didnt ^^.
Now im coming to the odd part, which differs from most other posts i saw on other forums and here on xda: after quite a while my htc magic suddenly made that "bling bling" sound, as it did whenever it started android successfully. i nearly burst into tears when i heard that sound, hoping that i would be able to access the phone via fastboot or adb. but ... i wasnt able to :S. the screen went black after that "bling bling" sound and stayed that way until i pulled the battery again.
i could repeat that procedure and reproduce the sound and behaviour, but i couldnt access the phone via any possible way i could find on the web :S.
hopefully somebody, who knows more can help. my last step would be jtagging the phone. but the tools are kinda pricy for such an "old" phone. and i couldnt find anyone in my area who could borrow me the tools or repair the phone for cheap money.
thanks in advance im counting on your knowledge

Try this low cost JTAG
tested by me with 2 T-Mobile Mytouch 3G

thanks for your fast response. if jtagging really is my last chance:
- what did you pay for all the parts of the schematic ?
- how long did it take you to put everything together?
- do i need a parallel port on my computer, or is it possible to use an usb port ?
- and do you think a newbie to smoldering and stuff could be successfully assembling all those parts?
- can you provide me with links and/or other pictures, which could help me?
thanks again for your effort
kinda exciting this whole thing :>

[Q] URGENT HELP with a fully bricked defy

Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve

To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app

wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good: