Related
simple really, everyone says to hard reset when you install a new rom, but at what point do you do it??
i normally wait till it pops up to tap the screen to set the phone up and then take the battery out, reinsert it and do it then.
is that the right time, or can you do it anytime?
sning said:
simple really, everyone says to hard reset when you install a new rom, but at what point do you do it??
i normally wait till it pops up to tap the screen to set the phone up and then take the battery out, reinsert it and do it then.
is that the right time, or can you do it anytime?
Click to expand...
Click to collapse
Personally I do it straight away, i.e. when phone is in splash screen. Just take out battery and hard reset. Obviously only real difference between this and yours is the time waiting for device to initialize to tap screen
so i'm correct in saying that it dosetn really matter when you do it, so long as you do.
in the same vien, why are some cooks now suggest 2 hard resets?
I've noticed in the screen where it says it is setting up you blackstone and there is a progress bar, that it seems like the first reset is quicker and the second and longer. I think that just insures stuff gets installed correct. There may be remnants of other ROMs still there that could cause issues.
I do mine after it has got to the Windows splash screen. I then do a factory reset.
Personally I flash straight from the SD card, so I get a white screen says "Update Done" when flash process is complete.
(in my case it doesn't automatically takes me to splash screen).
Then I take the battery out and perform first hard-reset. Right after I set up everything and i get the manila screen,
I perform a second hard-reset.
Normally I do it straight after it finish flash and the first screen when it start up..
sning said:
... why are some cooks now suggest 2 hard resets?
Click to expand...
Click to collapse
In most cases, some members just want to make sure. I always do the one hard reset with no issues. Mind you, I also use the mtty tool as well before flashing but that's just me....
I actually do the hard reset before flashing... since it is just to remove any traces of the old sys from RAM, it shouldn't really matter if one does it before or after flashing.
Plus: I don't have to watch the flash process and can just leave the phone unattended.
Semicuda said:
I actually do the hard reset before flashing... since it is just to remove any traces of the old sys from RAM, it shouldn't really matter if one does it before or after flashing.
Plus: I don't have to watch the flash process and can just leave the phone unattended.
Click to expand...
Click to collapse
Actually Hard Resetting After a flash is highly recommended, not before. Although it won't hurt to hard reset before, however it will not help avoiding bugs unless you hard reset after your flash.
Care to explain why? The non-ROM parts are cleared either way, and I have yet to encounter any bugs that are fixable by hard-resetting again...
Semicuda said:
Care to explain why? The non-ROM parts are cleared either way, and I have yet to encounter any bugs that are fixable by hard-resetting again...
Click to expand...
Click to collapse
i cant explain it, but a HR has cured some bugs for me. (i've had bluetooth fail to work on cooked roms; HR fixed it).
for the 20seconds it takes, why not! saves you having to spend 30mins later on reconfiguring/reinstalling
There seems to be a belief by many uneducated users in these forums that multiple hard resets somehow make a difference, or that there may be bugs/issues with phones that haven't had a hard reset done to them after flashing.
Somehow, people have it in their mind that the reset that the phone does after the flash has been done >doesnt< totally clear out the RAM/ROM/memory of the device, and that traces remain of the previous ROM, or perhaps bits in memory are not set correctly.
This doesn't happen. Phone memory isn't made of putty or clay. Flashing a stock phone with a cooked ROM doesn't leave some bits of memory set with their old values. Flashing a phone with a ROM that's slightly smaller than the previous one doesn't leave those extra bits unset. Hard resetting a phone multiple times doesn't miraculously reset "stuck" bits that didn't quite get flipped earlier.
Sorry people, but memory doesn't work this way. ROM and RAM in your phones doesn't somehow act differently than ROM/RAM in any other computer. These beliefs are almost always generated by people that aren't quite clear on what actions they are following when flashing their phone. They may be installing additional code after flashing, making configuration changes, or have an auto-install feature active. Or their phone performs different actions based on their location, native language, or carrier. Or the phone's radio ROM interacts differently with the new ROM.
All of these can cause a newly-flashed phone to act unpredictably. NOT because they didn't hard reset their phone twice. NOT because they didn't flash their phone back to a base ROM before updating to a cooked ROM.
When a phone is flashed, ALL memory (ROM + RAM) is re-initialised, regardless of the new ROM's size. There are NO traces of previous ROMs remaining in memory. Safeguards in the flashing process ensures that the code being flashed does not have errors in it. The flashing process also checks for errors in the phone's memory chips to ensure that no hardware errors exist.
These are fundamental activities that happen during all flashes on all phones. There simply isn't any way for a flash to "not quite work". It either completes successfully and reboots, or it doesn't complete successfully and you brick it or are forced to try again.
Resetting a newly flashed phone multiple times is pointless and is simply an act of the uneducated masses rubbing their lucky rabbit's foot or praying to their deity. Do it if you like, but please don't post messages instructing others to do so because it's a necessary step. It's not.
douginoz said:
There seems to be a belief by many uneducated users in these forums that multiple hard resets somehow make a difference, or that there may be bugs/issues with phones that haven't had a hard reset done to them after flashing.
Somehow, people have it in their mind that the reset that the phone does after the flash has been done >doesnt< totally clear out the RAM/ROM/memory of the device, and that traces remain of the previous ROM, or perhaps bits in memory are not set correctly.
This doesn't happen. Phone memory isn't made of putty or clay. Flashing a stock phone with a cooked ROM doesn't leave some bits of memory set with their old values. Flashing a phone with a ROM that's slightly smaller than the previous one doesn't leave those extra bits unset. Hard resetting a phone multiple times doesn't miraculously reset "stuck" bits that didn't quite get flipped earlier.
Sorry people, but memory doesn't work this way. ROM and RAM in your phones doesn't somehow act differently than ROM/RAM in any other computer. These beliefs are almost always generated by people that aren't quite clear on what actions they are following when flashing their phone. They may be installing additional code after flashing, making configuration changes, or have an auto-install feature active. Or their phone performs different actions based on their location, native language, or carrier. Or the phone's radio ROM interacts differently with the new ROM.
All of these can cause a newly-flashed phone to act unpredictably. NOT because they didn't hard reset their phone twice. NOT because they didn't flash their phone back to a base ROM before updating to a cooked ROM.
When a phone is flashed, ALL memory (ROM + RAM) is re-initialised, regardless of the new ROM's size. There are NO traces of previous ROMs remaining in memory. Safeguards in the flashing process ensures that the code being flashed does not have errors in it. The flashing process also checks for errors in the phone's memory chips to ensure that no hardware errors exist.
These are fundamental activities that happen during all flashes on all phones. There simply isn't any way for a flash to "not quite work". It either completes successfully and reboots, or it doesn't complete successfully and you brick it or are forced to try again.
Resetting a newly flashed phone multiple times is pointless and is simply an act of the uneducated masses rubbing their lucky rabbit's foot or praying to their deity. Do it if you like, but please don't post messages instructing others to do so because it's a necessary step. It's not.
Click to expand...
Click to collapse
nice,thanks
@douginoz - thats exactly what i beleive too (or used to!)
however as i mentioned before, i had issues with a cooked rom (wifi or bluetooth wouldnt work correctly)
a HR cured it.
now this could of been a bad initialization of the rom from the get-go, however based on the fact that a flash resets the phone completely, it didnt correctly work *immediately after the first flash*.
weather it's placebo affect, i dont know but i've also experiencing slightly slower performance on no HR rom, vs a HR after rom flash.
as always, a bad install could happen at any time. i'm merely going off my own personal experience between doing a HR and not doing one. no HR after rom flash has given me atleast 2 issues. HR after flash has NEVER given me an issue.
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 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
Hi everybody,
I've been playing with my HD2 for a while (almost one year) and I'm experimenting my very first problem.
Currently under NDT MIUI v4.1 rom by Langthang, my phone is randomly freezing or hotbooting (rebooting without passing by mgldr).
I've tryed flashing ICS beta roms two days ago, the problem started at this point.
The OS was rebooting on his own without warning, even at the first boot after flashing.
Then I came back to stable releases.
And another problem appeared, the phone is getting stuck in mgldr (while booting on nanf or recovery)
I'm wondering if the nand isn't damaged as I've flash several other roms and the problem remain. I've also wipe and flash everythings needed more than once, without any impacts on it.
I'm running out of solutions, I think I will do a RMA and try to get a brand new as the phone is still under garantee if I don't fix it before the end of the holydays.
Someone got a idea on this ?
P.S : and Happy Xmas
P.S 2 : same problem under official WinMo 6.5 with 2.08SPL
have you fully task 29, reinstall winmo, and than hspl, than task 29 again and flash magdlr/ or clk. as that removes alot of the bad blocks associated with constant flashin.
Well, I've done : task29, SPL 2.08, WinMo, task29, HSPL 2.08 then mgldr/cwm.
I cleared some space on the internal storage, freezes and hotboots seems to have disappeared.
Anyway, I'll try later these operations in the order you said to see if it'll fix that.
Thanks for the answer
How old is your SIM card? I had been having increasing problems the past several months, which couldn't be solved by anything - task 29, revert to stock WinMo, reinstall HSPL, even tried flashing stock voltages.
A few days ago I activated a new SIM card, and all of my problems seem to be solved!
I have the same SIM card since 2 years or so. But I can't figure out how I'll explain to my operator that the SIM is dead
For unknows reasons, the phone seems to run well after having cleared almost 50mb of app on the nand. I'll try to fill it once more to see if freezes comes back.
Re SIM Card:
At least in the USA, there is no need to explain why SIM card is dead. I happened to have a brand new card (came with my HD2) which was never activated. All I did was call customer service and they activated it for me over the phone, no questions asked. If they give you trouble just tell them you lost the old one.
Also, they should be cheap to buy if you need. T-mobile sells SIM cards online for US $10.
Well, I've done steps by steps what tecle suggested me, and it works great so far.
I'll contact my operator to see if they can replace my SIM
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.