I bought my S3 I9300 (INTL) when it first came out. Since then, it has been working perfectly fine. I rooted it a year ago and installed cm10 at that time as well. Afterwards, I had also successfully switched back to stock rom via my nandbackup.
A week ago, I did a nand backup via CWM and then decided to install CM 13 nightly. After that I had no serious issues (just small issues such as data connection not automatically turning on. Had to do it from settings) so I didn't update either. Two days ago just when I needed my phone the most, it turns off suddenly. Every time I try to turn it on, it can't go past the CM boot logo. I then put my phone on charge. I turned it on and it worked while it was charging. At 88% i take off the plug and the same thing happens again (bootloop). I then plug the charger back on and restart after going to download mode (to stop the bootloop). It then shows a charge of 5 percent. I charge again then I decided to quickly to a factory reset as I was in a hurry. Then while I was in my car, I let it restore the backup from my sdcard1. However, I noticed that it said "failed to restore /data". I did another reset and cleared cache etc but everytime it would say either failed to restore /data or /system. Doing an advanced restore didn't work either. Then factory reset again and downloaded CM 11 more stable version. I moved it from my tab (which I downloaded it with) to my phone via sd card. However, it fails to install. At 20% it restarts my phone back in to bootloop but this time a samsung bootloop as I already did a reset. Now my phone is unusable and bootloops every time I try to turn it on. Further note, the charging icon shows the cm13 charging icon.
Right now: Downloading stock rom from a different country because can't find mine.
Hi,
Try posting your question here:
Galaxy S III Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
Related
Hi guys, my phone is right borked and I hope someone can help me out. I've been searching forums all day and I find bits and pieces of advice that apply to parts of my situation, but haven’t found a fix yet.
I installed CyanogenMod on my Rogers Samsung G3 a couple months back. Everything has been going smoothly until last night when I installed an update.
The phone rebooted and got stuck on the Samsung splash screen with the blue cyanogen dude. I left it for 30 min and when I got back, it was still the same.
I took the battery out, turned it back on and ended up in the same spot. I took the battery out again, turned it on and left it over night. Same thing this morning.
On advice from this forum I put the phone in recovery mode. I thought I had TWRP, but Clockwork Recovery comes up.
I did a factory reset, and cleared the cache. Rebooted and still the same thing.
I tried to flash the ROM, but it doesn't work. The android dude just lies there, dead. Poor guy.
I plugged it into my computer but even though the computer makes the connection ‘cah-ching’ its not recognized. Through the recovery screen I tried unmounting and mounting everything, and mounting as usb and the computer still won’t pick it up. I uninstalled Kies, and the drivers for the phone and re installed everything. The driver pop up says MTP has failed.
Any suggestions?
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!
Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").
Need suggestions for this.
A few weeks ago I rooted my phone to remove some apps that I never used. I just kept using my phone as always and did nothing special except removing those apps. Today I decided to unroot my phone because I felt it would be safer in case anything should happen to it (HOW IRONIC). It's only 3 months old and I didn't want to loose my warranty. I opened the SuperUser app and clicked full unroot and clicked continue. My phone instantly returned to the home screen and then powered off. Then it turned on again, but now the message "Samsung Galaxy S7 powered by Android" keeps flashing on the screen. I went into recovery mode and tried wiping the cache first, but nothing changed. Then I wiped all my data and did a factory reset, but my phone keeps flashing and won't turn on. I'm really desperate and don't know what to do because I'm afraid I can't take it to my retailer because my phone is rooted (if it still is rooted, but I have no idea). What should I do?
Hi,
Try posting your question here:
http://forum.xda-developers.com/galaxy-s7/help
The experts there may be able to help.
Good luck!
Hi Guys,
My S7 (SM-G930F, Netherlands PHN device) randomly reboots. I cannot use my phone anymore because it reboots somewhere between 5 seconds to max. 2 minutes after it reboots.
What did I do to try to fix it:
1. clear cache + full wipe via the recovery mode.
2. downgrade to stock (PHN via Sammobile and ODIN install) Android 6 rom (and after that upgraded to Nougat 7).
3. Fully charge battery and let it drain down all the way.
- My device is not rooted but original Samsung
- My device does not have a single scratch nor it ever fell down
It looks like a hardware problem to me or am I missing something?
I had the same problem with the Galaxy A5 2017. Couldn't fix it, decided to return it, and even the carrier couldn't fix it so they gave me a new one which didn't have the problem. So, if you're still under warranty, return it.
Hi @sanderh
I had the same problem with my G930F for a week. I left it off for 5 days. After that time I turned it on and it's fine now. Two months without reboots :victory:
No reboots to this day :fingers-crossed:
After one year the restarts returned. This happened while updating to Oreo. I left the phone switched off again for 5 days but the problem remained.
When I made a backup files from phone to PC, I noticed that everything works when the MicroSD card is removed. No reboots. I decided to change SD card - it worked. Formatting the memory card also helped so... I'm enjoying again with the working phone