I'm having this problem from stock ROM (unrooted) to latest rooted ROMs (Virtuous Sense, InsertCoin...). I've already have it's firmware reinstalled by HTC first and then board replacement the second time I have the problem.
The phone just shutdowns itself and I cannot turn it on again unless I pull out/in the battery or plug in the charger. There is one time that I can't even turn it on by doing anything but after numerous battery pulls I can boot into Recovery and restart in there.
Is this a hardware faulty? If so the do I have to revert it back to unrooted in order to have it repaired by HTC?
I'm living in Vietnam and there are authorized HTC support center here but I don't know whether the policy to deal with rooted phone is different? And also will I have a new replacement because it has been repaired many times
I have a similar problem with my g2. No matter what rom I flash the phone just randomly shuts down and wont start unless I pull the battery. Sometimes it take a day or 2 for it to happen, sometimes it happens with couple of hours it seems. Any thoughts?
deleted post
rage2wrath said:
I have a similar problem with my g2. No matter what rom I flash the phone just randomly shuts down and wont start unless I pull the battery. Sometimes it take a day or 2 for it to happen, sometimes it happens with couple of hours it seems. Any thoughts?
Click to expand...
Click to collapse
Exactly the issue I'm having... this is a known common problem with Desire Z / G2, isn't it?
Anyone with the experiences dealing with HTC support can help me and others having this same issue?
I'm still looking for some experienced insights about this matter...
Any other have had this issue and did you return your phone to HTC for repairing and how is the result?
I am also having a similar problem, sometimes my phone just powers off. There is no warning or shutdown animation just one second its working fine next its a black screen and I have to press the power button to boot the phone back up. Now I don't have to pull my battery like the rest of you so it may be a different issue. It happens on multiple roms.
Related
My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
It may be hardware related but it could also be an app that you are installing on each rom. Try a new rom and don't install anything for a few hours and see if it still happens.
Sent from my SGH-T989 using xda premium
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
SOD? whats that?
sleep of death
i think its related to the wi-fi being on while charging , just fully charged it and left the phone on the cord for an hour after charging and it never went off. ran it down to 90% and turned wi-fi back on and hooked it up to see if it does it again
that has happened to me with other phones, like Nexus S, I9000, Moto XT720
so it's definitely not hardware related AFAIK
the way i narrowed it down to has always been a ROM problem
after I flash clean up, or load a more stable ROM the Sleep Of Death goes away.
i had a lot of that with the recent "stable" CM 7.1 for Nexus S
flashed to a newer nightly unstable and it fixed the "stable" problem LOL
well i just got my new phone in yesterday and so far no random reboots or SOD's ,phone seems a little faster than my previous got 3700 quads stock unrooted and over 15megs download and almost 3 upload , i think i got a better device this time and im pretty sure it was a new one and not refurbished, im gonna run it stock for a couple days just to see if any problems re-occur, i was having them on my first phone before i rooted ,thats why i decided to root and install custom roms
Hello everyone! I own a Galaxy Nexus that's running one of the Cyanogenmod 4.4 snapshots. While watching a youtube video my phone froze up and shut itself off. I rebooted and after a few moments the same thing happened. When I power up my phone one of two things happen. It either reboots while booting and automatically attempts to boot again or it manages to turn on for a short while and then turns itself off.
I believed the issue was a battery or hardware one at first but after leaving my phone booted in recovery for half an hour with no ill effects I think something else might be up. What do you guys think is the best course of action? The only thing I've done is a factory reset that has done nothing.
Anyone?
Stryking said:
Anyone?
Click to expand...
Click to collapse
Factory Reset and reflash the rom. If that doesn't work try flashing another rom like Vanir. If your phone still shuts off...well unfortunately this may be a hardware related issue, nothing you can do if that's the case. Unless it's your battery which I highly doubt.
I think it's the same thing that happened to me a year ago, check this out:
http://forum.xda-developers.com/galaxy-nexus/help/bricked-phone-t2306672
for me it was a hw related problem, i had to send the phone back to assistance and have it repaired (it was still under warranty).
Good luck :good:
Thank you all for your ideas. I'll report back my findings later today.
Same problem over here. Tried a lot of roms (custom and stock from Google page), took it to assistance (no warranty though) was told is a hardware issue. Since replacing the mainboard its the same price as a new phone... well you know.
But a curios thing happened: tried to flash the Ubuntu Touch rom, same problem (reboots at Ubuntu start screen) and the Firefox-OS, that one worked (considering it's limitations obviously)!
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
jb1207 said:
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
Click to expand...
Click to collapse
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
marshallartsoz said:
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
Click to expand...
Click to collapse
Hello and thanks for you answer,
Just to precise i never faced this issue while flashing an official or custom ROM, dont know if it is just luck or it can help in anything
Anyway ill try to check it the power button just in case
It's weird I just started having this exact problem myself. One morning I unplugged it and it had shut itself down overnight. Since then it randomly reboots. Sometimes I can get 20/30 minutes out of it, but once it starts, it can get into multiple reboots with the only way to stop it is to plug in the charger. I tried wiping cashe/dalvic (no help). Nothing was recently changed (including apps). Tried resoldering battery connector (battery was replaced a year or so ago with OEM Sammy). The P600 is rooted with TWRP installed, but no custom ROM. Usually the reboots start while I'm doing something (surfing, email, etc.), but I don't think it will do it while sleeping. I'm considering the power button, but I don't see this exact problem anywhere else, but this post. Any ideas?
OK. My tablet has taken a turn for the worse. Now it is stuck in a continuous boot loop. I tried the power switch, no help. I tried booting into TWRP, and it went back into rebooting before I could do anything. Strange thing is I can put it into download mode indefinitely without it rebooting. Should I ODIN back to stock? I tried the resoldering of the battery connection earlier. Any other ideas?