I'm using CWM on my XPERIA LT26i running fw 6.1.A.2.55 with a rooted OS.
If I get the following error in CWM, does that normally mean my internal memory is failing/about to fail???
CWM Recovery for 2012 Xperia v02
by kenjidct
Checking MD5 sums...
Restoring system...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error while formatting /system!
E:Error in /cache/recovery/log
(I/O error)
/cache/recovery/log
Formatting /system...
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
warning: wipe_block_device: Discard failed
error: file_write: write: I/O error
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /system!
I can "doggedly" recover from this error my just keep formatting the /system partition and eventually it completes successfully.
I don't seem to get any operational errors when using my phone and my OS appears to be stable.
This only occurs when attempting to restore a previous backup and the restore fails on the /system partition when attempting to format it.
Manually formatting the /system partition also fails..but can successfully complete after a few attempts. (fingers crossed)
I have seen this 'type' of error reported in the XPERIA U/P/Sola forum too.
Is it possible (I have root access) to run fdisk on the /system partition and if so.. what do I need to do to do that.
And what are the risks?
Thanks for any advice.
[UPDATE]
Additional information that may alleviate my panic ... a bit. Found this in "Advanced Stock ICS Kernel for Xperia S" ROM
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Howdy all,
I recently tried to switch to CM 10.2 M1. It's not working out for me for two reasons:
Poor mobile data performance - requires frequent reboots to maintain data connection
openPDroid is not playing nice with it
So, I'm trying to restore my 10.1.3 backup. I have done a factory wipe from CWM and formatted /system (though I may have tried just restoring previous to that, I don't recall). When I try to restore the backup, the boot.img is restored successfully, it starts /system, and after some seconds it gives the following message and stops the restore process:
Code:
Error restoring /system!
The relevant excerpt of /cache/recovery/log is below. Fortunately I finally got ADB sort-of working again (won't connect from fastboot but does from CWM).
I suspect one of two things:
Somehow the size of the /system partition has changed, but I don't know why, how to verify it (what should it be?), and how to safely change it.
The backup is corrupt. I don't know how to check this. The log indicates md5s are okay for system.ext4.dup, but I don't see any indication in the logs that md5s of all of the blobs are okay or even checked.
Has anyone seen something similar or have any advice?
Thanks!!
VZW toro
CWM 6.0.1.0 used to create the backup and to attempt the restore
Using Linux, which has not always played nice with this phone (MTP not supported, udev hell), which is probably the adb issue during fastboot
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
I:using /data/media for /sdcard/clockworkmod/backup/2013-11-02.14.40.11/.
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
recovery.img: OK
system.ext4.dup: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-11-02.14.40.11//system.ext4.dup
Restoring system...
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
Unable to copy file ./app/Apollo.apk
system
lost+found
addon.d
50-cm.sh
blacklist
70-gapps.sh
71-gapps-faceunlock.sh
app
Apollo.apk
Error while restoring /system!
Hello,
I compiled aosp for my nexus 7 2013 works fine, but i wanted to add apps and tweak things like bootanimation.zip and remove things like email app, i don't use it why waste space. I use the the follow to allow edits
simg2img system.img system.img.raw
mkdir system
sudo mount -t ext4 -o loop system.img.raw system/
I add my edits and than use this but get and error
[email protected]:~/Downloads/imagedisassemble$ sudo ./make_ext4fs -s -l 512M -a system mesystem.img system/
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
error: do_inode_allocate_extents: Failed to allocate 3 blocks
I have tried to change 512M to 600M it will finish without error, however when I flash with fastboot flash system system.img, I get stuck on the Google screen and have to force off with power and get into bootloader to try again.
Any help would be great
Thanks
Tony
I tried to hard reset a zenfone 2 and it failed. When i try to do the recovery mode, it does not give me the option to reset it so then i did it thru fastboot, it wiped everything on the phone minus the passcode so it still does not let me access the phone. can someone help please
c:\Android\android-sdk\platform-tools>fastboot -w
Creating filesystem with parameters:
Size: 3687800832
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 14067
Label:
Blocks: 900342
Block groups: 28
Reserved block group size: 223
Created filesystem with 11/225344 inodes and 30010/900342 blocks
Creating filesystem with parameters:
Size: 1228931072
Block size: 4096
Blocks per group: 32768
Inodes per group: 7504
Inode size: 256
Journal blocks: 4688
Label:
Blocks: 300032
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/75040 inodes and 9887/300032 blocks
erasing 'userdata'...
OKAY [ 13.495s]
sending 'userdata' (59473 KB)...
OKAY [ 2.399s]
writing 'userdata'...
OKAY [ 7.166s]
erasing 'cache'...
OKAY [ 3.867s]
sending 'cache' (21084 KB)...
OKAY [ 1.131s]
writing 'cache'...
OKAY [ 2.016s]
finished. total time: 30.120s
SOLVED: Changed partitions to ext3. Which made it possible to use twrp and adb
Hello! For a couple of months now my google pixel c has been bricked. I have messed around with the tablet alot and this time im unable to fix my mistake.
The os is completly gone and twrp is broken.
I have tried for months, using google, using different computers etc.
In fastboot it does recognize the device. However it refuses to let me flash any kind of zip/img
Also no computer i have been using have been able to find the correct drivers, i have to manually install them.
When i try to download the official factory image for my device i extract it and then i run the flashall.bat command i get this:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.497s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.509s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.27.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking partition-size:system...
OKAY [ 0.018s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.057s
Press any key to exit...
Hello, what do you mean by twrp is broken ? Because i had the same problem with my pixel C but i still had access to twrp so i update the recovery with twrp then flash the tablet. Now my pixel c works fine but i'm still unable to flash it via fastboot
rhmanoa said:
Hello, what do you mean by twrp is broken ? Because i had the same problem with my pixel C but i still had access to twrp so i update the recovery with twrp then flash the tablet. Now my pixel c works fine but i'm still unable to flash it via fastboot
Click to expand...
Click to collapse
Thank you for the reply. Twrp is partially broken is more correct. Its a while ago so I don't remember how exactly I broke it. But I think I partially updated the os which made it impossible for twrp to read my storage. So twrp is unable to write and read my internal storage.
And I'm unable to flash a new recovery since I can't use fastboot
I had also the same issue but you just had to change the partition type of data to ext3 then it should be fine.
Hmm... I have not touched those settings. Will try it when I get home! I saw yesterday the partition type was ext4. I never touched those settings so it seems weird. But I will give it a shot! I appreciate you guys helping me I even tried to advertise it as a job but no one knew what to do. So this is my last shot before selling it broken
Thank you very much for the help! After changing partition i was succesfully able to push Linage os through adb and twrp.
Will try to install it now. Thank you very much!
This feels like christmas
Anytime.
who can tell me how to change partition to ext3 via adb?sorry for my poor ability...
Guys I have been trying to fix this for the past week and I had no clue how to format using ext3 since I wasn't even able to go into TWRP recovery. But I found these two posts which were great help.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool and it's actually pretty straightforward. Just in case it is not very clear, I'll try to explain the whole process step by step below.
The second link above has a download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot flash-all should also work.
I hope this helps everyone and good luck...