My moto defy+ goes bonkers on me sometimes. It remains unresponsive to touches & needs to be locked & unlocked again. Is this a common problem on this phone? and also on some instances starts typing on its own and needs to be locked and unlocked again. Should i update the software again?
samueljohanson said:
My moto defy+ goes bonkers on me sometimes. It remains unresponsive to touches & needs to be locked & unlocked again. Is this a common problem on this phone? and also on some instances starts typing on its own and needs to be locked and unlocked again. Should i update the software again?
Click to expand...
Click to collapse
I have seen such behavior while my defy is getting charged. otherwise it's fine. Which ROM do you have? Maybe you can try doing a factory reset, but DO backup your apps, contacts, messages etc before that and restore back once you're done. Also deleting the cache may help.
Yes, i would also do a factory reset, or may flash the same ROM new
Alritey. Gonna try a factory reset.
I have this problem when connected to charger or when screen is damp if it's just those tines don't worry about it
CM9 ICS Defy MB525
Related
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.
Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
clay0001 said:
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
Click to expand...
Click to collapse
I don't think anything can be done except going to the service center.
clay0001 said:
HI have search many post but feel like I am going round in circles.
I am just trying to get back to stock Froyo which the phone came with, it was bought new and unlocked from Ebay (e buyer I think).
Problem started when I noticed the phone kept freezing, pull batt, reboot, would freeze again within a few mins, guessed it must be a app playing up after an update or something.
So done a stock recovery but then it started with boot loops etc so tried wiping before and after, phone started but it would not start up wifi, done recovery again, got wifi working but then it would not open any browser. so after read lots of how to's I decided to use rsd lite and use 3.4.2 117 003 which was english retail but on loading i get checksum errors after group 33-34 and it fails.
I now only get the boot loader screen 9.10, code corrupt, batt ok, ok to program, how ever I try taking battery out putting back holding different buttons always this screen.
has this problem been solved? seen similar in other post but nothing saying it is solved
I just want back to stock and usable
Thanks in advance
Clayton
Click to expand...
Click to collapse
Try dfp231 sbf. If still stuck then there is a hardware fault
Sent from my MB526 using Tapatalk 2
mb525
It has been a couple of weeks, I tried the file but it would still keep starting in BL9.10 have turned it on today to try again and it started….at press sitting there charging, connects to internet over wifi, frightened to turn off to out in sim and sd card in case it does not start again….
Will up date.
from the settings it is working on
firmware 2.2.2
kernel 2.6.32.9.ga28fcc4
bp flex usajrdnemarab1b8rtgb03a.or
built jorem_u3_3.4.2_177-3
only problem noticed is google maps force closing
thekguy said:
Try dfp231 sbf. If still stuck then there is a hardware fault
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
mb525
clay0001 said:
It has been a couple of weeks, I tried the file but it would still keep starting in BL9.10 have turned it on today to try again and it started….at press sitting there charging, connects to internet over wifi, frightened to turn off to out in sim and sd card in case it does not start again….
Will up date.
from the settings it is working on
firmware 2.2.2
kernel 2.6.32.9.ga28fcc4
bp flex usajrdnemarab1b8rtgb03a.or
built jorem_u3_3.4.2_177-3
only problem noticed is google maps force closing
Click to expand...
Click to collapse
It restarted, but did not save any blur or wifi settings, all set up again but now it force closes browser although it does connect and download gmail…phone works, sms works,
few more google processes force closing starting to worry
update
clay0001 said:
It restarted, but did not save any blur or wifi settings, all set up again but now it force closes browser although it does connect and download gmail…phone works, sms works,
few more google processes force closing starting to worry
Click to expand...
Click to collapse
still no browser, (application browser process com android.browser has stopped, please try again)
read about try to clear data by going into manage applications, I open the manage browser and it shows NO data for the app, does that mean it has not loaded correctly?
data does flow as I get gmail on both wifi and 3g
Force close after flashing only sbf? Try a system wipe, and ensure that your system partition has some free space
This looks like a eMMC problem, so if wiping doesn't work then it may not be fixable by software means
Sent from my MB526 using Tapatalk 2
I just got this phone on Swappa, I've been having a series of issues with it.
At first my home button stopped working. I tried booting in safe mode, it still wouldn't work. So I did a factory reset, but then my apps were crashing constantly.
Now... My wifi isn't working. Any advice? Has anyone had this happen before?
Magnik said:
I just got this phone on Swappa, I've been having a series of issues with it.
At first my home button stopped working. I tried booting in safe mode, it still wouldn't work. So I did a factory reset, but then my apps were crashing constantly.
Now... My wifi isn't working. Any advice? Has anyone had this happen before?
Click to expand...
Click to collapse
You need to post more information. Moto X Style or Pure? Which Android version? Which ROM are you running? Is the bootloader unlocked? Rooted? My initial thought is that the phone is rooted - in which case you don't want to factory reset from within Settings. You can check this from the bootloader (volume down+power). And if you look under Settings > About Phone, you should see details regarding Android version, ROM build, etc.
If the phone is unlocked, I would restore stock firmware and start from scratch. Here's the thread with firmware for the Pure Edition (XT1575). One note, before you do anything, remove any type of security you're using (e.g., pin, password, etc.). This will keep you from getting locked out of the device through Google's Device Protection.
Yeah you should flash stock images and start clean.
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
Hey guys, so i have s7 edge for 1 year, but since a couple days ago, the device keep reboot/freeze after i install app/update an app, i thought it was bcs of my sd card so i remove it, but the problem still persist, i already tried revert back to stock rom with odin but still no effect, any idea guys? Any help will be appreciated, thank you
Bumpppp
Please guys, its getting worst
Have you booted to safe mode and stayed for a few hours just to see if it was behaving differently.
Try to do a factory reset and restore your phones to its original settings!
Factory reset steps:Mod Edit
Go to Menu -> System Settings -> Privacy (or User and Back Up) -> Factory Data Reset
All data and apps added by you in the interim will be deleted. It is recommended to make a backup (if you can do that in the present state) or to save all data you want to keep.
sanctitude888 said:
Have you booted to safe mode and stayed for a few hours just to see if it was behaving differently.
Click to expand...
Click to collapse
Ok will try
RossTeagan said:
Try to do a factory reset and restore your phones to its original settings!
Factory reset stepsMod Edit
Go to Menu -> System Settings -> Privacy (or User and Back Up) -> Factory Data Reset
All data and apps added by you in the interim will be deleted. It is recommended to make a backup (if you can do that in the present state) or to save all data you want to keep.
Click to expand...
Click to collapse
The current state of my phone is now on stock rom no root, and the problem still persist, yes i already tried factory reset but no help
Then is hardware failure.
Nothing you can do but going to Sam's service
aditia581999 said:
Ok will try
The current state of my phone is now on stock rom no root, and the problem still persist, yes i already tried factory reset but no help
Click to expand...
Click to collapse
Hi! I'm dealing with a friend's no-warranty S7 Edge with a similar problem: the S7E would reboot and gets into bootloop until I go to SafeMode and let it cool down (I mean the phone heats up a lot before it reboots). I'm think about rooting and limiting frequency cores to avoid overheating. Did you try this? Any kernel manager app could do this. I have a Nexus 5X, and they suffer from a similiar overheating problem. Good luck!
CLPose said:
Hi! I'm dealing with a friend's no-warranty S7 Edge with a similar problem: the S7E would reboot and gets into bootloop until I go to SafeMode and let it cool down (I mean the phone heats up a lot before it reboots). I'm think about rooting and limiting frequency cores to avoid overheating. Did you try this? Any kernel manager app could do this. I have a Nexus 5X, and they suffer from a similiar overheating problem. Good luck!
Click to expand...
Click to collapse
The thing is when the first time this happens, its when i use a custom kernel with undervolt + limiting freq, and goes on bootloop. So i revert back to fully stock rom, so yeah your mileage may vary.
Latest fw is causing overheating, bootloops, fast battery drain, stuck black screen with pulsing blue notification lights and buttons unresponsive. Just Google it.
Is there anyway to downgrade stock rom without tripping know.
tandeh said:
Latest fw is causing overheating, bootloops, fast battery drain, stuck black screen with pulsing blue notification lights and buttons unresponsive. Just Google it.
Is there anyway to downgrade stock rom without tripping know.
Click to expand...
Click to collapse
Hi! Could you please specify which update causes these issues? We may not be in the same build . Thanks!
It was released in November the latest one in UK Vodafone, version:
NRD90M. G935FXXU1DQJ3