Develop Bugs

Running hot and buggy

Okay so I will let you know the history of my phone before i start.
No water or falling dmg at all, I Have taken care of this thing like it was my baby.
I rooted the phone and put starburst ROM on my phone it ran good for a little while
but then decided to go to blazer rom. That rom was great and everything and ran amazing for months then 2 days ago I woke up to my phone with a purple tinted screen, frozen and pretty warm. So i took the battery out and it seemed to restart okay. (I charge it every night so it was charging when this happen)
The rest of the day I started having issues like battery drain, Screen not turning on unless i took battery out, heat, account Unsyncing, calls auto going to speaker, Message LED light not turning off, and more!
So I decided to go to Calkulin's E4GT to see if that would fix my issue. Its amazing rom and things seem to be working okay. But still having a issue with my phone heating up and the screen not turning on also the message red LED light would not go away....
I called sprint and was told to take it to a repair shop or i could get it replaced for $100 (which i am not doing) Will the repair shop be able to fix this? Do i need to put official back on my phone before i take it in? anything would help at this point (sorry ahead of time for spelling and size of this post)

enp82003 said:
Okay so I will let you know the history of my phone before i start.
No water or falling dmg at all, I Have taken care of this thing like it was my baby.
I rooted the phone and put starburst ROM on my phone it ran go for a little while
but then decided to go to blazer rom. That rom was great and everything and ran amazing for months then one day I woke up to my phone with a purple screen, frozen and pretty warm. So i took the battery out and it seemed to restart okay
The rest of the day I started having issues like battery drain, Screen not turning on unless i took battery out, heat, account Unsyncing, calls auto going to speaker, Message LED light not turning off, and more!
So I decided to go to Calkulin's E4GT. Its amazing rom and things seem to be working okay. But still having a issue with my phone heating up and the screen not turning on also the message red LED light would not go away....
I called sprint and was told to take it to a repair shop or i could get it replaced for $100 (which i am not doing) Will the repair shop be able to fix this? Do i need to put official back on my phone before i take it in? anything would help at this point (sorry ahead of hand for spelling and size of this post)
Click to expand...
Click to collapse
I'd say use odin to bring it back to stock unrooted. If you are still having problems with it, then it's probably a hardware issue and will likely persist. However, my experience with people at sprint who are smart and actually know what they are doing either don't mind if you have it rooted or have rooted phones themselves. They have a machine that they plug it into and if it is rooted, it won't damage your phone, but it will give a whole lot of weird errors. Good luck!

Super Fast reply! thank you! I am so sad because Calkulin's E4GT is such an amazing ROM! I hate to lose it. Would they be able to replace the motherboard at the repair shop? because it seems like the device is overheating alot. No processing are running but mainly when its plugged in.

Definitely just take it in and see what they say .. if they find a problem Sprint repair center will fix/ replace it for you.

Well I took it to the sprint repair center today and the guy told me that it's due to my my hot spot service that i am suppose to be paying for.
I told him i don't even use that feature it just came with the ROM but he said he was sure this is what was causing the issue.
He said he could do a hard reset on my phone but other then that i am out of luck

That sounds like bull. Go back to completely stock and see if the problem persists. Of it does, take it back to Sprint, but try a different store.
Sent from my Epic 4G Touch using Tapatalk.

demonlordoftheround said:
That sounds like bull. Go back to completely stock and see if the problem persists. Of it does, take it back to Sprint, but try a different store.
Sent from my Epic 4G Touch using Tapatalk.
Click to expand...
Click to collapse
Yeah, I gotta agree, if that was in fact the problem here, I doubt your phone would be the only one doing this stuff. Shoot, I actually use hot spot app and mine has never acted like that.

Yeah think the company told him to blame stuff on that because they are not getting my $30 a month for the hot spot feature. So far phone hasn't really been acting up just the red LED been staying on 24/7 but i went in to setting and disabled it.

Sorry for double posting just wanted to give you guys a update
Saturday my phone did the thing where the screen would not turn on.
I drove right to my sprint repair shop and sat down with a over weight female tech.
This was our convo
me: "Hi, My phone's screen is not turning on and the phone has been acting really weird when the screen is on.The last tech said
this was because it was rooted and the wifi hot spot THAT I DON'T USE made the battery over heat but the heat is clearly
coming from the top right as you can feel"
tech: "WEELLLL did you know i could refuse to look at the phone if its rooted according to our policy?"
me: "Well what time do you close, because I will unroot it and put stock back on it and bring it back within the hour"
tech: "please sign these papers to get a replacement......"
I left feeling really annoyed. It's nice having empty threats throw at you by ass hole techs who think they are the ****.
I do not want anything for nothing i pay for my service and use root for titanium backup. Blah well glad to get my replacement either way.

[Q] An issue with the display going dead

Hi guys, recently I've been having quite an issue with my Wildfire S. It worked fine, rooted S-ON with CM7.2RC from alquez, until one day.
It all started two weeks ago when I was on one open air party where a thunderstorm overwhelmed me and left me completely wet. I've been terrified of that day before cause WFS is my first smartphone and I've been wondering how would it react on water. Maybe there is no causality between this, idk.
But since then, everytime somebody called me, the display shut off and after the call has ended, I couldn't awake my phone by normal means - the on/off button didn't work, so I started using quite dumb solution - a hard reset with taking off battery and putting it on.
(then I figured out that it could be awaken by plugging it to USB)
quite stange issue, isn't it?
I did a factory reset and flashed the CM again on clean. The frequency of a dead display has lowered down to every two calls appr. but it was still happening. Today, finally, I took off and on the battery again and that somehow did a factory reset... that's it, I have to solve it.
I'm quite worried it has something to do with HW (after becoming wet). However, if I'm not calling, it WORKS FINE!
Anybody can say anything about this?

Crusheer said:
Hi guys, recently I've been having quite an issue with my Wildfire S. It worked fine, rooted S-ON with CM7.2RC from alquez, until one day.
It all started two weeks ago when I was on one open air party where a thunderstorm overwhelmed me and left me completely wet. I've been terrified of that day before cause WFS is my first smartphone and I've been wondering how would it react on water. Maybe there is no causality between this, idk.
But since then, everytime somebody called me, the display shut off and after the call has ended, I couldn't awake my phone by normal means - the on/off button didn't work, so I started using quite dumb solution - a hard reset with taking off battery and putting it on.
(then I figured out that it could be awaken by plugging it to USB)
quite stange issue, isn't it?
I did a factory reset and flashed the CM again on clean. The frequency of a dead display has lowered down to every two calls appr. but it was still happening. Today, finally, I took off and on the battery again and that somehow did a factory reset... that's it, I have to solve it.
I'm quite worried it has something to do with HW (after becoming wet). However, if I'm not calling, it WORKS FINE!
Anybody can say anything about this?
Click to expand...
Click to collapse
It sounds like the proximity sensor got wet. Normally, i'd tell you to take the case and battery out and leave it all in a bucket of uncooked rice for a day to pull out the moisture. But beings that this has been awhile, idk if it will help

BigChillin said:
It sounds like the proximity sensor got wet. Normally, i'd tell you to take the case and battery out and leave it all in a bucket of uncooked rice for a day to pull out the moisture. But beings that this has been awhile, idk if it will help
Click to expand...
Click to collapse
I was thinking about something like that too (since I have very little expertise at smartphones). Could I disable it for calls somehow? (what would it do to normal use?)

As far as I know there is no actual setting to disable it. If you were a code ninja (or knew one) i'm sure they could. And it would just mean that you would have to manually turn it off to talk on the phone. But, we're not sure that's the problem. So, I personally would try the rice and hope for the best.

BigChillin said:
As far as I know there is no actual setting to disable it. If you were a code ninja (or knew one) i'm sure they could. And it would just mean that you would have to manually turn it off to talk on the phone. But, we're not sure that's the problem. So, I personally would try the rice and hope for the best.
Click to expand...
Click to collapse
Thanks for your help mate. You told me about the proximity sensor - which I googled and this popped out - http://forum.xda-developers.com/showthread.php?t=951858
"Screen does turn off when holding to face on a call, but fails to come back on, requiring taking out the battery"
I may have found a solution. Thanks again!

I hope so. If not, just come back and light this topic up again

Well, it seems my enthusiasm was premature as the app doesn't work on WFS. I tried a factory reset & flash once again, called from my gfs phone to mine and it happened again:
Even though I didn't put the phone to my ear, the display went black and after the call has ended, it hasn't awaken.
I'll try the rice, but damn, I don't understand it at all.

Crusheer said:
Well, it seems my enthusiasm was premature as the app doesn't work on WFS. I tried a factory reset & flash once again, called from my gfs phone to mine and it happened again:
Even though I didn't put the phone to my ear, the display went black and after the call has ended, it hasn't awaken.
I'll try the rice, but damn, I don't understand it at all.
Click to expand...
Click to collapse
I don't get it either. The only thing besides it being dead that i can think of is that there's still moisture in the lens or something causing the sensor to trip (or not in this case).

I may have found another solution, but I don't understand it at all. http://forum.gsmhosting.com/vbb/f634/solved-wildfire-s-proximity-sensor-problem-1413248/#post8066168 Could you translate it to normal language, if you think it could be the fix?

That actually seems good. It basically says to get JTAG manager, and rewrite the broken nand files with the working ones at the bottom of the post. It IS a pretty advanced operation though, and it seems you would have a pretty good chance to brick your phone if you don't follow it to the letter.

I guess CM has an option to turn proximity off. Try that maybe?

Try a different rom.
Sent from my HTC_A510c using XDA App

Bricked or not?

Ok so i pulled my phone out of my pocket and noticed the screen stuck on lockscreen, couldn't do anything so I turned it off,note : I did nothing out of the ordinary to the phone, it's been running fine on CM9 for months now and all of a sudden after rebooting..the light stays on and i get nothing. Tried everything I can think of and really don't have money for a new one at the moment. I'm wondering what happened and thought someone hear might have a little more knowledge as to what happened. Any replies would help...thanks.
Edit: After looking around it seems to have the blue light of death brick-ish w/e..I just don't understand how it would do it out of nowhere without even flashing/downloading/just sitting in my pocket? wtf...oh well..i'll probably just goto the sprint store and bs them to getting another..weird..

Hold down power and volume down for a while to see if it will boot into download/odin mode.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT

casperlt1 said:
Ok so i pulled my phone out of my pocket and noticed the screen stuck on lockscreen, couldn't do anything so I turned it off,note : I did nothing out of the ordinary to the phone, it's been running fine on CM9 for months now and all of a sudden after rebooting..the light stays on and i get nothing. Tried everything I can think of and really don't have money for a new one at the moment. I'm wondering what happened and thought someone hear might have a little more knowledge as to what happened. Any replies would help...thanks.
Edit: After looking around it seems to have the blue light of death brick-ish w/e..I just don't understand how it would do it out of nowhere without even flashing/downloading/just sitting in my pocket? wtf...oh well..i'll probably just goto the sprint store and bs them to getting another..weird..
Click to expand...
Click to collapse
If you can check the battery before all else. Do a spin test, try replacing (or have the store swap out for testing) and see if this gets you back to life.
Next option - USB Jig or try holding the buttons long enough to see if Odin or Recovery responds.
Don't think this is the eMMC bug so JTAG may also be a way to rescue it if needed.

[Q] Boot loop - insurance wont fix as saying it is water damaged

Hi, I have looked everywhere to try and get this problem fixed, but haven't found anything to help.
I have a HTC One X which is absolutely stock. I got it on contract last September and have never rooted it/played with it/etc (I wouldn't know what I was doing!). My problem is that it is on a boot loop and I cannot get it to to get beyond the first HTC splash screen. If I hold down the volume down button to get to the boot menu then it runs for around 1.5-2 seconds then reboots again. The details below show where it gets to.
I contacted my insurance company and sent it in and they have told me that the phone has been water damaged and they will not fix it. I am covered for water damage, but as I didn't declare in my insurance form that this was the cause for the failure they will not accept responsibility! The thing is that while I accept that I have used my phone in the rain on a number of times (I'm a keen walker despite the weather), I have never immersed it in water. I can only assume that the indicators have come up because I've used the phone while out walking in the rain. Despite what I say they will not fix the phone and HTC don't want to know because of the indicators, just referring me to my insurer as the water indicators are red. I am obviously hacked off, but surely if the screen isn't a problem and it's booting this far then surely I can get the phone to work?
The display is as follows:
*** LOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure Boot: enabled
MODEM PATH : OFF
Dec 17 2012,13:59:37
Battery level is too low to flash
HBOOT
SD Checking...
Failed to open usb master mode
loading PJ461MG.zip image..
Failed to open usb master mode
When I try to charge the phone it just enters a boot loop, lasts about 4/5 seconds then reboots, so I can't see how to get it to do anything else. This means that I cannot flash it/link it to my pc/etc.
Can anybody help me get the phone back up and running so I don't use it as a frisbee?! I am still under contract until September 2014 and would hate to think that I've got to pay for a phone I can't even use!

You can charge it when it boot loops - see here: http://forum.xda-developers.com/showthread.php?t=1738274
That will allow you to charge it to 100%, even though it cant boot.
Next, did you expose it to water, or is the insurance company BS'ing? What happend when the bootlooping started? Any updates (On The Air) that caused it, or anything?
EDIT:
to get to the boot menu then it runs for around 1.5-2 seconds then reboots again
Click to expand...
Click to collapse
Does it reboot by ITSELF, when in the bootloader menu??
Kind Regards
TwinAdk

TwinAdk said:
You can charge it when it boot loops - see here: http://forum.xda-developers.com/showthread.php?t=1738274
That will allow you to charge it to 100%, even though it cant boot.
Next, did you expose it to water, or is the insurance company BS'ing? What happend when the bootlooping started? Any updates (On The Air) that caused it, or anything?
EDIT:
Does it reboot by ITSELF, when in the bootloader menu??
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Thank you for the quick reply.
The phone is not holding any charge at all. I left it to charge for 6 hours yesterday to try and get somewhere with it, but the whole time it was on charge it was rebooting itself and when I unplugged the charger then it booted twice more and gave up as the battery was flat. I assume it was using all of the power coming in to reboot as it went.
I can remember about a month ago that I did have my phone in my hand and I was texting through quite severe rain, so yes, I assume it must have been then that the indicator marks came up. It has worked fine since until this episode last week and it just seemed to die on it's own. I was sending a text at the time, the phone froze so I tried to reset it (power and volume up) and it just boot looped after that.
I'm not aware of any updates in the last week or so; and the phone is rebooting by itself. Even if I leave it for 24 hours then moments after plugging in the chager it tries to boot, lasts a few seconds til the HTC logo screen, then stops and reboots.
I cannot get the phone to link to my PC. As soon as my computer begins to recognise it then the phone reboots and it disconnects from the computer. This rules out the possibility of adding in the .rar file.

Sv: [Q] Boot loop - insurance wont fix as saying it is water damaged
chouman said:
It has worked fine since until this episode last week and it just seemed to die on it's own.
Even if I leave it for 24 hours then moments after plugging in the chager it tries to boot, lasts a few seconds til the HTC logo screen, then stops and reboots.
Click to expand...
Click to collapse
Ok, what is 'this episode last week'? The sudden freeze or? And when you connect the charger, does it turn on by itself?
While in the bootloader menu, do you have time to ask the phone to turn off? That way it can charge while off. But if it does not hold battery AT ALL, I think it's a new phone....
Kind Regards
TwinAdk
- Via the premium XDA app

Last week was when the phone froze.
I cannot get the phone to shut down, it doesn't give me long enough. Plus, when plugged in the phoje tries to boot without me trying to turn it on, which isn't good either.
I really like(d?) My phone, should I just accept its gone and move on?
My son's old Wildfire is driving me bonkers this now!

Sv: [Q] Boot loop - insurance wont fix as saying it is water damaged
Well, I would say it's toast.. From the given status of the hardware i see no way to recover, without involving a technician. But with water in the game it can be hard to pin down the reason for the behaviour.. I would say the main print since it turns on and off by itself..
Have you tried drying it, and for how long has it been this way? Also, do you have the guts to open up the phone for a diy fix?
Kind Regards
TwinAdk
- Via the premium XDA app

TwinAdk said:
Well, I would say it's toast.. From the given status of the hardware i see no way to recover, without involving a technician. But with water in the game it can be hard to pin down the reason for the behaviour.. I would say the main print since it turns on and off by itself..
Have you tried drying it, and for how long has it been this way? Also, do you have the guts to open up the phone for a diy fix?
Kind Regards
TwinAdk
- Via the premium XDA app
Click to expand...
Click to collapse
Hi,
I am in the process of appealing with my insurance company. Their case is that I didn't disclose all the material facts, but I am of the opinion that if it was water damaged at some point, then it has worked for weeks before it decided to play up, so that cannot be the reason. I did put the phone in a sealed box of rice and placed that in the boiler cupboard for 3 days when it was returned by the insurance co. When I took it out it was exactly the same as before. The phone came out on Monday of this week.
I'll wait for the result of my appeal before I pull it apart. Not entirely sure what I would do once in the case, but I'll cross that bridge when I come to it!

Sounds like a plan, post back I have *NO* experience taking these things apart though.

If you need to take it apart its not that bad. I had to dismantle mine when my sons drink spilt all over it and it started rebooting and went into safe mode before I could turn it off. There are videos on youtube to show you how. However if you have dried it as much as you say I am not sure what you can do once in there
Water got all around my SIM and volume controls but all ok once dried out.
Good luck
Sent from my HTC One X

herbie13 said:
If you need to take it apart its not that bad. I had to dismantle mine when my sons drink spilt all over it and it started rebooting and went into safe mode before I could turn it off. There are videos on youtube to show you how. However if you have dried it as much as you say I am not sure what you can do once in there
Water got all around my SIM and volume controls but all ok once dried out.
Good luck
Sent from my HTC One X
Click to expand...
Click to collapse
Thanks herbie. I should hear back from my insurance company regarding the appeal I made over the next day or two. Fingers crossed I wont have to resort to pulling the phone apart. Pretty sure that the board is fried, so not sure what I would achieve anyway.
I've still got the phone and have had it in the boiler cupboard again inside a box full of rice, so if nothing else, anything that may have been in there will be long dried up by time I hear back. I'll pull it out after they get back to me.

chouman said:
Thanks herbie. I should hear back from my insurance company regarding the appeal I made over the next day or two. Fingers crossed I wont have to resort to pulling the phone apart. Pretty sure that the board is fried, so not sure what I would achieve anyway.
I've still got the phone and have had it in the boiler cupboard again inside a box full of rice, so if nothing else, anything that may have been in there will be long dried up by time I hear back. I'll pull it out after they get back to me.
Click to expand...
Click to collapse
Guys, just want to thank you for your time on this one. I've had a letter through this morning accepting my appeal. They asked me to get a letter from my network confirming that the IMEI of this phone was in use up until the date I said and I sent this in, and I sent this on.
I've just called them and they said that the phone was unrepairable and I should expect contact within 3 working days with either a replacement being sent out (reconditioned phone) or a cash payment to buy a replacement.
Just a few more days with a 3/4 year old HTC Wildfire then back to a speedy One X (or One if they make a cash offer!).

Sv: [Q] Boot loop - insurance wont fix as saying it is water damaged
Thats great Nice that they accepted the appeal. They seems thorough in that they are asking for the imei number and proof of usage, wow
Kind Regards
TwinAdk
- Via the premium XDA app

Hi!
Sorry for bumping the topic, but I had the same problem.
The power button was broken, and was constantly pushed in. The device rebooted all by itself, and couldn't charge.
I replaced the power button and it all works like a charm right now!
Sorry for being to late, but I discovered yesterday

Sv: [Q] Boot loop - insurance wont fix as saying it is water damaged
Didn't the constantly pressed power button result in the buttons below the screen flashing? I don't know if the OP experienced this..
Kind Regards
TwinAdk
- Via the premium XDA app

TwinAdk said:
Didn't the constantly pressed power button result in the buttons below the screen flashing? I don't know if the OP experienced this..
Kind Regards
TwinAdk
- Via the premium XDA app
Click to expand...
Click to collapse
I don't think there was any issue with the power button, but it would make some sense. I did ask what they found to be wrong with the phone and the lady on the phone just said it was unrepairable.
I called again today and I've been told to expect a white 32gb One X to be coming my way (again within 3 days which seems to be their standard response to anything!), so glad it's all over. Hoping to get my wife to take it on to replace her white iPhone 4S which is coming out of contract in a couple of months as she's after something faster and I'll get the new HTC One, but not too confident of pulling that off!

No, my buttons weren't flashing at all, if you try yourself, they aren't flashing too.
Glad it's fixed but I'm pretty sure it was the power button

[Q] How concerned should I be about my SGS3?

This is a bit of a long story but I need advice and I'm not sure where else to go. I have the phone rooted but the only thing I've done is install KT747.
I'm not sure if it's related but I'll open with that about 6 months ago I dropped it in the bathtub (dumb as hell I know), took it to the sprint store and BSed them about what happened. They opened it up, saw the water indicator/water, called me on my BS, dried it off and cleaned the contacts with rubbing alcohol and my phone came back.
Fast forward to Tuesday, at work with my phone plugged into my laptop it cut off and would simply not come back on. The samsung logo would come up and then the KT747 "Kernel Domination" screen for a moment but then it would cut off. The phone would be on for maybe 3 seconds total. Even if I tried to boot into recovery or even download mode the same thing would occur (I think one time I got it to show the flash count and all that jazz in download mode). As the water indicator will still show water damage and you can clearly tell I've rooted it I was worried I might be screwed out of a phone, but I thought I was screwed the last time I went to sprint so I left to go do that, half way between work and the sprint store my phone cut back on in my pocket. Over the next day and a half it had similar problems but eventually came back (quicker than the first time). And now it's been running well for 3 days.
I've been doing some research on google and I've seen something about a motherboard defect that can cause sudden death, but I think this might be the international S3. It's really hard to tell what's what. Also I saw someone say it could be a battery issue so I ordered a new one but I'm still concerned this might not be the issue.
It's working fine now but I'm in constant fear my phone will just die any moment now.

Fr33dan said:
This is a bit of a long story but I need advice and I'm not sure where else to go. I have the phone rooted but the only thing I've done is install KT747.
I'm not sure if it's related but I'll open with that about 6 months ago I dropped it in the bathtub (dumb as hell I know), took it to the sprint store and BSed them about what happened. They opened it up, saw the water indicator/water, called me on my BS, dried it off and cleaned the contacts with rubbing alcohol and my phone came back.
Fast forward to Tuesday, at work with my phone plugged into my laptop it cut off and would simply not come back on. The samsung logo would come up and then the KT747 "Kernel Domination" screen for a moment but then it would cut off. The phone would be on for maybe 3 seconds total. Even if I tried to boot into recovery or even download mode the same thing would occur (I think one time I got it to show the flash count and all that jazz in download mode). As the water indicator will still show water damage and you can clearly tell I've rooted it I was worried I might be screwed out of a phone, but I thought I was screwed the last time I went to sprint so I left to go do that, half way between work and the sprint store my phone cut back on in my pocket. Over the next day and a half it had similar problems but eventually came back (quicker than the first time). And now it's been running well for 3 days.
I've been doing some research on google and I've seen something about a motherboard defect that can cause sudden death, but I think this might be the international S3. It's really hard to tell what's what. Also I saw someone say it could be a battery issue so I ordered a new one but I'm still concerned this might not be the issue.
It's working fine now but I'm in constant fear my phone will just die any moment now.
Click to expand...
Click to collapse
If it was working fine before you dropped it in the water, then that's probably the cause. I doubt it's sudden death syndrome if there were no signs of shutting on and off before you dropped it in the water.
sent from my GS3 usin Tapatalk4

joeyhdownsouth said:
If it was working fine before you dropped it in the water, then that's probably the cause. I doubt it's sudden death syndrome if there were no signs of shutting on and off before you dropped it in the water.
sent from my GS3 usin Tapatalk4
Click to expand...
Click to collapse
But would I expect to see problems from water damage so long after the contact with water? I figured if there were going to be problems from the water it would have happened much quicker than this. Like I said the water damage was MONTHS ago.

Sounds like SDS power button failure. Very common on S3.
Sent from the future via Tapatalk 4