Hello everyone. I was using a rooted stock rom with TWRP and magisk installed for my S7 and decided to encrypt it. However, after rebooting I got a message saying it was unsuccessful and that I would need to wipe the phone by pressing the button. I pressed it, the phone rebooted again and a TWRP screen showed up, with lots of errors, for about a second or two. Then, it reboots once more into the "Encryption unsuccessful" warning, and I'm stuck there. Any advice? I'll try to write down the TWRP error log, but it goes away too fast.
Update: I managed to enter download mode and flashed an updated version of TWRP (3.3.1.0). The errors are gone, but I'm still bootlooping. Can't seem to boot into twrp using Vol Up + Power + Home
Related
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.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
When I installed the CM13 using the TWRP recovery, my screen was stuck on the boot animation for long time. I to get into recovery mode by pressing Volume-up & Power button but my phone vibrated 3 times and nothing happened.
So i googled around for solution and one of the post said "clear your sd card" which i followed blindly and now that has resulted in the screen getting into "Encryption unsuccessful" screen after few seconds of boot animation. This screen also has a button to "Reset to factory " which restarts the phone but results back in the same "Encryption unsuccessful" screen. So now i have a phone with the following,
Empty/formatted SD Card
Corrupted TWRP (since the files are gone from SD Card)
Unable to enter into recovery mode (by pressing Volume-up & Power button)
How can I get my phone working again?
yash0087 said:
When I installed the CM13 using the TWRP recovery, my screen was stuck on the boot animation for long time. I to get into recovery mode by pressing Volume-up & Power button but my phone vibrated 3 times and nothing happened.
So i googled around for solution and one of the post said "clear your sd card" which i followed blindly and now that has resulted in the screen getting into "Encryption unsuccessful" screen after few seconds of boot animation. This screen also has a button to "Reset to factory " which restarts the phone but results back in the same "Encryption unsuccessful" screen. So now i have a phone with the following,
Empty/formatted SD Card
Corrupted TWRP (since the files are gone from SD Card)
Unable to enter into recovery mode (by pressing Volume-up & Power button)
How can I get my phone working again?
Click to expand...
Click to collapse
Greetings and welcome to assist. I think the safest option is to return your phone to stock first by flashing stock rom and then twrp but you could just try reflashing twrp. If you ask in the DesireHD forums the experts there will help you
http://forum.xda-developers.com/htc-desire-hd/help
Good Luck
Sawdoctor
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
Not able to get into TWRP recovery, stuck on "Your device is booting now..."
Hey everyone,
I just unlocked my bootloader and now want to flash TWRP and SuperSU. My Phone is already Nougat with Emui 5.
The Problem is that I'm just not able to enter the recovery. When pressing volume down + power or trying "adb reboot recovery" in the command line, the phone starts in the "unlocked bootloader warning screen". But not like in the normal warning screen it doesn't give me options but just shows a white line saying "Your device is booting now..." and thats where it gets stuck. Only gets hotter...
The fun thing is I already was in the recovery but wasn't able to flash the SuperSU (r275). Maybe it was not compatible with Nougat. TWRP just couldn't mount various things. After reflashing the recovery below instead of some other version (don't know anymore) I'm not able to enter the recovery again.
Feels like I searched the whole Internet and there is nearly nobody with the problem or a solution. Tried this as well: https://forum.xda-developers.com/honor-8/help/honor-8-boot-to-twrp-recovery-lost-root-t3567462. It seems like nobody who published a Honor 8 + Nougat + TWRP + SuperSU "How To" acutally tried it himself.
I used this TWRP https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Please help me I can't use WhatsApp because I need to restore it with Titanium (Database way doesn't restore all chats... Other problem)
Thanks everybody I just can't stand this anymore
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
sysak said:
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
Click to expand...
Click to collapse
Thank you I got it!
So I got my L09 with Nougat/Emui 5 on it. Then just used TWRP from https://forum.xda-developers.com/showpost.php?p=70228949&postcount=252 (bootable, think ist ist 3.0.2.0) then flashed 3.1.1.0 from https://forum.xda-developers.com/honor-8/development/twrp-t3566563 (bootable) and finally flashed SuperSu from first Link again. Other SuperSU versions (like the phh r275) WERE NOT flashable.
Magisk is the most compatible root solution for the Honor 8 on Nougat. The only thing that doesn't work (seamlessly) is MagiskHide, but the root itself works and flashes fine from TWRP.
I have tried to flash twrp multiple times to no success. I have tried multiple variations of the tool but for some reason when I go try to boot into recovery it takes me to erecovery which fails to do anything.
Are you sure about button combination
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
sysak said:
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
Click to expand...
Click to collapse
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Dalg1991 said:
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Click to expand...
Click to collapse
Try adb reboot recovery in command line on your PC when phone is turned on
0mrwhatsupguy0 said:
Try adb reboot recovery in command line on your PC when phone is turned on
Click to expand...
Click to collapse
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Few problems with Binary SU and BusyBox
My phone seems to be rooted. Titanium Backup works but I have to accept every App instalation manually. With other settings restoring gets stuck. Also SuperSU reminds me every time that my BinarySU needs an actualisation but fails if it tries. And finally BusyBox just isn't able to get itself installed.
I'm thinking about restoring stock firmware, update to Nougat, and flash the two TWRP Versions and SuperSU again but hate to spend ours on my phone. OnePlus One rooting was sooo easy...
Dalg1991 said:
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Click to expand...
Click to collapse
Is there a number of times you have to do it? How should I transition from this stupid "Your device is an enemy of the state" screen to something that will connect to adb?