I'm having a wierd problem with my Hermes. I have the Scnaps 4.01 WM6 rom on my phone right now, but the same thing happened with Blacks rom when i was running that.
Sometimes when i turn it on, it says it has signal so i try to make a call i get operation failed, and then you see the signal drop back to searching, it finds the network and then logs back on. Same thing happens even if i dont make a call, turn on the hermes, and look at it, has signal, then 10 seconds or so later it drops to searching (it never really had signal) then logs back on, and then sms's get delivered. I've also had people try to call me during this time and it's like the phone is off.
I've tried a few different radio versions recently but same behavior with all of them. 1.54.30, 1.54.07 and currently on 1.43.
Something else weird is the fact that it seems like (I could be wrong) this only happens after having the rom on for a week or so, ie after flashing a rom, the first week or so i don't get the issue, then it slowly starts to happen - this could just be my imagination.
Has anyone else had this issue? Any ideas/suggestions welcome, thanks
Hi Ferni...
This is something that is becoming quite an issue recently
Firstly, have you made sure the SIM contacts are nice and clean and everything is fitted OK - and have you tried a different rom image? If not - try these first.
Secondly, where abouts in the world are you and what network are you on?
Thirdly - when did you install 1.54.30 and 1.54.07 - did your problems start before or after you flashed a 1.54x radio - and what radio were you running before trying these.
Finally - What other information do you have about your device - is it a herm100,200 or 300, what IPL/SPL is it.
Sorry for the 100 questions, but I'm investigating these issues at the moment as a lot of users have had similar problems especially after using radio 1.54.x as this thread discusses.
Thanks for the reply. Just read the other thread you linked to (and the threads it linked to). Interesting to know i'm not the only one.
I just pulled the sim out and gave it a rub and the contacts and put it back in. I also had a bigger battery in it, so i removed that and put the standard one back in. See if that makes a difference.
I used to run the black rom, now I run the schaps one, trying to avoid flashing it again just a pain to resetup everything you know....
I'm in Australia, on the Optus network. The JasJam is actually only sold by Telstra here, but i got one 2nd hand and use it on the optus network fine (Optus sell the Dopod). The latest radio rom 1.54.30.10 i belive is actually from Telstra - in the offical WM6 rom from them for the JasJam.
As for when i flashed which rom and when the problems started happening - i can't really say sorry, i didn't keep track. I've had the phone around 6 months, flashed it with a cooked WM6 rom (black i think) when i first got it, i probably updated the radio as well.
How do i tell if it's a 100, 200 or 300? Also not sure what SPL it is, HardSPL or something?
Tempted to flash it to the official telstra rom released recently with the latest radio, so if it does die completely i can send it back for warrenty. What do you think?
Thanks for the info - every little helps at the moment!
Firstly, yes - the radio you're running is native to the area and network and so if you're running 1.54.30.10 and it goes duff you should be covered by your warranty so don't worry. Also, it's not certain yet that there is definitely a problem with this radio so don't loose too much sleep. (Most of the problems linked with this radio that I've researched so far seem to be coming from Europe and after rolling back).
As for flashing with the official ROM, that's a decision for you - however in the cases of sudden GSM death, the phone will still boot to Windows and it is still possible to flash the OS and bootloader roms (just not the radio) so if it did go bad with an unofficial ROM on it you should still be able to roll it back - again sleep easy ;-).
As for the problem - the steps you've taken are a good start, see how it goes and keep us informed here.
It may be worth also trying to manually set your band (if applicable on your network). Sometimes problems like this can be caused by issues on the network itself and trying an alternative (maybe a friends) SIM card for a different network or even manually switching the phone to GSM (if available) can "cure" a problem (although it's a pain if you specifically need to use 3G and it's data speeds!).
Finally - to see your full device information you need to enter the "bootloader" (tricolour) screen. Hang on to this information on the bootloader screen as it can be useful if you ever encounter a bad flash.
To do this, hold the OK button on the left of your phone and the power button on the right then press the little reset button with your stylus. You will then see the model at the top with the IPL version below it and then the SPL version below that. To get out of the tricolour screen, press the reset button again. Needless to say this won't erase anything or damage your device but make sure you close your apps and save your data first
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
ferni said:
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Click to expand...
Click to collapse
What radio are you currently running? Thought it was 1.54.30.10 or did you change that the other day when trying a new ROM?
ferni said:
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
Click to expand...
Click to collapse
*IF* this is the sudden GSM death syndrome then it will progressively get worse unfortunately - but it might not be that (think positive!)
[edit : removed - brainfart you answered my question] Incidentally, just updated this thread here - Look at post #60, it's a long post but there is a couple of possible things for you to try there (multiple flashing on a "chilled" phone) for users who STILL have some GSM connectivity... Might be worth a go and certainly could do no more harm... The post itself is very technical but just follow the instructions about 3/4 way through the post and ask any questions back here in this thread so things don't get too confused!
In terms of flashing your ROM - when you _really_ feel the phone may die _very very soon_ then it's worth considering flashing it with the latest OFFICIAL rom from your provider while you are able to do a full flash but don't leave it until DHL are at your door to collect it just in case you need some help!
Oh yeah... and finally for tonights post - Rolling back from Olipros Hard SPL... back to the normal, official SPL - Mr Vanx has written a fantastic guide to this here complete with illustrations - That should save you some searching
The SPL rollback, of course, should be the very last thing to do before shipping it back under warranty of course tho - just incase you need it in the mean time!
Good luck - and keep us updated - particularly if all works again (or not)forum.xda-developers.com/showthread.php?t=299070&page=32
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
ferni said:
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
Click to expand...
Click to collapse
Yes. Crazy as it sounds, if the previous radio caused "logical" bad blocks - a combination of a couple of flashes in quick succession with the PLA at a cooler temperature might recover them! (temperature issue came from the data sheet for the chip itself - Apparently more efficient writing at temperatures a minimum of 10C below ambient).
Good luck - let us know how it goes... I've got my fingers crossed you'll have a Hermes with it's wings back shortly
Last night the phone got worse, i had a missed call, tried to turn the unit on to see who it was and it wouldn't turn on, so i soft reset it, it booted up ok, but wouldn't pick up a signal.. eventually after about 5mins it did, but then it locked up. So i pulled my sim card out put it into an old phone which i'm using for now.
This morning came into work and put it in the fridge for 15mins, and flashed the latest radio firmware on it. Then flashed the latest official telstra rom onto it (getting ready for warrenty). That's just finished, only step left is to put the original boot loader back on. May test it again for a couple of days to see if i can get it to do the same thing on the offical rom/radio before i send it back. Will let you know.
Thanks for your help so far.
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
ferni said:
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
Click to expand...
Click to collapse
We did indeed - Ah well, at least you're covered by warranty
Mr Vanx has written a fantastic guide to rolling your bootloader back - complete with illustrations. (repeated for others who've just started reading this thread)
Yeah hopefully it gets covered under warrenty. That bootloader guide worked perfect
For anyone who cares, they replaced my radio board under warranty - I now have a new IMEI number. Haven't got the phone back yet to test to see if it's fixed.
Did you ever upgraded the Radio ROM ?
Or was it always 1.43.
My first ROM only upgrade.
http://forum.xda-developers.com/showpost.php?p=1462158&postcount=292
Yeah i had tried a few different radio roms before this. I suspect it didn't like being flashed so many times.
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
gondalguru said:
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
Click to expand...
Click to collapse
I flashed one of the wm6.1 roms and ended up with 1.54.07 radio and was getting the "modem disconnected" error message everytime I tried to log on to the internet.
I reflashed the original WM6.0 ROM from AT&T and then reflashed my radio to 1.48 (can't go back to 1.16 because of the radio bootloader I think) and then tried to log on to the internet.
That didn't work
But then I made a phone call to my home phone
tried logging on and it worked.
Been working fine since
crossing my fingers and hoping I dodged the bullet, not gonna flash again til ATT comes out with 6.1 then if it acts up even a little I am gonna send it in for warranty repair.
I hope this procedure works for you mate.
pedro2k said:
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
Click to expand...
Click to collapse
Not exactly sure where this setting is, the closest thing I could find was to install HTweakC. And now I have auto attach off. I also live in WI rural area, and 3G has been growing. Coming closer my home, and when I go to work it switches to 3G from Edge and I believe this is the biggest cause of this problem. I will let everyone know if this has helped me or not.
Thanks pedro for your suggestion. I will try that and will report back.
Hi,
Couple of days back while on call my phone brightness blinked couple of times and then went dim forever. Since then i have tried couple of DEV roms and nothing helped. No matter what i do with brightness it always stays at low level. I can't even seen anything outside in bright light. To use my phone i have to find a dark place..
Does anybody had this problem. Looks like something went wrong with hardware. This happened when I was using Sense Hero ROM.
Any help will be greatly appreciated.
Thanks
try to flash the offical RUU and root again maybe..
try reflashing the radio and maybe the spl?
throw on the power control widget, it can turn your brightness back on.
Thanks for answers guys.
I can not find the original Canadian RUU anywhere. It was
Build number: 2.73.661.46
I should try to re flash radio. I will let you know the results.
what is spl?
I tried brightness control widget. i t doesn't work.
Thanks
Are you sure the led backlight aren't just damaged or something?
I find it very strange that you're not able to change them. Especially cause you tried different roms, since that should reverse al previous settings making it impossible to be a software error?
I tried latest radio and new rom [ROM][2.1 Sense] BeHero+ v1.2. No change. still the same. i can not change the brightness.
Any more tips ???
Has the warranty period expired? If not, flash official ruu and run to the closest htc maintenance shop :/
I got it around December 2009. so warranty is still there. I am in canada and the phone was offered by Telus. I bought it from telus and unlocked to use it with my provider which is Bell.
I called HTC and they told me to go to telus but telus said warranty is void because i unlocked it.
I am stuck.
I can try calling HTC directly again.
On more problem is that i can't find the original RUU which was installed on the phone when i bought it.
Thanks
ysandhu said:
I called HTC and they told me to go to telus but telus said warranty is void because i unlocked it.
On more problem is that i can't find the original RUU which was installed on the phone when i bought it.
Thanks
Click to expand...
Click to collapse
Dunno if that does any good to install original RUU. Telus has probably flagged your phone as warranty void if they already used that as excuse.
Changing screen may fix the problem, you should ask someone that can fix it to take a look.
I did try to replace the phone with Telus weeks after i got it because the GPS for the phone never worked and they check my phone in there system and told me that i have unlocked the phone and warranty is void now.
So i went ahead and rooted the phone and tried couple of community ROMS to see if GPS works properly .. but none worked.
So i was living with this phone without proper GPS working... mostly relying on cellular AGPS find ..
But now with this brightness issue.. this phone is becoming useless.
I don't know how expensive it will be to replace the screen...
Thanks
Hi, firstly i'd to apologise if a thread is dedicated to this issue, but i cant find anything remotely that applies, completely new to the xda scene, dont understand which roms are which, radio's etc and ive stumbled across an issue that i simply cant resolve.
My phone the HTC elf is displaying the tricolour screen, ive tried to re-flash the phone to no avail, a grey screen appears and its stuck at 0%, i left it over night last night expecting the rom to of flashed, but alas no!. have i screwed my phone or is there anyway or anywhere that someone can point me in the right direction, to resolve this issue.
It did have WM6.0 professional installed, is it possible to put a higher version on this phone or android if so, can someone please point me in the right direction with links etc with explanation's, totally at my witts end.
If someone can help me just get WM6.0 pro back on i'll be happy
my provider is o2 UK dont know if that makes a difference on flashing with different roms...
also the phone is unlocked to any network it was on orange but im on o2...cant ring o2 as i swapped my contract phone for this one...(oops, FAIL!)
Kind regards
Lee
read the unbricking section in Rollup sticky and then post in an appropriate thread.
Hi folks,
I'm having this weird behavior with my Galaxy S4 LTE. The problem is that since yesterday, the phone is locked displaying only time and date, with no unlock options or other messages. If I reboot the phone, this "lock" screen -which I attach a photo of it with the post- is "always on top" and it's no possible to get around it.
I flashed and rooted a stock firmware and I've been using it for 15 days without a problem until yesterday. If I do a wipe/factory reset, the lock screen is still there, with and without SIM card. I have also tried to flash other ROMs like the pure Google 4.3 v2.1 and it's no working, the screen is still there. The mobile phone is brand-new and simlocked with Vodafone Spain.
Do you know if that's a locking or protection mechanism of some time?
thanks in advance!
TheEfrit said:
Hi folks,
I'm having this weird behavior with my Galaxy S4 LTE. The problem is that since yesterday, the phone is locked displaying only time and date, with no unlock options or other messages. If I reboot the phone, this "lock" screen -which I attach a photo of it with the post- is "always on top" and it's no possible to get around it.
I flashed and rooted a stock firmware and I've been using it for 15 days without a problem until yesterday. If I do a wipe/factory reset, the lock screen is still there, with and without SIM card. I have also tried to flash other ROMs like the pure Google 4.3 v2.1 and it's no working, the screen is still there. The mobile phone is brand-new and simlocked with Vodafone Spain.
Do you know if that's a locking or protection mechanism of some time?
thanks in advance!
Click to expand...
Click to collapse
it seems to be that the problem is that your phone is detecting a magnet sensor (the same as the SVIEW Cover Mechanism) because those information you see is what the SVIEW Cover shows up. Maybe hardware problem . . . (WHAT IM SURE IS THAT ITS SHOWING UP THE SVIEW SCREEN)
Solved
Hi folks,
Just an update. The problem was fixed by technical service. Full board change after an unsuccessful change of the sensors pack. Definitively a hardware problem. By the way, the technical service was great, in less than a week got my phone back and working.
TheEfrit said:
Hi folks,
Just an update. The problem was fixed by technical service. Full board change after an unsuccessful change of the sensors pack. Definitively a hardware problem. By the way, the technical service was great, in less than a week got my phone back and working.
Click to expand...
Click to collapse
I have EXACTLY the same issue, and have spent all day trawling forums looking for a solution. At this point, having found this tread, confirmation that the problem is a hardware issue will do me! I just wanted to say thanks.
So I really hope that someone can help me here as I seem to have a big problem... I'll try to write this out from the beginning...
Ordered my phone from Hong Kong. It is a D802 model. 3.4.0 kernel, d80210b software 32gb (likely the HK version right?). I knew that it was upgradeable to kitkat and so I downloaded the LG mobile support tool and plugged in my phone. I set the country and region to UK and set it to upgrade the software. Then I let it do what it does. At the end of the process the phone was stuck in bootloop on the LG screen with the indicator light switching between blue and green.
I then tried to fix it using the LG flashtool, but it wouldn't go into download mode and went to fastboot. I figured that it was stuck in fast boot and so I did the laf.img fix that is out there to try to restore download mode. The laf.img file I used was for a 16gb D802, not a 32gb like mine. I'm wondering if that is what created the issue that I have. Anyway, this allowed the phone to start in download mode and from there I flashed the software to Hong Kong d80210b 32gb.
This is where I noticed the big problem that I am currently experiencing and need help with. My phone screen does not register my touches in the right places. If I try to tap a location on the screen (an onscreen button) it will register the touch somewhere else completely. I thought that it might be an android version issue, but I upgraded to European open D80220D_00 (it doesn't seem to specify 16gb or 32gb) using LG flashtool 2014 and the issue remains the same.
I am unable to use the phone completely and I assume that the issue is deeper than the android version. I would really like to resolve this issue somehow. Does anyone have any idea? I'm thinking that if I could force a complete re-install of everything that might fix it. I was told by a useless LG rep (over the phone) that I would have to give my phone to my service provider and have them send it off to a technician to re-install the software, but I figure anything they can do I can do as well... right?
Any help would be appreciated.
Thank you!!
Seriously, all this knowledge and no one can offer me any help? Is there maybe some driver on the phone that is bad? Where would I find that? How would i replace it with a good one? Do I replace the Kernel? I don't really know how to go about this. Any help would be great.
ParticleDragon said:
Seriously, all this knowledge and no one can offer me any help? Is there maybe some driver on the phone that is bad? Where would I find that? How would i replace it with a good one? Do I replace the Kernel? I don't really know how to go about this. Any help would be great.
Click to expand...
Click to collapse
You may not see the replies you want because alot of times your questions have already been answered and some of us have moved on to other phones etc and no longer visit these forums.
Search....
Your problem sounds like a faulty digitizer
I appreciate the response and info.
As far as searching goes, I did, for hours. I spent my long weekend here and all over the web looking for a solution with any possible number of keywords. I didn't come up with anything.
Faulty digitizer would make sense, although it appeared to be working prior to the upgrade... I would be happy for a faulty digitizer as that should be covered under warranty.
Thanks,
Mike
so sorry to burst your bubble but i don't think its hardware prob i have the same prob as you , ppl say update ur touch S/W and i know u cant cos u cant even dial 3845#*802# to do it , i also spend 2 days trying to fix it with no luck