Okay, I've searched and can't find this problem but hopefully somebody may have some ideas.
Quite frequently, I lose the top line of my display (the one with the start button and the system status icons). Everything else works but that line just disappears.
If I then lock the device it comes back. When I unlock it, it sometimes stays but sometimes disappears again once it's unlocked and I then have to turn my phone off and back on again.
I have a standard Orange UK phone, standard ROM and I've used some of the performance tweaks listed here. I've also disabled Touchflo and am using spb diary as my home page.
Anybody any ideas because this is driving me mad?
I had the same, but only when TF3D was deactivated. Since I use it again, it doesn't happen anymore...
It happens on my Orange diamond as well - stock 1.37 rom with TF3D enabled.
It seems to happen once every 4-5 days, and doesn't really have a pattern. Sometimes it's switching between Today and Second Today, sometimes it's rotating, sometimes it's unlocking etc..
flash a new ROM
Hello there.
Well i just recommend you to flash a new cooked ROM. I havent seen this behavior with a cooked ROM.
Best regards.
Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?
I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.
unwired4 said:
I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.
Click to expand...
Click to collapse
I know it's the wrong forum to say this but I'm just a bit scared to flash it because I've never done it before.
I'm worried about either a) bricking it or b) losing some setting that Orange put in to connect to their network (voice, data, voice mail etc).
Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck
TheFlash007 said:
Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck
Click to expand...
Click to collapse
And what happened?
Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.
TheFlash007 said:
Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.
Click to expand...
Click to collapse
Okay. I still have the problem and am very, very tempted to try flashing a new ROM (and Radio). But I just can't quite work up the courage to do it since I've never done it before and it's the fear of the unknown.
dastewart said:
Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?
Click to expand...
Click to collapse
This happens to me too. I have a T-Mobile Compact IV.
I've found that using FreeUP RAM (part of SKTools) not only releases memory, but also fixes this problem (until the next time it happens, which admittedly is not often).
Just wanted to say that I've upgraded my Orange ROM to the new 1.93 and I haven't had this problem....yet.
2 days without problems so I thought it may be safe to post.
IVe also had this on 1.37.x.x on my mda cmpct IV. Like everyone on here Im considering flashing but Im waiting for t-mobile to release an update (they keep telling me the will, presummably the 1.93.x.x) so that if I then brick the puppy - I can blame it on there rom upgrade.
I want this phone to be better, I know it can be with a ROM change...but I dont want to brick it and for once in my life will have some patience to wait.
Related
Hello,
I know you're all very knowledgeable, so I need your help!
I turned off my diamond last night when the battery was running out and since I put it back on charge whatever I do I can't get into it.
Edit: It's actually the T-Mobile version MDA Compact IV but with Manila TF3D and skin.
It starts up, says windows mobile etc. then it gets to the phone lock screen (which is always a bit laggy) but I can only manage a few digits before it locks up and completely freezes, then I have to do a soft reset or remove the battery to even turn it off.
I've tried everything, even typing the password as fast as I can, but I entered the wrong password too many times and now it's asking me enter a series of letters and numbers before I try again (which would be ok if it didn't lock up by then).
What can I do!?
Daveraven
Panic over - read some posts and figured out how to do a hard reset - all sorted now, thanks anyway!
That'll teach me for setting registry cache tweaks to maximum!
glad all is well
now theres...tweaking and there is tweaking
Yeah.. I think I'll stick to the tweaking for now and avoid the tweaking..
daveraven said:
Hello,
I know you're all very knowledgeable, so I need your help!
I turned off my diamond last night when the battery was running out and since I put it back on charge whatever I do I can't get into it.
Edit: It's actually the T-Mobile version MDA Compact IV but with Manila TF3D and skin.
It starts up, says windows mobile etc. then it gets to the phone lock screen (which is always a bit laggy) but I can only manage a few digits before it locks up and completely freezes, then I have to do a soft reset or remove the battery to even turn it off.
I've tried everything, even typing the password as fast as I can, but I entered the wrong password too many times and now it's asking me enter a series of letters and numbers before I try again (which would be ok if it didn't lock up by then).
What can I do!?
Daveraven
Click to expand...
Click to collapse
I had a similar thing and had to remove the SIM and refit....I got mine replaced and have since flashed SwiftBLs rom on the replacement to get rid of all the horrible t-mobile, slow and buggy 1.37.x.x rom......even though they claim everyone is happy with the device.
Ahh .. right - may have to try that SwiftBL ROM then, haven't tried flashing a new ROM yet, will have to read all the instructions etc.
Apart from the pinkness, the original one doesn't bother me too much, I find it pretty fast - especially compared to when I installed the Manila TF3D - it was really slow after that!
** By the way - I've just noticed that since my Hard Reset the weather cannot update it says it cannot connect! What is wrong here? I can get onto the internet but not download the weather!? **
Daveraven
Does anyone experience "Grey Screen of Death"??
Every couple of days my Diamond crashes, the screen is stuck displaying a noisy grey screen.
Most likely I will have to reinstall the ROM (I'm using SwiftBL 5.5) ... but if there is a simpler solution out there I'd love to know it,
Thanks,
Mike
I've seen that kind of screen but only when I'm playing a particular game and if I switch the Diamond off before closing the game down; when I next switch it on I get the noisy (mostly) grey screen. When this happens to me though I just need to toggle the power on and off a couple of times and it sorts itself out. Or just not switch the thing off when playing that game of course.
None of which helps you of course as yours sounds like a much more serious and randomly occurring issue.
never heard of it before. try changing to a different Hard SPL, these can have funny effects sometimes.
Thanks for reply. Well, at least I'm not alone.
Mine is more worrying alright. I left the Diamond in standby last night, it wasn't running any apps before that, and the phone didn't wake me up with my normal alarm as it had crashed sometime during the night, not doing anything in particular.
do you notice it get unusually hot at any time?
with some diamonds, when it is processing a lot and on charge it can get very hot, and this may have caused ur problem.
Maybe the Hard SPL will help.
One possibly odd thing I notice is that my ROM is listed as 1.93.00.00 on the bootup screen, I expected this to be 1.93.405.1. Is that usual?
It's not the hot or charging possibilities.
I can't find a pattern really, it definitely crashes just sitting there doing nothing.
Does this also happen with a stock rom?
I didn't see it on the stock rom, but that didn't last too long in my diamond and I've been running the Swift one for a couple of months now.
To rule out SPL and radio, you could try different versions there. If that doesn't help, try flashing another rom (maybe also the stock rom).
If this still doesn't get rid of the GSOD, I would send the phone back for repairs.
Sorry, I couldn't be of more help...
Good suggestions, thanks. At least there's something to try without flashing whole rom.
mine is the same, seems to only do it when phone is charging but idle overnight, and certainly not hot when it does it. I am running the stock 1.93 ROM. Maybe it just gets bored lol!
Then mine was very bored.
Always restarted itself during the night - and lost half the battery charge while doing so.
Had it repaired twice and now it works great. They told me it was a software problem, but I wonder what they fixed, because I have flashed the same SPL, radio and rom on my phone as before.
Glad you fixed it. Mine was ordered on the cheap from HK (to Ireland) so I'm reluctant to send it back except in dire need.
I often see it get very hot around the crash time, as if some app is running crazy, would explain the low battery.
BTW, what rom, spl, radio do you use?
I had the same exact problem up till a week ago.
Now I'm happily a satisfied Diamond user. To solve this issue, do either of the following:
1. Find a rom with a newer Manila version, e.g. Dutty > v2.6.
2. Install the latest Manila cab.
Changing hard spl doesnt work, as I had tried them all. Stock rom was more acceptable but the problem still occurs once in a while.
I had changed to Dutty's rom more than a week ago I haven't had the problem ever since. Try it and share with us if it works.
Reason I say its due to Manila is becos Dutty is using a newer version of Manila as compared to the rest.
Oooh, tasty. A confirmed software method of fixing the problem! I'll give that a go and observe the phone for a week. I'll post then if all is well.
Many thanks,
Mike
I'm running Olinex HardSPL 1.93, Radio BS14 and O2 Germany stock rom 1.93.207.2.
I hope knave's solution will do the trick for you.
Hi...
This just append to my phone sometime tonight..!
A left it charging over night ... like I always do..
and when I wake up... there's just a gray screen of death!
I've just flashed my first cooked rom... had stock HTC ROM before...
and my TF3D version is 1.2.35091.2_1813.6..
maybe this was just a freak accident... one time happening??
lets wait and see...
i'm backing up my phone at the moment to hard reset it later. i've got the problem, that in opera when the page (spiegel.de especially) is fully loaded and it idles for 5 secs, the screen turns grey with stripes and blocks slowly. after hitting power on/off 2 times it's normal again, but as soon as it's idling for 5 secs it fades to grey again.
must have messed up something while updating opera
I have searched and found some thread's about this sort of this but not exactly the same problem. I am using GARMIN'S FINAL ROM which I must say it awesome. Stable and the fastest I have seen yet but I am still have one problem, at certain point's my phone doesn't respond to touch, clicking of the front key's and even sometime I have to press button's on the keyboard 3 or 4 time's just to get it to type. I thought it could just be lag but even when I give the phone a few second's to do it's thing (load fully) it doesn't work properly? I mean even sometime's when I press the end key the friggin button's don't even light up.
I hope there is some help because I just got the Tilt and it seem's like a great phone but this is just getting to be stupid.
Thank's ahead of time.
i have the same issue with hyper dragon rom. and no, im not running any programs, memory usage is 48% (running nothing) however the screen wont respond to touchs, the keyboard wont respond etc but the cursor still blinks, animations still play etc.
ive already tried all of the "keyboard" fix's, adjusted the settings manually etc yes i calibrated the screen multiple times *waits for somebody to reflash even though i did that *
I was having that problem and I found the only way to workaround it was to re-align The screen in the Start>Settings>System>Screen menu. But, I have not had it since installing SJ's 15 November 08] HyperDragon III Raphael version here
http://forum.xda-developers.com/showthread.php?t=397121
I strongly recommend it. All you need to do is remember to install Opera 9 last per Notes at the top of the post.
Hope that helps.
I am going to try that out, it look's cool but it look's like there is way to much stuff for it to run fast? Also if I don't use Opera I don't need to install it correct?
bump! Any other idea's?
I have the same problem but mostly notice it when the phone comes out of sleep. The phone will work right then slow to a stop and not allow any input via the screen or keys. 10 seconds later it's good to go.
Edit
OK the fix I can confirm that woks is that you have to sim unlock your phone with the newer 6.1 roms. I did it and it completely fixed my lag problem. Use the kaiser unlocker to do it and it can be found with a simple search. Make sure you have a the right SPL and newer radio to make sure everything is compatible.
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.
I just got mine, even flashed the ROM for mine (T Mobile) and this phone freezes almost literally every 5 minutes and programs freeze a lot and won't allow me to open any other programs and I'm just curious if this is common with other people? I cannot use this phone at all for daily use unless I ONLY use it for texting and not open or use any other programs .
why did you flash it? :S
Mine actually works really nicely, and after changing my polling to 30 minutes instead of as items arrive, i get a completely full day of hard use out of mine...why did you flash it?
Moved to General
Well if you flashed anything theres your answer
You can flash HD 7 ??? never knew it lol what did you flash it with...
I do get a bit of lag now and then if i open too many programs, but not that bad
must say MS has done a good job of winmo 7 hope the updates come soon though
What ROM? How did you flash? Where did you buy the device.
This is the FIRST device I am using with MS OS on it, that actually did not freeze on me at all. The WP7 on my HD7 is fluid, fast and stable. Not a single freeze or hangup. Of course if you are talking about loading of apps like Twitter and Facebook, well, they take time to update and thats an App issue. Not th OS issue.
I think there is something seriously wrong with your device or what you have done with it. Better call up the customer care and get a replacement.
Not even one freeze in 8 days
I flashed the official TMOUS ROM that's been posted in these forums, and nah I mean it way freezes like every 5 minutes... guess I'm the only one with the problem then ? Even factory resetting it still freezes then reboots like every 5-10 minutes... man this sucks, and the phone is so fluid though...
I do mean it freezes/reboots A LOT!
Is there any way I can get a replacement even though I bought it off a friend? (practically straight up brand new) Like lie or something to T-Mobile and say I got it off some smaller T-Mobile dealer? The phone is scratchless and scuff free.
Or any suggestions?
Is it possible that it's a hardware issue? I don't think it could be though...?
buru898 said:
I flashed the official TMOUS ROM that's been posted in these forums, and nah I mean it way freezes like every 5 minutes... guess I'm the only one with the problem then ? Even factory resetting it still freezes then reboots like every 5-10 minutes... man this sucks, and the phone is so fluid though...
I do mean it freezes/reboots A LOT!
Is there any way I can get a replacement even though I bought it off a friend? (practically straight up brand new) Like lie or something to T-Mobile and say I got it off some smaller T-Mobile dealer? The phone is scratchless and scuff free.
Or any suggestions?
Click to expand...
Click to collapse
T-Mobile has a 14 day return policy, and if your friend purchased it on contract (new line, or as a upgrade), then only he can return it as he will be asked for proper ID in order to identify himself as an authorized person the account.
If he bought it outright (full price) and gave you the receipt, you should be able to go back to the same store and return it and get a new.
Either way, I'd say return it and get a new one. And however you flashed it, don't. Its perfect out of the box. Not once has the phone froze on me.
Blah guess I just got bad luck , it seems to freeze 90% of the time whenever I start up the HTC Hub and am in it or go to the main screen. But thanks everyone for your input .
you still haven't answered what rom you flashed.
Also, maybe your friend knew it was defective and hosed you.
nrfitchett4 said:
you still haven't answered what rom you flashed.
Also, maybe your friend knew it was defective and hosed you.
Click to expand...
Click to collapse
he did actually answered on post #9
anyway, does anyone experienced a lockup when using the alarm when the alarm sets off but left alone for a long time? cause i tried using this phone as an alarm but could never wake me up even on full blast volume. so it is left there for hours .. then when i do eventually wake up .. i see the snooze and dismiss buttons up front and when i tried pressing any of the buttons ..the phone doesn't respond.. so i restart the phone and its back to normal.
Ah yeah guess I did get scammed blah. Oh well, **** happens... the one time I did use the alarm it worked for me and woke me up.
But I seriously wonder why it's all super messed up?
Could it be a hardware problem?
Hmm and right when it freezes it automatically enters airplane mode... then stays frozen until I take out the battery.
EDIT: Actually it seems like the HTC Hub makes it freeze 90% of the time and makes other apps not pop up or nothing. Bah! Would like an update (when HTC/Microsoft releases one) fix this problem?
Please, can you tell us, HOW excatly you've flashed a new ROM , because I thought it was actually impossible before someone find a kind of HSPL or something like that for WP7 ????
tenzin said:
Please, can you tell us, HOW excatly you've flashed a new ROM , because I thought it was actually impossible before someone find a kind of HSPL or something like that for WP7 ????
Click to expand...
Click to collapse
see developers section...
http://forum.xda-developers.com/forumdisplay.php?f=783
I flashed mine because of reboot issues too. Mine would reboot and not only that it would hard reset ! After the flash the phone works like a charm. No freezing, no reboots, no hard resets.
Be sure to choose the right one. I don't believe these are upgrades in anyway, just a fresh ROM to install to start from the beginning.
mine hung at the white splash screen / boot screen, so i hard reset (dialled into my memory from HD1 days!) and it was fine. Took the SIM card out later to put into HD1 to write down things to manually move across (cheers MS for no easy option to migrate*), put it back in, frozen again.
Hard reset: still frozen. Doesn't seem like anything i can do - phone seems bricked. Will have to take back - can't find anything on forums. LAME!!!
*option to migrate / set your own ringtones / use swype / send texts, etc, will be available from 2011
OP, have you called htc and reported the problem. It might take them a couple weeks, but they will warranty it for you since you can't take it to t-mobile.
It has to be hardware if it did it before and after flashing.
call htc @ 888-356-2375 (for USA HTC)
If you have an SDCARD in the phone it could be the problem, remove it.