When I bought Samsung Galaxy Trend Lite in 2014, because I couldn't afford Galaxy Trend Plus.
I had great experience with that phone, until this happened.
Random restarts, shutting down didn't work, hard resets didn't work. Anything.
That random restarts looked like it was being even brighter, and brighter then it showed small landscape bars, then it restarted.
The ROM was official, so I still didn't know what happened.
I even tried to install CWM custom recovery and ROM for the phone via Odin, but with no avail. It still was in the previous state.
Is there any other programs that can help?
Related
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
Hey guys,
I was innocently listening to music at the office when I noticed that I didnt have any reception when I tried to send a text. Reception is pretty spotty in my office so I went outside and still got 0 bars even though my data was working. So I reset my phone and now its stuck on the glowing samsung logo I tried to boot it into recovery mode but it just says "recovery booting" and nothing loads after 10 minutes...
Any ideas what to do? I haven't tried to flash any roms onto it yet cause I'm still at the office but I'm just panicking haha anyone else experience this problem before? My phone has been running completely fine for the past few weeks before this and I havent had a single issue with it...
Thanks!
Update: I got home, flashed a custom recovery onto it and did a factory reset and still it gets stuck on the glowing samsung screen Downloading a ROM now... HALP T_T
Hi guys!
I devoted myself a complete evening into fixing my little brothers GS5. 2 weeks ago he told me he was installing an original Samsung update. However after this update his phone would randomly turn off after a few minutes of being on. So I guessed something was wrong with the software. I flashed a stock rom onto the phone, but now it doesn't even boot. I tried multiple stock versions of Android 4x 5x and 6 for the GS5. None of them made the phone boot. Sometimes it showed the Samsung logo, but most often just black screen. I can't boot into recovery either, the same story. I tried twrp, the lights of the buttons were on, but the screen wouldn't turn on. When the phone normally boots with a black screen I sometimes get notifications though. LED flashes sometimes and there's audio.
Anyone having any thoughts how I can fix this? Help is much appreciated!
I've been having some problems with my Galaxy S5 recently after ~2 years and some change of owning it. I'm stock rooted on the original ANCG KitKat version.
The problem: If I power off my phone, it will cause it to go into a bootloop, not going past the first screen (Samsung Galaxy S5, powered by android). I haven't found a reliable way to fix it from the loop, but I usually just remove the battery, wait, and try again until somehow it just works and boots up. This is extremely problematic because sometimes my battery runs out and after charging I'll have to go through this game of chance again until my phone works.
The next problem also adds to this frustration as well. When I attempt to pick up a call, my phone will sometimes just not work and restart itself. This leads to lots of confusion and I can't call them back for some time because the phone is stuck in a bootloop.
In the few times that I do get my phone to actually boot up, everything works fine except sometimes my Wifi just doesn't work. It gets stuck on "turning on" where the notification drawer quick setting icon is dim green and never gets to the turned on full green state, eventually just turning itself off (no green color).
I haven't done a factory reset or any real troubleshooting yet, as I'm a bit worried I won't even be able to boot up the phone and I don't have the time yet to spend a full day fixing it. Any help would be appreciated, thanks!
The calling problem may be caused by the google dialer app not being set as the the default phone app but as for the other issues i have no idea a factory reset is a good start though
unfortunately I had the same problem but I have marshmallow but the factory reset helped with the not booting up and see a big difference with the battery
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