So there's some issue with my phone, it started with an issue where my phone would crash, restart, and then go into a booting loop (the samsung logo part). Well after a few retries of installing that rom again (phantom blazer), after that very version of the rom had worked without an issue for 4 months, the crash/boot loop happened again. After this instance, reinstalling the same ROM would not get me into the android OS.
So I moved on to a new rom (paranoid android), which worked for a little while, and then had the exact same issue. After two times in a month of the same crash/boot loop, I moved on to a new rom (wicked sensations). So here I am now with the same issue, but it seems to have gotten worse. Now the crashes happen more often, randomly while in my pocket, and often when trying to place/answer a call, but the frequent crashes are without the boot loop and need to reinstall a rom.
I follow the installation instructions for each rom to the T, all the wiping of dalviks and cache, but the same **** keeps happening. Does this sound like a hardware error in my phone?? Should I return to a stock rom and see if my issue keeps happening? I'm in a rage at this point . Please halp.
I would try this link-http://forum.xda-developers.com/showthread.php?t=1904099. And like you said, see if problems continues. I think any ROM can and will reboot at some point, are you updating your ROMs as developers update them?
Sent from my hybrid GS3
Have you considered your experiencing the 'sudden death syndrome' you may have a faulty power button it's a known issue with the S3. Sprint does repair or exchange the phone for this. It's exactly what you described it powers off and on. It can power up until the splash screen and it powers right down. It just so happens that you start playing with the power button when trying to go into recovery to flash another rom or what not and it clears the issue for a while. Until it sticks again. Just something to consider you can search it here under exactly what I called it 'sudden death syndrome'
Sent from the future via Tapatalk 4
Related
I have a T-mobile Samsung s2. The sucker keeps randomly freezing usually 10 to 30 seconds after reboot. Sometimes i can go for about 10 to 30 minutes without freezing, but...it always ends up freezing sooner or later(only thing I can do is hold the power button for 10 seconds and restart the device). I did the whole master reset and recover from stock to no avail. It keeps freezing. Second step was, I rooted and installed clockworkmod. Did a back up of my phone, and tried to install different roms. I tried jedi mind trick and cm10 hercules, but both of these get stuck on the start up screen. I restored my original back up image and now it boots but it keeps freezing like always. Is there something physically wrong with my device? any input would be appreciated.
The only other thing I'd try would to Odin back to stock then update with Kies; if u haven't all ready? If that doesn't work then without re rooting the phone call T mobile and tell them that after u updated the phone it keeps freezing on u. Hopes this helps and good luck!
Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.
Jyjieng11 said:
Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.
Click to expand...
Click to collapse
If your phone is functioning normally.....there's no reason why you can't flash any rom made for our phone.
Sent from my cell phone telephone....
The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.
Jyjieng11 said:
The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.
Click to expand...
Click to collapse
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....
kj2112 said:
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
It couldnt have been a bootloop because it was working just fine for a while after flashing and then later on I set it on the table to come back to it flashing where it kept unlocking and locking and unlocking. I was unable to do anything with the phone at the time and after a while it kept restarting and vibrating. You dont think its hardware issues?
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
Hello,
my phone is stuck in reboot loop since yesterday.
I have this phone since 2 years. It was rooted and on fulmics 5.3. Since few weeks i had random reboots, more and more often, since yesterday when it became unusable because of the reboots.
It wasn't in bootloop, but the phone starts, the rom loads, and after some seconds it reboots.
So i changed rom, went on exodus, but the problem remanins. The rom boots, and after 1 or 2 mins it reboots, go in bootloop, then starts and reboots again.
Today i've made the Flashtool procedure to go back on stock, but the problem still remain. The rom booted, changed the language then rebooted again.
Wad can i do now?
Thanks
perhaps to be hardware problems, there are some parts of poor contact caused by repeatedly reboot
its not the problem of rom . its a battery issue
replace battery
Maybe this ^
I'm using phone connected to power and it seems to works!
Thanks!
Buy a new battery
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.