TWRP won't start after updating from 3.3.. to 3.4.0-0 using fastboot. Output includes "Failed to mount '/data'" - see following post.
I guess because I accidentally ran fastboot unlock although it was already unlocked. (The TWRP website fastboot update procedure starts right back with installing the tools and I jumped in at the wrong place)
Tried installing previous TWRP version but no dice.
Any ideas?
I did a TWRP backup before all this. Not exactly sure where it's located but would like to recover it if possible. Will a factory reset likely overwrite it?
Lenovo P2 LineageOS 17.1 Kuntao
Output when booting to recovery:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Unable to mount storage
Failed to mount '/data' (Invalid argument)
fs_mgr_mount_all
Full SELimux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands
Failed to mount '/data' (Invalid argument)
Formatting cache using mke2fs...
Done.
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
Related
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.
Hi there !
I have an Ascend Mate(M1-U06) here which stopps booting, first it shows the Huawei logo, then a white android logo - thats all.
When i enter recovery mode it works, the phone shows me this line:
""""
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
""""
Flashing or wiping in this menu fails.
Meanwhile I'm familiar with adb/fastboot.
Drivers are installed(Win10), phone is recognised, bootloader is unlocked.
I tried flashing several images, I tried flashing TWRP, everything worked well but nothing changed.
After flashing TWRP 2.6.3.3 I enter recovery mode and there is still stock recovery mode(3e).
What am I doing wrong, did i forget something ?
Can i use every TWRP Version for the mate ?
Tried to flash stock rom without success.
any ideas
thanks in advance
VirtuAl
Hello everybody,
I'm facing an issue with my phone. I was running Fulmics Rom 6.1 on my LG G3 for a few days, when, this morning, I woke up to find my device caught in a bootloop. I had a recent TWRP backup, so I tried to restore it, but it failed with the error : "Unable to wipe System".
I tried to wipe everything but my SD Card and got :
Code:
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
I tried to use "Format Data" in TWRP Wipe Section, but got :
Code:
[B]Unable to open '' to wipe crypto key[/B]
Unable to wipe Data.
[B]Unable to format to remove encryption.[/B]
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Flashing the Rom again fails as well as it stays stuck at this step :
Code:
Install new system
Extract:/tmp/unpackbootimg
I'm using TWRP 3.0.0-0.
Any idea about what I could do next ?
Thanks a lot.
my model is FIRE TV 2, it boot loops (amzon logo
then will eventually display this twrp screen
and Runing OpenRconveryScript screen then will
loop).
OpenRconveryScript screen:
failed to mount '/data'(Invalid argument)
Unable to recreate /data/media folder.
Updating parititon details...
Failed to mount '/data'(Invalid argument)
...done
Unable to mount storage
full SELinux support is present.
Running boot script...
Done.
Unable to mount /data/media/TWRP/.twrps
Runing Recovery Commands
Failed to mount '/data'(Invalid argument)
Formatting Cache using make_ext4fs...
Failed to mount '/data'(Invalid argument)
Done processing script file
Online wait for guidance
maleclub said:
my model is FIRE TV 2, it boot loops (amzon logo
then will eventually display this twrp screen
and Runing OpenRconveryScript screen then will
loop).
OpenRconveryScript screen:
failed to mount '/data'(Invalid argument)
Unable to recreate /data/media folder.
Updating parititon details...
Failed to mount '/data'(Invalid argument)
...done
Unable to mount storage
full SELinux support is present.
Running boot script...
Done.
Unable to mount /data/media/TWRP/.twrps
Runing Recovery Commands
Failed to mount '/data'(Invalid argument)
Formatting Cache using make_ext4fs...
Failed to mount '/data'(Invalid argument)
Done processing script file
Online wait for guidance
Click to expand...
Click to collapse
Can you pop in a USB flash drive or micro sd with a pre rooted ROM and flash?
My realme 6 pro is broken, it does not allow me to install anything through twrp, or flash the stock roms, I tried using a different twrp and the error still persists, the operating system was deleted, so I cannot turn on the phone, it was trying to install a new custom rom, but no longer possible
The following is the copy of the twrp record, without having performed any action
E:Unable to decrypt FBE device
Updating partition details...
...done
Updating partition details...
...done
**********************************
PicthBlack Recovery: Welcome! ^_^
Maintained By PBRP Team
**********************************
Encryption Status : unencrypted
MTP Enabled
Failed to mount ´/system_root´(Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
Update partition details...
Failed to mount ´/system_root´ (Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
...done
Failed to mount ´/system_root´(Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
E:Unable to open ´/system_root/
Full SELinux support is present
ps: i'm kinda new and i really have no idea how to fix this please someone help me
Attached pictures of the device status
Which recovery Better Between TWRP or PBRP?