Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
Phone was running stock os. I rebooted my phone and it's now stuck in a boot loop. I tried to reinstall it through Smart Switch and it's still stuck in a boot loop.
After the reinstall it goes to "Installing system updates" and almost right after it stops and shows "Erasing" for a second. It then reboots a few times and it usually goes to the Kernel Panic error but it has also gone to Manual Mode once to try and install the updates but then it fails to mount any partition.
I've tried installing Lineage OS (I used it before I went back to stock os) through TWRP and I also got the same errors. I was unable to mount any partitions and left the phone without a battery for a few a day.
When I tried again just now I was able to mount the partitions but installing Lineage OS or stock OS was still not possible and it gave me the same errors again.
Is there anything I can do to fix this?
First error after boot loops: imgur.com/a/ZOTfR
Errors on TWRP: imgur.com/a/qYqsY
Manual install in recovery: imgur.com/a/YHeyS
Another error: imgur.com/a/xPHdm
EDIT: After trying for three days, it suddenly booted. I can boot to the OS but the phone still crashes and boot loops every time. If I go to recovery and wipe cache it will boot again. What can I do to stop it from crashing and going back to boot loops?
I tried to root my phone.. without installing any custom recovery i just installed magisk manager then the zip file and started recovery booting (by pressing home+power+vol up). First it showed installing system updates then its displayed that failed to open recovery cause no such file. Now i cant reboot my device. There is a boot loop. I have tried wiping cache partition, data factory reset but still it dosn't opens. its stuck in samsanug logo page and keeps on booting again and again.
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
I was using OrangeFox and tried to flash PixelExperience 11 from PixelExperience 10.
The flash went smoothly, but it goes to bootloop after i restart.
So i go back to OrangeFox to format my data and tried to reboot once again to finally get it working.
Then i tried to install magisk but my my recovery has encryption problem.
So i tried to install OrangeFox from ADB sideload but got error message halfway.
Now whenever i tried to reboot into recovery, it just go through the system and reboot just fine.
And to make it worse. Everytime i go to bootloader i just get blank screen and fastboot can't detect it.
My problem is PE 11 is so unstable and some of my apps won't even open.
Now is there any way to fix my recovery or bootloader?