PDA

View Full Version : radio problems


rocqua
24th April 2009, 08:22 PM
i appear to have a corrupt radio, though it might (i hope not) be a radio hardware problem.

the problem is that i get the NO GSM error, combined with freezes (i feel the 2 are connected, for a while i didn't have the error, and it didn't freeze either).
i first figured it was a radio problem, so i attempted to flash a new radio. it simply went to the progress bar, on both my PC and hermes, but it stuck at 0%. then it tells me the upgrade failed, error 262, the standard procedure, and then i can't do anything, have to reset the device, it boots into bootloader, i use the set 16 0 command with mytt.exe, and i can boot back into OS, still without phone function.

the problems started either when i both CID and sim unlocked the device, or after that when i installed the newest offical HTC rom (which contraines a radio, right?).

the real problem is the NO GSM, and that whenever i flash a radio, i get the error 262 problem, and everything around it i described above.

any help would be greatly apreciated, since the device is basically useless to me right now, since it freezes, and can't be used as a phone.

Model: herm200, vodafone 1605
ROM Before Flash: shipped rom (don't know which one)
Radio Before Flash: shipped radio
Bootloader Before Flash: 1.04
Flash failed at: didn't fail
Flashing ROM: any radio
Flashing Radio: any
Bootloader After Failure: hard spl 2.10
CID Before Failure Super CID: success
CID Corrupt: no
Radio Corrupt: probably
No GSM Error: yes
Stuck In Bootloader: no
Stuck On Windows Mobile Splash: no
Can boot into OS: yes, but freezes after about 30 minutes
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: cmd> instead of usb> but it works, used set 16 0 a lot of times after radio flash.

rocqua
26th April 2009, 01:36 PM
no one can help me? no suggestions at all.

if i have no choice i'll have to send it to the repair center.

bmaggot
26th April 2009, 02:51 PM
i have the same problem, but i didn't do anything to my device..

it usually disconnected from network once or twice a week and asked for my pin but that was all

and all of a sudden it started disconnecting every 30-60 minutes or so and i couldn't receive sms and calls but occasionally i could send them myself

and now it does not connect to a network and when it rarely succeeds, calling someone freezes the phone, and noone can call me because it says that my phone is busy

i tried flashing to shipped rom but no luck

rocqua
27th April 2009, 03:41 PM
it seems then that we are dealing with a hardware problem, but i'd still rather not send it in for repairs until i have to, since the CID unlock surely voided my warranty.

bmaggot
29th April 2009, 11:35 AM
now it is clear that i have h/w problem, sometimes when starting up it shows "no gsm" and sometimes not

AND it is possible to revive gsm capability when pressing device at lower part of the battery, seems like some wire got disconnected

stim141
1st May 2009, 12:25 AM
That sortof confirms that there is a design flaw with the Hermes. I have the same problem - very interesting that you can press on the lower portion of the battery to get it going. I think whats happening is that the metal backer plate - behind the battery is too close to the chip heatshields on the mainboard The excess pressure overtime is what is killing the radio. Constant pressure or battery expansion from heat (charging) presses against the plate and against the chipsets either weakening the joints or flex micro cracking the motherboard which is multilayered.

Pressing on the battery more than likely makes the connection again but will break again.

On mine I left it working on my desk for a week - checked it daily by rebooting and it still found the radio. As soon as I took it out of the house and used it for a day it starting acting up. Phone was in a SENA flip case - initially thought it was the magnets messing up the phone but it wasn't that. The heat from the interior 80F outside - hot inside of the car was the problem as I would also get some white screens and freezing. Took out of the car - cooled it and the whitescreens went away and the GSM eventually came back - although not for long.

Orenk
3rd May 2009, 01:53 AM
I have exactly the same problem.
When I Flash through Windows XP, it hangs on 0%, with error 262.
after reset I get Tri-color screen.

When I Flash through SD, it hangs about 10-20%. After reset I get tri-color screen.

I Tried few radio versions, also,
I tried the original radio version. I Get the same symptoms.
I Tried to upgrade .NBH and .NBF files.

I Have HERM100 - Jasjam.
The WM Version is irrelevant (I Even tried to downgrade to WM5).
The HERMES worked fine before, it had radio ver 1.03 or something...
IPL 1.04
SPL 2.10.Olipro

Any suggestions anyone ?

stim141
6th May 2009, 02:28 PM
Had the same issue - the radio in this phone fails due to heat/pressure and I think the solder joints to the chip are bad and develop cracks over time. You can flash all the available radios and ROM sets and it still will not improve. Just buy a KNOWN working beat up phone on eBay for a little money as possible and swap out the board if you screen/casing are in excellent condition. Be warned though I think several people are doing the same thing and the bidding is pretty fierce. Did the same yesterday but I bought mine locally for 40 US which is a pretty decent deal since most on eBay are going for 40-60 plus shipping. Phone was in decent condition but it had a bad digitizer - the LCD looks perfect - maybe I'll try and replace the digitizer and keep it as a spare. The seller did a hard reset and couldn't get past the setup screens.

The phones's dPad and flex were perfect whereas mine are suspect. Swapped the motherboard last night in about 10 minutes total and everything works perfectly. Do have to CID/SIM unlock it as it was an AT&T phone. Will swap the dpad and flex this weekend. I also will look at the solder joints under a scope to see if I can see if anything is wrong with the joints. That will take a while.

Mastha-Hacker
7th May 2009, 09:08 AM
Hi,
I have the same problem.. Isn't there another solution??

stim141
7th May 2009, 02:09 PM
No - you can't fix it just by doing another flash because no one is home or is on their way out. Its a chipset failure PERIOD and the board has to be replaced or the phone scrapped for parts. There are too many of these problems to just be coinsidence there has to be some sort of design flaw with the chipset, motherboard or overall design of the phone because if the phone works for a month after its made it should continue to work if the components and design were sound - not including any physical damage.