I have a KF 7" 5th generation that my kids use almost every day until last week, when it started freezing up on the FIRE logo.
I went into recovery and attempted a wipe of everything, but interestingly I'm seeing a dozen or so error messages such as:
E:failed to mount /cache (invalid argument)
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
I thought it was strange, but then even stranger when wiping data/factory reset didn't work and threw the same messages.
I figured, time to reflash firmware using ADB sideload, but that threw the following:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache
E:failed to set up expected mounts for install; aborting
Installation aborted.
Well, this sucks. I can boot into Fastboot mode, so I tried the oem format command, which says:
FAILED (remote: the command you input is restricted on locked hw)
Everything is stock, stock recovery, stock rom, never rooted. What gives, am I out of luck? I can't think of what else to try. If my partitions are corrupted, I don't even know where/how to begin fixing such a thing. Someone tell me there's something simple I'm overlooking!
Dishe said:
I have a KF 7" 5th generation that my kids use almost every day until last week, when it started freezing up on the FIRE logo.
I went into recovery and attempted a wipe of everything, but interestingly I'm seeing a dozen or so error messages such as:
E:failed to mount /cache (invalid argument)
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
I thought it was strange, but then even stranger when wiping data/factory reset didn't work and threw the same messages.
I figured, time to reflash firmware using ADB sideload, but that threw the following:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache
E:failed to set up expected mounts for install; aborting
Installation aborted.
Well, this sucks. I can boot into Fastboot mode, so I tried the oem format command, which says:
FAILED (remote: the command you input is restricted on locked hw)
Everything is stock, stock recovery, stock rom, never rooted. What gives, am I out of luck? I can't think of what else to try. If my partitions are corrupted, I don't even know where/how to begin fixing such a thing. Someone tell me there's something simple I'm overlooking!
Click to expand...
Click to collapse
Bootloader is locked on this device. If partitions are messed there is nothing you can do to remedy. Also possible the low end NAND/eMMC is borked which could easily manifest as a partition issue.
Yes i know its old ... you can try in recovery factory reset, this works for me
To the original poster:
I have this same problem with a Fire 7 5th gen. The 5.6 update broke my tablet. I made a thread about it a couple months ago. I have only been able to get it past the fire loading screen twice in two months. I got back to the factory reset pages and set up the fire again twice, worked normally, until you try to power it off or reset it and then it forever stays on the fire screen or black screen. Never been rooted or messed with and I am positive it didn't happen until the update. I gave up, thank goodness I have a new Samsung tablet you don't have to screw with 100 ways to get it presentable. I'm done with Amazon tablets.
Dishe said:
I have a KF 7" 5th generation that my kids use almost every day until last week, when it started freezing up on the FIRE logo.
I went into recovery and attempted a wipe of everything, but interestingly I'm seeing a dozen or so error messages such as:
E:failed to mount /cache (invalid argument)
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
I thought it was strange, but then even stranger when wiping data/factory reset didn't work and threw the same messages.
I figured, time to reflash firmware using ADB sideload, but that threw the following:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache
E:failed to set up expected mounts for install; aborting
Installation aborted.
Well, this sucks. I can boot into Fastboot mode, so I tried the oem format command, which says:
FAILED (remote: the command you input is restricted on locked hw)
Everything is stock, stock recovery, stock rom, never rooted. What gives, am I out of luck? I can't think of what else to try. If my partitions are corrupted, I don't even know where/how to begin fixing such a thing. Someone tell me there's something simple I'm overlooking!
Click to expand...
Click to collapse
You solve the issue? i have the same issue with the same device.
BeStMaker said:
You solve the issue? i have the same issue with the same device.
Click to expand...
Click to collapse
Nope. Junked it.
Dishe said:
Nope. Junked it.
Click to expand...
Click to collapse
So sad, im checking many threads and forums with the same result.
It's my nephew's tablet
Related
I'm not sure what I've done, but I obviously wasn't paying attention. I had RyanZA's 2.3 beta lagfix installed and I decided to uninstall it using the supplied script. At some point I saw my phone reboot and I thought it had finished, but I don't really remember what happened after that.
Anyway, I've got it to the stage where it just shows the i9000 startup screen, goes black, then shows the i9000 screen again. I can get into recovery and I've got clockwork recovery installed as well, so I can get into that. I've used adb, but I can't get a log of it booting because it just says waiting for device and never gets past that stage. I used adb shell to see if I could manually process the scripts, but it looks like all the data and the backups of the data folders are gone.
I've wiped data in both clockwork and stock recovery, but I still can't get the phone to boot. System still looks ok, so I'm not sure why it's not working.
Anyway, my main question is, how can I get my phone back up and running? The mount usb option doesn't seem to be working, so I guess I'll have to use Odin or KIES, but what do I flash? Is there a link for a stock UK i9000 firmware somewhere?
Update:
Ok, I've got the phone working again, but after using Odin to flash the firmware, it reboots into recovery and I get the message can't mount /dev/block/stl11 (invalid argument)
The phone boots ok, but I can't download anything from the market ("download unsuccessful" almost immediately)
Internet works fine, so I don't think that's the problem.
Further update:
After Odin has flashed, the phone boots into recovery with the following messages:
E: Can't mount /dev/block/stl11 (invalid argument)
update media, please wait ...
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media:Can't mount DBDATA: copy default media content failed
E: Can't mount /dev/block/stl11 (invalid argument)
E: Can't mount /dev/block/stl11 (invalid argument)
This was after flashing WJM6 with .513 pit
You can try this...connect your phone with KIES and update it with the official firmware. I have not tried this so I dont know if it will help you.
Thanks, I eventually got it to work by flashing the WJG5 firmware. It would probably help if I'd known what it was actually running in the first place.
Now I've got it working though, I might try connecting to KIES and seeing if there's an updated version.
hey there, is this resolved? i got mine working after
can't mount /dev/block/stl11 (invalid argument)
but its still there. Do u know how to clean this error?
Update: I Fixed it by reflashing to WJG5 as stated above. BUT when i tryed reflashing with newer rom its still there..
Joans said:
I'm not sure what I've done, but I obviously wasn't paying attention. I had RyanZA's 2.3 beta lagfix installed and I decided to uninstall it using the supplied script. At some point I saw my phone reboot and I thought it had finished, but I don't really remember what happened after that.
Anyway, I've got it to the stage where it just shows the i9000 startup screen, goes black, then shows the i9000 screen again. I can get into recovery and I've got clockwork recovery installed as well, so I can get into that. I've used adb, but I can't get a log of it booting because it just says waiting for device and never gets past that stage. I used adb shell to see if I could manually process the scripts, but it looks like all the data and the backups of the data folders are gone.
I've wiped data in both clockwork and stock recovery, but I still can't get the phone to boot. System still looks ok, so I'm not sure why it's not working.
Anyway, my main question is, how can I get my phone back up and running? The mount usb option doesn't seem to be working, so I guess I'll have to use Odin or KIES, but what do I flash? Is there a link for a stock UK i9000 firmware somewhere?
Update:
Ok, I've got the phone working again, but after using Odin to flash the firmware, it reboots into recovery and I get the message can't mount /dev/block/stl11 (invalid argument)
The phone boots ok, but I can't download anything from the market ("download unsuccessful" almost immediately)
Internet works fine, so I don't think that's the problem.
Further update:
After Odin has flashed, the phone boots into recovery with the following messages:
E: Can't mount /dev/block/stl11 (invalid argument)
update media, please wait ...
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media:Can't mount DBDATA: copy default media content failed
E: Can't mount /dev/block/stl11 (invalid argument)
E: Can't mount /dev/block/stl11 (invalid argument)
This was after flashing WJM6 with .513 pit
Click to expand...
Click to collapse
Hello
I had the same and i solved through the guide here:
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
But i think the problem really was that i have make an ext2 partition on sd-card.
I removed the sd-card during flashing.
Hi Guys, I'm looking for some help for a mate of mine who can't get his Samsung Galaxy S to start up.
The phone is box standard from Vodafone and only a couple of months old. It hasn't been rooted or tampered with in any way.
Today he decided to plug it into kies to check for updates and it showed him that there was an update available for his phone. he followed the on screen prompts and went about updating it. After it updated the phone just died on him. I have spoke to him over the phone to try and explain the 3 button recovery method to him but he still can't get it to boot up. He has sent me a photo of his phone so hopefully that may help for any potential advice. I'm no phone expert but could easily follow any instructions/ guides on flashing etc.
Any advice or help would be most grateful
Cheers, Sean
Pull out the usb cord.
Sent from my GT-I9000 using XDA App
DamianGto said:
Pull out the usb cord.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
He has done that and still no Joy
sean2476 said:
Hi Guys, I'm looking for some help for a mate of mine who can't get his Samsung Galaxy S to start up.
The phone is box standard from Vodafone and only a couple of months old. It hasn't been rooted or tampered with in any way.
Today he decided to plug it into kies to check for updates and it showed him that there was an update available for his phone. he followed the on screen prompts and went about updating it. After it updated the phone just died on him. I have spoke to him over the phone to try and explain the 3 button recovery method to him but he still can't get it to boot up. He has sent me a photo of his phone so hopefully that may help for any potential advice. I'm no phone expert but could easily follow any instructions/ guides on flashing etc.
Any advice or help would be most grateful
Cheers, Sean
Click to expand...
Click to collapse
If the phone can enter download mode, it can be rescued. Otherwise, it was definitely bricked.
Sent from my GT-I9000 using XDA App
Try to pull out the battery for 10 minutes. Then but the batteri back.
Then try to get in download mode.
If you can't, the try to see if odin see it.
If odin can see it try to flash back original firmware.
If you are lucky it can work.
If not then it seems very bad.
Sent from my GT-I9000 using XDA App
Thanks Damian, I will pass this info on to him tomorrow. I wish my mate lived closer so I could have a go at it myself.
i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?
XlAfbk said:
i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?
Click to expand...
Click to collapse
Why dont you flash crc also?
Try to do a complete flash.
Then go in recovery more and do wipe catch and a factory reset.
If you manage to get it to boot do format your internal sdcard.
Sent from GT-I9000 Jpm OS kernel with z4mod
This SGS had the original O2 ADJM1 firmware without the 3 button combo, which I fixed using the 3 button fix from another thread. SGS was working fine but I thought I'd give in and try a custom Rom.
Installed Darky's 6.0, worked great, but when I tried a factory reset from the settings menu, it kind of semi bricked, so I used Odin to install "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM" with pit 512 to recover the SGS.
Problem is, Android Market will not download "download unsuccessful" pops up all the time.
The I installed GT-I9000_I9000XWJM9, hoping to fix the problem, while keeping recovery 2e, but Android market still does not download.
When I try the "wipe data/factory" reset using the 3 button combo, I get the following errors:
Appling Multi-csc
installing Muli-csc
mps_dat value: KOR
copy_multi_carrier from : KOR
multicsc : can not access to /system/csc/KOR/system/
copy common_data E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
wiping data...
Formatting DATA:...
format_root_device: /dev/block/mmcblk0p2Formatting CACHE:...
format_root_device: /dev/block/stl11Data wipe complete.
E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
I'm guessing "E" is the internal SD card, so maybe there's a problem there
Also how do I fix this android market problem ?
I really need a pointer to installing a stock fully working Rom with recovery 2e, then I can move back to Darky's new 7.0 ROM.
Any help would be great.
forcedv said:
This SGS had the original O2 ADJM1 firmware without the 3 button combo, which I fixed using the 3 button fix from another thread. SGS was working fine but I thought I'd give in and try a custom Rom.
Installed Darky's 6.0, worked great, but when I tried a factory reset from the settings menu, it kind of semi bricked, so I used Odin to install "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM" with pit 512 to recover the SGS.
Problem is, Android Market will not download "download unsuccessful" pops up all the time.
The I installed GT-I9000_I9000XWJM9, hoping to fix the problem, while keeping recovery 2e, but Android market still does not download.
When I try the "wipe data/factory" reset using the 3 button combo, I get the following errors:
Appling Multi-csc
installing Muli-csc
mps_dat value: KOR
copy_multi_carrier from : KOR
multicsc : can not access to /system/csc/KOR/system/
copy common_data E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
wiping data...
Formatting DATA:...
format_root_device: /dev/block/mmcblk0p2Formatting CACHE:...
format_root_device: /dev/block/stl11Data wipe complete.
E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
I'm guessing "E" is the internal SD card, so maybe there's a problem there
Also how do I fix this android market problem ?
I really need a pointer to installing a stock fully working Rom with recovery 2e, then I can move back to Darky's new 7.0 ROM.
Any help would be great.
Click to expand...
Click to collapse
Hi, i have exactly the same problem.
With the invalid argument problems on data/factory reset, and the download unsucessfull problem! i have reflashed 4times JM1 on my phone !!!
i give 25$ for someone who solve the problem !
The way I fixed this problem was in two steps.
I used the Kies registry hack (someone here has created a program (which I can't find a link to right now) for windows that fools Kies to recognize your SGS as requiring an official firmware update).
Once your SGS is back on your official carrier firmware, Android market will work again.
From there, I was able to do a proper factory reset, followed by installing Draky's 7 Rom, using the 3 button combo and update zip method......and till now it's all good.
My SGS went from being a useless paper weight, to a kick ass device.
Good luck.
*You mentioned JM1* you may not need to go back to that firmware, but whatever official carrier firmware that Kies updates your SGS to, should fix the market problem.
With the Internal SD Corrupted Fix, i have formated my internal SD and there is no invalid argument when i do a data/factory reset.
but i think this is another problem, i have tried anything.
The hang on installing/unistalling problem come when i add my Google Account on the Android Market.
After this, i can't install or unistall anything.. that show installing.... at the infinite.
(sry for my english)
i have created a new google account for re-downloading again applications on the market, but i'm really sad because i have bought a lot of with my other account! wtf...
can't someone have any ideas or can help me?
thanks!
ok now that i sucesfully reparttioned my shw-m180s,
i have a tiny bit of problem on the internal sd card...
its not showing the 16gb storage,instead its 210mb size..
.i have now sucesfully collected all the files i need to flash and keep on reflashing,
but i cant find a way to successfully make the internal sd to gb
,instead it keeps goin back to the 210mb,
before i have the no internal sd card detected or error,
but it shows upfor a sec then gone,now its just 210mb,
anyone else who have this problem that successfully corrected the repartition process kindly guide me to make it to gb instead of just mb...
for those interested heres the file url links for you to use
stock SHW-M180S Files:
http://gadgetmodder.com/2012/11/how-to-flash-samsung-shw-m180s-korean-anycall-tablet/
Ice Cream Sandwich rom:
http://gadgetmodder.com/2012/11/gui...m180s-korean-anycall-tablet-to-android-4-0-4/
Theres another thread here on forums for the Jelly Bean system but i wouldnt suggest it coz i cant access the recovery mode but ill add the link too
Jelly Bean Rom Thread Link:
http://forum.xda-developers.com/showthread.php?t=2057050
this threads and files are not mine,i just looked hard to get these from all the sites i came across,thanks to them i can use my tab even with 210mb (^^,)
after many months of being stuck,
i have now successfully restored my internal to stock with some threads and files ive collected,
all came clear after 2 days ago,why? coz I was always partying and drinking lol
ok the trick is
1. enter download mode to flash m180s_4.1.2_CN_130109 tarball via odin 1.85
2. it be a constant loop in recovery choose advance option reparation sd card to settings u want
3. mount sd card to pc to check desired internal
4. clear all data cache dalvik etc if u can
5.enter download again to flash the rom that worked before,as for me im stuck with Jiwon ROM 2.0S Full
I cant retun to stock froyo,gb and rooted ics. the error still shows when im using those roms
now its what im working on,hope to fix it as soon as possible
and they say it cant be fixed lol, go prove them wrong (^_^)
heres a site with the files I used,credit goes to all to ones that shared it
http://main.develoid.com:81/samsung/Galaxy/Galaxy Tab/SHW-M180S/
site is moved
hi this site is moved to mobile-hub.net
here is the new links
4.0.4 ugrade is here http://mobile-hub.com/how-to-flash-samsung-shw-m180s-korean-anycall-tablet/
root guide is here http://mobile-hub.com/guide-how-to-root-samsung-shw-m180s-korean-anycall-tablet/
back to stock is here http://mobile-hub.com/how-to-flash-samsung-shw-m180s-korean-anycall-tablet/
After Flash it shows E:failed to mount
After i flash my Samsung Galaxy Tab SHW M180S(B) with \HOME_M180S.UC27.2041_CL1058960_REV03_user_low_ship.tar.md5
and it seccessfully pass in Odin.but after reset it shows a error message like
E:Failed to mount /Cache (Invalid Argument) what should i do now......
E:failed to mount /data (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can’t mount /cache/recovery/command
Checksum confirmation -> check(0)
Not need checksum confirmation
Already executed!!...
# MANUAL MODE #
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernal_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/reovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
stock rom i have same result, only way to fix that is by jtag, the solution i found was to bring back the internal
Ive had this phone for a month as a backup and I rooted it perfectly. Now for some reason it just stopped working. When I turn it on, it shows
Android System Recovery <3e>
Android System recovery utility
-Reboot system now
-apply update from external storage
-wipe data/factory reset
-wipe cache partition
-apply update from cache
-wipe nv partition
-toggle console VART Log
None of these work and I cant even factory reset.
On the start up, below it shows the Prompt
"Formatting /cache...
E:Format_Volume: Make_extf4fs Failed on /dev/block/platform/sdhci-tegra.3/by-name/CAC
E:failed to mount /cache (Invalid argument)
E:Can't open /cache/recovery/log
E:failed to mount /cache(invalid Argument)
E:Can't mount /cache/recovery/last_log
E:cant open cache/recovery/last_log
E; Failed to mount/cache (Invalid Argument)
E:cant mount /cache/recovery/last_install
E:cant open /cache/recovery/Last_Instal
E:can't write NV Partition.
E:can't write NV Partition.
E:can't write NV Partition.
E:can't write NV Partition.
E:failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/0 Error)
E:Failed to mount /cache (invalid Argument)
PLEASE HELP ME
How did you manage to get your phone in that state? But seriously, what did you do after rooting your phone that could cause this?
Bad thing you rooted your phone but didn't install CWM, you could recover a nandroid backup but, somethings weird here, "can't write NV partition" some people say restoring a nandroid backup fixed their issue.
Does your phone write this "E:can't write NV Partition." itself or did you choose option "Wipe NV partition" ?
As far as I know, NV partition contains IMEI etc., if the files are corrupted in there, theres nothing much you can do.
Try wiping cache partition, shouldn't be any danger in doing that, perhaps factory reset too but I don't think this'll fix your NV partition, you'll probably need to get your phone repaired and its rooted so your warranty is now void.
This problem is common among SGS3 & samsung users, but they usually can boot their phones, but can't access network.They r using some programs to re-flash their original files, they wouldn't work on our phones though.
I'm used to get such errors on my old phone. (not NV partition though cause I didn't touch it ever) These errors were usually due to using ext4 filesystem on kernels that didn't support ext4, so I guess your partitions are corrupt and your phone can't format them, did your phone sustain any physical damage lately?
Cache partition is supposed to be corrupted over time and formatted by system whenever that happens, It's easy to corrupt it but the problem with your phone is that it can't format it.
Try getting your cache partition working, perhaps you can still boot with your IMEI etc. corrupted and rescue your phone.
Try that 'KDZ firmware flash' method, most people use it to update their firmware versions but seen some people using it for unbricking their devices, however I didn't use anything other than LG pc suite so I don't know how you'd exactly do that.
It could also be that CAC file "/dev/block/platform/sdhci-tegra.3/by-name/CAC" corrupted, I don't know what that file does but it sure does have a role while formatting /cache, so firmware flashing may help with that
I'm not an expert, these are the only methods I have in my mind, good luck mate
there was none from the start. and I didnt do anything. I was just texting people.
Also do you have a skype? i need your help|
add EllisPlayist
I tried all those options, even factory reset, none of them worked
did you try to flash kdz file trough kdz flasher?
im new to all this, i need help manually. Skype pref. EllisPlayist. id love to fix my phone
aznjab said:
im new to all this, i need help manually. Skype pref. EllisPlayist. id love to fix my phone
Click to expand...
Click to collapse
Hi,
First of all what important is that you keep yourself cool. Read first and understand it then take any step.
http://forum.xda-developers.com/showthread.php?t=2179126
Try the above given link if you can reboot into software update mode.
Otherwise you can try the instruction from @RuedasLocas in Post 7.
But as far I think LG Flash Tool should do the trick for you.
Hope you will be able to do it.
All the best.
It doesnt work
I tried them and none work. please help
aznjab said:
I tried them and none work. please help
Click to expand...
Click to collapse
Specify please.
We need to know what didn't work, the process or you
Kidding... what was the result?
Hi there,
Just wanted to install a custom recovery image for the first time on this device and make a nandroid backup. Well, not everything went as expected
here's what I've done:
-unlocked the bootloader via htcdev.com [worked]
-fastboot erase cache [worked]
-installed TWRP [worked]
in TWRP I wanted to create a Backup and selected everything. However it gave me an error message that /cache couldn't be mounted (or something like that, can't remember exactly, but read on). So I tried it with CWM (again, first I erased cache with fastboot, then installed CWM) Well, these are the messages I get when I try to make a backup:
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
then it backs up boot img, recovery, system and data, which works flawlessly. Then, the error messages continue:
No /sdcard/.android_secure found. Skipping backup of applications on external storage. [seems logical, as I don't have an external sdcard]
Backing up cache...
Can't mount /cache!
Is it possible that it can't mount /cache as I erased it via fastboot? Or what could've caused the issue, and how do I resolve it? Thanks in advance.
Doesn't matter, just ignore it
EDIT: To expand on the above, if you've not booted the phone up since flashing the recovery there is no cache to backup
Didn't think the soultion was that simple haha, but thanks
/Edit:
To expand on the above, if you've not booted the phone up since flashing the recovery there is no cache to backup
Click to expand...
Click to collapse
well, that kinda explains it. thanks again.
b0ld said:
Didn't think the soultion was that simple haha, but thanks
/Edit:
well, that kinda explains it. thanks again.
Click to expand...
Click to collapse
You see, lots of nice people around
Sent from my HTC One using xda app-developers app
For reference, this bit:
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
Seems to be present in both CWM or TWRP (never used TWRP personally). It's never affected the backups I've made in the past