Unable To Update After Encrypting (flo) - Nexus 7 (2013) Q&A

EDIT--Resolved via Sideload Method--
Has anyone run into issues upgrading encrypted devices? I've been using CM for a few years and decided to encrypt my tablet yesterday. Now when I attempt to update CM I am unable: when it reboots into Recovery it asks for the password to decrypt, I put it in but it fails to decrypt saying Password Failed.. When I reboot the tablet normally, I get into it fine with the same password (as usual). So I'm stuck on 0813 with no way to update unless I wipe the tablet and start over, which I hate to do, although I do have Titanium backups of everything and the tablet is nightly backed up via rsync to my desktop - so I won't lose data, it would just be a hassle..

Resolved via Sideload

Related

[Q] unable to mount system

I was running the latest CleanRom on my nexus 7 tablet and it randomly rebooted and stopped working. The tablet now doesn't want to boot into the OS. When i boot into TWRP recovery mode i need to wait at least 20 minutes before the TEAMWIN splash screen goes away and finally boots into the TWRP recovery interface. I'm trying to reflash a rom but it fails everytime, in doing so i'm prompted with a log message that says "/system, /cache" was unable to mount.
My biggest concern right now is getting all my user data such as music, document, books, movies off of my tablet so i can restore the tablet to factory defualt. Is there a way to recover such files? (~26GB of Data)
This is what i have tried with no luck:
TWRP backup of user data to OTG USB
adb install of factory image. (-w removed from bat file)
Nexus root toolkit 1.7.9 backup of virtual SD. (says successful but backup size is 0MB)

Cannot undo encryption on KitKat based rom

Ok, so I was on stock 4.3 rooted.
Installed resurrection rom, booted fine, google restored all my apps. everything was great. then I tried to install air watch mdm agent to get my work emails. it started the encruption process. I gave the password 1234 when it said "enter a password to decrypt device. encryption finished but Air watch mdm reported incompliant device so I could not get the work email setup. Now I tried to decrypt the device by doing factory reset from settings menu, it asks for my password, proceeds to reboot the phone, then it boots into team win recover and asks for my decrypt password but will not accept it. I cancel out, reboot using team win recovery reboot option and phone boots and asks for decrypt password, 1234, it takes it boots up but still says device is encrypted.
Since I can't get air watch mdm to work, I must go back to my stock using nandroid backup restore.
Do I need samsung recovery to decrypt? TWRP will not accept the password.
TWRP is 2.6.3.1
Baseband 1747UCUEMJB
How do I decrypt this phone now? please help.
Thanks in advance

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Password - TWRP & Start Android?

I recently used sideload (TWRP) to install a custom ROM (RR (LOS)) on my OnePlus 3
I did not set up a PIN / fingerprint
Rebooted into recovery since install in order to perform TWRP backup
Rebooted into recovery today to flash something different and TWRP is asking me for a password (have no idea what changed)
Since I do not know password, I tried to mount system and it apparently will not mount
Rebooted Android and now asking for password
The bootloader appears to be unlocked (checked in fastboot to be sure)
Wiped Data in Fastboot and have a phone again. So, let's change the question...why or how did this happen?
Was it because I sideloaded the ROM (never did it before and wanted to try it lol)? Or...?

Upgraded to Android 10, unable to decrypt in TWRP.

I upgraded a couple months ago from 8.1 to 10. I ended up doing a full wipe ( or so I thought) through TWRP and flashing the 10 image. However, it seems that I somehow screwed up the encryption on my phone. I can boot the phone and put in my PIN to access and use the phone normally, but inputting the same 6 digit and my old pre-10 4 digit PIN into TWRP does not decrypt the phone and allow me to flash things. If I continue in read only mode in TWRP, I can flash but everything in my data partition has jumbled file names.
So my question is: Am I going to need to back everything up and wipe in order to fix this? Can I simply use Magisk to disable Force Encryption then decryp that way while keeping my data intact?
I would prefer using the simplest least painful way possible, but if I have to wipe to fix it then so be it.
Twrp decoding doesn't work for Q .. best to remove lock before entering TWRP
Also try "default_password".
Well I got impatient and ended up screwing up everthing.
Now I'm having trouble getting TWRP installed back on the phone. I have wiped everything, flashed the latest January factory image, booted to TWRP image, but when I attempt to flash the TWRP zip I get "failed to mount /system" and "failed to mount /vendor". If I boot back into the installed TWRP, I am not able to flash any other zips such as Magisk.
Sunsparc said:
Well I got impatient and ended up screwing up everthing.
Now I'm having trouble getting TWRP installed back on the phone. I have wiped everything, flashed the latest January factory image, booted to TWRP image, but when I attempt to flash the TWRP zip I get "failed to mount /system" and "failed to mount /vendor". If I boot back into the installed TWRP, I am not able to flash any other zips such as Magisk.
Click to expand...
Click to collapse
Disable your screen lock. Download twrp again to your pc. Put a copy of the twrp.img file on your phone as well. Fastboot into twrp, select instal, select image, go to your twrp.img,.select to install it to Recovery Ramdisk. You'll have to flash custom kernel and magisk again if applicable :good:

Categories

Resources