I have a Motorola Moto E4 XT1768.
Last year I rooted it and installed TWRP. I haven't been able to install OTA updates since.
More recently I replaced the screen with a 3rd party replacement. It seemed to work okay at first, but now there have been unresponsive areas on the screen. However, in TWRP this issue seems to vanish, making me guess it's somehow a software problem. Also of note, I accidentally destroyed the fingerprint reader in the process.
I tried to do a basic factory recovery. It didn't fix the screen problems and it introduced an issue where many apps crash immediately on startup. Clearing data and cache hasn't helped those apps. Last night I used the RSD Lite Mac Linux script to attempt to flash back to unrooted stock. (Supposedly works the same as RSD Lite on Windows). I used flashfile from XT1768_PERRY_RETAIL_7.1.1_NPQS26.69-64-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet. I got a lot of "bad key" errors but it also seemed to take, only now I'm also getting a black screen that says "bad key" at times, and the startup error screen (lettng it sit for a minute takes it into the OS though.) The screen issue and app crash issues are unchanged.
I'm lost on what to do here, and also don't know if the screen issue being tied to the OS even makes any sense. Is getting it back to basic functionality a lost cause? I realize it's a cheap phone but it was fine for my needs and I don't like buying new phones all the time, for both eco/waste and budget reasons.
Related
I've had my 16GB N7 for about a year. After some initial experimentation with ROMs I went back to stock and left it there. The device isn't used too much, generally streaming music and for web browsing.
About a month ago the device began locking up and rebooting maybe once every few days. This seemed to happen most when video was played or music was streamed. I didn't do anything about it, just ignored the trouble and made a mental note that I ought to wipe the device and start fresh.
Then a couple of weeks ago, I picked up the device and it was displaying the "Google" bootloader screen. As I watched, the screen went blank for a moment, then the bootloader screen again. This repeated 5 or 6 times before I force-powered the device off and on. This time it got past the bootloader screen to the Nexus 'X' screen, then to the lock screen, and then froze and rebooted. From that point on, the device would boot to the lockscreen, crash, and reboot - eventually ending up just loading the bootloader over and over, never showing the 'X', just the 'Google' logo.
So I flashed TWRP and did a factory reset, cleared the cache, etc. No difference. Device was completely unusable. Crash on lockscreen.
I wiped all partitions and did a restore from factory images. This bought me a week. Crashes began on day 2, and by day 8 the device was back to looping on the "Google" bootloader screen.
I wondered if maybe there was some problem with Google's factory image (unlikely, but worth a shot. I did a full wipe and installed CM10.1M1. This bought me about a week of use.
As it stands now, the device gets past the bootloader, gets to the CyanogenMod' splash screen, spins for a while, freezes, reboots, repeat.
So, two different ROMs, same random crashes escalating into a completely unusable system within about a week of light use. No abuse, no water damage, no drops, this tablet has been babied.
Questions:
Am I special, or has anyone else seen this behavior?
Is there any way to determine the health of the SSD?
Does anyone have any idea what might be going on here?
What should I do now?
Thanks.
Hey, just to ask you mate.
Does this happen alot in Chrome?
I have an Issue, caused by different things but always the same causes :
Either multiple tabs open
Video playing in full screen
Trying to close a tab with a video/flash in it.
My Tablet FULLY and I mean FULLY Crashes, so I have to hold power to restart.
Then all back to smooth silky nexus.
I hope this isn't a sign that I'm going down the same road you are.
Does this sound a similar issue?!
Definitely can't be the SSD, as there is none. What you mean is the NAND Flash, but without actually seeing it troubleshooting this via a forum isn't especially feasible. Heck, it could very likely be the SoC, but who knows?!
Unless you were handed a pre-release model, your period of ownership is closer to six months than it is a year (the N7 has been on the market for roughly 7 1/2 months). This is good news for you, as it's still covered by warranty. Restore to stock and RMA it.
The symptoms you describe could be caused by any number of root causes.
If you have any time left on the warranty, I would strongly encourage you to return it to pure stock (including stock recovery), relock the bootloader, factory reset... and get the RMA process started.
Those eMMC flash memory chips are supposed to have a wear-leveling controller, but I suppose that doesn't preclude problems from occurring, nor does it guarantee the controller algorithms are implemented in a bug-free fashion. It is sort of impossible to know if the OP's troubles are common or rare; there have been a few similar-sounding reports here, but there are millions of devices in circulation.
The OP's post surely motivates me to have a pure-stock ROM backup waiting in the wings. Any hint of the same kind of trouble on my N7 while the warranty is still good, and it's going back to Asus under RMA.
good luck
you're not alone
This clearly is a common problem as now my tab has started doing the exact same thing 2 years after a motherboard replacement however unfortunately I have bootloader 4.23 and therefore can't flash anything to my device. My question is what exactly causes it?
Hi there, I never thought I would ever need to register onto a forum like this one and have to seek help directly, but it seems I have little other choice.
Anyway, I have a Nexus 7 (2012 model), and it has been working fine and dandy ever since I got it used back in June of this year. Only problems I had up until yesterday were occasional touchscreen jitters and unresponsiveness that I managed to fix with the guidance of a Youtube video. Moving along, I started to have odd problems occur yesterday that seemed to be quite the chain reaction and avalanche of even more problems that are making me awfully suspicious and paranoid.
The device kept on booting off after leaving it for a while. Turning it back on would sometimes result in the screen freezing up, prompting me to go in there and physically disconnect the battery. An antivirus scan showed no bad files of any sort. After some Google searching about the problem, I decided to go into fastboot and wipe cache partition. All seemed to be going fine until it freezes up in the process. Ok, time to forcefully remove the battery again. This time around, right before entering recovery menu, I see something a bit different. The red warning triangle still appears over the little Android mascot, but the words "No command" no longer appear. (I would provide a link, but I have not made enough posts yet.) I tried to wipe cache partition again. No avail. Ok, screw it, let's try formatting. Same result. Booting it up normally had resulted in the dreaded infinite Google logo loop.
That being said, is there any hope of me salvaging this device? I can still go into fastboot if that's any indication of hope!
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.
I bought a droid turbo 2 about a year ago, and after a few months of use it was dropped into a sink causing minor water damage. Other than minor screen bleed everything seemed to have been in working order after a few days of drying.
About a week and a half after it finished drying and was in use, the phone shut down and went into a boot loop. It will boot to the motorola M but after 30 seconds it shuts down and restarts.
I have tried doing a verizon update from my computer but after the program says "updated" my phone is unable to restart dissallowing the update. I do have the ability to boot the phone in "fast boot" or "recovery mode", But if i go into recovery mode and do a factory reset the problem persists through it.
I figured the best way to try and fix my phone would be to flash a factory android version onto the phone, but that is where i am running into issues. Maybe it is my lack of understanding of ADB and flashing, but i dont understand how i am supposed to allow debugging on my phone if it is already stuck in a boot loop? I also am running into the issue of my phone not being recognized by the ADB daemon. even though the verizon updater recognizes it and allows for an update. Please any help from somebody with experience with these sorts of things would be extremely appreciated.
Bootloop after disconnecting charger, tried everything
I am having same problem after disconnecting charger from phone, went into bootloop. Did you ever fix yours?
Same problem, different reason.
Goes to Motorola logo and restarts until battery dead. I have flashed up-to-date stock ROM both with "Verizon Software upgrade" program with windows 10(once) and 7(several times), and have flashed with old "RSD lite" in win 7. Both flashing methods worked flawlessly and says "successful". but still looping. Have tried draining battery to totally dead and full recharge, no joy. Can boot into recovery fine. Did full factory resets, etc. Thought battery may be problem, but battery lasted full day or more before needing recharge before problem, and drains normally now with constant restarts, but gets hot. (plugging in to check % charge after restarts says still in 90+% range after many restarts).
I know this is an old thread, but any suggestions are appreciated. Cant understand if flashes good, why cant restart.
Old thread, old problem -- my problem, as well. (In my case it's a hand-me-down phone for experimentation; all my own androids are rooted starting with my first.)
This 'Droid Turb'o 2' worked fine until left alone a while, after which time its battery then seemed to lose its "elasticity" as it were, resulting in poor charging/capacity characteristics, and then shortly thereafter, this annoying and horrid bootloop. (It's also a Verizon phone, they like to "tighten-up" the phones they sell to one, or so I have read.)
All I have to offer really, are my observations, and possibly some insight. My suspicions of something to do with the current flow/battery-drain are also pure conjecture, and perhaps an educated guess at best. I, too, continue to solve this mystery because it's somewhat atypical of my own android experiences, and this is the sort of knowledge that broadens the spectra of engineering as a whole (and the suspense sometimes can give one a hell of a headache).
For now, my conclusion is that this appears to be a problem specific to a particular model that is no longer made, and perhaps for good reason. I still hope to find this mystery solved some day.
73 DE N6BHU
Hi, I have owned a One Plus 6T for a few years now, didn't have many issues, until the last few months. I used to be on Android 10. (something) can't remember and the issues I'm about to describe happened on that version too. I have recently updated to Android 11.1.1.1 and the problems still persisted. And I've run a factory reset a few days ago and that still hasn't solved the issues. My bootloader is unlocked and I am not rooted.
Issues:
1. Phone randomly rebooting (almost like there isn't any RAM but there's over a gig spare) eg Ill be listening to spotify and suddenly phone reboots
2. Extreme System UI delay/lag and screen lag. This is the weird one. Happens at completely random times. Phone will slow down extremely to the point where nothing will be responding. For example if I click the power button to look at the lock screen the screen will just stay black for ages. Apps will not open etc. Can barely even swipe or do anything, it happens multiple times a day too.
I was wondering if anybody knew why this might be occurring, considering I am running a fresh install, unless it comes down to just bad software.