Okay, i had Marcel's CM10 with his kernel and i wanted to try miui v4 (http://forum.xda-developers.com/showthread.php?t=1527336) ...so i did a backup, wiped all, (factory reset/dalvik wipe), then flashed miui and strarted...but it stuck at bootlogo!
I retried the whole process, the last time i did factory reset again after flashing, but still the same... Then i wanted to restore backup...so i first wiped all, flashed CM10 again, installed my app2script, and restored. But i aborted at data restore cause of mount error...of course, i retried, this time only wipe and cm10, but it still stucks...only formatting data gives error "[E] format_volume make_extf4fs failed on /dev/block/st17.
/data not wiped"... Please help!
Sent from my Nexus 7 using Tapatalk 4 beta
Here is the CWM log at wiping with the error:
Starting recovery on Tue Jul 16 11:29:45 2013
framebuffer: fd 4 (240 x 400)
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /cache rfs /dev/block/stl8 (null)
3 /data ext4 /dev/block/stl7 (null)
4 /system ext4 /dev/block/stl6 (null)
5 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
6 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
stat() of /dev/block/stl7 succeeded on try 1
Command: "/sbin/recovery"
/*Build props*/
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping data...
Formatting /data...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/stl7
Formatting /cache...
I:Formatting unknown device.
Formatting /sd-ext...
Creating filesystem with parameters:
Size: 511539200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7806
Inode size: 256
Journal blocks: 1951
Label:
Blocks: 124887
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/31224 inodes and 4013/124887 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
Try this: Flash a rom in Odin and then install cm10 again and when its installed reboot recovery and try with restore. That always helped me on my old g3 when i had problems
Sent from my GT-I9100 using xda app-developers app
Worked after temporarely flashing CM7 via CWM!
Sent from my Nexus 7 using Tapatalk 4 beta
DELETED
DELETED
Sent from my GT-I8160 using xda app-developers app
G3 - Made a mistake
Hi there !
I'm new to this forum just for the Samsung Galaxy 3 Apollo GT-I5800 even I've got a Samsung Galaxy S3 LTE (GT-I9305) I still wanted that one to work after reading different threads on this forum...
What I've done is I've wiped the phone without making any backup before that, which is my first mistake... Before that I did not root the phone :crying: Which is my another mistake... Now the phone is getting stucked on the boot with a Samsung GT-I5800 writing on the screen...
The Memory Card is completely new so I ain't got any data on it... I am very new to the phone systems and I'd need step by step instructions if any1 could be that kind and do it for me please.
The phone is on 2.2 Android and I'd like that phone to be for gaming for my gf so I need some good performance ROM I thought something like KEvolution v1.1 or Kyrillos' ROM
Wiping the phone should not cause a bootloop, especially if you aren't rooted and have no custom ROM...
Flash another rom with ODIN.
I've already tried it. It won't work. That's the problem. If u need any info about it just let me know what is it that u want and I'll get it for ya.
Writin on my Phone usin tt.
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
do you have access to the bootloader/recovery?
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
[email protected] said:
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
Click to expand...
Click to collapse
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
noutsos said:
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
Click to expand...
Click to collapse
are you on S-ON?
post your bootloader details
rzr86 said:
are you on S-ON?
post your bootloader details
Click to expand...
Click to collapse
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
noutsos said:
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
Click to expand...
Click to collapse
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
rzr86 said:
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
Click to expand...
Click to collapse
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
noutsos said:
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
Click to expand...
Click to collapse
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
rzr86 said:
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
Click to expand...
Click to collapse
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
noutsos said:
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
Click to expand...
Click to collapse
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
rzr86 said:
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
Click to expand...
Click to collapse
tried ruu exe but nth happened,cant find the device,and cant fastboot
How does fastboot not work? Does usb not connect at all?
Hey guys, any news about fixing bug in TWRP which caused corrupting partitions and bricking phones?
Hi guys,
I have the same issue as OP, however only the /data won't get mounted. My phone got stuck while doing wipe of the data partition in TWRP 2.6.3.0 (it didn't freeze, but it was taking over 40 minutes already), so I had to take the battery out and put it back in.
First, I tried using TWRP 2.6.3.0 to perform the wipe again, but I got
Code:
E:Unable to mount '/data'
I got the same error when I tried to install any ROM, so the installation got aborted.
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'.
Here is my bootloader info:
S-OFF
Firmware 3.33
HBOOT 1.27.1100
Radio 11.24A.3504.31_M
I am pretty much desperate at this point. Is there any way or chance of fixing my partitions? I haven't tried fixing it using parted, because I was unable to find a good howto for Sensation. I would be happy for any advice.
MatesCZ said:
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'..
Click to expand...
Click to collapse
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
rzr86 said:
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
Click to expand...
Click to collapse
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
MatesCZ said:
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
Click to expand...
Click to collapse
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
rzr86 said:
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
Click to expand...
Click to collapse
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
...
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Click to expand...
Click to collapse
MatesCZ said:
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Click to expand...
Click to collapse
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours
someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit
I posted this in the OnePlus forum as well, but hoping to get some more help here.
Over the weekend I finally got the OTA update for CM12. Before installing, I made a system/data backup in TWRP and made a full backup in Titanium Backup. After installing the update, things were mostly ok, but felt extremely buggy and things just overall didn't work well. After a few reboots things seemed to get a little more stable then I realized I wasn't rooted anymore. After multiple reboots I saw that the TWRP custom recovery got overwritten and replaced by the CM recovery. After searching for hours yesterday I was finally able to get TWRP back on so I could root and from there things only got worse.
I flashed the SuperSU file to root my phone again and it booted back up. After checking a couple of things and another reboot it started getting stuck on the boot animation, and would no longer boot up at all. After another hour or 2 of trying to get it to boot, I decided to just wipe it and start over. I flashed the factory cm image cm-12.0-YNG1TAS17L-bacon-signed.zip and after the "Android is Upgrading" screen, I started getting constant loop errors that Google App has stopped working and Google+ has stopped working. These would pop up every 1-2 seconds. I did another wipe and flashed the previous version cm-12.0-YNG1TAS0YL-bacon-signed.zip. After flashing that, it was the same thing, constant loop errors about one of the google apps not working. "Patiently" clicking ok to get past the set up screens and updating everything in the Google Play store those errors stopped, but then I noticed Chrome would not launch. At all. It would open and immediately force close.
I also get the "System UIDs Inconsistent" error.
After all of this, there's another issue that I see every time I try to flash or wipe anything in TWRP (current version is 2.8.6.0). Here's part of the recovery log:
I:Set page: 'action_complete'
Iperation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'action_page'
Iperation_start: 'Format'
I:wipe list 'DALVIK;/system;/data;/cache;'
I:wipe_path 'DALVIK'
Wiping Dalvik Cache Directories...
-- Dalvik Cache Directories Wipe Complete!
I:wipe_path '/system'
Formatting System using make_ext4fs function.
Creating filesystem with parameters:
Size: 1388314624
Block size: 4096
Blocks per group: 32768
Inodes per group: 7712
Inode size: 256
Journal blocks: 5296
Label:
Blocks: 338944
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/84832 inodes and 11157/338944 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
I:wipe_path '/data'
Wiping data without wiping /data/media ...
I:Unable to unlink '/data/data/com.google.android.googlequicksearchbox/cache/http/1b92ca0903b529c5a5afb687a70b51ef.1: I/O error'
Done.
I:Get_Max_FileSize::maxFileSize: 17592186044416
I:sending message to add 65537 '/data/media/0' 'Internal Storage'
mtppipe add storage 65537 '/data/media/0'
MtpStorage id: 65537 path: /data/media/0
E:MtpServer::addStorage Storage for storage ID 65537 already exists.
I:Message sent, add storage ID: 65537
I:wipe_path '/cache'
Formatting cache using make_ext4fs function.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
I:Recreating /cache/recovery folder.
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
Updating partition details...
E:Unable to stat '/data/data/com.google.android.googlequicksearchbox/cache/http/1b92ca0903b529c5a5afb687a70b51ef.1'
E:Unable to stat '/data/data/com.google.android.googlequicksearchbox/cache/http/ddc8e46ee73b718c1040ea22416705d5.0'
E:Unable to stat '/data/data/com.google.android.googlequicksearchbox/cache/http/41e7cc2b141b99226d68ca551f169eec.0'
E:Unable to stat '/data/data/com.android.chrome/cache/.com.google.Chrome.5gc7PN'
E:Unable to stat '/data/data/com.google.android.music/databases/WearableDataSync.db-journal'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050004'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050005'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050006'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050014'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050010'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2012050009'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/event_themes/2013050005'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/media_sync/1/1b2fe9e4d4ddd6-t'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/media_sync/8/845d63ac5ae7d30-t'
E:Unable to stat '/data/data/com.google.android.apps.plus/cache/media_sync/2'
Iata backup size is 671MB, free: 40173MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done
The part that says "E:Unable to stat..." has been happening for a long time and I'm not sure how to fix this or even get my phone working again. In TWRP, if I use the file manager and go to the location for (example):
E:Unable to stat '/data/data/com.android.chrome/cache/.com.google.Chrome.5gc7PN'
And try to copy, move or delete that file, the operation fails. I'm wondering if these cache files are causing my problems, but I don't know how to fix it. This makes me wish I never even touched CM12 at all.
Can anyone please help me get this thing working again?
I was able to fix these issues by following the steps here to restore the device back to factory settings:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390