I dropped my one x and the screen shattered but the phone was still usable, after a few days i noticed out of the blue all the apps would crash giving the error 'Unfortunately, the process (every app i open) has stopped working' so i was unable to open anything, if i restart the phone it will either get stuck in a boot look or will not turn on at all, sometime it turns on if i put the power in. I have factory reset the phone many times and that gives me an hours use with it before it happens again. I have sent the phone away for repair they have managed to fix the screen but still has the same crashing problems and they are struggling to find a fault. It is not routed and running on the latest jelly bean. Please help im going out of my mind, what could be causing this hardware or software???
im not guessing.....hardware and software. probably something broke on the mainboard (memory or such) so the rom cant load stuff from the memory and start crashing. definitly a warranty story here. send it back again. unlocking and trying to fix it here is a no go because you will loose the warranty that you still have now !!!
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.
My HTC One X has been running fine for a few months. A few days back it started telling me a system error report should be sent to HTC everytime I restarted it. Then apps started crashing and even some Sense UI related processes. The phone then started rebooting or turning itself off. I factory reseted it a few times until I understand it would not make any difference since the problem persisted. Then it was harder to even turn it off.
Today I find myself with a phone with an unlocked bootloader (Yeah I am really considering in installing a ROM to check if that fixes the many errors in some way) that does not work. If I manage to turn it on and reach Sense, turns off in a few minutes. Any ideas what could have caused this or how could I fix it? I already contacted HTC and I am still waiting a reply from them. I would really not like to send it to repair since I live in South America and it would require a long process.
Hope someone answers, thanks in advance :good:
It seems like there may be a problem with your ROM (not RAM) which is where system data and the OS is stored. The phone might be encountering a bad sector of memory, hence why you're getting random reboots. If the entire thing was bad, your phone wouldn't boot at all
If you factory reset already, and your problem still persists, it has to be a hardware issue. Unless you're ready to take that up yourself, I'd say it's worth it to send in and get repaired.
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
nexus24 said:
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
Click to expand...
Click to collapse
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
had tisesr
mentisimperium said:
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
Click to expand...
Click to collapse
I've heard of that too, I took apart my s3 and removed the power button as well as blew some compressed air through it. Still didnt work but yes keep me updated!
I ripped my power switch from the motherboard. To turn it on you plug it in and hold home and volume down to go to the odin screen. click volume down to reboot the phone. I am waiting for a new switch to come in the mail which I will attempt to solder onto the board.
Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!
Same situation. This thing is a lemon!
Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk
One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.
My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.
Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.