No bad block, but randomly hard reset with WM 6.1???

[vichet007]

Dear all,

I am having a problem of random hard reset or stuck at boot sreen with WM 6.1 (ShadoW and Faria). I had check if I have bad blocks but the results are as follows:

Cmd>info 2
HTCSSuperCIDHTCE
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x1D700
Partition[3], type=0x4, start=0x20900, total=0x1E700

CE Total Length(with sector info) = 0x4224800
CE CheckSum Length(without sector info) = 0x4120000

Cmd>task 2a

Cmd>

From my understanding, it has no bad block. I noticed that I never have this problem with WM 6 with many flashes. I started havig a few hard reset with ROM SadoW 2.1TE and several problems with Faria and Faria R3.2/ Dr. P. It sometimes stuck so when I do a soft reset, it stucks at boot screen.

Your responses will be very much appreciated.

[miffymiffy]

i was having the same issues with both roms and like yourself thought i had bad blocks, turned out i didnt so i reflashed shadow ce and then its been good since, I bypassed doing the service providers rom and it is running fine.
my thoughts were that it was these roms.

[ultramag69]

Had same problem with a few WM 6.1 roms. It seemed to be after I'd synced for a while with active sync on my computer. Since WM 6.1 Hasn't been "officially" released just yet I'm wondering if there might be an upgraded version of activesync coming too.....

[larsuck]

I'm wondering if there might be an upgraded version of activesync coming too.....

Doubtful. Since WMDC is now part of Vista, my bet is they stop ActiveSync development altogether. But to be honest, ActiveSync has been dog puke for as long as I have been messing with PPCs and I think it might not be a bad idea to throw that baby out with the bath water.

Edit: To address the topic, the idea has been floated that this problem has something to do with superstorage.
Question: Has anyone had this problem with a non-superstorage ROM?

Also, I have noticed that this problem often presents itself in the ROM after the ROM responsible. So for example, an install of Pandora Naked 9 (a 6.1 ROM) will have no problems, but then after installing Pandora 7 (6.0 ROM) trouble starts.
Question: Has anyone had this problem with their first 6.1 flash?

[Fallen Spartan]

I think it might not be a bad idea to throw that baby out with the bath water
If they get rid of Activesync, how will we sync are ppc's to computers?

[tonyb15re]

I think he has done what quite a few people on here do, confuse the Desktop AS with the PPC AS.

[vichet007]

Thanks to all for the respnses. I am now going to K's final 6 to see if this is because of the specific 6.1 ROMs (ShadoW and Faria/Dr. P). However, I wonder that many people using Faria/Dr. P had confirmed that they did not have such kinds of issues. If they have, it is because of bad blocks.

Other users having semilar issues may want to report if this is because of specific 6.1 ROMs or hardware or something else on this thread.

[larsuck]

Other users having semilar issues may want to report if this is because of specific 6.1 ROMs or hardware or something else on this thread.

I agree. Maybe we can notice a pattern or two by listing our problems.

I'll tell you some things that I have noticed, or think I have noticed.

First, the two things I said before: that problems seem to occur in the ROM flashed after the one that seems to be causing the problem. And that the problems seem to happen only with superstorage ROMs.

Also, I have noticed that of the number of times this has happened, for some reason it seems to happen a lot when recieving an SMS.
Two times the ROM froze when I was reading new SMSs.
Once it recieved a SMS, started vibrating and just kept on vibrating.
After all three of these times a softreset with the stylus hard reset the device.

Although I have only checked it a couple of times after these kinds of problems, I have never found any bad blocks on my device.

[MrDSL]

I had the same problem on Farias 6.1 ROM and checked for bad blocks and that was fine. I really have no clue what was going on but I just flashed an offical at&t wm6 ROM and then went back to Farias ROM and all is fine now.

I wish I knew the answer on what was wrong whether its radio related or superstorage etc..

[Bruce Inman]

My first 6.1 ROM that I flashed ran smooth for 2 weeks then froze at the end of a call. I did a soft reset and it froze again at boot. I did another soft reset that resulted in a hard reset. I flashed a "more current" version with bug fixes and now nothing works right. I do not believe these were Big Storage ROMS, these were Dutty's latest ROMs.
I have had issues with both Activesync and WMDC as well as internet sharing and many other bugs, but only with the 2nd ROM.
I am going to try one more non-Dutty 6.1 and see how it runs, if it craps out I'm going back to 6.0

[8525MD]

I too have had freezing problems resulting in a soft reset. Each time I did a soft reset it wiped everything clean. Also my WMDC up to that point worked fine and this last week nothing. I have since gone back to att official and two days no problem......WMDC still doesn't work....:mad: This all started when I flashed the Shadow 2.1 rom. I cant say that it was the problem but that seems to be when it started.

[burkay]

I had the same problem with shadow and pays 6.1 roms. I had the problem in my first and second flashes. So the first flash may give you trouble as well.

The weird thing is, the hard reset is not really a hard reset. The first time my soft reset resulted in a hard reset, most of the things were truly hard reset but some settings related to old programs stayed there. I was quite surprised to see that my settings were preserved after what looked like a hard reset.

My guess is, if you switch from a big storage rom to a normal storage rom or vice versa, the storage space is not properly formatted and some "junk" from the old system stays where it shouldn't. These leftovers mess the system up in time. Buffer overflow?

After going back to pays 6.0 rom I didn't have any hard resets for a long time. Then I wanted to risk CRC's latest 6.1 rom. So far so good.

[vichet007]

OK, the problem seem be solved right now (after more than 24 hrs test):cool:, but I still continue to test more:rolleyes:. What I had done is:

1. Go back to official "AT&T official ROM WWE 3.62.502.3_6275". And it seems that it works with this one only (basing on my try). I had tried other versions of official ROM, but the problem is still happening. You can find this version here (http://www.htc.com/us/support/8525/software-downloads.html).

2. Then flash Schaps 4.31. This step may not be necessary. The reason that I flash this is to change the boot screen that I like.

3. Finally flash Faria R-3.2/Dr. P. Untill now (after 24hrs), there is no any hard reset or stuck yet. Anyway I still continue to test this.

Reasons for problems I had noticed:

Here is the history of 8 lastest ROMs I had flashed:

Schaps 4.31 (no problem) -> K's Rom v1.30b (no problem and I like it so much) -> Schaps' 6.1 Pro 4.40B (seem to be no problem) -> Pandora Naked 9b1 (seem to be no problem) -> ShadoW 2.0 and 2.1TE (the problem may start from this) -> Faria and Faria R-3.2/Dr. P (and problem may continue to this).

I think that's what I had learnt...

You may also want to share your experiences if you had the same/semilar problems and solutions here..:D

[milleniumbug89]

[did like you desribed, but not solved]

I think that this is a serious problem, because it seems so many users got it...

I post my experiences here:

I think it is not a problem of the radio Rom, I have tried 1.33.31.00, 1.48.00.10 and 1.54.30.10 and not solved...

the only two Roms that work without problems are CRCs PHK v12 Release 10. (WM6.1 Build 19209) and "storm" ...

I also tried flashing olipro's SPL 2.60 (before had 2.10), thought that might be what gave the problem...

To me, and also to my friend, the problem began after the flashing Rom "S64 WM 6.1/HTC v2 World Wide English 30.03.2008"

Abid885 in other topic (http://forum.xda-developers.com/showthread.php?t=386865&page=2) says: "Im also having the same problem .. all sorts of experiments has been done to test on why WM6.1 crash when I install them .. but 1 thing i noticed that it always hang before softreset that eventually lead to hardreset .. i thought hardware accelerations problem ... so what i do is .. every changed to the WM6.1 8mbpp .. until now my machine ok. "

I have not tried since I've to play tennis but could be a solution I'll tell you later when I come back...

p.s. i not exclude the "bad blocks" issue but is strange that some rom work and others not... so i will update you later ;)

EDIT: NEW IDEA: I noticed that just before the phone completely blocks, you lose the first all links programs folder, then the links in the start menu and in the end no longer anything ... This reminds me of when in the very first rom windows mobile 5, the phone did the same thing ... The problem in that case was solved by changing drivers ( or rewriting, i can't remember...) .. This would be consistent with all the problems of our Hermes probably the rom were working, were built with kichen different from those used for "not working Roms" , and so on newer motherboards, the Roms work while those older no ...

I think this is a possible cause...

[milleniumbug89]

p.s. MODS or lyhuoth can you PLEASE change the title of this topic, cause the problem is NOT solved? :D thanks ;)