Database Develop

CWM Failed to format system & cache - can't do anything now

I'm on a rooted m7spr, was running cm11 official, S-ON. I was prepping to try out the cm12 build so I went to CWM 6.0.4.8, made a backup, adb pulled it, and proceeded to format /system. It spent about 30 minutes before I decided to reset and try again. It never completes and now I am unable to restore my backup or boot (trying to restore the backup hangs)
Ideally I would adb and use fdisk to check the disks and formats and mkfs.whatever /dev/sdWhatever to manually format system and cache (the 2 partitions that I have tried and failed to format) but fdisk -l shows nothing and mkfs doesn't exist. I have no idea how to proceed. I'm lucky my laptop is authed to adb shell so hopefully I will be able to recover from this.
Any ideas? Any help is greatly appreciated!
Additions: I also tried fastboot erase and fastboot format - erase says "FAILED (remote: not allowed)" and format says "FAILED (remote: unknown command)".
I noticed there's a "factory reset" option in the bootloader. Is this something I should try or could it make things worse?
EDIT: I think I got it - Apparently CWM sucks, which sucks because CWM looks so much better to me than TWRP, but I guess it had to be done. Flashed TWRP with fastboot and it seemed to format fine.

unable to encrypt phone

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..

Can access fastboot and Recovery, but cannot flash anything

Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René

Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.

Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René

XT1068 flashing problem

So I have a moto g xt1068 (dual sim), apps started crashing all of a sudden. Including google play store and the rest of the apps. So I:
Tried to factory reset through settings, that didn't work (pushing the 'erase everything' does nothing)
So I unlocked the bootloader and tried to flash a custom recovery, it flashes successfully but gives something like a 'mismatch' error, then I boot to recovery, but its still stock recovery. So I copied a lollipop ota to external card to apply through stock recovery, that didn't work either as the stock recovery refused to show my external SD card.
Then I downloaded the stock lollipop rom to flash with mfastboot, every command line says okay, but when I reboot the device, its still on KitKat.
I then tried to upgrade the bootloader from 0x4807 to the latest bootloader, so I can flash a custom by live booting twrp, flash latest bootloader with fastboot commands, everything says okay,but still on radio, which means I can't flash custom ROM.
So I live booted twrp,then tried to copy ota.zip to internal SD, but it won't copy, I try to format all partitions through twrp, they all format ok, but reboot device back to crashing KitKat, live boot twrp again, copied ota.zip to external SD card first, then use twrp file manager to copy ota.zip to internal SD card, that also brings out another error. Tried to restore the device with twrp backup of stock 5.0.2, boot.IMG flashes fine, but when installing system, it cuts midway with a 'fork' error or something. So I can say that both system and data partition is corrupt. I am currently outta options. I know this device isn't in a hard brick situation. Help anybody

[HELP] I've messed up somewhere, need experienced users

I haven't formatted my phone in a while, so rather than delete files while my phone was working. I booted into recovery and selected the format data option in TWRP. Now I am getting all kinds of errors in TWRP. I was on a custom rom when I did all of this and somehow I screwed up. I can't even get a zip on my phone as my phone is only recognized as charging and not a storage device under these circumstances. I have tried adb sideloading a rom, but that is to no avail. I am thinking about flash a stock recovery in hopes that I'll be able to flash a stock rom and fix my phone.
this is what it says when trying to wipe anything:
could not mount /data and unable to find crypto footer.
failed to mount '/data (invalid argument)
without typing out everything the rest of it says failed to mount '/data' (invalid argument)

Boot the phone into fastboot, type fastboot format userdata
fastboot format cache
then fastboot flash recovery <name of twrp recovery>.img (don't put < >)
boot into recovery and go to advanced wipe and wipe everything except internal
everything will be fine now
you can flash any rom now.
If it worked, hit the thanks button

Try unbrick tutorial from XDA to back to new alike!
This is the best option

Well actually I took a different route altogether. I don't know why I didn't think about it initially. You would think after almost 10 years of dealing with custom ROMs and recoveries that I would of been a lot quicker in finding a solution, so I googled it. Came to the conclusion that I needed a stock OP3T recovery, so I downloaded it and fastboot flashed the stock recovery. From recovery I was able to wipe data, cache, dalvik-cache. All was good after that. Now I'm running coltOS.
Sent from my ONEPLUS A3000 using Tapatalk

Glad you fixed it. If you face a similar issue in the future you can download MSMTool for the OnePlus 3T which will restore stock OOS through fastboot