Hi ,
Today when i want to use my phone he was rebooting and he doesn't boot , when i go to the Recovery it tells me :
-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
and i can't install rom , i can go to fastboot but when i want to install rom or erase partition it tells me "failed (remote failed to erase partition)"
Thanks for helping !!!
Anyone that knows about partitions able to help him out?
I still have the same problem..
sachou75 said:
Hi ,
Today when i want to use my phone he was rebooting and he doesn't boot , when i go to the Recovery it tells me :
-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
and i can't install rom , i can go to fastboot but when i want to install rom or erase partition it tells me "failed (remote failed to erase partition)"
Thanks for helping !!!
Click to expand...
Click to collapse
did you try flashing recovery through fastboot?
yes and i have "failed (remote failed to erase partition)"
sachou75 said:
yes and i have "failed (remote failed to erase partition)"
Click to expand...
Click to collapse
I would try to boot a recovery image via ADB and try your luck from inside the recovery
if that doesn't work you should google fixes for "-E: Can't mount /cache/recovery/command " and see what people did to fix the issue on other devices
it's also quite possible your emmc is fried
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
It seems to be pressing volume keys all the time, hence might be going into fastboot mode
stoppnadav said:
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
Click to expand...
Click to collapse
Download TWRP file and flash it via fastboot. Then try a custom ROM. While flashing the file you can try fastboot boot twrp.img to boot into recovery. Then when TWRP opens up it will grant access to the storage, copy the files for flashing a custom ROM, don't forget the firmware zip file too. Try this if it helps.
Regards,
Sharan
sharan.nyn said:
Download TWRP file and flash it via fastboot. Then try a custom ROM. While flashing the file you can try fastboot boot twrp.img to boot into recovery. Then when TWRP opens up it will grant access to the storage, copy the files for flashing a custom ROM, don't forget the firmware zip file too. Try this if it helps.
Regards,
Sharan
Click to expand...
Click to collapse
Is there any other way to flash TWRP via fastboot without using ADB? I had USB Debugging Off in my device, before it got stuck in a boot loop. I can only access FASTBOOT and RECOVERY .
zak31 said:
Is there any other way to flash TWRP via fastboot without using ADB? I had USB Debugging Off in my device, before it got stuck in a boot loop. I can only access FASTBOOT and RECOVERY .
Click to expand...
Click to collapse
Actually we don't use ADB to flash the recovery. We always use FASTBOOT. The commands are to be ran when booted in fastboot mode. Just make sure that all the required drivers are installed or the phone will reboot at FASTBOOT mode if it is not detected by your computer.
ADB drives showing error code 10
sharan.nyn said:
Actually we don't use ADB to flash the recovery. We always use FASTBOOT. The commands are to be ran when booted in fastboot mode. Just make sure that all the required drivers are installed or the phone will reboot at FASTBOOT mode if it is not detected by your computer.
Click to expand...
Click to collapse
That's what is happening with me I think. I have installed all the ADB drivers required. When I go to Device manager, those drives show little yellow triangles with a !. I proceed to update them, they get updated but error code 10 shows up. Also, now my device isn't getting detected by my computer, and rebooting at FASTBOOT mode continuously. Sometimes, it does get detected by the computer. I enter into FASTBOOT mode and I start the flashing with MiFlash, then the device reboots itself. Please help.
zak31 said:
That's what is happening with me I think. I have installed all the ADB drivers required. When I go to Device manager, those drives show little yellow triangles with a !. I proceed to update them, they get updated but error code 10 shows up. Also, now my device isn't getting detected by my computer, and rebooting at FASTBOOT mode continuously. Sometimes, it does get detected by the computer. I enter into FASTBOOT mode and I start the flashing with MiFlash, then the device reboots itself. Please help.
Click to expand...
Click to collapse
Install Mi suite. Probably that will solve the issue. ... hopefully. :silly:
I am also facing similiar problem..... after flashing twrp when rebooting twrp via fastboot teturns error dtb not found...... if someone can help
i have the same problem,
I try to flash with any version of rom,
when i see the fastboot device info,
the bootloader status
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
then i do bootloader unlock,
and the bootloader status become
(bootloader) Device unlocked: true
Click to expand...
Click to collapse
but after fastboot reboot,
the status of bootloader become false again,
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
anyone know what shoult i do?
stoppnadav said:
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
Click to expand...
Click to collapse
Were you able to solve this problem?. I have the same issue since past week. MiFlash works, tried fastboot commandline flashing, device restarts to fastboot only.
loaded twrp, unfortunately internal memory 0mb.
Hi guys,
+1 from me
I've totally screwed up ferrari.
Scenario: I was on Resurrection Remix 5.8.5 For some reason, I've started storage encryption. Probably it wasn't successful, and on next reboot, I've got error "Decryption unsuccessful, your password is ok, but data partition is corrupted, blah, blah, blah. I've successful rescued my storage files:
Code:
boot into TWRP:
adb pull /dev/block/mmcblk0p36
then, mounted mmcblk0p36 partition file under Linux on my PC (example):
sudo mkdir /mnt/data
sudo mount /home/stiw47/mmcblk0p36 /mnt/data
Whoala, few files was corrupted, but all from android internal storage (my personal files) was rescued.
Ok. After this, I've performed factory reset on phone, but device going to fastboot, not in Android OS. TWRP says that /data cannot be mounted.
I flashed latest MIUI from fastbot
Reboot
device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted.
Variable : In following text, "same" is equal to "device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted."
I've tried to flash fastboot ROM zilion times - same
Tried to flash from MI PC Suite - same (MI Suite giving "success" info)
XiaoMI Flash Tool - same (tool giving success info)
Was want to flash with QFIL (Qualcomm Flash Image Loader), after several Qualcomm Xiaomi driver installation, founded here and there over the internet, on two different PCs - No COM port detected, both in QFIL and in Device Manager
[*]Wipe from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Format Data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Repair or change file system from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Mount system cache data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]TWRP => Advanced => Terminal:
Code:
Example:
mount -o remount,rw /dev/block/mmcblk0p36 /data
giving error:
mount: '/data' not in /proc/mounts
(same for adb)
/proc/mounts is pretty empty (wtf)
Code:
adb shell
cat /proc/mounts
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=949708k,nr_inodes=237427,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=949708k,nr_inodes=237427 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
And here is the question
Can someone, please, upload /proc/mounts file here, I would like to do:
Code:
adb push mounts /proc/mounts
After that, I will try to reformat partitions with parted.
Of course, if someone has some more elegant solution, I'm listening, thanks in advance.
Notice: Sorry cause kilometer post, I was want to full explain that I've really tried every usual method to alive a phone. I suppose that first ~6 answers and propose would be - "Flash fastboot ROM", but this not helping in this stage.
Same problem with my MI4I
stiw47 said:
Hi guys,
+1 from me
I've totally screwed up ferrari.
Scenario: I was on Resurrection Remix 5.8.5 For some reason, I've started storage encryption. Probably it wasn't successful, and on next reboot, I've got error "Decryption unsuccessful, your password is ok, but data partition is corrupted, blah, blah, blah. I've successful rescued my storage files:
Code:
boot into TWRP:
adb pull /dev/block/mmcblk0p36
then, mounted mmcblk0p36 partition file under Linux on my PC (example):
sudo mkdir /mnt/data
sudo mount /home/stiw47/mmcblk0p36 /mnt/data
Whoala, few files was corrupted, but all from android internal storage (my personal files) was rescued.
Ok. After this, I've performed factory reset on phone, but device going to fastboot, not in Android OS. TWRP says that /data cannot be mounted.
I flashed latest MIUI from fastbot
Reboot
device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted.
Variable : In following text, "same" is equal to "device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted."
I've tried to flash fastboot ROM zilion times - same
Tried to flash from MI PC Suite - same (MI Suite giving "success" info)
XiaoMI Flash Tool - same (tool giving success info)
Was want to flash with QFIL (Qualcomm Flash Image Loader), after several Qualcomm Xiaomi driver installation, founded here and there over the internet, on two different PCs - No COM port detected, both in QFIL and in Device Manager
[*]Wipe from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Format Data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Repair or change file system from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Mount system cache data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]TWRP => Advanced => Terminal:
Code:
Example:
mount -o remount,rw /dev/block/mmcblk0p36 /data
giving error:
mount: '/data' not in /proc/mounts
(same for adb)
/proc/mounts is pretty empty (wtf)
Code:
adb shell
cat /proc/mounts
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=949708k,nr_inodes=237427,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=949708k,nr_inodes=237427 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
And here is the question
Can someone, please, upload /proc/mounts file here, I would like to do:
Code:
adb push mounts /proc/mounts
After that, I will try to reformat partitions with parted.
Of course, if someone has some more elegant solution, I'm listening, thanks in advance.
Notice: Sorry cause kilometer post, I was want to full explain that I've really tried every usual method to alive a phone. I suppose that first ~6 answers and propose would be - "Flash fastboot ROM", but this not helping in this stage.
Click to expand...
Click to collapse
Did you find any solutions for this. I have tried every single method mentioned above and getting same errors mentioned above like unable to mount/invalid cache/invalid data etc....
nepya1009 said:
Did you find any solutions for this. I have tried every single method mentioned above and getting same errors mentioned above like unable to mount/invalid cache/invalid data etc....
Click to expand...
Click to collapse
Hi,
Yes, I found solution, I bought MI 6
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
E:failed to mount /data
Cannot mount /data and unable to find crypto footer.
E:failed to mount /cpefs
Click to expand...
Click to collapse
HELP ME!
natanjuniors said:
hi!
I have trouble when i put twrp and make wipe cache, system and dalvik. The phone gives me the following information:
Help me!
Click to expand...
Click to collapse
Format Data
natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format data and fully wipe
You just erase or deleted files on your internal memory. But no biggie, just flash firmware with Odin (on windows) heimdall (on Linux).
Sent from my SM-J700P using Tapatalk
natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format Data ... Yes ...
JHAM2005 said:
Format Data ... Yes ...
Click to expand...
Click to collapse
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
Ignore the cpefs error, it's erroneous and will be fixed.
As long as you can mount data you are good.
Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
How to ... Unlock Memory and have Root on the J710MN with Nougat 7
https://forum.xda-developers.com/ga...d-7-nougat-t3674417/post73826249#post73826249
hey i have solution
first 1. flash letest twrp
2.flash magisk 19.2
3. reboot system
100% done
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
goister said:
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
Click to expand...
Click to collapse
Enabling the OEM Unlock option is the first step but it doesn't unlock the phone. It merely enables unlocking the phone. You have to use a specific adb command to unlock the phone. Since the command varies with models and I am not familiar with your phone, please search for the correct command on Google.
Thanks. I'm following this page - https://www.xda-developers.com/how-to-install-twrp/
I managed to unlock it with fastboot, but I can't seem to flash the recovery. I downloaded the TWRP image from https://dl.twrp.me/sailfish/twrp-3.7.0_9-0-sailfish.img.html and renamed it to twrp.img. I then performed the following steps as per the instructions from xda above:
booted to bootloader with adb reboot bootloader
Temporarily booted to TWRP with fastboot boot twrp.img
Copied TWRP image file to device with adb push twrp.img /sdcard
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
I get the following error
Updating partition details...
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot...
/sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1
Error repacking image.
I tried to mount vendor partition, wipe and format the device and retry step 4 and made it a bit further (no more failed to mount '/system_root' and '/vendor' errors, as below, but still fails.
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot... /sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1 Error repacking image.
Any suggestions?
goister said:
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
Click to expand...
Click to collapse
You can download both the .img and the .zip files. After booting using the .img file, instead of step 4 above, you can try Install from the booted TWRP and navigate to where the .zip file is and simply install it. That is what the TWRP page for Pixel recommends:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse
Damn...why did the xda instructions say otherwise?
OK so I managed to reflash to stock image again after the boot loop, and then I followed the TWRP instructions. I was prompted to enter the device password when booting up to TWRP temporarily, and was able to get to TWRP once I entered my device PIN.
After I installed the zip file, I get the following screen:
Installing zip file '/sdcard/twrp.zip'
Updating partition details...
...done
Attempting to decrypt FBE for user 0...
User 0 Decrypted successfully
Data successfully decrypted
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Installing zip file '/sdcard/twrp.img'
Unmounting system...
########################################
# TWRP Installer for A/B devices #
########################################
Unpacking the installer...
Running image patcher on boot_a...
Running image patcher on boot_b...
Image patching complete!
Done installing TWRP!
*** NOTE: You are now unrooted! ***
Updating partition details...
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
After this, it reboots to Android fine, but whenever I try to reboot to recovery, it goes to the white screen with the Google logo, then reboots to Android.
I'm using the latest TWRP for sailfish - twrp-installer-3.7.0_9-0-sailfish.zip.
Any ideas why?