Hello, while flashing does work both from TWRP and IDON, every ROM I tried will only boot for a few seconds, then the device just restarts.
It is not a problem of the power button, because I can do anything in TWRP.
Flashing official ROM from Samsung works, but it also reboots after a few seconds. (and keeps rebooting)
This all started with a kernel panic. After that the device didn't boot anymore.
So, I flashed official ROM. This booted, but was incredibly slow.
I flashed TWRP and various ROMs, but these only started to reboot repetitive, so I thought that maybe those were incorerct.
Flashed the same official ROM (also tried older version btw) but then it just started the repetitive reboot sequence.
So, is this device broke? What can I try?
Bright.Light said:
Hello, while flashing does work both from TWRP and IDON, every ROM I tried will only boot for a few seconds, then the device just restarts.
It is not a problem of the power button, because I can do anything in TWRP.
Flashing official ROM from Samsung works, but it also reboots after a few seconds. (and keeps rebooting)
This all started with a kernel panic. After that the device didn't boot anymore.
So, I flashed official ROM. This booted, but was incredibly slow.
I flashed TWRP and various ROMs, but these only started to reboot repetitive, so I thought that maybe those were incorerct.
Flashed the same official ROM (also tried older version btw) but then it just started the repetitive reboot sequence.
So, is this device broke? What can I try?
Click to expand...
Click to collapse
Must be something with the hardware. Maybe it is overheating and shutting down.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Must be something with the hardware. Maybe it is overheating and shutting down.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Hmm.. I might try to freeze it before booting (I did retrieve all data from a defective harddisk (click of death) by freezing it)
Related
I was flashing the newest cm10 as I do every few days. I flash that, then inverted apps, then kernel, then reboot and never had a problem. Now I am getting a blank screen after the "Samsung Galaxy SIII" splash with the button back-lights lit. Nothing else happens, no response. Never had an issue, but now I am worried. Any help here?
EDIT: I tried booting into recovery a few times with no success. Just tried it again and held all 3 buttons past the recovery flash on the top of the screen. Booted into that and re-flashed the update by itself. Phone just booted back up. Not sure what happened, but all is well in my s3 land again.
Usually not a good idea to flash a ROM and kernel at the same time. I know you said that that's the way you've been doing it buuuut....what happened to your phone is the symptom of your phone trying to match up a ROM and separate kernel at the same time, it got confused while booting lol. Best practice it ROM, gapps, reboot system let phone fully boot, reboot recovery and install kernel. Its an extra step but usually avoids what happened to you.
If your using ktoonsez kernel he has a special build for the latest nightly for people with the same problem as yours, it's not in the op, start from the end of the thread and work backwards.
Sent from my SGH-I747 using Tapatalk 2
I've got SGH I927R with litekernel rootbox(ootBox-JB-i927-Nightly-20130223.zip + gapps-jb-20130120-i927.zip).
Many times it's frozen while boot animation. Recovery works correctly (TWR). I try to reinstall kernel, clear cache, and after 7-9 tries it boots up.
adb logcat show nothing when freezing.
Same was before with literoom and ics stock kernel/litekernel ICS.
Once it boots up, then it's stable.
Any idea?
solved,flashed with other bootloder (thanks yohan4ws), and reflash the kernel, clear caches.
had the same issue
bubor said:
solved,flashed with other bootloder (thanks yohan4ws), and reflash the kernel, clear caches.
Click to expand...
Click to collapse
which rom you used to fix your phone? i had try with 2.3.5 but doesn't solve the issue
meny512 said:
which rom you used to fix your phone? i had try with 2.3.5 but doesn't solve the issue
Click to expand...
Click to collapse
I couldnt fix it, I live with the problem. Mine frozen after reboot only, I have to power off phone and wait 2-3 minutes, then it boots normally.
bubor said:
I couldnt fix it, I live with the problem. Mine frozen after reboot only, I have to power off phone and wait 2-3 minutes, then it boots normally.
Click to expand...
Click to collapse
solved freeze by change the rom to an original at&t ics rom but the phone gets locked and i can't unlock the phone so im thinking on pay for the code my phone isn't root so i doesn't have backup my EFS folder. maybe it can help to you
I have a similar problem, the phone sometimes hangs on the "SAMSUNG" logo when using the CM10.2 build. No issues with the official 4.0.4, though.
I think the phone boots fine when the charger is not connected and hangs if the charger is plugged in. I did too many things at one time (rebooting and cleaning caches from recovery and stuff), that's why I'm not entirely sure if the charger connection is related.
I'm not sure how else to describe these two problems I have.
Just for reference, I am using Cyanide L RC 7.1 from here: http://forum.xda-developers.com/galaxy-s3-att/development/rom-cyanide-l-v1-android-5-0-2-t2980174,
and I am using TWRP 2.8.5.0 for d2att. I have a i747M on Rogers.
Problem #1: boot loop only when plugged into AC charging
In the past week, I found that my phone gets stuck in a boot loop only when the phone is plugged into the AC charger. It will boot up, show the Samsung logo, then the Cyanogenmod logo with Cid, then show the Cyanide L boot animation. Once the animation is over, the phone just reboots. This happens endlessly (I didn't let it go on for more than 20 minutes, I didn't have time to wait). However, if I let the phone boot while it's not plugged in, then it boots up just fine. It also boots up just fine if I am plugged in via USB as a data connection to a computer. This only happens when I am plugged in via AC.
I have tried different combinations of USB cable and USB AC adapters. Doesn't seem to make a difference. I thought maybe it's a battery thing and borrowed a colleague's battery (also i747M), no dice.
Thoughts on what's causing it to boot loop like this?
Problem #2: Cannot wipe Data in TWRP
I discovered this problem when I was trying to update to the latest version of Cyanide L RC 8. I booted into recovery (TWRP 2.8.5.0) and proceeded to dirty flash the ROM. First boot had terrible com.android.phone FCs every 5 seconds. So I booted back into recovery a couple more times to reflash, same problem. I decided to do a clean flash and do a factory wipe. That's when the problem began. Once it reads "wiping Data without erasing /data/media" (or words to that effect) TWRP would freeze (the animated progress bar at hte bottom stops moving) and the phone would just reboot. The phone then gets stuck in an endless boot loop. I tried this numerous times, same problem. Couldn't restore a NANdroid either because it wipes Data before restoring.
I had to boot up into Download mode to use Odin to flash a custom ROM back and work my way back to a NANdroid I had. Took me the better part of 2 days without a working phone to get back to my latest NANdroid backup.
Any ideas what causes this freeze + crash in TWRP? I have reflashed TWRP, but I'm too afraid to test it out, only to lose another 2 days like that.
Thanks
Maybe you'll have better luck with Philz Touch recovery for the d2lte?
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
daver68 said:
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
Click to expand...
Click to collapse
If Odin doesn't get it try a wipe in the stock Samsung recovery.
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
audit13 said:
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
Click to expand...
Click to collapse
I'm on NF2, so definitely not an issue with the bootloops and bricking that might happen by being on 4.2 or earlier.
Flashing with Odin worked perfectly, and yes I used a ROM from sammobile.com. After that, I flashed SuperSU and TWRP 2.8.6.0 through Odin as well, before downloading another ROM to test wiping, flashing, more wiping, and more flashing. So far no crashes in TWRP when wiping data.
I haven't been able to re-produce the boot loop when plugged into AC, it's only been a day, but we'll see if that rears its head again.
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
daver68 said:
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
Click to expand...
Click to collapse
The problem 1: you mentioned that the you are suffering with the problem of rebooting in the loop that occurs only when you use the AC wall outlet for charging. You must see in its rectifying circuitry detail. The problem may be there.
I eventually found a solution, though I don't know if it was a solution to the root problem.
My problem was that I was getting bootloops when plugged into AC charger. My solution, how ever random it seems, was simply to flash back to stock (via ODIN) to 4.4.2. Since then, my Problem 1 and Problem 2 were solved. This completely wiped everything on my phone (luckily I did a complete backup to my computer), but it also solved both of my problems.
It seemed the problem #1 was not caused by a bad charger or cable, as one might have thought.
CyanogenMod version: 11.0-InstallerXNPQ09Q
Hello, I just installed CM on my S3 via the one-click install. Now I have problems powering off or rebooting my phone. I select "Reboot" from the power menu, and click OK. Then it hangs displaying the "Reboot phone" window, displaying the busy animation and saying "Rebooting...". Power off does much the same thing. Is there any solution to my problem? I have to take the battery out to shut the phone down. Once turned off, it starts up just fine.
Sometimes, though, the phone restarts properly. I don't know what would make the difference.
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
audit13 said:
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
Click to expand...
Click to collapse
That's what I ended up doing. I've been running it now several days and everything is working fine. I should have done that in the first place, oh well. The installer sure didn't leave a good impression on me, but now that I have successfully installed CM and it is working, I love it!
I did a search and maybe not correctly but I did not find my particular problem.
So I have stock root66 rom flashed with odin 3.11 on my phone goes into boot loop.
I flashed twrp 3.1.1-0 with odin and I can go into recovery but as soon as I select any rom (OCT-N-WEEKLY-20170811-1427-d2tmo) it starts to do something and just reboots the phone and back into the boot loop. I reboots to fast for me to even figure out what it says on the phone.
Has anyone else experienced this? Battery is charged to 80%+
edit: tried CWM same symptoms reboots right away. Only thing I can flash with is odin otherwise with any recovery reboots right away. I was able to flash a modem with twrp and that works but no roms work.
update 2: I finally was able to get root66 installed. Gets to the set up part. Once I finish the setup the phone turned off on its own. It never turns on on its own so leads me to believe the power button isnot stuck but why does it turn off on its own? I turned back on and goes into bootloop.
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
audit13 said:
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
Click to expand...
Click to collapse
Thanks for the reply. I have tried 6.0.1.2_CWM_Touch-recovery-image & twrp-3.0.2-0-d2tmo.img but not 2.87.
However, as I stated above I was able to flash a modem but just not flash any roms which is weird.
If the power button pressed and the phone reboots when i pull the battery and put back in wouldn't the phone turn back on? I'm just finding it odd the phone keeps rebooting but when I pull the battery and put back in it doesnt turn on automatically.
update: So 2.8.6 twrp worked which is odd installing as we speak phone has not rebooted yet so lets see how it does once rom is flashed. I did odin root66 and after that installed it kept rebooting so fingers crossed this works. Using OCT-N-WEEKLY-20170811-1427-d2tmo hopefully this works
so after the flash seems to just back to the bootloop. I'm still not convinced my power button is stuck since it doesnt auto turn on and during the whole process of flashing it didnt reboot on its own only after the flash. Any ideas?
Literally gets to the samsung galaxy siii logo and reboots right away.
Try flashing the latest stock ROM, not a rooted stock ROM.
audit13 said:
Try flashing the latest stock ROM, not a rooted stock ROM.
Click to expand...
Click to collapse
same bootloop. Gets to the tmobile animation and then reboots.
It's possible that the memory chip is damaged. You could take it to a repair shop and have it flashed via jtag.