Database Users

HD2 keeps crashing/hardresetting itself...

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??

Did I kill my Hero? FC's and other weird problems.

So for the last 5 days I had some very weird problems with my phone. About 2 weeks ago I started with my first Cronos Rom and it worked great. I flashed 1.5 and 1.5.1 without problems and I used it without an ext partition all the time. But then the problems started. When I wiped my whole phone and tried to reinstall 1.5.1 JIT, the phone didnt boot anymore (stuck on the "Android" bootscreen). I wiped again and again, tried 1.5.1 without JIT, 1.5 etc, but I couldt get the phone to work. Nothing worked, so I created an ext partition and tried again. It worked. My phone started and I was able to use it for about a day without problems though I didnt want apps2sd. But then some other weird things happened. 3 Days ago I bought a bigger SD Card, partitioned it, wiped the whole phone and flashed 1.5.1 JIT. The phone started, but after I installed a few apps, I got an error message (installing xxx failed). I found out that theres an "repair ext" function, and it worked, but after I installed some more apps, the problem was back. The second problem was, that after rebooting the phone, more and more apps wouldnt start anymore (FC). The last problem that occured was an FC of the market app. After that, I wiped everything again, tried to flash 1.5.1 JIT, but it happened exactly the same like on the first time. Problems installing apps, FCs, stuck on boot etc.
I am totally down at the moment because I killed my whole weekend trying to get my phone working again. Could anyone please help my with this? I just dont understand what I did wrong. Shouldnt a complete wipe fix almost every problem? And I dont understand why I suddenly cant use my phone without an ext partition. Any Cronos version I try freezes on bootscreen without an ext patition. Is there any way to get my hero working again? Please please help me.
(PS: I also posted this on the Cronos Board.)

I would take out the sd card, wipe system and dalvik cache, and install some custom rom.

well, to make sure it is NOT your phone, did you try another ROM? Eliminate possible problems?
At least try something that is known and stable, like a stock rom, the Taiwain-rooted-repacks (not a rom based on it, but just the taiwan rom rooted) or good ol' MoDaCo 3.2 (based on 1.5 stock).

Til now I just tried the last 2 or 3 Cronos Roms, and as I said, they didnt work, but when I get home from work I'll try the Modaco Rom I used before.
I dont understand what this has to do with the Rom I use. I always wiped the whole phone, dalvik, etc. so shouldnt it just work like the first time I flashed it? No matter what Rom I use?
Another weird thing (could have something to do with this): After I wiped everything and flashed Cronos 1.5.1 JIT, the market still knew what apps I had installed last time. It showed my bought apps AND the apps I was able to install before the latest crash. So does this mean the phone wasnt wiped completely?

The market tracks your purchases and (free) downloads through your google account. So that's normal that the download-list is full.
But it might very well be that you didn't wipe correctly, although I'm curious how you manage to accomplish that. What is your current recovery?
The whole point about trying another ROM is elimination. It doesn't need to make sense, but you need to check things of the list.
There is something weird going on, so trying to solve it logically will only get you so far . Keep trying to narrow down the list of causes. Might well be a bug with Cronos 1.5, or the overclock not working these days because your phone is just a bit hotter than before, who knows.. Like I said: eliminate causes!

I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.

Try another ROM , and if that doesn't work, try without SD card.

tombond said:
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Click to expand...
Click to collapse
Maybe sdcard faulty? What are the logs you get when booting up the phone?

Soooo, I wiped everything again and flashed Modaco 2.8 without an ext partition. It booted correctly, so I wiped the dalvik cache and flashed Cronos 1.5.1 JIT. It also booted (wow, first time it booted without ext since all the problems started to occur) but I instantly got FC's (phone app for example). Now I wiped completely again and flashed 1.5.1 JIT. I hope it boots, as I still dont have an ext partition. As soon as I know something new, I'm gonna tell you.

So now it seems like its working again. I was able to install all the apps I need without a single error and now I'm restoring my settings and contacts. Suddenly it even works without ext again.
I guess there was something very big f*ked up that I couldnt repair by simple wiping the phone. Very weird that just flashing Modaco got it running again. Now I have back my working phone with ultrafast Cronos Rom and without App2SD, perfect. At least till now I hope it keeps working.
Thanks for your help guys, I think I would have smashed the phone to the wall sooner or later. I never thought about flashing Modaco so I'm happy there are people like you.
Thanks again, and thanks to Feeyo for his unbelievable Rom.
PS: Can I uninstall, Facebook and Footprints without destroying everything again?

Yes, just delete both apps using ADB or use a root explorer, search both apps in System/app and delete them.

Or you could use the MoDaCo online kitchen for removing those apps.

Repeated MAGLDR 1EFATAL HIT Errror after Task29 + radio flash

I had been running WP7 on my HD2 (TMOUS) for a while now. I had been running MAGLDR and although I noticed some bugs, I never had any real issues. Recently I flashed MAGLDR v1.13 on my device and continued not having issues. Then one day suddenly my device started rebooting on boot up (this had happened a couple times before) at DFT screen. I figured it was probably bugs in my SD card formatting. At some point the DFT screen froze once while I was at work and I pulled the battery. After I put it back in I got a FATAL HIT ERROR (of which type I don't remember, but I'm pretty sure it was 1E). Now I came home and did a task 29 and then I tried to flash clockworkmod and that's when I started getting the 1EFATAL HIT error on AD RECOVERY boot. I've done this literally 20 times and it either hangs or doesn't boot or restarts, or MAGLDR loads with a black screen and only title info on top. I also tried reflashing HSPL3 and that didn't fix the issue. I also tried flashing a stock 2.12...50 radio and it froze at 96% and so I had to flash HSPL3 back (the only one I could get to work). I also tried to flash an energyrom but it just hung at boot. I've also tried 2 different computers and 2 different cords.
Has anybody figured out how to fix this? I feel like this is a corruption/partitioning issue that task29 just doesn't seem to fix. I've seen about 10-15 threads with the exact same but no one has seemed to resolve it.

metroidnemesis13 said:
I had been running WP7 on my HD2 (TMOUS) for a while now. I had been running MAGLDR and although I noticed some bugs, I never had any real issues. Recently I flashed MAGLDR v1.13 on my device and continued not having issues. Then one day suddenly my device started rebooting on boot up (this had happened a couple times before) at DFT screen. I figured it was probably bugs in my SD card formatting. At some point the DFT screen froze once while I was at work and I pulled the battery. After I put it back in I got a FATAL HIT ERROR (of which type I don't remember, but I'm pretty sure it was 1E). Now I came home and did a task 29 and then I tried to flash clockworkmod and that's when I started getting the 1EFATAL HIT error on AD RECOVERY boot. I've done this literally 20 times and it either hangs or doesn't boot or restarts, or MAGLDR loads with a black screen and only title info on top. I also tried reflashing HSPL3 and that didn't fix the issue. I also tried flashing a stock 2.12...50 radio and it froze at 96% and so I had to flash HSPL3 back (the only one I could get to work). I also tried to flash an energyrom but it just hung at boot. I've also tried 2 different computers and 2 different cords.
Has anybody figured out how to fix this? I feel like this is a corruption/partitioning issue that task29 just doesn't seem to fix. I've seen about 10-15 threads with the exact same but no one has seemed to resolve it.
Click to expand...
Click to collapse
Mate, can you go into boot loader?
If yes, have you tried to reflash stock winmo rom using sd card method?
What is the result?
I m really curious because it might be there is damage or defect in The NAND, which can be known by the existance of bad blocks. If this is the case, task 29 is not really helpful.
My hd2 has bad blocks in the NAND, and now, I can't flash Android. Luckily, I still can use winmo rom all these bad blocks, IMO, is due to my excessive flashing habit in the past
Too check whether there is bad block, I flashed recovery via cLK method ( using command line in dos prompt) it can show you what happen during flashing..
Good luck mate

See, I thought it might have had an issue with the NAND blocks but the thing is practically new and all I flashed was WP7 ever so I doubt it's hardware. I think task 29 doesn't get all the blocks like you said. And yeah, I can get into the bootloader. I can boot into MAGLDR usually.
Do you have bad blocks? And after flashing back to winmo did you try flashing MAGLDR and then AD RECOVERY or WP7?
My thoughts were if I flashed a stock WM ROM, it would erase that part of the NAND and then I could go back to flashing.

I flashed it back to stock 3.14 (radio, everything was flashed back to stock) and it works like a charm. No unusual crashing or reboots so far.
NVM, just had one but it was a freeze and then it rebooted and now it's stuck at stick together. Will try restart. May be because battery is really low.
1:47:
Now it just keeps booting and restarting lol! I'm gonna try a task 29 and then wipe it again.
Wait now it booted. And then it restarted again. it seems to be getting closer and closer to booting.
1:50
Just booted into SPL to flash again and it says that it's still CotullaHSPL. I thought that the SPL was wiped with the method I used... Will come back to this forum later, have to do stuff. (going to trade my other HD2 for a Nexus S!)

Any news on this? Still having the same issue. Anyone resolved this yet?

I've been having the exact same issue, which I believe was initially caused by overheating.
I've had this phone for almost a year, and have gone through a handful of Android builds, both SD and NAND (more recently). Lately it has been having issues with high temperatures, to the point where I would have to hold it against an ice pack in order to make calls or use the internet. The phone would not operate if the internal temperature was over 93 degrees. If it passed the 93 degree mark, it would freeze, and gradually get hotter until I removed the battery.
I've been good about keeping it cool, and barely using it (other than texting), until it froze during a phone call. I turned it off for an hour and a half, and when trying to reboot, I would get the Fatal Hit 1E error. I've tried re-flashing, downloading new ROMS, and most of what the OP has said, and the error persists..
Is there any update on this issue?

I don't think my problem was caused by heat. What OS are you running?

My last OS was Ultimate Droid 3.3, which I upgraded to around the end of April. I was still getting the freezing issues in the OS I used before that, which I had since January, but was discontinued shortly after I installed it.
My last option is trying to go back to stock Windows mobile.

Let me know how this goes. I tried restoring stock winmo and it still had restarting issues.

i had same problem... lucky me i fix it
if any one of you has warranty immediately go for it, if not than read this thread.
Solving the thermal problems of HD2 or other snapdragon powered devices

My phone is fairly lukewarm when this happens. I don't think it has to do with overheating. It's never been that hot. Also it's under warranty until December so I'm probably just going to send it in if I can't software flash it. It also restarts on boot, before it can even get hot at all.

I think I'm going to try this later today. You guys should too and let me know if it gets you anywhere.
http://forum.xda-developers.com/showthread.php?t=908915&page=2

Nothing works as it should...

I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.

I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App

As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...

Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App

The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.

When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.

yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)

download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.

It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...

that's probably due to voodoo, which takes about that time to install/initiate.

Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh

Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.

I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.

If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.

There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.

That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App

Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...

Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...

es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...

4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.

[Q] Phone wiped and reset itself (NAND) after charging battery

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.