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 !!
Related
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.
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
HI i flashed this aosp rom
https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499
i flashed the rom, the gapps file and mr bump, and figured i would get root later.
After setting up my D855 i decided to get root, so i pressed to reboot to recovery and there was none!!! the phone kept "recovery bootloopin" and showing the tre triangle with android logo for a split second, then the screen turned black-off then egain and again, untill i pulled the battery and it booted normally.
i tried kingroot and similar options but nothing worked. I tried to adb flash recovery but it was my first time with adb and could make it work. PLease HELP!!!
bamiasHELLAS said:
HI i flashed this aosp rom
https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499
i flashed the rom, the gapps file and mr bump, and figured i would get root later.
After setting up my D855 i decided to get root, so i pressed to reboot to recovery and there was none!!! the phone kept "recovery bootloopin" and showing the tre triangle with android logo for a split second, then the screen turned black-off then egain and again, untill i pulled the battery and it booted normally.
i tried kingroot and similar options but nothing worked. I tried to adb flash recovery but it was my first time with adb and could make it work. PLease HELP!!!
Click to expand...
Click to collapse
I would just reflash the kdz and start again, it would be way easier that way if you have the time.
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.