Hello,
My XDA I (ROM: 3.17.03 SER v1.2, Radio: 6.24.00) all of the sudden had a GSM failure this morning, which could only be solved by a hard reset, and I was wondering if someone could offer an explaination (or point me to one) of why this happened.
I read all through these forums for a solution before attempting the hard reset, and it appeared that most GSM failures were caused by failed radio upgrades, and weren't resolved by hard resets.
In my case, I have not had any upgrades lately, and the device was working beautifully as of this morning. I had been on the internet earlier, so I know it was working then. I only noticed the problem after transferring files to the XDA from my PC, then disconnecting it from the PC. It was running slow, the back light was flashing on and off, and I had no signal. The bootloader confirmed the GSM failure.
The only thing I can think of is that I have ActiveSync set to do an automatic backup of the RAM each time it connects, but this time I cancelled the backup (as I do many times when I'm in a hurry). The backup screen says not to use the device while it is backing up, but it seems like it is just a simple file transfer, and I've done it many times before without hurting the device.
Any thoughts on this?
It would be very rare if not impossible, for software to accidentally flash write to memory, I think it is a hardware fault.
I don't think it was a h/w fault or it wouldn't be solved via hard reset. I believe that the RSU code deals dynamicaly with a shared part of the memory with the ROM which in this case (cancelling the backup) was not stopped in a neat manner. This can be compared to power off your PC while windows is updating the FAT area data on the hard disk. This may leave you with a corrupted OS that can't be solved except by reformating the hard disk which exactly the same like XDA hard reset, but again I agree it's a very rare situation.
I misunderstood, when you said "hurting the device" i assumed it was a permanent fault.
Related
I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
Hi experts...
Well, I have just recently upgraded to WM2003SE with ZeroXtreme modified ROM. Lately, while I was using my xda 2, probably it process pretty much heavy task and got hang. I did a soft the first time, it was somehow froze at the splash screen. Thought I waited longer than the usual time it'd load to windows, impatiently I soft reset the second time.
Surprisingly It proceeded to the align window which was actually done by hard reset. I was still puzzled even now, wonder whether it does happen like with the upgrade or just on my machine.
However, before this happen, I did somehow accidentally got my xda 2 knock against the ground quite lightly and a little scratch was on my baby's... Not sure if that was part of the cause of the auto-hard reset?
After reinstalling all applications back, I did some trial and error to test if it reoccur by soft resetting a few times and pressing multiple buttons simultaneously or any other way that I could think of to test out.
And so far it didn't auto-hard reset again. But, sometimes, if I soft reset it, it'd froze at the 2nd splash screen (the first splash screen where it displays the rom version,etc for short). Hence, i need to soft-reset it another time to get back working.
Experts please give advise or anyone experience the same occurence please do share. thanks.
Hi buddy,
The hang/delay while soft reset seems to be a common problem for 2.06 ROM. I have the same problem as well. Someone suggested the XCPUScaler could help a bit and it does....well, not totally. Sin from Australia suggested a merge of 2.02t and 2.06 ROMs can resolve the problem. I haven't try it yet but if you would like to give it a go, do a search in the Forum.
Have a great Christmas!
Cheers!
Check the DB_notify_queue database as it might contain lots of records ... use CheckNotify to clear it as the clearnotify.exe fix doesn't
P.S: it shouldn't contain more than 20 records in average
Biso007 said:
Check the DB_notify_queue database as it might contain lots of records ... use CheckNotify to clear it as the clearnotify.exe fix doesn't
P.S: it shouldn't contain more than 20 records in average
Click to expand...
Click to collapse
Hi!
I use CheckNotify and check that they were 21 records. I guess it's normal then, since you said it shouldn't be more than 20 records. So, do you think I should still run the "clearfix.exe"?
I was just puzzled, how on earth that it could hard-reset by itself, when I was expecting a soft-reset on the machine.
I tried to recollect how was it possible to happen, and I thought it could be due to the one time that it slipped off my hand and knock on the ground lightly while I was trying to snap a picture that's closed to the floor. Other than these, I'm not too sure what's the cause could be, cause it might be too technical for me to discover :?
I think this is the problem of using non-official rom, especially main one. I have similar problem but not that serious. This is our trade off as no one force us to flash our rom.
Sometime I think it might be hardware problem too, as my wife is using 1.66WWE (I did not flash her machine), it sometimes hard reset automatically too... Also, everything change sim card - even if the 2nd battery is full, it still lost all the data.
Might be the machine is too complicated or might be this is a common feature of all the windows products.
I just tried WM2003SE upgrade, but after erasing message, it just gave connection 101 error!
i tried, hard reset, soft, etc, but no lock it just says:
Serial
v 1.01
if i put it in the cradle, it will show "USB" instead of "Serial",
is this dead? i just bought it and like a hero, tried upgrading
It's not dead.
Put it in the cradle and try the upgrade again.
Don't forget to connect the power charger to the cradle for in case the battry is drained during upgrade.
Regards,
Mark
and if that doenst work try to upgrade it on another pc with active sync
Finally, my advice starts to stick!! :lol:
Have you done lots of upgrading on that particular PC? If so, then it's definitely worth trying a diff PC.
Cheers
Ant
It Worked!
Hi, thanks everyone for your replies, i managed to get it working today on a another PC, looks like its time for me to get another laptop, this one is dying.
It worked sometimes, then cuts off in the middle, then stops working, i tried it all night yesterday, though i lost it all, only had about 2 hours sleep because of that but i tried today on another pc, and it worked the first time.
Probably onboard usb is faulty (although it works with my cable modem, external dvd-rw, etc), but it seems to me, the update/upgrade program needs error-free connection and mine might be ill.
anyway, i downloaded the rom from o2 xda website and updated to that(wanted to upgrade to WM2003SE before it went in coma), i cant afford another crisis , i like my xda 2 too much! :wink:
Thanks for your replies, appreciate it 8)
I don't think it's anything wrong with the hardware. My advice would be to ensure you backup any backup files then uninstall ActiveSync, before removing all registry and folder references to it. Then, reinstall and then see how things go from then on. Glad it's working though now!
Cheers
Ant
Backups
Yup, i've done a backup of the ROM and also the Extended Rom, don't know how to backup or where the Radio Stack is, so i'm assuming its in the main Rom.
The reason i think its the hardware fault is because things like cable modem, dvd rewriters, etc work beneath the drivers, and they do all checksums and checking, with Him upgrade program, it uses ActiveSync APIs, so any hic cups in activesync would be passed down to him upgrade, if activesync did proper data checking and resend data (or might be that the bootloader is limited so it might be limited on what it can do) then the errors could be rectified.
These are all my assumptions. thinking out loud.. etc
I tried reinstalling activesync, etc also created new admin user, tried safe mode with networking (without networking gives TCP/IP error message).
All failed.
i wanted to fix it yesterday night with this laptop, and didnt have access to any other computer, so ended up staying up til late and trying all possibilities, but all failed so i gave up and waited for the next day. came back from work and then tried it on another computer and it went smoothly.
Also tried resetting the xda2 many times, taking the battery out, soft hard cold hot yellow green, tried all, but no luck. :roll:
So i assumed it was a hardware fault, or XP sp2 fault (the other one is a desktop with win2k).
anyway i'll be formatting this xp sp2 soon and putting windows 2k, seems more stable, trying to get maximum mileage out of this laptop.
thanks for the tip though.
Have HardSPL installed on phone. Got phone on eBay - has very few hours. Came with a Rom that displayed TEST ONLY which was WM5. GSM radio worked, Bluetooth worked and Wifi worked. Tried installing shipped HTC WM6 Rom - did it through ActiveSync - should have used MSD card. - Rom installed though everything was ok but didn't install a SIM card to test phone - used it as PDA and WIFI for a week no freezes. Now this morning wanted to switch phones over and inserted SIM - saw NO GSM on boot - never really noticed it before.
Checked in ABOUT section to see if a radio was loaded - comes up blank. Read some things about NO GSM errors - got a little nervous - so I thought I'd reflash entire ROM tonight with SD.
Followed directions and get into update process and it seems to freeze at GSM with progress bar at about 15% - for about 30 minutes.
Removed battery and it boots to TRICOLOR. (I freeked out at this point)
Put a HardSPLv7 on SD card and did the above - update was successful
Phone boots up to OS still with no GSM
Tried the update process again with the same ROM - still has problems and never gets past the same point as before. Will try another ROM but I'm a little doubtful. If I can recover it back again will try just upgrading radio to see if it makes a difference.
ANY SUGGESTIONS or is the hardware fried?
Thanks.
OK, think it may be back and I was able to reflash using a wm6 stock HTC ROM. Think either my original flash of the same ROM was bad - downloaded a new file and flashed with the SD - originally did it via ActiveSync.
To get it to work I did a couple of hardspl reflashes and got into the OS. DID a couple of hard resets and magically GSM appeared. Turned phone off and then NO GSM appeared again. Did the hard reset again - came back. Not taking anything for granted put in a SD card and reflashed. Held my breath and for some reason it did a complete flash and never really hung up for more than a minute or two. Soft reset - GSM was there. Turned phone off and on a few times and its still there. Phone now finds the GSM radio much faster than before. Can make and receive calls (does wake out of sleep) - signal strength is same on my other Cingular 2125. Will try out tomorrow and see how it goes. Either the reflash does it or something is loose in the hardware but if it works a few hours tonight it should be good.
Will be a little hesitant to reflash after this but will see after a stress test.
Hold both softkeys and hold the power button
You can also hold both softkeys and put the stylus into the reset hole. Tell me if that works.
Initially no. When I attempted to flash the HTC Factory Rom it froze. Prior to that I did a couple of hard resets using the two softkeys and reset pin. With the resets couldn't get the GSM radio to turn on. Tried the ROM flash but it froze (about 1/10 of the way) - so I basically OS bricked it by removing the battery when it was at this stage. Got to the bootloader screen. Tried to flash OS again with SD card - still froze. SO I thought reflash HardSPL and the OS magically appeared and did the steps above.
After a couple of hours - call made, turned off and restarted device no problems still have GSM radio. Can receive a call when in standby. May try to do another hard reset and see if it still works after a day or so of testing phone but I want to try it for a few days by turning it on and off and making and receiving calls. If I can do another hard reset and everything works I think it was just a bad initial flash through ActiveSync. May get bold and flash another ROM as a test.
Since the phone worked with the TEST OS when I got it I think the only factor is the WM6 flash that I did. More than likely the hardware is OK but only time will tell.
I don't believe you will recover your radio rom now as you interrupted the flash. It generally takes 30 MINUTES to flash a complete rom. You stopped it during the radio rom flash, BIG MISTAKE....
If you can find the SHIPPED STOCK ROM or the original radio rom then you might have a small chance at recovery, we're talking about you winning the lottery 10 times in a row chance...
If you try to flash anything but the original radio rom then you can kiss the phone functionality goodbye....
Good luck finding the right roms...
Cheers...
Its not bricked. In my post said I did a full recovery and its working with the stock HTC WM6 ROM with the HTC radio. I can receive and make calls. Able to ActiveSync with the PC and have hard reset a few times just to make sure all is well. I believe there is still a hardware problem - either a loose connection inside or something else is going on but I think its definately hardware. When the stylus is out of the holder EVERYTHING works fine - have a signal - can sync - can charge it - no issues. If I put the stylus in part way no problem - push it in all the way during a call it will still say connected yet will hear nothing and can't disconnect. Pressing end has no effect yet the phone will still function - just the in call symbol stays and the green led still flashes.
Turn it fully off and back on with stylus out - shows GSM radio code and phone will now work.
Have to check the service manual to see if the stylus holder when the stylus is inserted pushes on anything vital. Can't imagine thats it. But so far with the stylus out everything is ok. Will attempt to use it tomorrow see if thats it.
Know it sounds stupid but thats what I'm observing so far. Its late here see what happens tomorrow
Thing is running and can use the phone (no static, three bars) but last night had a few no GSM messages during a cold boot. Ran it all night and it seems to be working - booted a couple of times, charged it, sync'd it and actually put the stylus in (don't know if thats the problem) and still working. May be a loose connection that is currently ok but who knows when it will stop working. Other possibility is heat or a failing radio. Could also be battery but thats doubtful. Could have messed up the stack during the initial flash so I'll see over the next few days. This one is starting to drive me a little crazy because it works then for no reason it will stop then resume after a hard reset or reset. Could also just be the version of the ROM I'm using but it came from the repository on XDA-Developers. Just rebooted it when I was typing this and it still finds GSM radio.
Tried it for a day and I think the radio is fried. Started out finding GSM then when driving around with my Bluetooth heard a bleep which indicates loss of signal - saw it hunting then it finds the signal. During a call for about 3 minutes just drops call and on the screen the dialer won't let you disconnect the call.
Rebooted got the NO GSM message - eventually found it - briefly then NO GSM again.
Tonight opened it up and reseated and cleaned motherboard contacts including radio. After hard reset got GSM again - briefly. Then no GSM
Tried upgrading and downgrading radio via SD card - no go would only hang up Tried complete with OS - same thing. Tried through ActiveSync method SSPL and got same.
So I think the phone is pretty much not really a phone - can still boot into OS. May try some more but I think its definately a motherboard issue. Shouldn't be that hard to flash and the GSM should at least be stable.
When I bought it on eBay and first turned it on saw a TEST ONLY message on boot with a WM5 Rom. The seller was a little vague just said it freezes sometimes. Got it cheaply thankfully so I'll keep hunting around for another unless someone has a suggestion?
The Radio seems to be the touchiest part of the Hermes. When it fails theres nothing that seems to be able to fix it. Look for another cheap Hermes. At the very least you will have spare parts.
how weird is this I have just gone through just the same problem and took a day to sort it out . ok here is what I did in the end . now what you need is any official rom pref wm5 . I can send you a link if needed to the one I used ... now try flash it from the pc it will stop at 12 percent ....... now take battery out and boot in bootloader mode .... now flash any rom that's wm6 etc .... devise will restart .... now take battery out and re boot it may take two or three boots to get it working prop without the no gsm error but trust me it will boot . when its booted up flash the original wm5 shipped rom run through the rom sequence and when its waiting to flash saying zero percent manualy put your phone in bootloader and wait 30 odd min tadaaaaa phone is now perfect ... now flash any rom you like as the radio is fixed . its something to do with the 12 percent bit it hangs on .??!!! sorry its long and complicated but I have my hermes back to life through doing it ................... let me know how you get on bud. if needed 07832999919 uk . so its 0447832999919 oh I have hard spl 1.40 spl 1.1 or something lol can't remember . anyway good luck
Ok, think I initially really messed up my flash and the WM6 which was the official HTC version may have been corrupted but showed full flash. When I tried again I would also get the 12% even with a SD flash. So I tried flashing just a RADIO ROM which did complete. The NO GSM message still would pop up maybe 50% and not necessarily everytime.
When to MTTY.EXE and did a bad block check - no problems
In MTTY did a FORMAT/CLEAR.
Left everything alone and again reflashed just the RADIO - things seemed to be better - less NO GSM.
Tonight - just before you posted I successfully did a complete reflash with the HTC WM6 rom with Radio 1.48. Very surprised it worked this time - no hangups except during the GSM part which only stopped a minute or two.
Complete reflash in about 10-12 minutes with the SD card method.
SO far things are working - tried a reboot a few times and now radio is found every try. Will try for a few hours and try again tomorrow.
What I did have is a white screen/with image once - it was cleared by just pressing briefly the power button. So it may be heat related - don't know.
Keep me posted in this thread whats going on and I'll do the same.
What ROM WM5 did you flash to get yours to work?
Spoke too soon! Put in a sim card - powered up and it worked. Tried making test call and it worked. Tried again and it showed dialer and dialing and never connected. Could not use the dialer to hang up. Also showed drop in network. Tried turning phone radio off in dialer and back on - showed !X. With the phone off hook image at the top bar. Tried again - same thing. Expected to see no GSM when power cycled and it did show NO GSM.
Right now its working even after a few power cycles but honestly I think the successful flashes may be due to the GSM radio being found. If it doesn't find the radio and you attempt to flash thats why it hangs. If you phone works for a few days or day I'd be very surprised. The real test is to try it when moving from tower location to tower location. Thats where I noticed the radio was acting up. With a bluetooth headset it will beep indicating a drop in carrier. When its doing this the radio isn't working properly and can't lock on to a signal
If your phone does work PLEASE post what you did and what files were flashed.
For my phone I think its heat related. Possibly the heat from the circuitry is opening up or stressing out a component causing it to fail. I really think my motherboard is faulty and reading on the HERMES this isn't that uncommon. Being that the phone has so little hours I think it must have been a return or factory reject.
More than likely I'll have to purchase another phone needing a screen or one thats in poor shape to salvage the motherboard and attempt to put it in my case since the housing and screen are pristine with little to no use. I've been told that any 8525 motherboard will work but I doubt it since the Dpad is different and I have a front video camera.
No, ANY Hermes mainboard will work... Hermes are identical internally, even the 8525 is able to use the front camera, it just isn't included in that model.
Cheers...
Thanks, makes my life easier!
ok mate i used htc orig rom by orange uk google the words,,,, orange spv m3100 update ummm ok hang on il grab the link for you ...
http://www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_1007.exe then flash hard spl then update your rom to whatever you like ,,, hope this helps buddy
Might try it tonight but I really think I need a new mainboard. I am able to flash only when it finds the GSM and I think any hangups are due to the GSM radio circuity failing or some strange power flux on the motherboard. I am having strange multiple freezes/slowdowns as well as NO GSM errors. Tried a WM5 and WM6 specific for my HERM200 and no change. When it works it will work and make and receive calls but after a while without a load but under load - multiple calls, running excel or other things the radio will drop or it will attempt a call, not connect and will not let me hang up. No software update will fix this issue - it has to be hardware.
If I have successfully done base HTC ROM flashes - complete with radio phone should theoretically work. I have to face reality with this one which although looks pristine is a lemon and have to buy a working beat up 8525 and try the motherboard as long as the seller assures that the phone can make and receive calls without problems.
Also have other issues with screen fadeout which I know is tied to the dPad controller - but I can live with that for a while and I have a source for a part replacement and can try a quick fix to verify its just the dPad.
You got lucky so far - but if you try to use the phone all day running multiple programs or CPU intensive tasks your radio still may fail. You could also try upgrading the ROM again to something that is MFG and see if it takes.
It is possible to flash the OS without flashing the radio, It will be a cooked rom but they're better in most respects than a stock rom. Faster, leaner with all the bloatware removed.
No software change is going to fix this. Its not a software bug its a flaw in the hardware. Can't flash a radio Rom - thats a chip problem. Its basically a low level format and write to eprom. Thats pretty basic. Also making and receiving calls is also pretty basic. The dialer has been around for a while and is pretty stable.
Hello,
First off I want to explain what happened exactly. Since April I am using an HTC One, but I gave my S3 to my girlfriend. I gave it to her exactly like I used it: running CM10.1 nightly's, no other mods, no custom kernels, etc. I updated her S3 once every few weeks with a new nightly. It performed normally, like it has been doing for many months.
Since a few weeks, the S3 started to show problems. The camera app would act weird sometimes, but it wasn't anything big. Then the freezes came. Once every few days, the phone would freeze and she needed to reboot. In the past week, the freezes happened many times daily. No matter what you did with the phone, it would freeze very fast. It just got worst and worst, until yesterday the phone wouldn't even turn on anymore. It would stay in the bootup screen.
The problem was, I had only downloaded a CM10.2 nightly update recently, had no Android 4.3 Gapps yet and hadn't succeeded in making a proper Titanium Backup (due to the phone being so unstable, it would freeze at 80% of the backup). Moving to CM10.2 without a wipe wasn't the best idea, but having no TB, I didn't want to wipe data. In the end, desperate measure called for desperate actions. I flashed a nightly build of CM10.2 I had downloaded already on the phone, but still the same. It wouldn't get past bootup animation.
To keep this story as short as I can, I ended up flashing the latest Samsung Touchwiz build (4.1 based) via Odin, but even that wouldn't get past the bootup animation. So I managed to get in some sort of recovery, where a wipe data option was available. Did that, phone started working normally again. Only problem is, this wipe data option apparently was a different kind of beast. I am used to the "wipe data" option that deletes your apps + data, etc, but doesn't touch your photo's, music, etc. This one did.
Is there any known way to recover some of the files that got deleted?
And if anybody is in the mood, any explication on what exactly happened to this S3? I mean, nothing changed, it was working normally for months with CM10.1...
Kind regards
I've never found anyone that recovered any data from the internal sd card, there are pc programs that claim to be able to do this for sd cards and hard disks but doubt they will work on MTP device.
Freezing is common for a minority of phones due to nand block failures, or it could be due to the rom you were using.
boomboomer said:
I've never found anyone that recovered any data from the internal sd card, there are pc programs that claim to be able to do this for sd cards and hard disks but doubt they will work on MTP device.
Freezing is common for a minority of phones due to nand block failures, or it could be due to the rom you were using.
Click to expand...
Click to collapse
Thank you for the quick reply. I suspected this but I though it's worth asking.
I guess my S3 was one of this minority, can't imagine CM10.1 to be the bad guy here. Ah well, at least now she can use the damn thing again. RIP photo's and other important data though. It's near impossible now for Samsung to get me to buy another product from them again in the future.
Unless you have a government grade software/hardware that's being used on digital forensics then it's really quite impossible to recover the files.
For future, look at FolderSync on play. It will sync sdcard data to the cloud or to a computer that is always on.
I set my sdcards syncing over wifi whilst I am asleep. I never lose anything.