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
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
3vilrabbit said:
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
Click to expand...
Click to collapse
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
CCallahan said:
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
Click to expand...
Click to collapse
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
3vilrabbit said:
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
Click to expand...
Click to collapse
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
CCallahan said:
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
Click to expand...
Click to collapse
I'm gonna bring it back to the shop and hopefully, if I put up a poker face if they ask me about rooting my device :angel:, they accept it and treat it with warranty
For some reason, I really don't know what I have being trying...my tablet miraculously is working again!
Thread can be closed...
Hello all
I was updating my gf phone from rooted UVALJ4 or UVALH2 (Cant remember now, but it was an old Firmware) to root66 T999_UVUENC2 via Odin 3.09 on my Win 7 pc but after the odin install (which passed) I rebooted the phone and I got stuck on the Samsung logo on the start up screen. After about 10 mins I pulled the battery and tried to enter the Recovery mode, but nothing appears. Just a black screen.
So i Odin flashed the TWRP 2.6.3.1 to try to get to a recovery, but that didnt work. Still no Recovery.
I then used odin to flash the stock tmobile UVUENC2 4.3 firmware and it still gets stuck on the Samsung screen.
Next I tried to unbrick it via http://forum.xda-developers.com/showthread.php?t=2439367 using "SGH-T999 4.3 only Debrick Image" and reflashed the stock 4.3 rom, but that didnt work. :crying:
What can I try next? WHat should I do? I can still access download mode, thats about it.
Please help if you can.
Thx
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
synplex said:
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
Click to expand...
Click to collapse
Never Mind Used Unified Android Toolkit to fix recovery and flash stock rom.
Thank god for that toolkit.
...time to donate
:victory:
Mod Please delete Thread.
Thx
In the future, try a factory reset, almost all boot hangs are solved with this. Happens because of incompatible data between versions, which would make sense condidering the jump you made. Kind of makes sense with the error message too, but I'm not 100% certain there.
Be careful with the toolkit. There is no support for it and it has bricked phones in the past.
Ok here is the story about a year ago I rooted my AT&T GS3 installing CWM and Cyanogenmod. I hadn't had an issue until mid-september. For some reason one of the updates caused certain phone functions to quit working, specifically my mobile data. I searched around on the internet and found out that it had probably affected my modem files, and was told to flash back to stock and that that should solve it. I found a stock firmware file and flashed it with odin. When my phone rebooted it boots to the point of the samsung emblem with the oscillating blue background and just sits there. I tried flashing different versions of the firmware to the same result. I later learned I probably flashed just the modem which I found while trying to solve the problem. When I boot into stock recovery i receive the following message:
E:failed to mount/data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
E:failed to mount/data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount/data (Invalid argument)
Anything will help because I am currently without a phone so.... thanks
Edit 1: The Firmware I attempted to flash came from samsung-updates.com though I am not sure of what build and can't check since it won't boot all the way
What firmware build are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I cannot tell what build, I got it from samsung-updates.com in a zip titled ATT-I747UCDLK3-201211116120549
I would download it again in case it was somehow corrupted. The build is in the filename, LK3, which appears to be 4.1.1. I would say to try 4.1.2 instead, but it appears that wasn't released by AT&T either.
Or if you want you can try flashing the root66 firmware instead. It's LK3 too, only pre-rooted. It's in this thread: http://forum.xda-developers.com/showthread.php?t=1739426
Either way, redownload and try flashing again. Then boot recovery and factory reset. (Will wipe internal sd)
If it still won't mount /data, try flashing Twrp recovery and factory reset. (Will not wipe internal sd unless you choose advanced > Format /data.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you so much! I ended up having to flash twrp but when I did what you said it booted just fine. Now the only question remaining is do I try to go back to cyanogenmod?
Since you have TWRP working, copy CM11 to your phone, boot to twrp, and flash CM11. If CM11 does't boot, try wiping data, cache, and dalvik.
Just remember, anytime you go between different based roms, such as TW and CM, you have to factory reset or it'll hang during boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
AshleyNG2 said:
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
Click to expand...
Click to collapse
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
If you can get into TWRP, wipe everything at least 2 times.. Then install a Flashable ROM/gapps ect..
If you cant get into TWRP and only into Download mode.. Then you will have to flash stock kdz file...............
you can find all types of guides on that around here............
Eliminater74 said:
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
Click to expand...
Click to collapse
Thanks for your response, once I got into TWRP I couldn't wipe anything as it couldn't mount any partition nor could I flash anything from the external sd.
When I plugged it in there was no internal memory so I decided to use the TOT restore method to go back to stock which was successful and now I've got my custom stock rom back on.