I had paranoid android installed on my phone running 4.1.2 and it kept crashing sometimes so I decided to go back to cm-10 which i used before but didn't prefer it. I did the exact same things I did last time but this time my phone would just stay at the cm-10 logo and never turn on. I had backup for paranoid android created before i flashed the cm-10 and so I tried restoring but it wouldn't work it my phone would turn off in middle of the restore. I tried that a few times and I just tried to retore the ORIGINAL 4.0 before i rooted my phone and it stopped in middle for that too and my phone just turned off. Idk what to do can anyone PLEASE HELP?? :crying:
I tried factory reset & clear data partition open it would also freeze in middle and turn off.
Also it says this at the bottom when i go to CWM recovery
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log/last_log
E:can't open /cache/recovery/log/last_log
PLEASE HELP ME CAN'T DO ANYTHING WITH THIS PHONE RIGHT NOW :crying:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
aplastar said:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
Click to expand...
Click to collapse
It wouldn't let me. That's the problem, anything I tried to do in recovery mode it would freeze and then turn off. And now it doesn't even go to recovery mode anymore! It just stays black the whole time. any help?
Last time I had this problem, I had to revert to stock using Odin and download mode.. works great now. It's a big hassle, but it is good to do a full reset every now and then. Then again, had so many problems with cwm that now I'm a twrp only man. That might help too.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hello all,
First some background
as you can tell i have an xperia s. I had initially rooted it in .45, installed CWM, installed .55 system and CWM again, and had a perfectly healthy tool on my hands. A week ago i realized it had suddenly started to eat up the battery in half a day. I uninstalled everything i could think of, and nothing happened. So i though of going back to a previous CWM backup.
That proved impossible since the backup sequence always stopped at a formatting error. After a dozen attempts i lost my patience and used flashtool to install and root .45. Then CWM, then OTA to .55, and then CWM again (it was lost after OTA update to .55).
Took me about a day to put everything back.
That was yesterday.
Today i tried to install the camera mod from xperia V (had it before and truly the focusing is faster, cannot vouch for anything else though)
And there it was:
Instructions for installing the zip require to wipe cache first.
Through CWM when i tried to wipe cache, both ways available, i always get the same error
make_extf4fs failed on /dev/block/mmcblk0p13
I have seen that before on my phone but everything works OK in normal mode. Only time problems arise is when i need CWM...
I have also seen it reported in xda but nobody posted a solution.
Any thoughts?
I cannot take it back as defective either, because it works ok:silly:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Guys. nobody knows, or nobody has the same errors?
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
sagardrokr said:
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
Click to expand...
Click to collapse
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
I am having this issue even after multiple(2-3) full wipes.
Let me be clear about that.
First time i encountered the situation i though it was just a glitch. So i went all out and erased everything. Reinstalled .45 , rooted, then OTA-ed to .55, then installed CWM (i actually installed it first at .45 but during the update to .55 it was lost, so i installed it again.) Problem insisted , so i re-did it all a couple of times until i run out of time to keep installing everything!!!
Now, as for the "manual" format you are referring to. How do we do that?
Can we do that through flash tool?
I was thinking of connecting the phone to the flashtool in flashmode and choosing only wipe cache.
But in order to do that i first have to choose an ftf and i was worried that i might erase everything again. I absolutely have no time to be installing everything again...!!!
m1st3r1 said:
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
Click to expand...
Click to collapse
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
sagardrokr said:
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
Click to expand...
Click to collapse
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
schumifer1 said:
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
Click to expand...
Click to collapse
DId you try the fastboot method?? Any success to pass through the errors?? We cant even install .55 firmware because of those errors..
schumifer1 said:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Click to expand...
Click to collapse
Same problems here. error at block 13. Is there any fix yet? TIA
edit: So block 12 is for /system and block 13 for /cache I think and block 14 is for /data or sdcard. errors on all of that.
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
I have the same errors again and again. Now each time i want to change the rom I have to flash Sony .45 rom, upgrade to .55 then root and flash CWM. It's either that or get stuck in à bootloop.
I've sent full error log on another thread.
Sent from my LT26i using xda app-developers app
silvershiver0323 said:
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
Click to expand...
Click to collapse
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Lodotux said:
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
That's true. My bootloader is locked as well
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Lodotux said:
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Click to expand...
Click to collapse
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
abcdjdj said:
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
Click to expand...
Click to collapse
that's this workaround we're trying to find. i've been told that a recent install of busybox should fix the problem but AFAIK it does'nt work on my phone.
Edit : problem is still here. I've tried to change the rom i'm using today, first, by flashing CWM v2, but get the same errors.
Had to flash .45 firmware, upgrade to .55 by sony upgrade, root, flash CWM and then wipe and install rom.
help
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Anime13 said:
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
Click to expand...
Click to collapse
Same for me too. My XS also needed a motherboard replacement. For everyone, if possible then just unlock your boot loader and flash a kernel in which this bug has been fixed. Hopefully in the JB update Sony will update the mmc driver.
Sent from my LT26i using xda app-developers app
Sliverer said:
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Click to expand...
Click to collapse
Deleting 20 giga and restoring it is certainly not my idea of a quick backup and restore .
For the time it would take to copy 20 giga back and forth i could have installed everything again by hand..
Good info though.
I have noticed that formatting /data also lets us use it without the block errors
Hi everyone. I've been having this problem since I started rooting my Note, and I haven't the slightest clue how to fix it. Basically, when I boot to TWRP recovery and try to do a wipe (the default wipe which includes wiping cache, Dalvik, and formatting data), the recovery hangs on "Formatting /data using make_ext4fs function," and after about two minutes the application restarts. If I attempt to flash a ROM after that, I get "Can't mount /data," and other can't mount errors and even though Aroma loads fine, the tablet gets stuck on the boot screen (Samsung logo). Someone on the TWRP website suggested that the tablet is encrypted but I never encrypted the device myself.
Thanks for reading!
P.S. I see similar errors to the picture at the botttom of this thread: formatting data using make_ext4fs function
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Note2Hunter said:
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
Click to expand...
Click to collapse
jun3280 said:
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Click to expand...
Click to collapse
So did you install it using an external sdcard?
I am getting a lot of little issues with this device. Its new, had it for a day now, was able to get lineageos on it and everything seemed fine. Then during a reboot, it stuck on the sony boot screen, no way to power off, no reboot. Had to wait till the battery died. then it booted, with lots of bugs. Went to twrp and factory reset, and cache cleared. Except now I get an error of
"Unable to find partition for path '/cache' "
Any idea how to fix? I can not wipe it, etc.