Question Cannot flash most ROMs - Failed to mount after install

Search This thread

TWeaKoR

Senior Member
Nov 3, 2011
68
17
Samsung Galaxy S6
Xiaomi Poco F3
I'm having difficulty flashing ROMs and not sure how to fix it. I've tried several over the last few months and had issues with all of them, sometimes the same issue. These are the ones I've tried in the last couple days:
  • Syberia
  • crDroid
  • Arrow
  • LineageOS(4MicroG)
It started a few months ago with one of the updates to Syberia. I was running Syberia, and had a notification for an OTA update. The update failed and put me back in the old Syberia partition. I then started trying to flash other things, and after that I couldn't even get the older versions of Syberia to boot.

The install goes fine, however after step 2/2 I get the following errors:
Failed to mount 'system_root' (Invalid argument)
Failed to mount 'system_ext' (Invalid argument)
Failed to mount 'product' (Invalid argument)
Failed to mount 'vendor' (Invalid argument)

I've been using MiFlash 2020.3.14.0 to restore back to stock EEA v13.0.7.0, and also flashed firmware EEA v13.0.3.0, however I've also tried some others along the way. Also using SKKK's TWRP V3.4, or whatever each ROM has suggested in its install instructions.

These are the problems I'm having with the ROMs above:
  • Syberia - bootloops back into recovery
  • crDroid - bootloops back into recovery
  • ArrowOS - works, screen flickers sometimes though, not my preferred ROM as no traffic indicators
  • LineageOS - boots, little bit unstable, USB OTG does not recognise my larger thumbsticks
I get the feeling this isn't a ROM issue, rather something with my device - particularly when multiple ROMs are having the same issue.

One other thing I've noticed, my Fastboot logo has changed. Instead of the little Chinese dude pulling apart an Android, it just says in faint orange text "Fastboot". When I first started tinkering this problem somehow it went back to the old logo but then it changed again on another reboot. I'm concerned that something has tampered with my unlocked bootloader, but maybe that's just paranoia.

Does anyone have any suggestions on what to try?
 

NOSS8

Recognized Contributor
  • Like
Reactions: TWeaKoR

NOSS8

Recognized Contributor
Thanks, I'd thought there was a new version however I didn't find it before.

No luck though, got the same errors. Took a logcat this time:
Part 1: https://pastebin.com/tkqvZvBe
Part 2: https://pastebin.com/U4q9QKLJ
Twrp/wipe format data write yes /reboot twrp flash rom.
If still the same, install with this tool the rom corresponding to the firmware of the one you want to install.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
 
  • Like
Reactions: TWeaKoR

DarthJabba9

Recognized Developer
May 5, 2014
3,962
3,938
Greater London
Thanks, I'd thought there was a new version however I didn't find it before.

No luck though, got the same errors. Took a logcat this time:
Part 1: https://pastebin.com/tkqvZvBe
Part 2: https://pastebin.com/U4q9QKLJ
1. Format data (with typing "yes")
2. Wipe cache/dalvik
3. Flash ROM
4. Reflash recovery ("Flash current TWRP" / "Flash current OrangeFox" - or, when flashing the ROM, tick "Reflash ... after flashing a ROM")
5. Format data (again)
6. Reboot to Android

PS: the recovery log (/tmp/recovery.log) would provide useful information
 
  • Like
Reactions: TWeaKoR

TWeaKoR

Senior Member
Nov 3, 2011
68
17
Samsung Galaxy S6
Xiaomi Poco F3
Right, so I managed to get it to boot into Syberia, then lost it again.

I forgot to install TWRP after flashing, it bootlooped me into Syberia's AOSP recovery, and I was able to format in here. Rebooting afterwards launched Syberia. However, when I flashed TWRP again (and then Magisk) it broke and just bootlooped over and over (had to manually go into recovery instead of being thrown into it).

Twrp/wipe format data write yes /reboot twrp flash rom.
If still the same, install with this tool the rom corresponding to the firmware of the one you want to install.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
MiFlash20220507 didn't work for me, it throws up errors that it can't access its own log file, both when trying to install drivers or find devices. MiFlash 2020-3-14-0 works fine however. I downloaded and flashed EEA 13.0.8.0 this time.

1. Format data (with typing "yes")
2. Wipe cache/dalvik
3. Flash ROM
4. Reflash recovery ("Flash current TWRP" / "Flash current OrangeFox" - or, when flashing the ROM, tick "Reflash ... after flashing a ROM")
5. Format data (again)
6. Reboot to Android

PS: the recovery log (/tmp/recovery.log) would provide useful information
In the past I've tried formats both before and after flashing with no luck.

This time, after flashing stock I Fastboot flashed the latest TWRP, then tried to format, but got the errors:
Failed to mount '/data' (Invalid argument)
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Doing a factory reset instead of format gave the same errors, without the 'Unable to format' line.

When I then flashed the ROM, I didn't get the 4 errors I had previously, only 1 error for /data. However rebooting to system still bootlooped the same, until an AOSP recovery format.

It seems like the issue is with the TWRP format step? It's strange that TWRP format doesn't work but AOSP recovery's does.

I forgot to get logs the first time, but I ran through it all again (back to stock and flashing in TWRP).

Recovery: https://pastebin.com/sU4LCcZQ
Logcat P1: https://pastebin.com/4pfLJ0pn
Logcat P2: https://pastebin.com/QLnahBjb
 

TWeaKoR

Senior Member
Nov 3, 2011
68
17
Samsung Galaxy S6
Xiaomi Poco F3
Wahey, got there in the end! Flash with Orangefox, then format data (otherwise on the reboot it will be encrypted). I then had a bit of an issue - I bent and borked the only USB OTG adapter I have with me. However I managed to dig out a flash drive with USB-C, it's a little dodgy but it got the files across to flash add-ons.

Orangefox is nice, and it seems a little more robust and better at handling the a/b partitions than the TWRPs I've tried previously.

Now all I need to do is get a working MicroG setup, then I'll be golden.
 
  • Like
Reactions: DarthJabba9

Top Liked Posts