I've been using Cyanogenmod 12.1 Nightlies for a bit over a month, only problem I've had so far is that it would randomly turn off (which I noticed other users have been experiencing). 2 or 3 days after the Snapchat update, I go to use the app, but it turned my phone off. I thought "Okay, this has happened before" so I try getting on Snapchat again. Same thing happens. So I just decide not to use Snapchat. Yesterday morning, my phone just shut off from a calculator app and I had around 73% battery, so I try turning it back on but it won't boot past the second Cyanogenmod logo. The only way to get it to boot is to plug it into my computer and use it, as it turns off as soon as I unplug it and gets me stuck in a bootloop. I backed everything up because I noticed this is a major issue right now, and my phone may be bricked. Now, there's a 1/5 chance that it will boot all the way to my homescreen while plugged in, but using any camera app kills it. It will boot into recovery and download mode. What do I do?
Edit: Forgot to mention I was using a Samsung Galaxy S III d2att
Just tried factory resetting/wiping cache/wiping dalvik cache. Still not going past cyanogenmod logo. Still unsure as to what the problem is. Desperately need help. Thanks.
improblem said:
Just tried factory resetting/wiping cache/wiping dalvik cache. Still not going past cyanogenmod logo. Still unsure as to what the problem is. Desperately need help. Thanks.
Click to expand...
Click to collapse
Hi,
Try posting your question here;
http://forum.xda-developers.com/galaxy-s3-att/help
The experts there may be able to help.
Good luck!
Related
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
InfuseIssues said:
Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
Click to expand...
Click to collapse
I'm sorry if your not able to save all your contacts but the only way to stop your phone from flashing samsung over and over again is to use odin. Or the case could be is that your power button is either stuck or messed up.
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
corrosivefrost said:
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
Click to expand...
Click to collapse
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
buhohitr said:
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
Click to expand...
Click to collapse
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
corrosivefrost said:
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
Click to expand...
Click to collapse
I know for a fact that there has been issues with the flashing of 4.4 and encryption. The best bet is to turn encryption on then off again. Now you said you never encrypted it but the Turn it on then off again approch might work here. I also know for a while TWRP had issues flashing 4.4 so it might be worth it to run CWM.
Hello community, I am new here so I don' t know where to put this.
Well I need some help, I am having problems with my old tab, A Samsung Galaxy Tab 2 10.1 GT-P5113, Flashed with custom ROM CM 10.1.3 for GT-P5110
Worked fine for a year and a Half, the issue that I am having now is that, it constantly restarts, after entering to the OS I can tweak change etc, but after a few secs it just turns of and reboots the system.
The other problem that I am having is that I tried everything that I could think of. I deleted some apps, which came back after the reboot. I booted to safemode, and deleted the last apps that I installed, still came back after the crash reboot.
I went to recovery mode (CWM) and did a Factory reset, delete cache and delete Dalvik Cache. Nothing when reboot everything was like last time.
wen't to and tried to reflash CM 10.1.3 (stable) following every procedure and nothing everything was back.
Last thing I tried is ODIN with stock ROM (which is hard to find for this tab.) but get write error after going to half. I am downloading a second stock ROM (android 4.1.1) to see how it goes.
Hope to find help here, I would be greatly thankful.
EDIT: Flashed now with the new stock ROM, ODIN says success, everything seems fine, but again I got received by the same splash and the same logon screen, and still crashes and reboots...
I really need the help
Isifth said:
Hello community, I am new here so I don' t know where to put this.
Well I need some help, I am having problems with my old tab, A Samsung Galaxy Tab 2 10.1 GT-P5113, Flashed with custom ROM CM 10.1.3 for GT-P5110
Worked fine for a year and a Half, the issue that I am having now is that, it constantly restarts, after entering to the OS I can tweak change etc, but after a few secs it just turns of and reboots the system.
The other problem that I am having is that I tried everything that I could think of. I deleted some apps, which came back after the reboot. I booted to safemode, and deleted the last apps that I installed, still came back after the crash reboot.
I went to recovery mode (CWM) and did a Factory reset, delete cache and delete Dalvik Cache. Nothing when reboot everything was like last time.
wen't to and tried to reflash CM 10.1.3 (stable) following every procedure and nothing everything was back.
Last thing I tried is ODIN with stock ROM (which is hard to find for this tab.) but get write error after going to half. I am downloading a second stock ROM (android 4.1.1) to see how it goes.
Hope to find help here, I would be greatly thankful.
EDIT: Flashed now with the new stock ROM, ODIN says success, everything seems fine, but again I got received by the same splash and the same logon screen, and still crashes and reboots...
Click to expand...
Click to collapse
It keeps with the boot loop.
Hi, thank you for using XDA Assist. After you flash with Odin go into the stock recovery and do a factory reset. If that doesn't work it may be that you're device is just getting old and giving up the ghost. There's a whole forum for your device which may also help. See this,http://forum.xda-developers.com/galaxy-tab-2
Oh, that would be bad news :/
Do you think it could be that I deleted CWM rommanager app, and then accidentally deleted the .recovery, that put me into this situation?
Isifth said:
Oh, that would be bad news :/
Do you think it could be that I deleted CWM rommanager app, and then accidentally deleted the .recovery, that put me into this situation?
Click to expand...
Click to collapse
After you flash with Odin, boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
After you flash with Odin, boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It didn't work. I noticed that after the transferring of odin it doesn't go to the installation procedure. It just skips that and goes to the logscreen with how everything I had.
Now I went to safe mode, and deleted all apps that I could from play store. when I came back after a restart, everything was there, back. :/
Please ask any further questions you have on the q&a forum in your drives forum, the link I gave you. They are the experts on your device
Thread closed.
I installed Lineage on my Moto G7 Power a few days ago, and after rebooting it yesterday, it's stuck in bootloop (the Lineage starting animation is displaying), i have left it for 4 hours with nothing changing. can reboot it by holding the power button and I am able to get into recovery. USB debugging still works aswell.
I installed the newest nightly Lineage build for ocean (19.1), along with MindTheGapps and TWRP.
This has happened again, 2 days ago. I tried dirty flashing the same lineage version and nothing happened. I ended up completely restoring my phone using the official tool motorola provides.
then, after reinstalling lineage and twrp this time (so i would have access to my data if it were to happen again), and setting everthing up again, it just happened again yesterday.
things I've tried:
- clearing the cache using twrp
- letting it boot for hours on end
- repairing the file system with twrp (idek what that does, but I had hopes)
I would really like to just find a solution to this, as I very much enjoyed using Lineage (when it was working), but reinstalling everything every 2 days is not an option. this **** is driving me insane, i haven't been able to find a decently answered forum post on this anywhere.
so yeah, i would be eternally grateful for any help I can get.
thank you <3
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
greenmatrix said:
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
Click to expand...
Click to collapse
no, I'm sorry, I have nothing. I gave up after the fourth time of wiping everything and am back to using the motorola rom. a real shame
good luck tho and if you find something that works, do let me know please!!
Bummer. I will let you know if I figure it out.
Got it working, see https://forum.xda-developers.com/t/...or-the-moto-g7-g7-power.4436929/post-87342621