Related
Hello,
My Desire S froze when updating Skype 2 weeks ago.
Removed battery. Phone stuck on HTC logo.
Went to bootloader for hard reset. When hard rest chosen phone freezes.
Went to recovery, phone starts recovery. Black screen, green icon. Then goes dark. Starts to vibrate 6-7 times. Then remains off. Battery out, battery in. Back to HTC logo again.
Laptop recognized phone when plugged in with fastboot mode. Under device manager (win 7) "HTC phone".
I bought the phone in Thailand, but am now in Philippines where there is no HTC repair center.
I managed to find RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed
Which matches my phone. However when trying to install the rom, the above app freezes on "restarting bootloader". I've left it there for over an hour.
I've tried ADB, but it's not picking up the phone.
I'm guessing either of the above can't load, as the phone is S-on.
But I cannot go S-off as I can't get the phone to boot, or any of the above software to find the phone. Again, windows is picking up that there's a HTC phone plugged in.
I've tried everything I know, and am at my wits end into thinking the phone is finished.
Can anyone help with something I may have overlooked, or have a suggestion to bring this back to life?
Thanks
It's most probably a hardware problem. There's a high chance that your phone's emmc chip is fried when u remove the battery. it's common in htc due to the phone design. My phone encountered same thing 2 weeks ago. sent for repair and they change the mainboard. I was lucky they ignored that my phone was S-on(warranty voided)
I was thinking hardware last week after everything was failing. But as it was still booting to fastloader, and being picked up via usb was holding out hope it might just be the s-on preventing me from putting on a new rom. And not a mainboard gone.
Flying back to Thailand for the warranty would cost the same as buying a new phone ...
If taking a battery out when a phone is frozen fries a mainboard on HTC ... I doubt I will buy one again.
Looking at Galaxy 2. But also having doubts due to wifi reports and overheating screen. Can't afford another dud smartphone.
If anyone's got anything else to get this thing up to see if the mainboard is indeed dead, or it's something else, do make a suggestion please!
I have same problem like this before and it's really pain in the a#$. Also, there is one HTC service center here in the Philippines, check it out on HTC site.
Sent from my HTC Desire S using XDA App
Thanks MarlX
Yes, I've been in touch with HTC repair center in Manila via phone and email. I've been waiting for reply for over one week now!
I'm not in Manila, which would mean using fedex to send it up to them. Then bank transfer to pay for repair and shipping back.
If it is the Motherboard that's gone, all the above will probably cost more than a new phone
But I won't know until HTC Manila actually bother to reply!?!
so what was the Problem is it becoz of Skype?
no,this problem happens if you pull the battery out when installing apps
the emmc chip is probably dead,if so you need to send it for warranty or replace the emmc chip yourself
Well unfortunately, when updating the skype app, the phone froze. As in no buttons working, phone getting hot etc.
What else is there to do but take the battery out?
Either way, to have a "premium" phone like the HTC Desire S, burn out a chip, or indeed have a popular app causing it to brick etc is simply not good enough.
More over the support center refusing to reply back.
It simply means they've lost another customer.
The phone, when working, was wonderful. Looking at the Galaxy S 2 today, by all accounts a "better" phone, and it was sad. As, for me, the HTC Desire S was much more preferable.
Except of course for it's 6 week lifespan ... bad customer care etc
Just to bad that you did not bought it here. My phone died two months ago (used it only for a month), sent it to the store and they've sent it to service center (in Manila). Had to wait for a month for them to fix it. Motherboard issues I think. Good thing I still have warranty.
Sent from my HTC Desire S using XDA App
DDesires said:
Well unfortunately, when updating the skype app, the phone froze. As in no buttons working, phone getting hot etc.
What else is there to do but take the battery out?
Either way, to have a "premium" phone like the HTC Desire S, burn out a chip, or indeed have a popular app causing it to brick etc is simply not good enough.
More over the support center refusing to reply back.
It simply means they've lost another customer.
The phone, when working, was wonderful. Looking at the Galaxy S 2 today, by all accounts a "better" phone, and it was sad. As, for me, the HTC Desire S was much more preferable.
Except of course for it's 6 week lifespan ... bad customer care etc
Click to expand...
Click to collapse
yeah,this is really bad
but mine has been working for 3months without any problem,& the customer support here is good
if you dont mind voiding the warranty you can buy a eMMC & replace it yourself
if you do so you wont get this problem again
refer this thread for more info
There is software "hard" reset option. Instead of pulling the battery out, press all hardware buttons together (vol up, vol down, power button) and phone will reboot. I said this many times before in many topics: never pull out your battery when the phone is on. I learned it the hard way.
Sent from my HTC Desire S using Tapatalk
kartkk said:
if you dont mind voiding the warranty you can buy a eMMC & replace it yourself
if you do so you wont get this problem again
refer this thread for more info
Click to expand...
Click to collapse
Thanks kartkk. I wouldn't know where to begin with the physical replacement of the eMMC chip. Not even sure I can buy one around here.
I might call HTC Thailand and ask if I can send it to them via DHL or the like.
Numline1 said:
There is software "hard" reset option. Instead of pulling the battery out, press all hardware buttons together (vol up, vol down, power button) and phone will reboot. I said this many times before in many topics: never pull out your battery when the phone is on. I learned it the hard way.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
maybe you should ask HTC to write that in big red writing on the back of their batteries as they start to reach burn your finger stage when the phone freezes.
Or maybe copy Nokia's hardware which is near on indestructible.
Quite simply, I am not a phone tech person. I'm a simple end user.
I've not had a problem taking a battery out of other phones.
Again, if taking a battery out of a phone kills it when it freezes, then quite simply the phone is not good enough. Or, if it is likely to. Then, again, in big writing for simple folk like me, big red writing on the battery saying
"don't take this out, even if it starts to feel like it's going to melt"
BTW if anyone can point me to a step-by-step on how to determine if the eMMC chip is fried or not, I would appreciate it.
I read the above link. But don't know how to get to that stage!
Apologies I see he was connecting via adb-shell. I've tried connecting via adb and it's not seeing the phone....
Which I think is half the problem.
DDesires said:
maybe you should ask HTC to write that in big red writing on the back of their batteries as they start to reach burn your finger stage when the phone freezes.
Or maybe copy Nokia's hardware which is near on indestructible.
Quite simply, I am not a phone tech person. I'm a simple end user.
I've not had a problem taking a battery out of other phones.
Again, if taking a battery out of a phone kills it when it freezes, then quite simply the phone is not good enough. Or, if it is likely to. Then, again, in big writing for simple folk like me, big red writing on the battery saying
"don't take this out, even if it starts to feel like it's going to melt"
Click to expand...
Click to collapse
try searching on ebay for sandisk mmc (or any other brand just dont get the same one used on the DS)
its always dangerous to pull the power from any device which works like a pc even in a pc pulling the power out while the device is on can harm the hardware &/or software i know many people who damaged their pc from pulling the plug while its on
Best to my knowledge it was an emmc chip that was recommended to be replaced. Not an MMC.
While removing "power" abruptly from any electronic device is not recommend, one is sometimes left with no choice. Complete device freeze, no buttons working etc.
There is also a destine difference between a PC and a mobile phone. Though, it must be said from my point of view: today's Android phones, are very reminiscent of old windows 95/98 OS's in terms of stability and hardware issues.
I recently flashed CMRex with Kejar's 4.1.1 gapps and was going about setting up my device. I got everything set up how I like with all the apps I wanted downloaded and running how I wanted them. I then ran the v6 supercharger mod that I had used on my past two roms with no problem whatsoever. After finishing the set up of the script, I rebooted my device and all was well. I went to browse on craigslist's mobile app, then I saw something I wanted to google, so I opened my browser. My browser took an ungodly amount of time to load my homepage(google), and wouldn't respond hardly. I couldn't get the touchscreen to respond. My hardware buttons did respond and I got haptic feedback from them, but no response on the screen. Eventually, after numerously pressing the home button, I got a message saying the browser wasn't responding, selected ok to close it, then back to the non-responsiveness of the touch screen and hardware buttons. And then another eventually later, after another multitude of home button presses, I got to my homescreen but everything was laggy. The most lag I have ever encountered with my device since I obtained it, not to mention that my device was beginning to heat up. So, I decided I would power off the device, remove the battery, let it cool down, and then replace the battery before powering it back up. Well, lo and behold, I did just that, went to power back up my device, and there was no sign of life at all. Tried to get into the bootloader, no response. Tried a normal boot, no response. Tried to plug it into the charger to see if it would charge, no response. Well, my girlfriend told me to leave the battery out for a while and leave it alone for a while before trying it again. So, I played some MW3 for about 45 minutes to an hour, repeated all the above, and still no sign of life. Can anyone help me out? (I don't know if this is supposed to go into the Q&A or here, so I just post here.) I'm so distraught at the possibility of losing my phone, that I'm finding it hard to cope at the moment. Should be thinking of ways to gain some money in order to purchase a new device or is there still hope?
what a long message.do you have any point form here?
i hope you solve the problem .
Do you have access to a separate charger? You can try charging your battery there and see if that works. Did you try connecting it to the computer? Maybe that will show some sign of life. Also, how old is your phone and did you over clock?
Sent from my Nexus S using xda app-developers app
kwibis said:
Do you have access to a separate charger? You can try charging your battery there and see if that works. Did you try connecting it to the computer? Maybe that will show some sign of life. Also, how old is your phone and did you over clock?
Click to expand...
Click to collapse
I did not overclock, I do believe that my clock speeds were at the kernel default, either 100/1k, or 200/1k. Not sure which, but definitely one of those. The only other charger I would have access to would be my mother's HTC charger, but I will try that and connecting it to the computer as well. Well, I'm not exactly sure on the age of the phone because I purchased it off of craigslist, but it's in great condition. Only had a small scuff on the top left corner, but I know that has nothing to do with the age of the hardware. ): Could it possibly be that my battery decided to die for some reason? I've been having horribly battery life lately. Granted, I had horribly battery life when I got the phone, but it's gotten worse and worse since then.
My Nexus S wouldn't start but gave a flash on the screen when the battery was first inserted. Just got it back from repair and it was a motherboard problem. Was looking at a Huawei G300 as a cheap replacement if the repair wasn't covered by warranty (which it was). Good luck!
Thing about it is, I bought the phone off craigslist so I have no idea if its covered by the warranty still. Should I try calling samsung and find out?
Sent from my SGH-i997 using xda app-developers app
Sorry for my late reply! You could try, but u guess you can get a battery from Ebay and check if that solved the problem. Or if you have a friend who has one...
Sent from my Nexus S
I'm the only person I know that has this phone. And I guess the battery will have to wait till I get a job, but if im waiting that long, I'm just going to get a new phone all together.
Sent from my SGH-i997 using xda app-developers app
Testing the battery can be done differently, do you have a multimeter? Maybe your neighbours have one, it's a common thing. You can measure whether it has any power left. If you measure low voltage (below let's say 3400 mV), then it could be battery related.
Sent from my Nexus S
DefinitiveX said:
I recently flashed CMRex with Kejar's 4.1.1 gapps ... or is there still hope?
Click to expand...
Click to collapse
Many reports on dead Nexus S with 4.1.1. Mine included after flashing CM10. Sent for repair 10 days ago and still waiting...
If you've got no warranty, perhaps time to buy a new phone? Bought myself a new Galaxy Nexus.
I would like to get a new galaxy nexus, but I have no money to do so. I'm currently trying to get a job and i m going to save up for a new phone. Im either going to get an s3, a galaxy nexus. Either one of those two or the new nexus if it comes out.
Sent from my SGH-i997 using xda app-developers app
Hi guys,
my DS did some strange stuff lately. It began with the screen staying black when I woke it up (hardware buttons did turn on and touchscreen also worked). I thought it was a software issue, because after a few on and offs the screen usually worked again. Also, this never happened when the phone was charging.
But a few days ago the screen never turned back on again, even when charging. I got a new battery but still no change. It won't even turn on when booting or when going to fastboot/ hboot.
Does anyone have an idea what is broken? I think my best guess is to have a look at these other screen replacement threads, but I wanted to ask first because the screen seemed to have gradually become broken, which confuses me. I didn't think something like that was even possible. Also, I can't return it since I bought it used and in Germany (DS is USA exclusive).
Thanks for help
Most certainly hardware as it is black when in bootloader and ROM. Best guess is the LCD but could also be the main flex the likelyhood of any thin else is fairly small.
Do read up on the screen replacement threads as this phone is one pain in the ass, you also need to be aware of what LCD to buy as there were different ones and they are not compatible.
Sent from my Nexus 7 using xda premium
demkantor said:
Most certainly hardware as it is black when in bootloader and ROM. Best guess is the LCD but could also be the main flex the likelyhood of any thin else is fairly small.
Do read up on the screen replacement threads as this phone is one pain in the ass, you also need to be aware of what LCD to buy as there were different ones and they are not compatible.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the tips. Screen might be still ok since it went out gradually, could be a defective contact since it also went on and off randomly. But I guess there is no way to only replace this contact, too complicated to find out... I will see.
Yeah, I had a look at these threads already, thank you
I had a program that I moved to the sd card that would cause the screen not to come on and would have to do a battery pull. When I moved the app back to the phone, the problem stopped.
(Walgreens app)
It has happened again since, so it may be another app I have to track down. Or I may be looking at faulty screen trouble too.
Sent from my MyTouch 4G Slide using Tapatalk 2
even if an app on sd were the cause of this it certainly couldnt make the screen blackout while in recovery and bootloader mode. to the best of my knowledge it has to be a hardware fault if screen wont turn on in bootloader... but well ive been proven wrong in the past
Well since I had problems with the screen turning off before when it did work in recovery, there might be a connection to daswerk's case. However I kept all my apps on the internal SSD and do remember checking it. Also, my screen turned back on sooner or later or when I played around with the keyboard.
However later it was off even in recovery mode. I did disassemble my DS lately (and broke my screen like seemingly everyone else hehe) and am now waiting for my new LCD screen to arrive in Germany from the states haha. Shipping costs were higher than LCD costs, d'oh! Thanks again demkantor, you've been helping me indirectly with your posts in the other threads as well
So guys, screen arrived, reassembled my phone, switched it on aaand... black screen.
Graphic chip or motherboard may be broken. I'm thinking about a loose connection because screen turned off once in a while before it never got back on. I found a user by coincidence here on xda who reported the same problem.
Any ideas are greatly appreciated. Don't want to forsake my dearly loved DS :'(
Next most likely would be main flex cable
Sent from my Nexus 7 using xda premium
demkantor said:
Next most likely would be main flex cable
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Are there other possibilities as well? I'm thinking about getting a whole replacement set so I can try everything shipping costs are high since I live in germany hmmf
btw, digitizer/ touchscreen doesn't seem to work either, is this another sign that main flex cable is the prolem?
There are always more possiblities I was just letting you know what I would replace next as the most likley cause.
Having multiple phones to exchange parts is a good idea and really about the only way to test different components
And yes have no digitizer working can be a sign of a bad flex as well
Sent from my SGH-T839 using Tapatalk 2
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
hollovoid said:
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
Click to expand...
Click to collapse
To put it simply, if there's ANY way I can determine if it's a software issue, I'd like to try it. A phone this expensive really has no excuse to have a hardware issue. I've heard the SIM reader can sometimes cause system problems, so I'll try blowing in the slot like an old N64 cartridge and seeing if maybe it misreads while charging and shuts off because of a speck of dust, or something ridiculous like that..
greydelta38 said:
Would it be worth reflashing the stock Motoblur 4.1.2? I used to run CM10 on the old GNexus, I'd love to use that again on my HD, if it's available.
As for a new phone, if need be, my upgrade happens to be right after the GS4 is released on Verizon so I might as well get that and then not have to worry about F-ing up my primary phone. I'm a little wary of rooting whatever my primary device is, because I've bricked a Bionic with a stupid mistake I made when I was new to Android.
Click to expand...
Click to collapse
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
hollovoid said:
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
Click to expand...
Click to collapse
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
greydelta38 said:
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
Click to expand...
Click to collapse
At this point, all CM builds are unofficial. All 10.1 builds are 4.2, 10.0 is 4.1. We are only going to get official when a proper kernel is ready and we have full functionality. 10.0 should have most everything working though, as the official moto builds are on 4.1.2. It does suck, Imagine if moto had never developed that ridiculous bootloader of theirs, we would be in great shape! But it is getting better, just everybody is starting from scratch now that its unlocked, so the pace seems slow.
If you don't mind the camcorder not working, the AOKP and Xenon HD builds are pretty awesome for 4.2. Best way to try them out is to put TWRP on and backup your stock, then you can switch between roms very easily and see if anything improves. The other recoveries should work the same as well, but ive only had experience with TWRP on this phone, and it works very well.
greydelta38 said:
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Click to expand...
Click to collapse
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
jfriend33 said:
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
As I said in my post, I don't have a warranty, and I don't particularly care about a warranty. Motorola CS is pretty awful, they're all bored and don't really give a crap about your problems, unlike the friendly and caring service I've gotten from Samsung before. I don't want to sell it, seeing as how the RMHD is arguably the best phone on the market for the time being.
UPDATE: I uninstalled a RAM booster called Memory Booster - RAM Optimizer a few days ago, and have yet to have a charging problem. I had the booster set to auto clean the system garbage when the screen was off. I'm making an educated guess here, but I'd be tempted to say that it was killing one of the Android processes that keeps the phone awake while charging, and it would bug out and crash.
Long story short, if you're having a problem with an HD shutting down overnight, UNINSTALL ANY APP KILLERS, TASKERS, OR RAM BOOSTERS.
Hope this works.
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
greydelta38 said:
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Yeah sounds like hardware.
Sent from my XT926 using xda app-developers app
scoobaspeaz said:
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
It's not hardware. I reflashed stock 4.1 AGAIN, and have yet to have it screw up. It's been about a week and a half since. Motorola sent me a new charger just in case. I know you guys think it's hardware but for some reason I'm totally convinced that it was an app screwing with Android. I guess I'll find out sooner or later. Thanks for the feedback.
Sent from my Galaxy S4 using xda app-developers app
Went to unlock my phone this morning off the charger and the screen is totally dead. Couldn't unlock or do anything to it or even see what was going on, called Google and ordered a replacement ASAP.
Went through the not fun task of doing a nandroid backup without seeing what was on the screen and doing some trickery with screenshots then backing up my entire SD card.
However, here's the strange and potentially dangerous thing that I noticed later when I got home this evening. I went to look at the phone and go to a fastboot flash with the factory images and went to touch the bottom of the screen. When I went to do so, to the little bit of the left of the LED light was a SUPER hot portion of the phone. I almost burnt my finger it was so hot.
Not sure what to do about the issue, I feel like if I just call the support line they won't actually take in my concern legitimately. Any suggestions?
thats something quite strange
let us know what google says about RMA and this issue
Agree, maybe it's just your phone, maybe it's all the batch. Which batch/model do you have?
Sent from my Nexus 5 using Tapatalk
kentoe said:
Went to unlock my phone this morning off the charger and the screen is totally dead. Couldn't unlock or do anything to it or even see what was going on, called Google and ordered a replacement ASAP.
Went through the not fun task of doing a nandroid backup without seeing what was on the screen and doing some trickery with screenshots then backing up my entire SD card.
However, here's the strange and potentially dangerous thing that I noticed later when I got home this evening. I went to look at the phone and go to a fastboot flash with the factory images and went to touch the bottom of the screen. When I went to do so, to the little bit of the left of the LED light was a SUPER hot portion of the phone. I almost burnt my finger it was so hot.
Not sure what to do about the issue, I feel like if I just call the support line they won't actually take in my concern legitimately. Any suggestions?
Click to expand...
Click to collapse
On my Transformer Infinity, sometimes the screen won't turn on at all. On a few occasions, if I press Power enough times, I get a glimpse of a message saying the Launcher process has stopped, but then my touchscreen doesn't register any input. The tablet is also sometimes running quite hot at those times. The only way I know to recover from this is press the Power button long enough to force a reboot, then everything is normal. Could this be what's happening? Do you know if the phone is still running under the black screen? Have you tried forcing a reboot, and did it work?
As for the hot phone, I've noticed my N5 does get a bit warm when I'm using it intensively (4G, WiFi, Bluetooth, GPS and screen on all at the same time and in use) but not enough to burn me. Could be hard to tell which component is heating up like that since I think it could be the screen backlight, SoC or battery... Do let us know if you find out more.
meethere said:
thats something quite strange
let us know what google says about RMA and this issue
Click to expand...
Click to collapse
I had called them and reported the screen totally dead with lines streaking vertically and got a new replacement ordered. It wasn't until late last night when I got back and had the screen on in this dead mode that the bottom was extremely hot. I'll have to call them back and let them know
dark_ente said:
Agree, maybe it's just your phone, maybe it's all the batch. Which batch/model do you have?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah hopefully, it definitely seems like it could be one of those things that could potentially start fire.The one I have is the LG-D820. Any more info I can provide?
daemonios said:
On my Transformer Infinity, sometimes the screen won't turn on at all. On a few occasions, if I press Power enough times, I get a glimpse of a message saying the Launcher process has stopped, but then my touchscreen doesn't register any input. The tablet is also sometimes running quite hot at those times. The only way I know to recover from this is press the Power button long enough to force a reboot, then everything is normal. Could this be what's happening? Do you know if the phone is still running under the black screen? Have you tried forcing a reboot, and did it work?
As for the hot phone, I've noticed my N5 does get a bit warm when I'm using it intensively (4G, WiFi, Bluetooth, GPS and screen on all at the same time and in use) but not enough to burn me. Could be hard to tell which component is heating up like that since I think it could be the screen backlight, SoC or battery... Do let us know if you find out more.
Click to expand...
Click to collapse
Yeah, no its definitely dead. There were streaked lines across it, rebooted it multiple times. I ended up going into the bootloader and recovery via adb/fastboot and all that jazz. It eventually just would not work now.
In regards to the hot part I definitely think it was the lower part of the screen. It was quite literally half an inch away from the LED to the left. Was super super hot then once I shut the defective screen off (I could tell by the backlit light or whatever) it wasn't hot anymore after a minute or so.
Is it black/white? 16 or 32? When did you get it?
Sent from my Nexus 5 using Tapatalk
dark_ente said:
Is it black/white? 16 or 32? When did you get it?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
32gb black version. I ordered it immediately when they announced it that day.
mine gets really warm when i'm doing a TWRP backup then it goes into bootloop after and wont cool down. i have to force it to power off from recovery and let it cool, but i've always seen it happen. i wonder if yours was attempting to boot over and over for hours and cooked itself.....? i have a launch day black 32gb too, running Cataclysm with Franco at the moment but it was doing it on rooted stock with stock kernel
I had to send my 19 day old 32Gb Red Nexus 5 in to LG for the same reason. I was using the phone and all of the sudden had vertical lines and the bottom of the screen got burn your fingers hot. Waiting to see what LG does with my phone. The only thin I can figure is the synaptics chip which controls the screen is bad. Its the only thing in that area that could get that hot. I also noticed when I first got my phone the glass in the same area looked like it had a slight wave in it. Didn't think anything of it at the time. I'll let you know how it goes.
Is RMA/replacement applicable for Rooted and unlocked devices?
I don't believe its an issue with developer phones as long as the issue wasn't caused by something you did like brick it by flashing a wrong radio or something like that. It has to be a manufacture defect to get it fixed for free.
Sent from my ME173X using XDA Free mobile app
Bear3825 said:
I don't believe its an issue with developer phones as long as the issue wasn't caused by something you did like brick it by flashing a wrong radio or something like that. It has to be a manufacture defect to get it fixed for free.
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
My device issue is related to power button. there is no software issue.
The power button is rattling since from the purchase of the device.
Hope my device gets repaired.
Like I said. Hardware issues that are production faults should be covered.
Sent from my ME173X using XDA Free mobile app