Hello,
My RAZRi turns on, but is unable to access the phone. I have been researching this problem and there doesn't seem to be any solutions, this problem seems very weird.
So recently my phone has just been restarting itself, absolutely no idea why but it only happened rarely (probably should have done something immediately when this started to occur, -sigh-). The issue begun to grow more severe, as the RAZRi was restarting itself more frequently and was becoming a nuisance as I may have been doing something at the time.
I had a theory that the problem may have been something to do with the battery. There was a couple of occasions where I would be charging my phone and I would remove the connector to then notice that the phone resets a couple of seconds later. The problem was getting more serious.
The phone has now entered a stage where I can't even access the phone. By which I mean it keeps resetting itself on the boot-up process, in fact this is happening as I speak. I have been unable to access my phone for the last 2 days and this is really strange. I tried booting in to safe mode to perform a hard reset but I literally can't do that as the phone just keeps resetting itself.
What the hell should I do!?
Thanks,
James.
JamesBarrett said:
Hello,
My RAZRi turns on, but is unable to access the phone. I have been researching this problem and there doesn't seem to be any solutions, this problem seems very weird.
So recently my phone has just been restarting itself, absolutely no idea why but it only happened rarely (probably should have done something immediately when this started to occur, -sigh-). The issue begun to grow more severe, as the RAZRi was restarting itself more frequently and was becoming a nuisance as I may have been doing something at the time.
I had a theory that the problem may have been something to do with the battery. There was a couple of occasions where I would be charging my phone and I would remove the connector to then notice that the phone resets a couple of seconds later. The problem was getting more serious.
The phone has now entered a stage where I can't even access the phone. By which I mean it keeps resetting itself on the boot-up process, in fact this is happening as I speak. I have been unable to access my phone for the last 2 days and this is really strange. I tried booting in to safe mode to perform a hard reset but I literally can't do that as the phone just keeps resetting itself.
What the hell should I do!?
Thanks,
James.
Click to expand...
Click to collapse
That's certainly not good. :/ Is it able to stay on at all, like if you boot into recovery? If it won't stay on in any mode (fastboot/recovery/OS) then without trying a new battery first, there won't be much else to try. If it's rebooting itself that quickly, in any bootable mode, then there won't be much else to do because if you try to SBF the original software back and the phone reboots in the middle of flashing, that could be a surefire recipe for an unrecoverable brick. I haven't worked on an i before, but for most Razrs the batteries aren't THAT hard to access. Generally it involves a couple of Torx screwdrivers, removing the 2 bottom screws, sliding off the back, and undoing some of the screws around the outer shell to give access to the battery terminal. I'm sure there are a few guides lying around either here, droidforums, or just YouTube.
Related
Ive been lurking around this site since the shadow was the new thing on the block, and ive never had a problem i couldnt figure out by just searching the forums... well, now i do...lol
I have a 17 day old g2, completely undamaged, unscratched. for some reason, intermittently, and with no apparent cause, it will shut off completely. it does not go through the shut down process, give any warning, or restart on its own, it just turns off like you pulled the battery out. (ive checked batt. voltage and amperage with a multimeter and ensured that the battery isnt loose in any way. also, it will shut off exactly the same way while charging which leads me to believe that it cant be a power problem.)
Also, though im not sure its related, sometimes the touch sensitivity in the screen will shut off (not the screen itself, still displays beautifully). Only way to restore touch functionality is to restart device manually.
Ive tried a master reset, and called T-Mobile tech support (which was useless).
Hopefully someone will have some idea whats going on here because i sure dont
Where did you get the device from, T-Mobile?
Have you flashed a new Recovery to the phone or hacked it in any other way?
G2 Randomly shuts down
I've only had mine for a week and its doing the same thing...no hacks, tampering etc.
Have you got the OTA update ? If not then you should find it online and update your phone. HTC has fixed the issue of random reboots for the phone
So, my Atrix is doing something quite strange, and possibly unique.
Just about every 5 to 10 minutes, my phone will randomly reboot. This seems like something a forum search would fix. But it gets significantly more... weird...
More than half the time, it will come up to the Motorola logo, and just sit there... doing nothing. No errors, no messages, no nothing. Just logo. Pull battery, repeat. Sometimes it boots, mostly, it just does it again. Motorola logo. Big. Red. Cylon-like.
However, sometimes it seems that if I give the body of the phone a bit of a twist, flex it a little bit, SOMETIMES, this will prompt it to boot. I tried the because I have had to do this twist and flex trick to get the USB port to connect and charge for some weeks now.
If I can get it to boot, it will sometimes boot normally. Run for a while. And then I lock the screen. Sometimes, the lock button will wake it up like normal. More often though, it shows no response. I attempted to press the button while doing the same twist and flex trick, and this occasionally works. It will unlock the screen, and I can keep going. But usually, it just decided to reboot, and back to that darn Motorola logo.
I thought maybe because I was running JokerSax CM9 beta, it was a rom issue. So back to CM7 I went. No dice. Same thing. I kept a Nandroid backup of the stock ROM even, so I rolled back to that. Again, no change. Same results.
Some inconsistent symptoms are that sometimes when it boots up, the wifi will not come on. Other times it dose fine.
And one time, just one single time, it gave me a "Could not connect to modem" error on that red Motorola logo screen. I haven't gotten it to do that again.
So, is this a Radio issue? A ROM issue? Or has my logic board gone kaput? I am at a loss. I ordered a shattered Atrix from ebay for a logic board swap in case that would fix it, but it won't be here for another week. If anyone has some alternate ideas, I am open to suggestions!
does your wifi work properly when the phone is functioning?
How warm does the phone feel? Almost sounds like an overheating issue.
dLo GSR said:
does your wifi work properly when the phone is functioning?
Click to expand...
Click to collapse
Sometimes it works, sometimes not. Its really pretty random.
xcguy said:
How warm does the phone feel? Almost sounds like an overheating issue.
Click to expand...
Click to collapse
The phone gets quite warm once it starts having its fits. I usually pull the battery to let it cool down before trying again. I was running an overclocked kernel, but have since flashed back to a normal 1ghz kernel. It seems to get hot only when it is trying to boot. It only started doing this recently though. I never had an overheating problem before.
Reboot into recover and flush both cache and dalvik-cache.
Still sounds like an overheating issue...
xcguy said:
Reboot into recover and flush both cache and dalvik-cache.
Still sounds like an overheating issue...
Click to expand...
Click to collapse
Tried that already...
Hello,
I have an international unlocked Samsung Galaxy S III (GT-I9300) that is no longer in warranty and that started behaving strangely (unresponsive) a couple of weeks ago on Android 4.1.2 (official ROM, rooted with CF-AutoRoot).
After reading several threads here on XDA I believed it was subject of Sudden Death. So I started with a factory reset and rooted the phone again with CF-AutoRoot but after that I still experienced the same freezes and started my mission to try and resolve this using whatever method was required.
I starting with trying the DFG app but to no avail. The freezing was provoked but did not go away after many days of iterations and freezes (it always recovered out of a freeze).
Next I tried the eMMC check app to verify on what version I was so that I could help my in further pinpointing the problem. It said I was safe, but while running that app the phone freezed again but this time the screen turned purple/pink and it did not recover from the freeze after several hours until I finally removed the battery. The purple/pink turned into purple/pink with black lines and after removing the battery I could not power on the phone.
In all desperation I started trying out different "SDS-safe" custom kernels, ROMs and bootloaders (all flashed using Odin on my laptop) but the problem did not go away. In fact, I discovered a very strange correlation between the time that I leave the battery out the phone and the time it takes before the purple/pink freeze occurs again.
If I wait half an hour, put the battery back in the phone and boot it (in whichever mode) it would freeze/flicker/die after about 20 seconds. If I would wait several hours, put the battery back in the phone and boot it it would freeze/flicker/die after a solid 1 or 2 minutes.
Whether the phone is connected to the laptop or not makes no difference. I also tried with a different battery but the same behavior occurs.
After waiting a solid day, in still in act of desperation, I decided to flash the leaked 4.2.2 (I9300XXUFME7) official ROM. But even after a factory reset and wiping of cache I found that the problem still remained.
Now I believe I've tried almost everything I've found on these forums I'm not sure what I can still do. It seems it's not battery, ROM, kernel or bootloader related and it also does not seem a case of Sudden Death (I never heard mention of the purple/pink flickering, and it also never snaps out of the freeze; also the strange correlation between battery out of the phone and time before it freezes is something I haven't read about).
From all the research I've done I've not encountered anyone with the same symptoms (does not wake out of freeze, purple/pink lines appear on screen when freeze starts and keep flickering for hours, there seems to be a correlation between the time the battery is out of the phone and how long I have before it freezes again when I turn it on) and I'm running out of ideas.
I believe it is hardware related (but not a screen issue) rather than software related because the USB connection with the laptop disconnects when it freezes, purple/pink flickering and no recovery; but I have no idea what options I still have.
Before I give up on the phone does anyone have any recommendations of what I can try before sending it to a Samsung repair center?
Attached are 4 pictures to show the typical process after waiting ~4 hours and powering on the phone:
Phone boots OK
The phone freezes and a purple/pink overlay appears
More and more flickering making the screen turn more and more purple/pink
The screen seems to be divided in 4-5 parts
Everything is pink and black lines start to appear
Thank you for your time.
I'd say you need a new motherboard or screen, possibly both - you've ruled out any software causes.
just had this issue
Did you find a solution, given the fact that this happened a long time ago?
I was watching a video and my screen turned pink like the 4th photo you posted.
Now it wont work, get the pink screen everytime is turned on.
dendera said:
Hello,
I have an international unlocked Samsung Galaxy S III (GT-I9300) that is no longer in warranty and that started behaving strangely (unresponsive) a couple of weeks ago on Android 4.1.2 (official ROM, rooted with CF-AutoRoot).
After reading several threads here on XDA I believed it was subject of Sudden Death. So I started with a factory reset and rooted the phone again with CF-AutoRoot but after that I still experienced the same freezes and started my mission to try and resolve this using whatever method was required.
I starting with trying the DFG app but to no avail. The freezing was provoked but did not go away after many days of iterations and freezes (it always recovered out of a freeze).
Next I tried the eMMC check app to verify on what version I was so that I could help my in further pinpointing the problem. It said I was safe, but while running that app the phone freezed again but this time the screen turned purple/pink and it did not recover from the freeze after several hours until I finally removed the battery. The purple/pink turned into purple/pink with black lines and after removing the battery I could not power on the phone.
In all desperation I started trying out different "SDS-safe" custom kernels, ROMs and bootloaders (all flashed using Odin on my laptop) but the problem did not go away. In fact, I discovered a very strange correlation between the time that I leave the battery out the phone and the time it takes before the purple/pink freeze occurs again.
If I wait half an hour, put the battery back in the phone and boot it (in whichever mode) it would freeze/flicker/die after about 20 seconds. If I would wait several hours, put the battery back in the phone and boot it it would freeze/flicker/die after a solid 1 or 2 minutes.
Whether the phone is connected to the laptop or not makes no difference. I also tried with a different battery but the same behavior occurs.
After waiting a solid day, in still in act of desperation, I decided to flash the leaked 4.2.2 (I9300XXUFME7) official ROM. But even after a factory reset and wiping of cache I found that the problem still remained.
Now I believe I've tried almost everything I've found on these forums I'm not sure what I can still do. It seems it's not battery, ROM, kernel or bootloader related and it also does not seem a case of Sudden Death (I never heard mention of the purple/pink flickering, and it also never snaps out of the freeze; also the strange correlation between battery out of the phone and time before it freezes is something I haven't read about).
From all the research I've done I've not encountered anyone with the same symptoms (does not wake out of freeze, purple/pink lines appear on screen when freeze starts and keep flickering for hours, there seems to be a correlation between the time the battery is out of the phone and how long I have before it freezes again when I turn it on) and I'm running out of ideas.
I believe it is hardware related (but not a screen issue) rather than software related because the USB connection with the laptop disconnects when it freezes, purple/pink flickering and no recovery; but I have no idea what options I still have.
Before I give up on the phone does anyone have any recommendations of what I can try before sending it to a Samsung repair center?
Attached are 4 pictures to show the typical process after waiting ~4 hours and powering on the phone:
Phone boots OK
The phone freezes and a purple/pink overlay appears
More and more flickering making the screen turn more and more purple/pink
The screen seems to be divided in 4-5 parts
Everything is pink and black lines start to appear
Thank you for your time.
Click to expand...
Click to collapse
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
In Need of Dire Help! Galaxy S Relay 4G(SGH-T699) Completely Bricked?
XmashMAN said:
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
Click to expand...
Click to collapse
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
XmashMAN said:
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
Click to expand...
Click to collapse
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
es0tericcha0s said:
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
Click to expand...
Click to collapse
I'm not sure what I did, but I'm able to stay into ODIN mode for as long as I want. I'm still unable to boot into recovery. Is it possible to restore my phone through ODIN?
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
es0tericcha0s said:
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
Click to expand...
Click to collapse
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device. But I put my default battery in, but it didn't change anything in regard to the movinand error.
The Galaxy S Relay 4G can be a very odd challenge.
XmashMAN said:
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device.
Click to expand...
Click to collapse
Wow! I'm just making a note here as a marker I can return to and follow up on. This seems almost the worst that anyone can deal with. If the person that made this post just so happens to still be around, or for anyone who may be unfortunately dealing with such an issue, I have an either or "possible" fix, yet haven't been in this particular situation. There are repair files for this device I would assume could be used for this. I'm dropping them, and the last official Samsung software issued for the SGH T699. If I so much as even get a hint my device is going in this direction, I usually flash in the original firmware if and when I can. Back it up and flash it again just to make sure I have a clean build. I can work with stock. It's hard to work with a brick. This device can be very strange so far with any results I'm getting. Which is odd to me on one level because I've haven't had as much difficulty with any of my other devices such as I'm having with this one. I always try to be prepared for any eventuality before I start working on "any" device. I'd call it a very important suggestion, especially for this Galaxy S Relay 4G, to prepare yourself, it's going to be a fun ride!