The first issue I noticed after updating was that it asked for my email and password about 3 or 4 times without giving an error while signing in. After that I noticed that my storage partition says 32gb instead of 64. I've tried doing a factory reset a few times. I've flashed the stock images over and over. I keep getting the same results.
Is anybody else experiencing the same thing?
I have on the nexus 5. Was a problem with userdata.IMG the fix was to clear userdata and factory data reset phone. Some reported simply factory data reset didn't work for them. But by using fastboot to format userdata and cache then factory data reset phone in recovery it worked
As was already mentioned, the "lost" 32GB is due to flashing the userdata image. You should never flash that image.
The way to fix the issue is to reboot into the bootloader and execute:
fastboot format userdata
fastboot format cache
fastboot reboot
Related
I recently did a factory reset and realized it didn't wiped my phone. It deletes the account but files and pictures are still in tact. For anyone returning the device or passing it on to someone please make sure you manually delete everything.
Did your phone have a custom recovery ?
Sent from my Nexus 4 using xda premium
fastboot oem unlock
fastboot oem lock
Job done, all wiped
Sent from my Nexus 4 using Tapatalk 2
Factory reset is just for the data partition (apps, preferences for these apps, accounts, etc.).
It's normal that it doesn't touch your sdcard.
If you want to wipe your personal files, do it manually, or, as suggested, with "fastboot oem unlock" and "fastboot oem lock".
You could also wipe the sdcard in the "mounts and storage" menu in CWM.
wipe it from a shell with dd or rm
if you're unlocked already, boot into a custom recovery which will give you the option
the factory reset feature from within the OS used to also have checkbox asking if you wanted to wipe the pictures too. maybe you missed it or I'm not remembering correctly
If you reset it through Android's Backup & reset -> Factory data reset, it does delete photos and everything on internal storage. I've done it twice for my RMA's.
Resetting through the fastboot menu doesn't erase internal storage/photos.
You need to rick a box to also wipe the sdcard, it's pretty easy to miss.
tsunzilla said:
If you reset it through Android's Backup & reset -> Factory data reset, it does delete photos and everything on internal storage. I've done it twice for my RMA's.
Resetting through the fastboot menu doesn't erase internal storage/photos.
Click to expand...
Click to collapse
Nexus-Revolution said:
You need to rick a box to also wipe the sdcard, it's pretty easy to miss.
Click to expand...
Click to collapse
So which one of you two is right?
Both... Same but different.
Although, the fast boot comment may be misunderstood. The fastboot OEM lock/unlock does work from a PC with adb interface.
Sent from my Nexus 4 using xda app-developers app
tsunzilla said:
If you reset it through Android's Backup & reset -> Factory data reset, it does delete photos and everything on internal storage. I've done it twice for my RMA's.
Click to expand...
Click to collapse
Yep, I checked before sending in my RMA, as well.
How do I format my fastboot cache partition? Every other time I need to enter recovery, it can't, and I need to connect my phone to a computer and 'fastboot erase cache'. I believe if I could format the partition, it could fix the problem.
bloodrain954 said:
How do I format my fastboot cache partition? Every other time I need to enter recovery, it can't, and I need to connect my phone to a computer and 'fastboot erase cache'. I believe if I could format the partition, it could fix the problem.
Click to expand...
Click to collapse
You need a Folder with fastboot.exe, AdbWinApi.dll, and AdbWinUsbApi.dll
Then you open a cmd window, and navigate to the Folder. Then you type fastboot erase Cache.
I also had the Problem, that i couldn't enter recovery. It said entering recovery, and then simply rebooted. What helped me was simply re-flashing the recovery. I hope that helps you.
That's the problem, it happens ALL the time. I need to FORMAT, not ERASE my cache. I believe the formatting is screwed.
BUMP
I turned on device encryption in order to play with it (bad mistake). Performance is suckish, it prevents me from flashing anything stored on the internal filesystem (have to use USB dongle), battery life has gone down, etc.
I tried wiping the device by doing a factory reset both in recovery and through settings. Neither method touches the encrypted data partition. Re-flashing the ROM makes no difference. The encrypted partition is extremely resilient
Based on some research, the only known way to wipe the encryption is to revert to stock and use stock recovery to do a factory reset. This sounds insanely cumbersome if all I want to do is wipe a partition. Does anyone know of a better way?
If stock recovery can do a factory wipe without mounting the encrypted partition, it sounds like a feature to add to CWM or TWRP.
Device is ATT HTC One, rooted, S-OFF, Super CID, CWM recovery, Sentinel ROM 4.0.
Many thanks
You can try and flash an ruu? See if that helps and if it doesnt try the stock recovery thing. Never heard of it though.
Sent from my HTC One X using xda app-developers app
So, the wipe of TWRP didn't removed the encryption like it say this when you will wipe?
Strange
However, flash the stock recovery and do a factory reset like you said, and see if it work..
you can do it via TWRP just make sure the rm -rf mode is disabled in settings... Or maybe in fastboot... Just type
Code:
fastboot erase userdata
Or another perhaps is ask someone to create a nand dump of their user data partition and use "dd" to write it on your own.
Problem Solved!
Eureka!!!!
I was playing with CWM and figured it out. In the "mounts and storage" tab, if you select "format /data" it fails with an error that it can't mount the volume.
If you select "format /data and /data/media" it works like a charm. For some reason, it performs the format operation on the raw partition while the prior option tried to mount it first.
Back in business
Thanks RootShot ["format /data ¨in advanced wipe first¨ and format/data ¨& write yes in second¨ " ] did the trick and saved my phone back to work ...
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've found two ways of wiping and reinstalling my rom. One way uses fastboot and the other TWRP recovery. I'd like to find out how they correlate with each other.
Method 1: Fastboot
Format data
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Transfer rom zip files and install them
Method 2: TWRP
Simply format data and wipe every checkbox
Transfer rom zip files and install
What are you specifically looking to find? TWRP probably just issues the fastboot commands.
You don't need to flash the bootloader, modem, or recovery unless their are new ones available. Flashing them again is just redundant and a waste of time. Personally I only use fastboot to flash my bootloader,modem, or new version of TWRP. I use TWRP for literally everything else. You can wipe the partitions easier and quicker than using fastboot, or you can format data and completely nuke the phone and disable encryption. I'm not sure why you're asking how they correlate, I'm pretty sure it's common sense. If you erase a partition in fastboot, it's the exact same thing as wiping the partition in TWRP.
Also if you want to reinstall your ROM why are you wiping your whole internal storage? This is pretty much never required unless you want to free up space or decrypt the device. If you just wipe every partition but internal storage, you can keep local files (like Titanium Backup, pictures, music, any files you have on there, etc..). Then when you flash the ROM, it's still a clean flash because your system, data, cache, and boot partitions are already wiped.
The most important thing for me is that with Twrp-recovery, there is no other device needed; PC etc.