What i've done:
I rooted my Nexus 5 some months ago, TWRP got flashed in the process and i flashed CyanogenMod 11 -> Everything works fine
A few weeks ago i used the built-in encryption -> Still everything fine
Today, i decided to flash the newest CM12.1. I downloaded the rom and gapps, entered TWRP, typed in my encryption-password and flashed the ZIP-Files.
CM12.1 started fine, all data and settings still and place.
My Problem:
Then i tried to start an app requiring Root-Access. -> Got denied!
To fix this, i wanted to enter the recovery and flash SuperSU manually, but suddenly i cannot enter TWRP anymore. It won't accept my password for the encryption!
Because i made backups, i then considered to reset my smartphone. I went to the security-dialogue, and pushed the reset button, but my phone just ended in a loop where it showed the TWRP-Logo and a blackscreen for a few seconds.
Now i can use my phone, but i don't have root access, cannot enter recovery and feel ****ed up. How can i solve this?
How do i regain root without being able to enter recovery or -> solved
how do i update TWRP without root? Iirc, to use adb sideload i have to be able to enter recovery, right?
or how i reset my phone, so i get rid of the encryption?
Related
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.
Hi,
last month I received an OTA update on my stock OPO Cyanogen 12.1, ever since then my settings app have disappeared (cannot access it at all, not even from safe mode)
a week ago I started receiving an OTA notification to update to the latest firmware (20MB download) (I think it's Yog4pas3jl)
anyway I was not able to update it, i would get booted back into recovery (OnePlus recovery)
*this phone does not have its USB debugging let alone developer options enabled.
in recovery I attempted to factory reset the phone (after half way attempting to unlock bootloader using Android SDK, Universal ADB and CMD)
now it appears that my phone has been "reset" but at the selecting language screen I keep getting Unfortunately CyanogenStats has stopped, and also getting Unfortunately Setup Wizard has stopped working (after tapping on language)
I can't use my phone now as I can't get past the setup wizard,
it does not appear that I am able to boot into recovery as well, please help me!
*UPDATE able to enter Cyanogen Recovery, tried wiping cache/factory reset, still stuck at Setup Wizard has stopped working. Oh no..
Try flashing a custom recovery and wipe dalvik+chache+data (doing that will not delete your sdcard). I also got such FCs in the past and that fixed it for me.
Try to flash system partition (or full firmware) via fastboot. Just follow this guide: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471, "8. How To Flash The Cyanogen OS Fastboot Images".
P.S.
You could get full firmware here: http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip
So I was on Marshmallow, got tired of the excessive battery drain and SD card limitations, and flashed back to Lollipop. I was able to flash TWRP, but then when I rebooted, I was told there was an update, so I reflashed the stock recovery and updated. Now I can't get back to TWRP. I flashed it repeatedly and every time I reboot into recovery, it's still on stock. I've lost root and nothing I've tried works. WTF?
Nevermind, I just tried flashing TWRP 2.8.7.1 and it worked. 2.8.7.3 apparently does not anymore.
Can a mod delete this?
Not really sure where I should have put this but have a weird issue. I have a droid turbo xt1254 that I have rooted and flashed many times. The most recent, today, I accidentally did a full system wipe and when I went to reflash the rom already in twrp, it gave me an error.
I then tracked down cm13 for my phone, which had worked previously and reinstalled it but every time I reboot the phone, it goes straight into twrp.
I have found that If I reboot into the bootloader, I can choose factory and whichever rom I have installed works until I reboot.
Can anyone help me stop this and get it to boot straight into the rom?
For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.
This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.
I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?
altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.