Related
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
Hi guys,
Upgraded to 1.16 radio - (Tmobile UK ROM)
This kept 'hanging' so upgraded to 1.20 - this failed
Left with NO GSM - followed steps as requested set pass etc.
Still wouldn't upgrade
Tried to put latest ROM on (South african?) this FAILED but installed boot load 1.09 - argh!
BOUGHT (£20) the imei-check to downgrade - this WONT WORK - keep failing!!
Please help - stuck now - phone boots - but has NO GSM all the time...
Please help!!
please attach a usb monitor capture of a full rom upgrade until it fails. Probably will be "cid not allow (255)", but just to make sure.
No T-MOB001 rom exists yet
Did that - thats exactly where it failed!
Is it stuffed? :-(
I don't know, never had one of those with "NO GSM" error on my hands.
Probably as radio is screwed CID is corrupted and you'll not be able to flash a ROM even with your original CID. I think for you the best would be to send it to service centre.
Yeh, thought it may be stuffed! FUnny thing is, when I do a hard reset, it doesn't have the NO GSM, it reports 1.16.0.0, it's as if the T-Mobile customs reset it all. Is there any way of stopping the customs?
Regardless, I have had the phone < a month so I'm ringing customer services to see what they can do - maybe not admit I've tried to upgrade it just yet!!!
roger said:
Is there any way of stopping the customs?
Click to expand...
Click to collapse
I guess by "customs" you mean the Extended Rom, if yes, just do a soft reset before it installs (3 seconds). But I don't think it would do any difference...
Ok- update to problem,
Managed to downgrade from 1.09 to 1.04 of bootloader usining IMEI-CHECK.
Did HARD RESET and plugged in hermes when "press screen to continue" came up (just booted) linked to ACTIVESYNC then ran the software IMEI-CHECK sent me, this connected to hermes and asked for .unl file from imei-check. This 'downgraded' to 1.04 of bootloader.
Then managed to install a 1.13 radio rom - hermes still kept hanging -but I could use phone a little (managed to make 2 calls before a lock up). I was going to re-install another full rom upgrade - I think this may have sorted it, but by this time I had rung T-Mobile support in UK and they agreed to replace unit (I pretended it had gone wrong 'all on its own' hope Karma doesn't catch up with me!)
I THINK I would have managed to sort this using the solution from IMEI-CHECK and this forum by reapplying another full ROM upgrade. So thanks to everyone for their help! Hope this is of some use to someone!
I was flashing my tytn with the new rom with bootloader 1.09 after 8% the usb cord came out and now my tytn is dead its stuck in bootloader mode..spl 1.09...please help
I am also in this boat, except my usb cord didn't fall off, it just stopped updating at 6%.
Connect to the device using mtty and type info 2. If you're CID is corrupt, then you're out of luck just like me.
It seems that the only way to fix this problem is to send the unit back to a service center and get the main board replaced. Unless anyone else has any other ideas. In BL 1.04 you could bypass the CID check but in 1.06 and 1.09 that bug has been fixed.
Great job HTC, you really messed everyone up now, I hope you're ready to start replacing some board on account of your ignorance to create a sufficient backup routine. I guess this means less money of new development and less devices from HTC in the near future.
Because you're in bootloader mode, you might be able to flash the 1.04 bootloader downgrader in; which would then allow you to re-flash any firmware.
Nope, even in boot loader mode I can't go back to 1.04. It doesn't recognize the CID and keeps saying invalid vendor id.
The only possible fix I can see is if someone hacks the hermes and finds a way to cook a rom and not check the CID. Otherwise, it's a full board replacement.
Somehow there has got to be a way to "Bypass" the CID check.
What I was trying to say, if you use the IMEI-CHECK downgrader it will bypass the CID checking enough to get you back down to 1.04?
Yes. Imei-check downgrades your bootloader to 1.04
sn00x said:
Yes. Imei-check downgrades your bootloader to 1.04
Click to expand...
Click to collapse
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
I've tried everything possible to get out of bootloader mtty says my cid is corrupt.does anyone know a number for the service center
depends on your country, go into htc website and look at it:
http://www.htc.com
Pof you are correct. The CID is completely corrupt, the radio sectors have a bad record, and the phone can't boot past the windows mobile splash screen. So the only way we can fix this problem, is to hack the flashing of the rom to not check the CID at all. If this can be done, then we're in business.
On another note, I've been seen 1 of these problems arise every day now. Someone either pulls the usb cord or the flashing just crashes.
I think there is a serious enough priority to hack the hermes rom flashing now aside from crossbow. We really need some resources on this so that we don't ever have to go through these problems again.
In the words of Russel Peters (a famous Canadian comedian)... Pof, be a man, do the right thing. Hehehe.
pof said:
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
Click to expand...
Click to collapse
But does that "other solution" which can't be posted here anymore bypass that requirement, as it runs through the bootloader and not activesync?
no it doesn't. The update still checks the CID before updating.
And it also needs activesync to transfer the fake bootloader to the device... remember it starts with M3100v3cUnlock.exe too....
Ooh, forgot about that bit .
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!
Hi all,
First of all I want to let you know that I did search the forum for a solution. In fact, I found a lot of workarounds but none of them actually worked.
Let me give some details about my problem: My Hermes was working fine. I was running the official WM6 ROM supplied by HTC, so no customized ROM here.
It was going fine until the WM frozed. Then I soft reset the device and after that I never got cellular signal again.
While booting the device I got the message: "no GSM".
First thing I tried was to flash a new radio ROM. In all the attempts the progress bar never moved from 0% and after a while I got the communication problem error.
Then I tried flashing a whole ROM. This time the progress bar stopped at 81%. Apparently in the first 81% it flashes the OS and in the last 19% it writes the radio. Anyway, I tried this a few times and never finished.
In fact, after every communication error message I got stuck in the bootloader screen.
The only thing that works is to flash a ROM WITHOUT the radio!!
Is there anything I can do to save my phone or am I condemned to use my Hermes as a phone-less pda?
I tried everything I found in the wiki/forums, but I couldn't find a working solution.
I suspect that the blocks of memory where the radio data reside got corrupted, could that be possible?
PLEASE HELP!
thanks in advance!
Chris
A similar thing happen to me several months ago. While on a call my phone froze and when I soft-reset it the dreaded 'No GSM' issue appeared. I tried flashing radios/full roms/etc, but nothing worked. I ended up sending my phone to the htc repair facility and they fixed it at no cost. (Other than not having a phone for ~10 days)
Thanks dang, but I don't have a HTC service center where I live (Argentina, LATAM)
I'm faithful that the people of this wonderful community will be able to help me.
Just for curiosity, where did you send your device? Is it in the US?
cheers
sounds like a hardware problem to me...
Hi, there! I found that a lot of us who have bricked our Hermes, don't have a responsive radio bootloader, so when they try to flash a full rom, the progress bar hangs to 13%, or 81%. This is because at that time the flasher is trying to enter the radio bootloader, but because it's corrupted, it hangs. Till today there is no known solution to this one. I'm far away from England where I bought my Hermes, so I'm not thinking to send it back for repair. I'm a programmer, so my knowledge may be usefull here. The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
How can I try that?
windshearx said:
The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
Click to expand...
Click to collapse
You can use 'lnb' in HardSPL without having a real SuperCID; however you will not be able to flash a radio with 'lnb' command. The radio chipset has its own bootloader, the and the SPL just acts as a pass-through sending the data directly to radio chipset through the s2410 UART.
I had one device with non-responsive htc_boot and tried all kinds of SPL patches to flash htc_boot again on radio, without success. The only known method to fix this is to take the BGA chip out with hot air and reflash it with special hardware, as it is not common to have this equipment at home, your only option is to send it somewhere to do it for you.
However, I don't want to discourage you to research on it, maybe you find something i didn't
I have a similar problem
I also have a NO GSM and corrupted CID but I can access KITL and use it with PB 5.0. and I followed this steps here but the phone doesnt boot completely. It stops just after the two boot screens on Black WM6 ending on a white screen and the debug window on PB after loading all sort of things begin showing these lines over and over:
@@@@@@ HUB state changes now @@@@@@
[HDC]HubStatusChangeThreadPN TRUE
[HDC]HubStatusChangeThreadPN FALSE
Is there any hope for me? I have the cingular 8525
thanks
Gents, do you think the solution presented in http://forum.xda-developers.com/showthread.php?t=280425 could help me?
Please advise.
thanks again
chriscec said:
Just for curiosity, where did you send your device? Is it in the US?
Click to expand...
Click to collapse
I sent it to the HTC service center in Texas, US.
I just got my replacement from ATT.. Had the same problem. Its a hardware problem.. I wouldnt waste anymore of your time.
first, i'm sorry for my english
I've the same problem with a V1605 (french SFR), i've tried every solution but flash radio doesn't work.
I can flash cooked os without any problem, but it's impossible to put official
It's only a pda now, it's better than a brick
My hernes use to be the same as you 'NoGSM'.I tried to install the official rom,but it 's not work at all.I called to service center ask this problem,so they said that it must be only changed the mainboard. That 's terrible!!!
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
otoro_315 said:
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
Click to expand...
Click to collapse
That only works with phones with KITL...which I don't seem to have.
Sorry, how to config the phone with KITL and solve the no gsm problem.
No GSM but when sim inserted
Hi all, First sorry for my bad english.
I also have 2 bricked Tytn Hermes 200. Its not my personal ones Its my company's property, which pple were using this phones. So i'm facin with problem which many pple here having but with exception. both phones having no gsm error when sim inserted but without sim its fine. In other words , device info showing every info including IMEI when sim unavailable. And some times works with sim but after making few call and receiving phone hangs(not system) and goes off from network but anthena signal still showing few bars. I'm thinking maybe the radio hangs totally and goes off, and after soft restart NO GSM. I also tried many flashing upgrading those things nothing can really help me.
When im flashing original rom from HTC (the latest one HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108) its hanging on 12% and doing 3 or 4 times recovery , but its finishes succesfully. So what exactly happening in 12th%?. Maybe its started flashing radio and stopped on bad block ? But then why its finishes succesfully after few retry?. Ok so if any one wants to experiments on the phones except radio welcome. I'll help. And some can give me quick example of how to check bad blocks?.
Tnx.
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
otoro_315 said:
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
Click to expand...
Click to collapse
My device is still SuperCID and I know I don't have KITL...I have SPL 1.04 as well and HTC Bootloader is 0108. I can't install any ROMs with radios as they will hang at 11/12%. I will attempt this "overload" method where it seems some people have had luck with it...after a few recoveries it just finally installs...but I don't think that will be the case.
If I can't fix this in a few days, I will most likely use my warranty or just wait for the Kaiser.
My variation of No GSM
I feel like I have problem 1A...where I am able to boot into OS but no GSM.
I am still SuperCID, SPL 1.04, HTC Bootloader 0108. Last known radio before corruption was 1.48.00.00. ROM where this problem occured: VP3G 3.60.1.
I was not even in the middle of an upgrade...just a soft reset after my phone ALREADY lost GSM capabilities during a tether session. It was stuck with no signal in Phone Mode...I put it in Flight Mode...then tried to move it back to Phone Mode and it wouldn't do so. I soft reset...and the no GSM stuck.
I tried to reinstall radio...many errors...stuck on bootloader. At first, OS's only were not installing as well but I got past that. Now I am able to boot into OS's with limited capabilities...and they will NOT ACTIVESYNC at all. Regardless of how old or new the ROM is. I tried older OS's that I knew worked in the past for me...but they refused to activesync.
Due to that, I am not able to install latest HardSPL 2.10Oli via SSPL. That seems to be the only way to do it according to my knowledge and what I've read. Maybe mtty was capable but I'm not sure. HardSPL 1.40Oli wasn't giving me any problems though, but I just wanted to have the latest one so I can avoid IPL damage.
I can only install anything if I start the device in bootloader...and I'm only limited to the OS since my Radio Bootloader seems corrupted.
I'm not sure what caused the corruption in the first place...but I feel annoying now posting on different parts of the forum with a problem that seems to be growing in the community.