Hello guys,
Thank you for reading, any help is appreciated.
My device was running the latest release of CM13 (cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NK-serrano3gxx) and TWRP v3.0.2-1
So yesterday afternoon my phone randomly shutdown and I was unable to get it turned back on until this morning.
However though when i did manage to get it powered on after hours of failed tries it was stuck on the Samsung boot screen.
I've since tried to access the TWRP Recovery (Pwr + Vol Up + Home) but it sticks on the TWRP slash screen and then attempts to reboot normally (which as i said stick on the Samsung boot screen).
I also tried re-installing TWRP via Odin and it appears to be installing properly and successfully but when i attempt to access TWRP it again sticks on the splash screen,
I've also tried installing CWM Record via odin and that also appears to be installing properly and successfully but when I attempt to access the recovery I am yet again greeted with the TWRP Slash Screen which has lead me to believe something is going wrong.
Any ideas or suggestions as to what may be going on here ?
Thanks in advance, any help is appreciated.
Hey again guys,
I have tried installing stock rom via Odin, It says Pass but nothing at all seems to be changing.
I'm beginning to think Odin may really not be working at all or something is wrong with the phone
Update: I tried flashing TWRP recovery via Heimdall and it appears to have completed successfully saying "RECOVERY upload successful" but when i reboot immediately after into Recovery mode it still sticks at the TWRP 3.0.0-0 Splash Screen then attempts to reboot normally which as mentioned earlier also sticks on samsung slash screen
Related
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
I'm unfortunately stuck in a very similar situation.
I was updating the firmware on my tablet to 4.4.2 downloaded off Sammy mobile, uploading using Odin. I've done this dozens of times since my S2 which was 12 handsets and 6 Android tablets ago. This time, about a third of the way through the process hung for a few minutes then the device restarted without warning and now its stuck in a loop where it starts normally
http://imgur.com/MTwiE5V [1]
Then says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery.
Then this
http://imgur.com/Ua1nmhi [2]
and stays on that screen for short periods before rebooting and starting the above again.
Thanks in advance for any tips or help you guys can provide!
SleepyDonald said:
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
Click to expand...
Click to collapse
Have tried factory reset/clear cache/clear dalvik?
shayind4 said:
Have tried factory reset/clear cache/clear dalvik?
Click to expand...
Click to collapse
Thanks, but it turns out the solution to my problem was simple. I took it to the place I got it from and the guy just pressed power, vol and menu button long enough until it rebooted. I'm quite a noob it seems.
I'm not sure if it will help you Nationalmaverick, because my problem was slightly different.
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
christanya99 said:
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
Click to expand...
Click to collapse
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
newbyp said:
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
Click to expand...
Click to collapse
Thanks for the advice.
I managed to make it into stock recovery but can't seem to get to CWM still. I reloaded Superusuer and the tried Oneclickrecovery. ADB shows success and say's I should be in CWM but I just get a blank screen.
Hi,
I had rooted my device with TWRP Recovery installed. I then updated my Cyanogen 12 version from cm-12-20150430-NIGHTLY to cm-12-20150502-NIGHTLY. Post that, I did a factory reset from CM12. Since then, my phone has been stuck in a constant TWRP Loop where the TWRP logo keeps flashing every few seconds. Unable to access the recovery. The phone buttons do not power off or restart the phone. However, I can access fastboot if i let the battery run out and then start the phone. Please help me.
AnirudhS89 said:
Hi,
I had rooted my device with TWRP Recovery installed. I then updated my Cyanogen 12 version from cm-12-20150430-NIGHTLY to cm-12-20150502-NIGHTLY. Post that, I did a factory reset from CM12. Since then, my phone has been stuck in a constant TWRP Loop where the TWRP logo keeps flashing every few seconds. Unable to access the recovery. The phone buttons do not power off or restart the phone. However, I can access fastboot if i let the battery run out and then start the phone. Please help me.
Click to expand...
Click to collapse
Got it done guys. Reinstalled twrp using fastboot. This stopped the loop.
Thanks !!
My phone is rooted, but I can't go into recovery mode. I've tried stock, TWRP and CWM images, all without success. The command line says everything went ok but upon trying to boot into recovery, the phone vibrates twice and then goes into fastboot.
After some tweaking I've deleted the recovery/flashed TWRP, and it only works in 50% of the screen, and this part is glitched.
Any help?
Hi xda developers,
so what happend is I updated CM to the most recent release, couldn't access TWRP recovery mode anymore for some reason, then tried to flash the newest TWRP release (3.0.2.0) via Flashify. After that I was stuck on boot at the Samsung logo, but could still access download mode (but not recovery mode). After some unsuccessful flashing attempts via Odin and Kies I'm stuck on the "Firmware upgrade encountered an issue" screen, any button combo goes directly to this screen. I came to the realization that I don't know what the **** I'm doing and have probably destroyed my phone.
Any help is greatly appreciated.