every time i boot into twrp for sm-t700 i get this error on the top which however doesnt effect anything
heres the error: e: unknown file system: 'ext4'
Are running f2fs?
Related
Hello,
I am trying to load CyanogenMod onto my Nexus 7 2013 (WiFi) via this guide: wiki.cyanogenmod[.]org/w/Install_CM_for_flo
I have successfully flashed the recovery partition (ClockWork Mod 6.0.4.7). However, when I boot into CWM, I am greeted with these errors:
Code:
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
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
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
I attempted to load CyanogenMod via the "push and install method", which entails mounting the /data partition. CWM errored out when trying to mount any of the following partitions:
Code:
Error mounting /system!
Error mounting /data!
Error mounting /cache!
So instead, I tried the sideloading method ("adb sideload nightly.zip"), and CWM spit back a bunch of mounting/filesystem errors:
Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
Patching system unconditionally...
failed to open /dev/block/platform/msm_sdcc.1/by-name/system: No such file or directory
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Can anybody help me out with this? Thanks!
Update:
I just tried TWRP (2.8.6.0) as an alternative to Clockwork Mod. FYI, my device is currently running stock Android 5.1 Lollipop, if that makes a difference.
I received the following errors:
Code:
E:Unable to find partition size for /boot.
E:Unable to find partition size for /recovery.
E:Unable to find partition size for /misc.
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data/' is not present!
E:Unable to mount /data.
E:Unable to find partition size for /sb11.
More similar mounting issues. Any idea what the problem could be?
Is TWRP 2.8.6.0 not compatible with Android 5.1? (Build: LMY47O)
Resolved -- Use TWRP MultiRom
I had the same issue on a number of new Nexus 7 2013 wifi devices. Turns out Google had made some firmware updates, rendering new N7 devices incompatible with KitKat stock images.
I resolved it by flashing a custom TWRP build (the MultiRom build) onto these devices. Here's the download links that someone uploaded. You need to be familiar with using fastboot on nexus 7 devices in order to flash these onto the recovery partition:
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view
As a refresher, after booting into fastboot mode (hold VolDn+Power), type 'fastboot flash recovery TWRP_multirom_flo_20150328.img'
(Thanks to csmnn for posting the original solution here: https://www.reddit.com/r/cyanogenmo...ng_cyanogenmod_onto_nexus_7_2013_wifi/cscxb93 and to masterchiefb117 for uploading the files in this forum post: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562)
Errr... This the Galaxy Nexus forums, not Nexus 7.
Sent from my Nexus 5 using Tapatalk
Hello to everyone
I have a problem when installing cm-13.0-20160305-NIGHTLY-nicki using twrp recovery. If I try to flash the zip it says:
"Installing zipfile ´/external_sd/Zips/cm-13.0-20160305-NIGHTLY-nicki.zip´
Checking for file MD5...
Skipping MD5 check: no MD5 file found
Tarjet: 1457165414
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at/system: Invalid argument
unmount of /system failed; no such volume
Patching system image unconditionally...
Verifying the updated sytem image...
system partition has unexpected contents after 0TA updated
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/Zips/cm-13.0-20160305-NIGHTLY-nicki.zip/´
Updating partition details...
Failed to mount ´/system´ (Invalid argument)
Failed to mount ´/cache´ (Invalid argument)
....done"
Does anyone know what is the problem and how to solve it?
LinuxHacker said:
Hello to everyone
I have a problem when installing cm-13.0-20160305-NIGHTLY-nicki using twrp recovery. If I try to flash the zip it says:
"Installing zipfile ´/external_sd/Zips/cm-13.0-20160305-NIGHTLY-nicki.zip´
Checking for file MD5...
Skipping MD5 check: no MD5 file found
Tarjet: 1457165414
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at/system: Invalid argument
unmount of /system failed; no such volume
Patching system image unconditionally...
Verifying the updated sytem image...
system partition has unexpected contents after 0TA updated
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/Zips/cm-13.0-20160305-NIGHTLY-nicki.zip/´
Updating partition details...
Failed to mount ´/system´ (Invalid argument)
Failed to mount ´/cache´ (Invalid argument)
....done"
Does anyone know what is the problem and how to solve it?
Click to expand...
Click to collapse
Download zip file again.
It was that I bricked the mobile.
hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?
Which version of twrp do you use?
i use Twrp 2.8.7.3
Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?
its CN
sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/
that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.
Long history: I was using Ivan_Meler CM 13.1 ROM for ~ 3 months, which was very stable. Last week I downgraded from build 10 to build 9 with only dirty flash and everything was working fine, just some occasionally FC. Then one night I left my phone ran on very low battery and when I woke up I found my GT-N7100 stuck on Samsung boot logo.
I'm still able to access ODIN download mode. When I get into recovery mode (CWM Philz Touch v6.26.6), I immediately get this messages:
E: could not mount /data to setup /data/media path!
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
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install
What I've tried so far:
1. Restore Nandroid backup (KOT49H.N7100UBUFNK1) using CWM
->>>>> got E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p13
2. Flash, using both adb sideload and ODIN:
Stock ROM 4.3 (N7100UBUEMK4_N7100ZTOEMK3_ZTO) and 4.4 (N7100UBUFNK1_N7100ZTOFNK1_ZTO), downloaded from Sammobile
->>>> got "NAND write fail" on ODIN and
->>>> on adb sideload the file loads 100% but I got "error:closed" and after "failed to write data 'protocol fault (no status)' "
3. Flash only the hidden.img of the stock ROM's mentioned above, I got "PASS" on ODIN but after phone gets stuck on boot Samsung logo
Tried this guide, using stock 4.1.2 (N7100XXDLJ2_OXA_FACTORY) with and without re-partition
->>>> got "NAND write fail" as well.
So I have ran out of options can anybody please help :crying::crying::crying: I really like my Note 2 and I don't have money to buy a new phone right now.
SDS for 99%
Try flashing the latest stock rom using a different USB cables, different versions of Windows, and different USB ports. If none of these work, the memory chip may be damaged.
Hello
I have a mini s4 gt-I9192 with error: E: failed to mount / system (Invalid argument)
is there a way to restore but can not access the custom recovery mode after having successfully rooted and installed the custom recovery
Only starts in donwloading mode or logo.
I need to know if anyone has had this error and if no way to fix it or enter custom recovery
Thanks