Related
Hey guys,
My work switched to Google Apps for their email so i wanted to test it out on my phone. Doing so required them to encrypt my phone. What this appears to have done is encrypt the data partition. So now when i go into (TWRP) recovery and try to do a backup / wipe / or anything else, it says it is "Unable to mount /sdcard" I'm unable to do a factory reset of any kind so i'm essentially stuck on this rom (ARHD) until i can figure out how to wipe data and get the /sdcard to be not encrypted. Does anyone have any ideas? I'm imagining that with the modified recovery not being able to access the data partition that i'm going to have to do some adb type stuff?
Please help! I want to keep flashing new roms!
Anyone??
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Guich said:
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Click to expand...
Click to collapse
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
jrun said:
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
Click to expand...
Click to collapse
Hi! Only TWRP recovery can solve your issue just do this...
Boot to TWRP recovery->Wipe
From there there are 2 options the left is the advance wipe and on the right is Format Data
Just select the format data button and it should reformat the whole data partition.
1st one would prompt so many errors and reformat then reformat it again 1 time and it should fully reformat your phone.
In theory it should reformat data partition even when encrypted but just in case it fails and I won't be able to go back to this thread just boot in bootloader and type
"fastboot erase userdata"
Well none of that works. TWRP doesn't support decryption yet for this device.
sevenalive said:
Well none of that works. TWRP doesn't support decryption yet for this device.
Click to expand...
Click to collapse
What I instructed basically doesn't decrypt the partition. It reformats it.
Riyal said:
What I instructed basically doesn't decrypt the partition. It reformats it.
Click to expand...
Click to collapse
I know what you instructed, it doesn't work. Only way I got it to work. Flash the stock recovery. Boot into system. Take off the encryption, phone reboots and removes the encryption, data is formatted. Then flash TWRP again.
I basically ran into this exact problem. I was hoping that I'd still be able to back up the encrypted device, but forget about it. What a pain in the ass.
Someone should make add something to the guides about how encrypting your device makes nandroid backups impossible.
So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?
Same problem...
Format data in twrp to fix encryption error
CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?
marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.
Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data
CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage
CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.
edit: wrong thread
Phone: xt1060, verizon, Moto X Dev edition (2013)
ROM: Cm 12.1 (however, I was unable to encrypt with my last ROM as well)
My data directory is formatted with f2fs. When I attempt to encrypt the phone, it reboots without error and without any encryption action. I've used logcat to capture these messages:
I/Cryptfs ( 242): Check if PFE is activated on Boot
E/Cryptfs ( 242): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 242): Error getting crypt footer and key
E/Cryptfs ( 242): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 242): Not a valid ext4 superblock
E/Cryptfs ( 242): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Click to expand...
Click to collapse
Because of the "Not a valid ext4 superblock" error, I tried changing the file system to ext4. When I boot after changing the data partition to ext4, the phone enters a boot loop. It boots up to an error that says "encryption unsuccessful" and the only choice is to reset the phone. I reset the phone and it boots back to the same error. I've formatted cache, system, data and sdcard, reinstalled both ROM and recovery and still I boot back up into this error message even though I am not presently trying to encrypt.
I read about a problem which requires the data partition to be reduced in size by at least 16KB, so I reduced it by about 4MB. The data partition was 27606912 blocks, and I reduced the partition to 27606000 blocks. However, this had no affect.
I have changed the partition back to f2fs because at least the phone boots using this file system without entering the "encryption unsuccessful" loop.
I have tried multiple recoveries in case that was the problem. I've tried CWM, the recovery for CM 12.1, and the most recent TWRP. I get the same problem in each of these.
I am most baffled about the boot loop after formatting the partitions in ext4 then installing a fresh ROM. Apparently my attempt to encrypt is remembered somewhere other than system, data, cache, or sdcard?
I considered flashing back to factory, however, I do not have the files, the links I've found on xda are broken, and I am waiting on Motorola to provide me access to the stock firmware - I requested it tonight though.
I appreciate any assistance that can be offered. Thank you.
I found the factory firmware and I attempted following the directions for a factory restore:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase userdata
$ fastboot erase cache
$ fastboot reboot
Click to expand...
Click to collapse
However, the system.img failed. So, I reflashed recovery to TWRP and found that I did not have a system, data, cache or sdcard partition. I reflashed recovery to CWM because it has a custom format option and I formatted data, cache, system and sdcard using ext4, then I reflashed recovery to TWRP and because I am able to transfer files using TWRP. I transferred the CM 12.1 and gapps images, flashed them both, then rebooted.
After all of that, I still booted up into an "encryption failed" screen!
I then went back into TWRP, changed the data partition to f2fs, then I was able to boot into the new CM 12.1. So, the exact same problem exists: using f2fs, I am unable to encrypt the phone. Using ext4, I am stuck in an "encryption failed" loop.
I'm giving this thread a bump in hopes someone can share a solution with me as I am still having the same problem.
I'm on Verizon Developer Edition, but I had a similar problem after the Lolipop update. I just got it working. I had to flash the moto recovery back and format data and cache through there. Then I could encrypt. I'm gonna try to restore a backup from TWRP onto my encrypted data partition now.
I used the recovery from 47-vzw_xt1060_444-kxa2112-l126_cfc_1ff (google the file I can't post links). I'm not sure if its totally perfect with lolipop, but it formatted my data to work with encryption (ext4).
Same issue here on Moto X (ghost) with cm-12.1-20151007-SNAPSHOT-YOG4PAO332 and cm-12.1-20151105-NIGHTLY.
I could get rid of the message
E/Cryptfs ( 242): Orig filesystem overlaps crypto footer region. Cannot encrypt in place
Click to expand...
Click to collapse
by applying the update from this thread, but the other error messages still remain and I cannot encrypt my device..
I'll make this one quick, so I know the userdata.img that comes with stock images is just a blank image that's sole purpose is to format your userdata partition for you, and that you can use fastboot format userdata for the same result, however is it the same deal with the cache.img file? Is the cache file just a blank image used for formatting the cache partition of your device or does it actually contain some data that the device needs to function? Thanks!
I have yet to flash either and have had no problems. I wipe both through twrp before booting up for the first time.
There is nothing of importance in either.
danarama said:
There is nothing of importance in either.
Click to expand...
Click to collapse
So in this sense, formating or erasing the cache is the same effect as flashing the cache.img?
H4X0R46 said:
So in this sense, formating or erasing the cache is the same effect as flashing the cache.img?
Click to expand...
Click to collapse
Yes and no.. Sort of.
The image itself, I don't really know why it exists. When you fastboot flash those images, it does a format first. Actually flashing the image afterwards has no benefit.
They could just put the format commands in the flash-all script. Perhaps they've done it for those who don't use the script to encourage them to format by flashing the image. Only thing I can think of. Or maybe those images are big enough that they wrote 0 byte data over existing data blocks that exist after the format to make them more secure, because really, a format or erase doesn't destroy data. It just makes it inaccessible by the average user. So it could be that they're overwriting a small section of data in the partition as that is the only way to destroy data.
Anyway, it should be rare that you need to format those partitions..
Formatting just erase allocation table, flash an empty.img overwrite and really cleans the data.. I think..
_____________________________________Read more write less and be smart
danarama said:
Yes and no.. Sort of.
The image itself, I don't really know why it exists. When you fastboot flash those images, it does a format first. Actually flashing the image afterwards has no benefit.
They could just put the format commands in the flash-all script. Perhaps they've done it for those who don't use the script to encourage them to format by flashing the image. Only thing I can think of. Or maybe those images are big enough that they wrote 0 byte data over existing data blocks that exist after the format to make them more secure, because really, a format or erase doesn't destroy data. It just makes it inaccessible by the average user. So it could be that they're overwriting a small section of data in the partition as that is the only way to destroy data.
Anyway, it should be rare that you need to format those partitions..
Click to expand...
Click to collapse
Yea it really is kind of confusing that they add these blank images, would it be a safer bet in this case to use the erase command as opposed to format? Or is it a better idea to just flash these blank images? They really made it confusing by adding them. I also have a 64GB nexus 6, so after flashing the userdata.img, it shows I only have 32GB! It requires a factory reset that, as you know, takes AGES on this device! In short, should the format command be used in more rare circumstances as opposed to erase or using the img file?
Use format to fix your issue. The images are known to cAuse this.
Long story short... My USB port is dead on my Nexus 6. I flash everything in TWRP such as roms, kernels and modems (YAY for the ability to do so). I am wanting to wipe everything in my phone to start fresh. Let's say I did a factory reset to the phone (wiped everything except userdata), got my rom to boot and then went into recovery to wipe my userdata partition only, would my phone go ahead and rebuild the partition on successful boot?
Thank you in advance!
thawte said:
...Let's say I did a factory reset to the phone (wiped everything except userdata), got my rom to boot and then went into recovery to wipe my userdata....
Click to expand...
Click to collapse
Wiping a partition in twrp will show a.o. the message 'formatting...'. The partition is already build but empty.
NLBeev said:
Wiping a partition in twrp will show a.o. the message 'formatting...'. The partition is already build but empty.
Click to expand...
Click to collapse
Ah gotcha. Also the rom will still boot with empty USERDATA? Just making sure it does not have important files for boot...
thawte said:
Ah gotcha. Also the rom will still boot with empty USERDATA? Just making sure it does not have important files for boot...
Click to expand...
Click to collapse
Wiping data in recovery shouldn't affect the system or booting.
But, personally, I'd take a full nandroid backup before anything. If you can't plug in to a pc and use fastboot to fix anything serious, you should be playing it very safe. :good:
Darth said:
Wiping data in recovery shouldn't affect the system or booting.
But, personally, I'd take a full nandroid backup before anything. If you can't plug in to a pc and use fastboot to fix anything serious, you should be playing it very safe. :good:
Click to expand...
Click to collapse
Doesn't the nandroid backup store to userdata?
Sent from my Nexus 6 using Tapatalk
thawte said:
Doesn't the nandroid backup store to userdata?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Data in recovery and userdata aren't the same. There's no "userdata" in twrp. (unless the newest twrp has changed?)
Userdata is apps, data and internal SD storage. You use fastboot typically to erase userdata.
You use twrp to erase data, and internal storage, separately.
Edit: and yes, it does store to userdata. But you can't erase userdata without a PC. Just erase data in twrp, and leave internal storage alone.
Or wipe it all, but without access to a PC, you could not fix the phone if anything goes wrong. That's why I'd keep a full nandroid backup on the device.