[Q] Totally Random Hard Reset - Windows Phone 7 Development and Hacking

hey all
Any ideas why this has happened ? I am gutted !
I was running an unlocked (via Ansars U2MB2 tool) HD7
Been running for about a week and a half and everything fine.
Looked down at my phone this morning and it was stuck on the white HTC screen.
I pulled battery - still it was stuck on HTC
After a while it booted in but I was faced with the "lets get started" routine !
The phone has reset itself losing all my data and has now also become relocked.
Any ideas as to what caused this ?
Could it be MS ?

It sounds like the flash memory corrupted and everything got reset. You may have a faulty device.

Cheers
I have since re-unlocked the phone but I am reluctant to do anythng with it now until I can get a relaiable back up solution.
Dont suppose you know of anyway to test the flash memory do you ?

I don't think there is any type of test you can run on it.

Hi, just an idea and I really hope that is NOT your case:
This reminds me of the random hard-resets of my good old Diamond.
I used to get them after quite a few flashes of custom ROMs. The cause for this was clutter in memory left by those flashes.
Fortunately, a cleanup tool had already been released and once I used it I got permanently rid of this problem.
Eventough I haven't heard of such issues on WP7 (yet) I wouldn't be surprised if they did start to occur as more people begin to flash their devices with custom ROMs.
Bad news is that I haven't heard of such a cleanup tool for WP yet, either...
For these reasons I hope that's not your case because this may become one more (of way too many, already) issue, developers will have to face.
Guess I will have to stick with my DFT 7713 for a bit longer while newer ROMs mature...

Thanks - I hope this isnt the case too
I have flashed a fair few custom roms to it

Related

Touch Diamond - Hard Reset Issue

I've read lots of comments, these very unwanted random hard-resets are suppose to be a common bug, however the suggested fixes dont seem to work for me, anyone else having the same issue?
Note: The issue must be software related, it only started happening to me immediately after a ROM update a few months back.
What usually happens:
- Install a ROM -> Configure It -> Install Apps... all looks good
- At some random point (could be days or weeks) the phone will lock up (usually on the password screen)
- A soft reset is required to rectify the lock-up
(i.e. the red button on back of phone)
- Phone hard-resets itself
Suggested Solutions:
1) Upgrade to HardSPL 1.93 - made no difference
2) I have tried running MTTY a few times, also no difference
3) Try different ROM's, I thought it might be just a bug with the WWE ROM, but it happens with the Energy ROM too
Just out of interest:
Interestingly, my wifes phone, which I do exactly the same updates on (same phone, same ROM, same Radio, etc), is working completely fine...
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
businello2000 said:
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
Click to expand...
Click to collapse
Hi, thanks for suggestion, although yep I tried that too. There is no stock ROM for an imported phone on Optus, but I just used the stock Telstra one that was on the forums, then after a while went back to the WWE ROM, and the same issue still occurs.
No other ideas for resolving the hard reset issues?
Next time it happens, I might try pulling the battery out instead of using the reset button on the back of the phone.. but clearly something is wrong :-/
i have had this a couple of times, about 6 months ago and last week. i just flashed a different ROM, flashing the same one again didnt help, so just downloaded a different one and went with that.
seems to be ok now
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
matrix77 said:
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
Click to expand...
Click to collapse
Thanks again for suggestions so far, but above fix only lasted about 5 days before another intermittent phone crash & subsequent hard reset, much the same as I have had experimenting with a range of stock and other ROM's :-/
I don't think the fix is as simple as just putting a Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset. Im pretty sure its a software problem, but I dont see how the problem can survive such rigorous formatting...
Is noone else having the problem? Sounds like most are solved with 1 use of MTTY.
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
The only solution is:
1st MTTY and run task 29 to format the device to make it clean and no left over stuff from the last ROM.
2nd Install different ROM
If you have bad sectors in the device, MTTY might not help much here, I guess.
Hi maddie, yes you might be onto something, I assume you already tried the usual fixes: (Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset)? You can tell it to format the NaviNAND during the hard reset.
I think my issue might be different to yours though, as mine does not happen 'when installing software' mine happens days/weeks after setting up the phone.. It usually goes down like this: I pull the phone out of my pocket -> its locked on the password screen usually (cant type) -> pull the battery out or press the soft-reset button -> bang.. phone hard-resets.
I will make 1 suggestion though, instead of using all the nice fancy mods, and SPB Mobile Shell (looks like sense ui), I went back to a boring old stock rom, and well after 1 month its still going.. I absolutely hate it, but I dont want to buy another phone quite yet, so gonna go old-skool.
Let me know how you go, and as above if you did all the standard suggestions? It sounds like you need to somehow instruct the phone not to use those bad memory spots, but ive no idea if such a tool exists im afraid.
maddie said:
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
Click to expand...
Click to collapse
I got the same problem recently and I am still trying different way to solve it.
My Hard-reset happen:
After flashing new rom -> Installation of software ->
-> launching programs -> when some got may holding or loading without response
-> Soft-reset (red bottom) -> It automatically Hard-reset....
Similar thinking with you, I think that maybe one of those reasons leading the hard reset:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
kenleekwanho said:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
Click to expand...
Click to collapse
I like this logic, im in the position of owning 2 HTC Diamonds with identical ROM, Radio, Applications, 1 works perfectly, 1 is resetting.
It 'probably' indicates that its hardware related, I doubt its Radio (due to the other phone working fine), so could be Internal Storage or Bad Sector.
Im not even close to filling up my internal storage though, so if its storage related, perhaps a particular sector is the problem (like maddie was mentioning).
Thanks for all your opinions!
It's the first time for me to think it's the Radio's problem. It comes to me now it seems this situation starts when I flashed the 1.15.25.14 radio. I will try another radio and update here.
I dont 'think' its Radio, but worth a shot.
I cant consistently reproduce my issue, so it could take me a month to find out if ive fixed the issue.. and there are a lot of variables in a month. But sounds like you have a way of reproducing it consistently, gl.
OK, it doesn't seem to work. I think that's it..
Maybe I should start looking at the bootloader commands..
ive got the same issue, but only with some ROMs, for example, the AZTOR X3 and GEN.Y D2 didnt work, but gen.y 1.4 worked for me.
I tried MTTY method to re-flashing, it seems fine to my diamond right now.
i have the same problem, i have tried about 10 different roms, but i don't think it's software related, i think it might be the phone overheating causing a faulty component, it started 2 days ago for me and usually after 5-10 min it crashes, and it started happening when the weather heated up and it will crash quicker if i try to charge it, anyone notice this?
Has anyone found a solution to this?
For me it started when I installed the Gen Y rom with the android dual booter (but not android itself). I have tried MTTY, Stock ROM but Im still experiencing the problem. I suspect it has something to do with the dual boot.
I get the same thing. soft reset = hard reset.
I have tried several ROMs but now the phone hangs on the loading screen

[Q] Thanks and quick help on recovery pls.

Hi,
I have a HTC Desire and just after I got it I managed to muddle through unbranding it to get rid of the Vodafone addons. At the same time I managed to root it.
I recently decided to take the jump and try some of the non stock ROMs as that's one of the reasons I went for Android.
I have to say there are some great tools out there and my sincere thanks to the developers, namely:
o AlphaRev
o ClockworkMod
o ROM Manager
o unrevoked
Wow nandroid is a real bare metal restore that works ))
When I decided to take the plunge I went through the recommended approach detailed elsewhere in this forum.
I've so far tried LeeDroid, Oxygen & Defrost.
I now have a slight problem that seems (perception) to be getting worse.
In summary, if I reboot into recovery (either power/back or ROM Manager) it sometimes works and more often now doesn't work. When it fails it just hangs at the AlphaRev screen, just a boot screen I guess. When it hangs it never recovers, battery out and try again, again, again .... then it'll work.
Does anyone have any thoughts on this boot into recovery issue ?
Colin
~~~~~~~~~~~~~~~~~~~
HTC Desire
AlphaRev S-OFF
Radio 32.49.00.32U_5.11.05.27
ROM currently Defrost (still trying the various flavours)
This is the issue, people get a brand new shiny phone and the first thing they do - as opposed to actually USING the thing - is find as many ways to bodge it as possible...
People need to actually read everything, take some time to absorb it and then read it again. Then use the phone as chances are unless they're a real app whore they'll never need to worry about internal space...
I've no idea why you're having issues but I assume you don't have a copy of the RUU your Desire originally came with so should you need to return to stock you can?? this is the first thing anyone should do before undertaking any type of customising and would save a lot of headaches
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
how bout reflashing recovery?
gol_n_dal said:
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
Click to expand...
Click to collapse
I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
>> I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
NP,
I get it all the time having to "help" people who tried things on their Home PCs or TVs, BluRay, HDMI inerconnect, ..... Shops offer bloody useless help to them. ;-)))
>> how bout reflashing recovery?
Yes, I've tried reflashing ClockworkMod through ROM Manager, it's currently 2.5.0.7 confirm by ROM manager and when it finally gets into recovery.
It just seems an intemittent issue that only arises when I want to do a Nandroid backup or "play" with the ROMs / Radio etc. The only solution I have is to remove the battery, count to 3 and re-insert it. Then try again.
It's not a show stopper just a real pain, especially when installing a new ROM/Radio when it's supposed to reboot. It's a case of how long do I leave it and hope it recovers to sod it, battery out and pray it's not bricked as a result.
Regards
Colin

[Q] eMMC issues - how do i tell if i have a bricked Desire Z?

Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )

Overheating and stuck in bootscreen

First.. that suggested topics thing is pretty awesome guys!
But anyway... I've been rooting my phone following the steps of the noob proof guide for a while now (http://forum.xda-developers.com/showthread.php?t=1016084). However after this procedure and flashing cyanogen (7...) my phone seems to make a habit of regularly overheating and then rebooting. It has happened a few times already that it ended up stuck at the "why so serious" boot screen, while not being able anymore to access recovery.
I've managed to reflash till now, but still it seems safer to avoid the problem. While using the stock rom right now my phone has not overheated once! However it highly annoys me that I can run somthing like NO app at all...
I wonder: Is it a cyanogen issue? Might it be due to the method of rooting? Somebody with a similar experience?
I suppose there are some easier ways to root by now anyway?

[Q] TWRP HTC DUMLOCK (Flash boot.img from recovery)

Hi all,
so there's this project of TWRP, and until now, I haven't seen anyone who tried this with success. But maybe it's just because this person who managed to get this working didn't felt the need to report about it. It's not like this person were commited to report about his success but...AFTER ALMOST A YEA....sry, I'll stay calm...what was I'm saying?, yes, so after almost a year, we still have to use a PC to completely flash a custom rom. So I hope you can comprehend the situation and tell us a bit of your successfull story with HTCDUMLOCK. If you don't feel the urge to do that...I'm gonna try it out and report to you guys.
Get info about it on their official site...
TWRP's HTC DUMLOCK
Tried it out like 1 month ago, the installed app crashes and refuses to open. Didn't complete the process after that. (Step 8)
PS. the supported devices are Evo 3D and Sensation, maybe we can find a parallel exploit for the hox.
AFAIK the problem would be, we don't know where the needed partitions are located. Am I wrong?

Categories

Resources