My phone keeps restarting. Black screen -> Warning bootloader unlocked -> Black screen... etc. I also cannot access the recovery, gives me a black screen only.
Is the phone broken, or is there something that can be done?
What phone do you have? What caused this to happen?
XT1032
Installed PhilZ Advanced Recovery. Made a backup, rebooted devices, and stuck in this bootloop. When enter Bootloader to get to recovery, all i get is a black screen.
Can't even shut the phone off, because it keeps restarting.
Flash Philz again but don't reboot the phone. When Philz flashes successfully, use the phone's volume buttons to go to recovery from fastboot.
The problem here is i cannot get the phone to show up as an attached device, unless i do it "manually" where i reboot into bootloader from the standard android/phone interface.
You need to be in fastboot mode on the phone to flash Philz. Re-booting to bootloader from Android is fine.
After a little tweaking and some work, I managed to get it working.
Thank you for your help.
Related
When booting into recovery mode, the system hangs.
(It can boot normal without a problem)
The device had JB without root, so did the following:
1. Installed the ASUS bootloader unlock utility
2. Installed TWRP 2.3.1.0
3. Installed CleanROM 2.4
Now, when booting into recovery mode:
Via the shut-down menu, the system reboots into the white ASUS logo screen and hangs
Via power+volume Up, and selecting the [RCK] icon, the system hangs (the top left of the screen says "Booting Recovery kernel image")
I'm guessing the system is looking for a ROM file and simply can't find it.
Do you guys ROM experts know what I did wrong and what the fix might be?
After reinstalling TWRP - Recovery mode is working again!
I'll leave this post up in case it happens to anyone else.
I scoured the forums, but have not been able to find out what I can do to solve my problem. So here it is.
I rooted my phone (to play around with some settings, what have you) and flashed TWRP recovery onto it. I got an error msg when booting up, so I decided to push an original recovery back onto the phone, because it wouldn't go to TWRP. I followed a guide (which I can't find now) to push back a stock version of recovery and it failed. My phone would boot normally just fine, but when I tried to go to recovery it would loop.
The OTA update came today, and dumbass me pressed continue (not thinking) and now I am stuck in a boot loop, and cannot get out of it.
Cannot get into recovery.
Cannot get into download mode.
Got any ideas?
Thanks
Same Problem
I have pretty much the same problem. Please help!
well without recovery/download mode working or the phone being in fastboot mode there really isn't much that can be done, you can always try to claim on warranty
boot loop
So, let me get this straight. If it failed when you tried to install the stock recovery, then you still have the TWRP recovery right?
I ran into a boot loop problem earlier when I tried upgrading TWRP. I just couldn't access my recovery so here is what I tried:
Code:
Turn your phone off.
Press volume down and power button until the LG logo comes on screen
Let go of both buttons
Hold the volume down and power buttons again until you see the "hard reset screen"
Press power once and then power again to confirm. The screen says it will reset your device but it will not as long as you have a custom recovery installed.
Your custom recovery should appear on screen.
Try the steps above and see if you can get into a recovery. Once you do maybe try resetting. Hope that helps.
Hello everyone
I own the Motorola Moto G ( 1st gen) xt1033 model. I had cm 13(latest release) flashed on it and my custom recovery is TWRP 2.8.4.0 and it was working fine until today after using it for around 2 months.
So what happened today is that while running an application, my Moto G shut down randomly( I don't know the reason for that),and it got stuck in bootloop ( Everytime I start it, the cm logo will appear and then it sometimes even shows my lock screen but instantly becomes black after that and most of the time its stuck only on the cm logo). After this I thought of restoring it back to the original firmware using this link: http://forum.xda-developers.com/showthread.php?t=2700502
I can get into fastboot mode but can't access the ADB as USB debugging mode was not enabled ( that's the main problem )
So following the procedures of that post, everything worked well on the log of the fastboot (no errors) but after that when I reboot my phone, again the cm logo appears (Even when I flashed it to stock 5.0.2 Lollipop!) and I can even get to my old lock screen sometimes and then instantly it goes black. Even if I try flashing a custom image like stock or some other ROM , it gives no effect as again the cm logo would appear.
I think this has to do with the fact that USB debugging mode was not enabled on it.
Also, I can't enter my recovery. When I use the standard procedure to get into fastboot (power button + volume (-) ) and select recovery, the TWRP splash screen comes then the screen turns black and normal reboot takes place( stuck on the cm head). I tried flashing different recoveries using fastboot (also tried mfastboot) like CWM and even TWRP again but still that bugged TWRP recovery remains.
I can't get to recovery neither can I boot up my phone. I can flash recovery or image files(It shows no errors flashing things, but no effect takes place :/ )
Can someone please help me in finding the solution for this problem? Thanks in advance
Just clear the data, cache and dalvik cache. Phone should boot
I have a oneplus one with faulty voulume buttons, I tired flashing my phone today and it got stuck on the boot logo so I enterted into recovery mode and chose to reset the phone. The problem is now that it has been reset and is still stuck on the boot logo and adb does not reconsige it either. Anything I can do?
have you tried taking the back off and checking the buttons? they may not be aligned right. and if you cant get into recovery or fastboot mode via key combo, not much you can do
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?
Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.
Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved