I bought it yesterday. Was listening to a podcast in Doggcatcher when all of a sudden the device rebooted.. and now it's stuck in a bootloop. If I do a factory reset, it boots up then notifies me that Android Core (acore) has stopped working.
What the heck? Do I just need to take this back to AT&T since we don't have an unlocked bootloader yet?
tjsimmons said:
I bought it yesterday. Was listening to a podcast in Doggcatcher when all of a sudden the device rebooted.. and now it's stuck in a bootloop. If I do a factory reset, it boots up then notifies me that Android Core (acore) has stopped working.
What the heck? Do I just need to take this back to AT&T since we don't have an unlocked bootloader yet?
Click to expand...
Click to collapse
Should be back to AT&T already.
That's what I figured.. ugh. If we had an unlocked bootloader, I could've fixed this thing myself. Don't know what the heck happened with it, but it's annoying.
I rooted my Samsung Galaxy S4 and now its randomly restarting. its not a whole restart just the boot logo shows up and after that im back in the home screeen (I doint have to type in my SIM code). Even after Factoryx Reset its still doing it.(Still Rooted) I got the TWRP recovery installed too.
Skybcraft said:
I rooted my Samsung Galaxy S4 and now its randomly restarting. its not a whole restart just the boot logo shows up and after that im back in the home screeen (I doint have to type in my SIM code). Even after Factoryx Reset its still doing it.(Still Rooted) I got the TWRP recovery installed too.
Click to expand...
Click to collapse
Do you have any custom rom installed? I had exactly the same issue on my Samsung Galaxy S2 with SentinelROM. That problem dissapeared after flashing AOSP NeatROM on my phone. You could also try unrooting your phone, again reset factory settings and test it. If it's working fine, you could try rooting your phone again.
Unrooting Samsung Glaxy S4: h t t p://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
I have a verizon sch-i535 samsung galaxy s3 that had 4.3 jelly bean and took the 4.4.2 update. I bricked my first phone trying to root and flash because im a complete noon but I got my second one did quite a bit of research and tried it again. Results...downloaded towelroot did the steps became rooted...downloaded supersu success...downloaded busybox installed it in the system/xbin path so far so good...downloaded root toolbox backed up the bootloader image disabled the bootloader the rebooted the phone and I now have an unlocked padlock and "custom" on the first screen....maybe? I then went back to root toolbox rebooted phone into recovery mode and it said no command...rebooted and again padlock and custom appeared but my last two screens that load didnt appear screen was black hit power key and I was on my lock screen. Odd I thought I went into root toolbox a third time booted into download mode in the top left corner it said custom in small blue letters and restarted on its own and yes the padlock and custom was there and still skipped my other two screens before loading.and screen was black. Hit power key and there was my home screen again.....this is only my second attempt to root anything in my life and dont want to brick my phone again...any ideas?
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
After factory reseting my samsung galaxy A2core at first it worked properly but after i rebooted the device it couldnt go past the samsung logo and it had something written on top of the screen in written on top in redsaying that only officially recorgnised firmware is allowed ro be flashed and after the mechanics tried flashing it it started working it could now even boot properly but cant not make calls or even text it says not registered on the newtwork
Mungu Chris said:
After factory reseting my samsung galaxy A2core at first it worked properly but after i rebooted the device it couldnt go past the samsung logo and it had something written on top of the screen in written on top in redsaying that only officially recorgnised firmware is allowed ro be flashed and after the mechanics tried flashing it it started working it could now even boot properly but cant not make calls or even text it says not registered on the newtwork
Click to expand...
Click to collapse
a friend got same issue. did u get solution?