I noticed a couple of weeks ago after updating to OOS 4.5.1 that the phone no longer asked for my decryption password at boot time. It just boots through to the system and asks for the the password at first boot, making it appear that storage is no longer encrypted. The bigger problem, though, is that TWRP doesn't ask for a password anymore either - it just goes straight to the TWRP splash screen and never goes farther. I'm running version 3.1.1-0 of TWRP - not the BlueSpark version, but it has worked up to now, and newer versions caused me no end of problems in the past that corrupted my partitions and forced me to reflash the entire phone.
Should I reflash TWRP - this version or a newer one? I've seen the BlueSpark one recommended, but I don't want to kill the phone by causing encryption problems. I've had this phone almost a year and have had problems with the encryption scheme at virtually every OS upgrade I've done. I'm tired of doing full wipes and going back to Marshmallow. Advice?
**UPDATE** After reading some other posts, I realized I might just not be waiting long enough for TWRP to boot, so I gave it time. After about 10 minutes, I got the TWRP menu and had full access to all my files. This is good news and bad news - since I never provided a decryption password, my disk is apparently unencrypted, although I don't know when that would have happened. So I can do a nandroid backup and proceed with the Oreo update, but I still have the issue of how to restore encryption. Again, advice?
I had another problem - TWRP didn't accept my password, but I could boot to OS with the same pass. Unfortunately full data wipe was needed.
PS Marshmallow is kind of deprecated nowadays
I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.
mobilityguy said:
I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.
Click to expand...
Click to collapse
Did you tried removing password protection from rom ...
Related
Hello,
Thought I would share my recent bad experience and the resulting solution.
My phone was on a GPE ROM, and I encrypted it for work reasons, encryption went smoothly, but once encrypted, it was impossible to go into recovery with the encrypted partitions visible (hence impossible to flash a new rom or even do a factory reset which is the only - or so I thought - way to remove encryption).
After many attempts including flashing the latest TWRP (not solved yet, they say 2.7 should include a solution) I was still getting the "unable to decrypt phone" error after entering the password (which works perfectly on regular boot) in TWRP.
Eventually, through a lucky mistake, I found the solution, at one point I mistakenly re-locked my phone (fastboot oem lock), later when I was trying to flash a stock recovery I realized I had to unlock it again... well, unlocking it through HTCdev automatically does a factory reset, regardless of the encryption!
viola, problem solved!
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
Hi, I updated my rooted OnePlus 3t with an OTA update (dumb, I know, I wasn't thinking). It failed and the device needed to be wiped. I've since tried to go through the process to reinstall twrp and supersu and I can no longer get it to boot when TWRP and superSU are installed. The weird thing is, I AM able to use it with the stock recovery and non-root, but any subsequent flashes fail, despite it appearing as if everything has been installed properly.
One last wrench to throw into this: I cannot access recovery (whether TWRP or stock) without running
Code:
fastboot boot recovery.img
. When I run that, I'm able to get into recovery, however if I go through the phone itself on the main menu after unlocking the phone, it just reboots and brings me right back to where I was.
Any ideas on what I may have done wrong and how to fix it? I've been following the guide from the oneplus forums, I've run that process about 5 or 6 times over the past day to no avail.
P.S. Have flashed the newest version of dm-verity
After unlockling bootloader and rooting my spare (Blue) X4 XT1900-1 with Magisk (patched boot.img), I attempted to restore /data via TWRP (3.3.1-0 payton) from a backup taken from my other daily driver X4 (Black). Both phones are identical Android One versions on the same build PPWS29.69-39-6-2 Nov. 1 patch. This initially failed with extractTarFork() process ended with ERROR: 255. I am booting TWRP via fastboot, as I am trying to keep the phones as close to stock as possible while having root.
Apparently some of the data.ext4.win00x files in the may have been corrupt or incomplete—I had copied them from the black X4 to my PC via wifi.
I re-copied the Black X4 backup to the Blue X4 folder on SD via PC and did another restore, wiping data & cache. It completed successfully according to TWRP. This time the phone initially went into a bootloop. I tried restoring a TWRP backup taken from Blue X4 just prior to flashing /data, that resulted in the phone hanging on the Android One splash screen but not bootlooping per se. I can get the phone into fastboot, recovery and boot TWRP via fastboot. I’ve tried various wipe and restore protocols, factory reset, flashing the stock unpatched boot.emmc.win, All yield the same Android One hang. Finally tried switching from slot A to slot B (the phone recently had several updates), that gave Error changing bootloader boot slot to B. However, hitting the Back button then shows Current Slot: B. Rebooting, still hangs on Android One. Back in TWRP, changing back to slot A in TWRP gives same error message: Error changing bootloader boot slot to A.
I saw a thread of similar issues with TWRP 3.2.3-1 from 2018, but no definitive fix short of factory flash and no working way to restore only /data.
https://forum.xda-developers.com/moto-x4/help/bootloop-restore-twrp-3-2-3-1-payton-img-t3853419
No mention of TWRP 3.3.1-0 having same issues.
Wondering if the bootloader is somehow borked? Any suggestions on a fix would be great. If I could find a recent X4 factory Pie firmware to flash would that get it working again?
One thing I am unclear on is which, if any, partitions should be mounted/unmounted while TWRP restoring. I’ve done the /data partition migration before on identical devices running MM and below with no issues. This is my first soft brick in 30 or more device unlockings, rootings and ROM flashings the past 7 years. Very humbling.
TWRP log from one of the attempts attached.
Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.
Factory FW flash solved boot hang
KrisM22 said:
Other than Pie on the X4 having 2 sets of partitions and you maybe restoring it to the wrong one, no idea.
Click to expand...
Click to collapse
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.
redwoodie said:
I checked that carefully before restoring, chose the active slot.
Tonight I flashed the latest factory FW and all is good, phone updating now.
The TWRP restore problem is worrisome (what good is a backup you can't restore?) Anyone else out there had bootloops after restoring a TWRP backup on the X4? I've seen posts about similar problems from 2017-2018 on several devices, but I would hope that whatever the problem was has been sorted out.
Click to expand...
Click to collapse
Glad you got it back! Dunno about TWRP - maybe a pre or early Treble problem? Scary!
EDIT: I wonder if maybe stuff like that won't really be sorted for a couple more releases when most folks will be on a full Treble.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.