Database Develop

[Q] How to wipe Data partition after it's been encrypted?

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.

HTC One Formatted phone and now cant mount data with twrp

I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/

xXxG0dzRAgexXx said:
I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/
Click to expand...
Click to collapse
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.

Seanie280672 said:
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.
Click to expand...
Click to collapse
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.

xXxG0dzRAgexXx said:
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.
Click to expand...
Click to collapse
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader

Seanie280672 said:
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ended up reflashing twrp with fastboot and then flashed Android revolution HD71.1 on it. The format of data in CWM worked to fix the mounting problem I had. Twrp probably could have fixed it too if I tried wiping data again. Will remember that next time for the other HTC One I'll be doing this to in the next few days.

[Q] encryption unsuccessful?

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

Can't mount /system in twrp 2.8.3.0

I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!

modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.

They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents

Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.

alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.

Unable to update CM13

Hello guys, i was trying to update my CM 13 today and it didn't work. It made the download but once in the recovery, nothing happened :S i'm trying to understand why and i hope some of you know of this.
By the way, my TWRP version is the 2.8.7.0 if it helps..

ugh...Can't really understand what happened
You installed via OTA/cm updater? meaning you downloaded with your phone
Just download the zip directly and flash it with twrp
You'll also need to re-flash gapps unless you're using TWRP 3.0.0

Make sure that you have not installed any additional mods which alters system partition (kernels, soundmods etc.) If not, easiest solution would be to dirtyflash new one or clean install.

Same problem here.
405. CM13. TWRP 3.0.0. Merged SD card with internal storage.
In Recovery I can see folder structure but no files. I know its because of SD-encryption but I hoped I could at least see files in internal storage to update. Hope there's a solution soon. Does anyone have a workaround?
Gesendet von meinem LG-D405 mit Tapatalk

Filesystem of sdcard mount point
What is your /sdcard mount point filesystem? Mine is 'auto' (Maybe that might be causing the problem?) , and you can check by going into TWRP -> Wipe -> sdcard -> Repair or Change File System

Thank you for your answer. I checked that quickly, but couldn't find the option 'repair or change filesystem' without actually wiping the storage... I'll check again later if there's more time.

I found and changed the option from exFAT to ext4. All folders on the SD were lost in TWRP. Changed back to exFAT: couldn't see them either..

When using adopted storage (i.e. formatting external SD and using it as internal storage), then /sdcard in Android becomes /emmc in TWRP. At least it's what I see here using TWRP 3.0.0 Dark Blue.
From what I've looked, all internal storage is used only for app and app data once I started using adopted storage, so the only way I can think of using internal storage in TWRP to flash anything is either sideloading or using MTP in TWRP.

I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now

kreativpause said:
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
Click to expand...
Click to collapse
What did you wipe prior to your sideload? I want to do a wipe and fresh install of gapps and cm13, but I am afraid I could soft brick my phone.

I chose both. Dalvik and the other option ( I believe cache). No issues.

kreativpause said:
I chose both. Dalvik and the other option ( I believe cache). No issues.
Click to expand...
Click to collapse
Mine gets stuck at "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" then it just reboots to TWRP again. Sideload says "
serving: 'cm-13.0-20160322-NIGHTLY-w7.zip' (~0%) * failed to read command: No error". Did you wipe system before you sideloaded?

I did not wipe anything beforehand.