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.
Related
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
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.
I have a rooted HTC U11+, I did not make a nandroid backup for what it's worth (yes im regretting it). (Build 1.24.403.12)
Anyways I ended up getting my phone to boot up flawlessly on a different build RUU (1.24.401.3)
Anyways, everything is great and all, but once I reboot in recovery for any reason, I lose access to my normal UI. It asks me for the password, I enter the one I set during the initial device setup and it works. But once im done and reboot for a normal startup, I'm locked out, it asks for decryption password and the one that I set doesn't work here (Have wiped my phone over 15 times trying to get this right, but it's a dead end)
This only happens When I reboot back into recovery after a normal startup
It seems like I can only flash the supersu file through recovery once, and never boot back in recovery to avoid being locked out. But that sort of kills most of the perks of rooting
Anybody help please.
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?
I've just got my Realme 5i returned after repair (replacement main board) and I've unlocked the bootloader, flashed TWRP and vbmeta9, flashed Magisk and enabled MagiskHide but I can't set a PIN. Whenever I try, after confirming the PIN it returns to the settings screen and shows "Lock Screen Password - Off".
I know I managed to set a PIN before it needed repairing, as when my brother received it from me from his Birthday, he phoned me to ask for the PIN to access it but I can't remember what I did then to get it working.
I tried to install "Realme 5i Magisk Fix for ColorOS by IT&AUTOS.zip" in Magisk as I did that before but now it isn't working and the log says "copying to temp, error unzipping file". Would installing this be what got the screen lock working before?
I've got a TWRP backup of all the partitions from before it was repaired but I can't seem to access them to restore, as when I select the Storage option from Restore it shows the SD card is only 6GB, when it fact it's 128GB and the only file it shows is "257eee4a" which is actually the folder above the dated folders containing the backups.. From the Install option, I can browse the SD card normally and I flashed Magisk from a folder on the card, so I don't know why it's not accessible from the Restore option. If I could, then maybe restoring the System and Data partitions would get me back to the state where the PIN was set but I'd be a bit nervous about restoring the System partition after then main board has been replaced, in case any files are tied to the old hardware.
I thought what I might have done to get it working last time is to relock the bootloader (after flashing the stock recovery to prevent bootloop) and then unlock it again but if that is what I did before, it isn't working now.
First I updated to A.20 via the stock recovery, as the service center had flashed A.15. It kept booting to stock recovery after that until I did Format Data and then it booted OK and after locking the bootloader I was able to set a PIN.
Then I unlocked the bootloader and it automatically wiped data but I still had to Format Data to stop it booting into stock recovery and now I can't set the PIN again.
I see there's a 5i Decryption (COs).zip. What does this do? I tried flashing that via TWRP before I tried the above steps but it didn't get the PIN working.
I just flashed TWRP and then installed 5i Decryption (COs).zip and wiped Cache/Dalvik Cache and now it gets stuck on the yellow realme logo when I try and boot. Can't even power it off when it's like that but thankfully volume up and power gets me to bootloader and TWRP and doing a factory reset wipe got it booting again.
I still can't turn on the PIN/Lock Screen password though.
I tried restoring my TWRP System and Data backup from last August when the Lock Screen password was working but it still doesn't work, so it must be something in one of the other partitions that affects this and I'm reluctant to try restoring those in case it bricks the phone because the main board has been changed.
Can anyone help me please? Does anyone have the lock screen password working with unlocked bootloader, or is everyone who has installed custom recovery/rooted their 5i just using it without any password to protect it?