So I just got this Captivate and it's not rooted or anything. I used the Sideloading Wonder just once for an app. But then I tried to do a software update and the phone went black. After about 30 minutes it was really hot and I could not turn it back on. Any suggestions as to what the problem may be?
Installing one app with sideload wonder mechine, should not have casued any issues.
If your phone "Bricked" while downloading and installing the update, I recommend taking it into an AT&T warranty center and have them replace it. There are ways in most cases to unbrick the phone (I think), but that requires flashing a ROM which will void the warranty and possibility make it so you cannot replace the phone under warranty.
When you go into the warranty store that you received a message to update the phone and it froze during the update and will not wake back up. They will either fix it on the spot, which I doubt, or excahnge it for a referb that will still be under warranty for the rest of your 1 year warranty period.
Is there any reason the phone isnt coming back on at all. I mean do you think maybe the battery could just be shot and all i need is a new battery?
If its a new phone and not refurbished, I highly doubt its just the battery.
On another android forum there was a topic about over clocking, it mentioned the battery will begin to deteriorate when it hits temperatures around 140F, it never said it would completely fail. (correct me if I'm wrong)
But, it may be possible, but I don't think it would be the complete reason.
Sent from my SAMSUNG-SGH-I897 using XDA App
Related
My wife is complaining about several issues with her Inspire (recent iPhone convert ), but the biggest baddest one is that the phone routinely will power itself off while unattended, and then it won't power back on until we pull the battery.
This has happened several times.
She doesn't have any unusual apps and the phone is unrooted running the regular AT&T software.
Anyone know what could be causing this? Is this likely hardware?
mr72 said:
My wife is complaining about several issues with her Inspire (recent iPhone convert ), but the biggest baddest one is that the phone routinely will power itself off while unattended, and then it won't power back on until we pull the battery.
This has happened several times.
She doesn't have any unusual apps and the phone is unrooted running the regular AT&T software.
Anyone know what could be causing this? Is this likely hardware?
Click to expand...
Click to collapse
I don't know how long you've had it but it should be under warranty whatever the cause. My last refurb from ATT was given the remainder of the warranty from the original device. I would recommend a warranty replacement.
Sent from my Inspire 4G using the power of the dark side
No point in going through the hassle of a warranty replacement if this is a software issue. That's a lot of stuff to set up again once you get the replacement phone. Remember this phone is not rooted, no nandroid backups...
mr72 said:
No point in going through the hassle of a warranty replacement if this is a software issue. That's a lot of stuff to set up again once you get the replacement phone. Remember this phone is not rooted, no nandroid backups...
Click to expand...
Click to collapse
Yes, but this doesn't sound like a software issue. You could try running the RUU. It's around here somewhere. This will reset the software to stock, straight from ATT. But again, you'll have to set everything back up. If it were mine I'd go for a warranty
I would rather spend time setting up a working phone than keep trying in vain to fix something that just isn't gonna be right. In either case, the next step is probably a factory data reset. A stock, un-rooted phone should not have any mods that would cause that. You don't undervolt or overclock. Market apps should not cause an overheat. It might be the battery, you could try that first, but if it powers back on after a pull, I don't think that's gonna be your problem.
Sent from my Inspire 4G using the power of the dark side
I know there was a rash of defective batteries out there, and that could very well be the problem. I saw that many people having suspected battery problems were able to get a new battery for free from HTC customer service. Worth a shot.
pazzo02 said:
I know there was a rash of defective batteries out there, and that could very well be the problem. I saw that many people having suspected battery problems were able to get a new battery for free from HTC customer service. Worth a shot.
Click to expand...
Click to collapse
I agree, that's probably worth a try short of a complete replacement phone.
This was happening to me lower ur CPU settings and it's should work better or try to plug in the charger and it will come back hopefully
Sent from my Inspire 4G using XDA App
Phone info: rooted, stock, s-off, CWM 5.0.2.7, BusyBox 1.17.1, ES File Explorer
In a nutshell, my phone's display died after a bit of condensation appeared under the glass. I have no idea how the moisture happened, as I've been babying this phone since my 1/7 purchase, and I haven't dunked the phone in water or exposed it to steam. Had it tucked in an inside coat pocket while going for a walk, discovered condensation spots later that evening (and no, I don't sweat like a horse, either). Screen began flickering over next four days, requiring brightness to be turned up to max, but otherwise operated normally--until day five, when the display went out completely. Liquid indicator under the battery is pure white, btw.
So, after discussion with HTC Warranty and Repair, my phone will be shipped off to be fixed, hopefully, under warranty, and I won't get dinged for out-of-warranty repair since this is a moisture issue (albeit one I'm baffled as to the cause).
What I'd like to know is what to expect upon return of my repaired phone. I know the HTC tech's will likely be wiping all data, and this means I'll have to reroot, correct? I have my most recent Nandroid backup on both my PC and my SD card, so I can restore to that, but I wasn't clear about the rerooting end of things.
Any experiences from others who have gone through the warranty repair process would be appreciated.
Many Thanks --
--
King Cheetah
Well I sent my 3G Slide in to get the camera lens cover and keyboard fixed. I had the old hboot and flashed back to stock with s=on. They fixed the 2 issues and updated my phone to the Froyo OTA with the new hboot.
It isn't unrealistic to think the same would happen. So the Fabulous work the guys in the dev forum will be more appreciated once the hboot issue is solved.
Sent from my myTouch_4G_Slide using xda premium
Actually, I just got back my phone from repair. hboot was 1.44.007 the one that is hackable.
It's essentially a roll of dice right now, because the OTA isn't in full effect yet. Maybe you can make a special request that they don't restore your phone (although that's usually the first thing they do) or tell them that you don't want the latest OTA
That pretty much answers my question--I'll have to go through the process once more for root once I get it back.
As far as I've been able to glean from the HTC and T-Mobile forums, the OTA is still on hold due to error troubleshooting, so I doubt that will be applied until all the bugs have been squashed. In fact, there's no word that the update will be ready this month, so I'm fairly confident the hboot will still be 1.44.007.
Thanks for the replies --
--
King Cheetah
Yea - I sent one in to be serviced and got it back as it went out (fixed though) and still had s-off 1.44.0007 hboot.
I restored everything else to stock retail launch before sending it in.
They told me on the phone before I shipped it that if they chose not to repair i'd get charged. If there was evidence of tampering it was their option to not do anything to it.
I was also told that it would be flashed to their current software as the last thing before it left the factory.
I imagine it's up to the tech to decide if they want to work on it if it comes in with s-off - but now we have a guide for how to get s-on so this should no longer be a concern - it's in dev here.
Also, my theory was that the update being on hold was why I got it back with the software I sent it out on - and seems to be what everyone else thinks too.
So I have a new Galaxy S3 I747 Bell Canada, and I'm thinking of rooting it, but I still have 11 months of warranty left. Now I know that I can just follow the complicated guides to 'unroot' it, if I need to send it back, but has that ever actually worked for anyone here?
Because think about it. If you need to send your phone back for warranty, it is probably broken, right? If your phone is broken, how can you possibly unroot it first? Sure there are some non-bricked reasons you could send your phone back, such as a broken camera or a small deadzone in the touchscreen, but I'm just worried that my phone will suffer a NAND flash breakdown (after that whole kefuffle in the news) or a malfunctioning CPU while in a rooted state.
But then I think, well if the NAND flash or CPU completely dies, will THEY even be able to tell if the phone is rooted? I mean sure they have tools where they can rip the flash out of the mobo and read it and see if it's rooted, but to do all that would cost them labour hours. I would imagine if I sent back a rooted phone with just a broken camera, they would turn on the phone and see the big "THIS PHONE IS ROOTED!!!" message and refuse my warranty, but if I can turn my phone on, I will unroot it before I send it in for a broken camera. But if the phone CANT turn on, would they really bother with all those low-level hardware tools to try and fix my phone and see if its rooted? Wouldn't they just send me a new phone, and possibly try and refurbish my broken one to resell, without ever noticing that its rooted?
Depends on what your issue. Most of the buttons on my D2 stopped working and I had to send it in for warranty. Had to sbf and wipe and then it was fine. VZ has additional "root counter" features, but as you aren't using their device the standard unroot procedures should be fine. I think they take care of the on-board root counter.
If your phone is completely unusable then you're just out back. Obviously you can't take care of what you need to do if the phone isn't functioning at all. That said, depending on the damage they might not even be able to check for root anyway, and they just might not care. Also depends on your carrier's policies.
Honestly i don't recomend rooting ur phone on the the warranty period
My wife's phone randomly turned off yesterday and we just ignored it. Today, it would randomly restart and/or turn off at least 3 times the whole day. When we have it plugged in to charger, it would randomly turn off and restart. Then we have to pull the battery out to turn the phone on. But now, the phone won't even turn on anymore. I have a G5 (w/ Verizon) and we tried swapping the battery packs and her phone won't turn on. Just to be sure, I plugged her battery to my phone and it started, though it displayed a "Module not compatible with Verizon"
Anyone else running into similar issues?
Yes. Today I had about 30 app updates to do in Google Play. I set it to update all while here at work, put it in my pocket, and went to take care of some tasks here in the building. The next time I pulled it out about an hour after that, I noticed the phone was off. It wasn't hot or overheating, and the power button doesn't respond regardless of how long I hold it in. Recovery mode also doesn't start up. I removed/reinserted the battery multiple times to no avail.
My phone did the same thing! It just froze one day and I had to battery pull to get it working again. Then later on it froze and started resetting over and over again. Finally it froze, shut off, and never worked again no matter what I did. It might be a bad batch of these phones. I am now on my fifth phone. The other three had dead pixels. I hope my fifth phone won't have any of the previous phones issues.
DarkMage619 said:
My phone did the same thing! It just froze one day and I had to battery pull to get it working again. Then later on it froze and started resetting over and over again. Finally it froze, shut off, and never worked again no matter what I did. It might be a bad batch of these phones. I am now on my fifth phone. The other three had dead pixels. I hope my fifth phone won't have any of the previous phones issues.
Click to expand...
Click to collapse
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
I'm in the UK on EE and I've also had this problem with both my original LG G5 and the replacement. The phone display would randomly disappear then it would be impossible to switch it back on using the power button and recovery mode didn't work either. The only way to make it work again was to plug it into the charger.
Luckily I was within the 14 days and have returned them both. The second is awaiting assessment by their engineers but I've lost faith and am going with the Samsung Galaxy S7 instead.
woodie said:
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
Click to expand...
Click to collapse
I called T-Mobile and told them my phone was dead. Saying it was dead allowed me to avoid all the tech support questions and they sent me a new phone with 2 day shipping. I was surprised how quickly they sent the new phone to me. I don't think there is any way they will give you a full refund if you are outside of the 14 day window but you are still well within the warranty period so I would keep bugging them till you get a phone you are fully satisfied with.
In addition you can use the LG backup app to save all apps and the associated data. After everything is backed up wipe the phone that way you keep your data with you on an SD card. I couldn't wipe the data off my dead phone but I doubt it could be retrieved anyway.
woodie said:
I'm on my second one, but now I'm past the 14 day return window. How do I go about getting this replaced? Can I take it to my local Tmobile store or do I contact LG? Should I be concerned about pictures and data being retrieved off of the phone if I ship it off somewhere in exchange for a replacement device? I know it's pessimistic to say, but if I wanted to return the device due to these defects for a full refund and go with a different phone, is that possible at this point?
Click to expand...
Click to collapse
if you call t mobile and tell them about yiur problem they will send you a new one try it
Sent from my SM-G935T using XDA-Developers mobile app
Hey all,
I'm admittedly not into the whole rooting scene, so I know very little about it... bear with me.
I have a Galaxy S6 with water damage to the screen, so I used my SquareTrade warranty to receive a replacement device. Just turned it on this morning and set it up, no problem - synced my Google account, re-installed my apps, etc. Then it popped up a message that Samsung had a major firmware update and that it needed to restart to complete the process, so I clicked restart and install.
Phone restarts, and doesn't come back on. Top left of the screen it says something about "Custom binary blocked by FRP Lock". I Googled this and found stuff coming up about rooting phones, but obviously that's not what I was even trying to do. Someone said if you try a hard reboot it can fix the issue, so I did that, but when I hard rebooted it a message came up warning me about the dangers of installing firmware from third parties and whatnot, but that I could proceed if I knew it was safe, so I did that. I also noticed in the top left of this screen it said "Knox Counter: 1 x 00500"
At this point it tells me it's installing and to not reboot the phone, but a half hour goes by with no progress. I Google the Knox counter thing and stuff comes up about rooting and voided warranties. I call Squaretrade, and speak to a specialist with broken English and try to explain. He says he'll send a replacement to me (and they can't guarantee that it will be a black S6 which I'm bummed about). I make it clear that I was not the one who "jailbroke" the phone because my concern is that Squaretrade will turn the device on, see the message and assume I did it and charge me the $750 replacement fee, believing me to have voided the warranty. He assured me that he made a note of it on the claim and that I shouldn't be charged... but I'm still worried about it.
Worst case scenario just in case something goes wrong and they try to charge me, I'd love to know what y'all think might have happened here. Do you think the previous owner of this phone (since the replacements are refurbished) tripped the Knox counter? Why did it work the first time I turned it on but then crash after I tried to install a firmware update? And when I receive the next replacement, how can I make sure this doesn't happen again?
Now I have TWO phones I'm on the line for sending back to SquareTrade (the original damaged phone and the replacement with the voided Knox counter) and I'm so paranoid that I'll get f**ked over somehow. Any input would be greatly appreciated!