Related
first things first: the hd2 is my very first windows mobile device. i've already read the wiki and searched the forum/the internet for help, but i didn't find a solution for my problem. i'm also not a newcomer when it comes to flashing (i've gained some experience from my psp/wii/nokia n82/creative zen).
so i got my htc hd2 a few days ago and one of the first things i tried was flashing a rom (i didn't like the t-mobile branding).
i had absolutely no problems installing hspl (this forum was very informative) and flashing the artemis rom (i strictly followed the instructions), which i found in the rom developement sub forum. since everything seemed to work fine, i started adding my contacts and some applications, still no problems.
but after a while one of the apps seemed to have crashed and the phone became unresponsive.
i removed the battery and turned my phone back on, but it was stuck in the boot screen (the very first screen on which it says "r g d" in red at the bottom). since i didn't know what to do, i simply flashed the artemis rom another time and so the story repeats: at first everything worked fine and after a while the phone got stuck again.
after 4 tries i decided to switch to the shock star r9 rom (also found on xda), which also seemed to work fine at first, but it didn't take long for the phone to freeze again. i took out the battery again and turned the phone back on. this time (to my surprise) it didn't get stuck on bootup, but instead it (automatically) performed a hard reset. the phone now does a hardreset everytime i turn it back on, which makes it pretty much unusable...
since i'm getting REALLY tired of adding my email accounts/favorites/application shortcuts (by now i'm just installing them on the sd card, so i don't have to reinstall them)/facebook associations for my contacts/etc and i thought i'd better ask for help.
does anyone know what causes this issue and/or how i can solve this problem? help would be appreciated!
and since i'm here, what should i use to backup my phone (once it's running perfectly)? i already tried pim backup (sadly it doesn't create a backup of everything) and spb backup (freezes on registry recovery). would it be possible to create a rom that contains ALL of my information (settings/contacts/favorites/applications/registry tweaks/...)?
tl;dr:
my hd2 automatically performs a hardreset on bootup, how do i fix it?
please ignore any grammar errors, i'm tired and not a native english speaker
I have the same problem exactly regarding self-hard-reset. I still did not find any reasonable cause for this problem which is starting really to push on my nerves
This sounds to me like a corrupt file system, which can happen after ROM flashes. I would try this:
http://forum.xda-developers.com/showthread.php?t=644781
@Moandal: thanks for the answer. i just flashed the shock star rom again and the phone boots up normally again. but i really doubt that it will stay like this, unless i know what caused the problem. next time it happens, i'll try the program from your link.
but if i'm not mistaken, that program also hardresets the phone (correct me, if i'm wrong), so i could just flash a rom instead and that's what i'm trying to prevent (as i said, i don't want to have to enter my personal stuff again and again and again...).
what exactly could cause a corrupt file system? could it be a problem with the rom(s) or am i just doing something completely wrong?
A "simple" custom ROM flash only overwrites the ROM's contents without prior erasing, which on the HD2 has been found to sometimes cause trouble like the continuous hard resets you've suffered.
The solution is a full erase of the ROM before flashing the new ROM, which this mtty command does. So, you obviously can't do it without hard resetting/reflashing.
@kilrah: ok, that made things much clearer. i'm going to use the program posted above and flash the rom again, i hope that will fix future issues.
thanks for the fast help, guys
I had the same issues, at first I thought it was the artiums rom but having done MTTY walkthrough I'm 1 week into the Miri rom without much issues (apart from the odd program crash)
since it started pretty much straight away on the first rom, id be a little concerned that it might be an issue with the phone.
if it continues after you mtty/task 29 then id flash back to stock, including spl, and monitor that for a few days.
Code:
@samsamuel: since my last post the phone crashed only once (i was using opera 9.7 when it became unresponsive again), but this time it didn't perform a hard reset!
the main issue seems to be solved and that's good enough, for the time being.
if the problem occurs again, i'll follow your advice.
opera 9.7 - have you moved the cache to the memory card? I've had a lot of freezes the last few days with opera 9 7, turns out it was cos the cache was on the sd card (default 2 gig that came with it).
moved the cache to the phone yesterday, not a crash in 30 hours.
no, but i was actually going to. won't do it now, obviously
please help cause it went crash and hardreset by itself over again..... how can I fix this??
I know there is similars topics, but I want to describe my problem as somebody may have an answer for me.
I have tried many times installing WP7. WM (official) was working well, some WM custom roms bugged sometime.
I tried to install WP7, first flashing the ROM, there everything is OK.
If I have a SDcard, and if I reboot the phone, the phone starts, then when it gets to the start screen it freezes after 1 second (and the contact tile is still working for few seconds)
If I don't have a SDCard, the phone works well. But I can't use it with Zune, because it says it is a test phone or it is not well connected.
So as I saw there may be driver issues with the SDcard, I have tried the CAB method update.
I can install the 7403 version without problem, but I can't install the 7661 version without plugging the SDcard, because it says I don't have enough storage.
* 1st question: How do I know if the 500M storage capacity is unlocked?
Ok, so I have put the SDCard, done a hard reset from settings and launched the 2nd set of update to 7661 (why? just to be sure everything goes well... As it does not work all the time, I prefer to go step by step instead of going straight to 7720).
The update is OK, but now I can't go to 7720 anymore, because it says my storage is full (the card is recognized in settings, so I have 7Go available)
Ok, I restart the phone... Frozen again after booting.
It is really strange because the system is still working (some animations, the battery hiding, ...) but it becomes unresponsive.
Sometimes when I restart it doesn't freeze, but I don't know why or when it does.
Do you have any idea about what can I do?
I have tried 2 sdcards sandisk 8 and 16GB, it is EXACTLY the same. So it is probably more a problem coming either from the phone (card reader??) or the way I install (I cannot format the SD anymore because it is undetected under win, I don't have any nokia with sdcard phones, and don't have any linux installed, nor CD reader, so I haven't tried killdisk
I bought my phone in december 2009, 1 or 2 months after its release, so it is getting old, but I would prefer to keep it for at least 4 more months!
The last 2 months have been a real pain so I am really looking for a solution!
Hehe, after many many many tries, I finally got my fresh Mango!!
Everything is working well, with the same hardware, same sdcard, don't understand why but it works!
I have set all accounts possibles to be sure this time it won't bug. It seems to work!
I just have to send 1Gig of MP3 to be sure, take few more picture, and it should be ok!
So gooooooood
Anyway, Mango is much much better than initial WP7! Almost everything missing in WP7 is in 7.5!
What did I do? hum... Nothing special, just many times the same thing:
flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing
then...
flashing WM6.5 ROM (with SD)
flashing magldr
flashing Radio (or maybe not??)
flashing WP7 (with SD)
flashing deviceprovisioning
setting time
flashing to 7392
RESET because lack of space? or maybe it was the time before?
flashing to 7720
reset
playing with the phone
being happy and relaxed
I am playing alone here, but if someone comes:
Everything works, everything BUT zune...
I cannot connect my device to Zune, it is not recognized I don't know why, it has never been (maybe once, but long time ago, many flashes since!)
So if somebody knows what could be wrong... (my device time is set right, same as my computer)
"Can't connect to your phone. Disconnect it, restart it, then try connecting again"... always.
I got a "your phone is synced, disconnect to see the content" because i was on the marketplace, but nothing on the computer!
If I can't get it working, is there a way to send MP3s to it without Zune?
Well I see you got the problem solved, but just I case others come across the same issue, you remove the SD card before going to WP7 and update as far as U can with Zune, then update as far as U can with cabs. I think update 7463 requires an SD card so format it using windows and insert it and continue updating. From my understanding, it is something to do with the way WP7 treats SD cards and locks them and at some point its like the SD card gets forgotten so when U try to update, the card is locked so cannot be used. Look at xboxmod/yuki updatable wp7 v2 and there is also a cab to unlock the SD card as well as update cabs and some other useful stuff. There is a very good install guide. Oh and FYI, there is also a 1 shot update to go from 7004 to 7720 mango RTM. Takes about an hour to do but much easier.
Thanks, but... Being able to use mango, I won't flash anymore, it has been too painful to reach that!!
I have never been able to update with Zune, because it has never been recognized well. I have been able to update with cabs, hoping that would resolve itself with updates, but still have the same pb, can't connect to Zune...
My plan is to upload photos using skydrive, and put MP3 via... another way, I just have to find it!
I am sitting here in a bit of a shock and am not sure what happened. I went to charge my phone which was off due to battery dying, nothing new at all, I just hit the power button, waited for my splash screen to pop up and plugged it in, walked away... I returned to my phone and it was as if it reflashed itself. Android was asking me to set it up again. Everything was reset.
This is a first for me and I admit that I probably had this coming because all my Nand stuff is old. I last updated this phone in February. So yes, I have old MAGDLR, (1.11 I think) my rom is NexusHD2-Gingerbread V2.2 by Tytung IIRC. My radio is 2.12.50.02_2 which I never had an issue with but I understand there is another one recommended. My phone is TMO US, for the record..
I am probably answering my own question by stating how old it all is, but I am just surprised as to why this even happened. I have had some random issues like trying to install things from Market and there is not enough space available so I have had to uninstall stuff. The phone would get laggy and I assumed it was due to apps eating memory which happened a lot. I am not sure if my memory failed in some way or files got corrupted because NOW it claims I have ZERO memory internal. Sounds to me like the partition is messed up. My SD seems in tact yet no apps show up that were on it.
I did some searching for my issue and did not find a lot so I apologise if I am redundant in posting this. I have a lot of catching up to do on what has changed in the past months with Android NAND for the HD2 and I am a bit overwhelmed by the idea as I was not prepared for my phone to reset itself for no apparent reason. Any input is appreciated.
Well, I have run into more issues and its with Windows 7 64bit not liking my HD2 and refusing to install drivers. I have the HD2 toolkit and the driver page is unavailable. I have searched and one of the only answers to this issue I found was reinstalling windows 7 I doubt I need to do all that since I have recently wiped and reinstalled windows 7. Updating my phone should not be this complicated but I suppose this is pertinent to Windows 7 because Vista gave me no issues ever when flashing things. Any idea what drivers I am to install and where to find them?
I update to retract my need for drivers. I found them. I then had boot loops for again an unknown reason and did a restore point all the way back to February from CWMR on a hope it would fix the issue. It seems to have worked. I hope I can update everything in proper order. In what order that is, I do not really know. I want to update the radio but am not sure if that can be done without reverting to Winmo.
I still am hoping for some input on why this whole thing may have happened. If I was not clear on my first post, I apologise. The whole ordeal has me pretty thrown. I think this was an internal memory corruption of some kind. Now that I have recovered my old Nandroid from Feb, it seems that I have 599MB of internal storage. That is better than the 0,00MB I had last night. Just confused why it would do that.
akq2296 said:
I update to retract my need for drivers. I found them. I then had boot loops for again an unknown reason and did a restore point all the way back to February from CWMR on a hope it would fix the issue. It seems to have worked. I hope I can update everything in proper order. In what order that is, I do not really know. I want to update the radio but am not sure if that can be done without reverting to Winmo.
I still am hoping for some input on why this whole thing may have happened. If I was not clear on my first post, I apologise. The whole ordeal has me pretty thrown. I think this was an internal memory corruption of some kind. Now that I have recovered my old Nandroid from Feb, it seems that I have 599MB of internal storage. That is better than the 0,00MB I had last night. Just confused why it would do that.
Click to expand...
Click to collapse
I do not know how to help you with your problems, but if you ever want to switch bootloaders my guide can help you. The radio can be flashed from the tricolored screen.
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.
hello,
phone was working pretty good up until roughly 2 weeks back, and then it started to slow down, stumble along, then came freezes, and reboots. i know very little regarding android phones, its as if the software has been corrupted. so i have backed up all my apps and data, got my contacts and other info off the phone.
i would like to do a complete reformat of the HDD, and install a new OS, (so to speak) then root and re-install all my personal crap
i have been reading over threads and what not, and unsure how to ensure the old os and everything is removed, prior to flashing the new stock rom.
or is flashing a new stock rom sufficient to ensure that what ever corrupted the old software has been silenced or removed.
thank you