After some tinkering, I finally got my XT1031 to install CM13 and get pass the stuck CM logo animation, which I'm calling a "boot loop."
One of the first things I did was enable encryption in the Android system settings. However, after the device rebooted to start the encryption process, it's again stuck on the same animated logo.
I would appreciate any tips you have on how to fix this, or how to go about troubleshooting it. A good place for me to start would be to figure out how to pull logs off the device.
Here's the recovery.log file if I reset immediately into Recovery mode: http://pastebin.com/8Vuv9Z01
One more bit of information: When I boot into TWRP 3.0.2-0, it sees that storage is encrypted when attempting to mount it, and prompts me for the password.
When I enter the wrong password, it fails. If I enter my device PIN, it successfully decrypts and I'm able to make modifications as normal.
This suggests to me that the root problem is not that the encryption process failed.
Related
I have a Samsung Galaxy Victory running Android 4.1.2 rooted with TWRP installed and it was encrypted.
Today the phone froze and I powered it off by holding the power button for 5 seconds or so. Once I turned it back on, I got to the encryption prompt to enter the PIN to continue booting. However, the PIN I entered (which I know is correct because I've been using it for weeks to boot the phone) was wrong according to Android and could not unlock the phone for continued booting.
I booted into TWRP and did a factory reset with no luck (got a lot of unable to mount errors). I entered enough failed PINs that the phone decides to erase all my user data. It went through that process, and now I'm stuck in a boot loop.
The phone will boot to the encryption PIN screen. I will enter my PIN, which works now, but the phone reboots and loads TWRP. TWRP will automatically run OpenRecoveryScript (there are lots of invalid and mount errors). After the script, the phone will automatically reboot into the encryption PIN screen again. Entering the correct PIN leads to the TWRP again running the script, rinse-and-repeat.
How can I restore my phone back to working order? I don't really care about keeping my user data anymore; I assume it's lost. I am able to boot into TWRP and into download mode.
I tried to use ODIN to flash the recovery.img and boot.img (each contained in its own .tar), but I got write/mount errors in ODIN. I assume the encryption is preventing access or mounting of /data or much of the files and I'm looking to get rid of encryption to restore the phone to stock (in order to start over). I'm a relative newbie to solving this issue and would appreciate any help!
Solved the problem. I had to use TWRP to flash stock recovery and that did the trick to stop the boot looping.
Hi everybody,
I'm here to ask for help cause i have a problem with my honor 6X.
I was looking to implement carstream on it in order to have access to my youtube playlists. So i did the following :
- Find the Bootloader code for unlocking
- I unlocked the bootloader with the appropriate commands. After that i got the message that the phone was unlocked on boot
- After that i flashed TWRP in order to have a recovery custom. It worked well and i was having the TWRP menu when booting the phone with the volume up and power button
- Next, i tried to root the phone by adding magisk. Flash on TWRP did well but after the first boot i was asked by a message to insert the password to unlock phone crypting. I wasn't having this password so i tried to flash magisk again. After two flash the phone was booting correctly and i set it up. I installed Root checker and the phone was correctly rooted. The only problem was that i couldn't access to some parameters options like developer mode or unknown sources. The parameter app was closing when trying to access this options.
- As the problem looked to be from the OS i tried to implement a custom one (Pixel Experience) using the TWRP recovery i added before. After that everything started to go wrong. When i was in flash menu of TWRP i didn't know which partition to use in order to flash the system.img file. I choose the system partition to do it and operation was done. I boot the phone and after that but it stayed frozen on the boot image (honor on blue background).
- After a whole night waiting for the phone to boot i tried to boot on the TWRP recovery in order to add a new custom rom but i couldn't do it. Th e only recovery i have access is EMUI recovery. I tried to do a backup on the EMUI recovery but the phone still don't want to boot.
As th e situation looks critical i ask you for some help in order to avoid to make it worst. I currently have access to the recovery EMUI and i'm pretty sure to fastboot too even if i didn't try. First step know is to try to make the phone working again and maybe with some help try to implement carstream again.
Thank you for your help
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.