Good night,
I have an ASUS Z010D device that entered a loop, when entering the recovery mode it throws a message E: / I Can't Mount / Cache also when applying any option in the menu it throws a mount error in the E: drive and several directories.
I have tried various commands in adb and fastboot but have not been successful.
Important: the bootloader locked and I have not managed to unlock it since the computer does not start the operating system.
Thanks for the support you can give me!
@jesusz24
Seems to be a TWRP related problem. Or partition /cache doesn't exist.
answer
jwoegerbauer said:
@jesusz24
Seems to be a TWRP related problem. Or partition /cache doesn't exist.
Click to expand...
Click to collapse
hi jwoegerbauer,
if apparently it is a recovery problem.
The cache partition allows me to format it without any problem through fastboot, which seems strange to me.
The problem really is that I can't root the computer or unlock the bootloader before it loops.
at the moment it does not let me install the twrp to try to distribute.
Do you have any procedure to unlock the bootloader?
thanks for him
@jesusz24
Never have installed TWRP or any other custom recovery on the mobile devices I have and/or I had, hence can't help you with your TWRP problem.
Related
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
sasawatd said:
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
Click to expand...
Click to collapse
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Lgrootnoob said:
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Click to expand...
Click to collapse
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
sasawatd said:
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
Click to expand...
Click to collapse
Driver issue?
Syntax for fastboot stuffz
try flashing:
Code:
fastboot flash recovery recovery.img
If flashing isn't working then try booting it directly
Code:
fastboot boot recovery.img
I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?
dakimMastamynd said:
I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?
Click to expand...
Click to collapse
When you flashed recovery did you fastboot erase cache after you flash it and before you rebooted? If not, you need to do that to clear out any thing left from the last recovery.
Which custom recovery are you using with the version number?
What was the RUU version and where did you get it?
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Gleichzwei said:
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Click to expand...
Click to collapse
Boot to bootloader, and enter the following commands:
fastboot format cache
fastboot format userdata (NOTE THAT THIS WILL WIPE THE CONTENTS OF YOUR SDCARD)
fastboot reboot
Hi I have installed miui 8 lollipop cn dev whith UB. When I install any recovery, first time there is a error shows that can not mount internal storage and second time when I reboot to recovery it shows it cant mount system. Plz note that I have wiped userdata after flashing twrp in fastboot and also have tried without data wiping. After second recovery reboot, system wont boot. I dont have hte same problem on mm firmware.
Errors:
Failed to mount /sdcard
Failed to mount system(invalid argument)
RE
SMYM said:
Hi I have installed miui 8 lollipop cn dev whith UB. When I install any recovery, first time there is a error shows that can not mount internal storage and second time when I reboot to recovery it shows it cant mount system. Plz note that I have wiped userdata after flashing twrp in fastboot and also have tried without data wiping. After second recovery reboot, system wont boot. I dont have hte same problem on mm firmware.
Errors:
Failed to mount /sdcard
Failed to mount system(invalid argument)
Click to expand...
Click to collapse
1) Try to flash ALKA Recovery OR
2) Dload ANDROID IMAGE KITCHEN extract boot.img from rom you want to flash put it in AIK Folder extract then open folder RAMDISK and edit file fstab.qcom where you will find ( ,verify ) delete this and then you will find (forceencrypt) change it to encryptable repack boot.img and flash it via fastboot this might solve your problem if anything goes wrong simply flash original boot.img
Hi
I'm running TWRP 3.3.1 and am rooted. I have no ADB sideload, at least it appears to be loading but does nothing.
I think the problem(you tell me)is that TWRP repeatedly shows the /data partition as not mounting e.g. 'Failed to mount /data (invalid argument)'. Whenever one attempts to carry out a process with TWRP this always comes up.
I have tried the following:
1) Repair the partition with e2fcsk
2) Change the filesystem to fat or ext3 and then back to ext4.
3) Wipe the partition
Still no go. This can't be normal. I should say I'm running ADB and Fastboot from linux and all commands work so it can't be a driver problem. The device is being seen.
I have googled this but there are no clear answers.
thanks
Cliff
cliffhanger54 said:
Hi
I'm running TWRP 3.3.1 and am rooted. I have no ADB sideload, at least it appears to be loading but does nothing.
I think the problem(you tell me)is that TWRP repeatedly shows the /data partition as not mounting e.g. 'Failed to mount /data (invalid argument)'. Whenever one attempts to carry out a process with TWRP this always comes up.
I have tried the following:
1) Repair the partition with e2fcsk
2) Change the filesystem to fat or ext3 and then back to ext4.
3) Wipe the partition
Still no go. This can't be normal. I should say I'm running ADB and Fastboot from linux and all commands work so it can't be a driver problem. The device is being seen.
I have googled this but there are no clear answers.
thanks
Cliff
Click to expand...
Click to collapse
I'm going to try downgrading TWRP
I'm going to try downgrading TWRP
cliffhanger54 said:
I'm going to try downgrading TWRP
Click to expand...
Click to collapse
Seems to have worked . Why? This was on Huawei 5c
Cliff
cliffhanger54 said:
Seems to have worked . Why? This was on Huawei 5c
Cliff
Click to expand...
Click to collapse
Seems I was premature. Mounting of /data cured, sideload not still doesn't work