Updating partition details... Failed to mount vendor (invalid argument)
The error above is one I faced today and I resolved. I decided to share this in case anyone else runs into a similar issue. There are very few ways you could end up unable to correctly boot a partition but the most common is a bad flash. In my particular case, it was my own stupidity, and it could have been a lot worse given that I mistakenly flashed a vendor image file to /vendor/ except it was for a completely different device and not meant for the Moto x4 (basically got confused between files from another project).
The result of this was that my phone could not technically boot on its own. Neither into a GSI/ROM or into Recovery either. I saw the first "Android One" logo, followed by the message warning that my phone was unlocked, followed by the second "Android One" logo, which was all normal up to that point, but I would remain forever stuck at that screen. I could thankfully reach the bootloader screen, but again, since I could not boot at all, I could not even boot into Recovery from the bootloader screen.
Thankfully, because I could still reach bootloader I could temporarily load into TWRP using fastboot
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view and installed
Rebooted back to bootloader and while at bootloader, I loaded the Android 8.1 firmware - courtesy @ptn107 https://androidfilehost.com/?fid=890278863836292604
From bootloader, I reloaded the bootloader again
This alone did not resolve my issue. I once used fastboot to temporarily load TWRP
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Installed TWRP https://dl.twrp.me/payton/
Installed LineageOS ROM -- It must be a full ROM and not a GSI. It must be specifically made for Moto x4 and not just a generic GSI (stock rom for example)
Reinstalled TWRP
Reboot
During the installs, you may still see the error. Ignore them as they will go away after the reboot. This will resolve such issues should you ever face them.
MotoX4 said:
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oir...t2eSGKt0F/view and installed
Click to expand...
Click to collapse
Fix google drive link, pls
Comby_sk said:
Fix google drive link, pls
Click to expand...
Click to collapse
Fixed in post #1 and full URL without text formatting is also here too
Code:
https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Related
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?
When i try to install zip package with weekly miui12 (unnoficial TWRP) i forgot to mount partitions and now i can't mount it anymore. Try to tick it but nothing happened.
So I can't install any package. Do I brick my device?
Is there any posibbility to mount those partitions?
Twrp errors:
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/odm' (invalid argument)
Are you trying to install Chinese weekly rom?
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
ZeroSherd said:
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
Click to expand...
Click to collapse
I jist flash fastboot rom twice and everything is ok xD
Is there a solution this error? I'm having the same problem.
I have the same problem. Can anybody help?
edit file rom, extract rom .zip, edit updater-script and delete first line. save and make file zip again.
tested rom global stable beta.
how edit updater-script,
https://forum.xda-developers.com/showthread.php?t=2522762
do my tutorial to get the phone and then start again, it's in Spanish but it's simple.
https://www.htcmania.com/showthread.php?t=1565656
you have to install the recovery "TWRP-3.4.2B-0623-REDMI_K30PRO-CN-wzsx150-fastboot.zip" and with that you will not have errors, the twrp of this website gives errors
i have the same problem How i can flash miui china beta on F2 Pro from twrp?
Koziol87 said:
I jist flash fastboot rom twice and everything is ok xD
Click to expand...
Click to collapse
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Latin_lion_ said:
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Click to expand...
Click to collapse
Did you use miflash?
NOSS8 said:
Did you use miflash?
Click to expand...
Click to collapse
yh BUT for some strange reason i cant flash the latest stock rom on my device arb error ive tried everything hoping to find help im new to this first phone ive tried to install custom roms on
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
cxm05 said:
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
NOSS8 said:
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
Click to expand...
Click to collapse
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
cxm05 said:
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
Click to expand...
Click to collapse
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
NOSS8 said:
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
Click to expand...
Click to collapse
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
in flash folder of rom, you have flashall.bat open it in txt format, find two rows that contain CRC and delete it, save file and than try to flash rom again. it will pass. I have the same CRC error and deleting this two row help me to flash rom
NOSS8 said:
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
Click to expand...
Click to collapse
The MI Assistant version is 3.2.522.32 beta. Once I start the Mi Assisant client on my phone and then plug my cable, the application prompts me to select a Fastboot ROM on my harddrive. ONce I select a valid imag, it flashes my phone and then reboots. After loading for 15 minutes or so, the phone reboots to the MI recovery where I can select to use Mi Assistant again.
This time, Mi Assistant detects the version of ROM I have installed and advises there is a newer ROM. On this screen I select the first button (which I believe downloads the image from MI server) or the sencond button (which allows me to select a local Recovery ROM stored on my hard drive).
Regardless of which option I choose, the 2nd flash occurs and my phone reboots again. in A cycle until I have the most recent ROM on the phone and it still sits at the MIUI boot screen for 30 minutes. I've gone from 11.2.0.9 ==> 12.2.0.4 ==> 12.2.2.4. All successfully flash to the phone but phone never boots past the MIUI logo.
I've even gone as far as flashing a beta ROM 12.2.2.5 on top of the latet stable version using MI Assistant (flash runs successfully ut phone still never boots).
I have also gone into bootloader mode & flashed the TWRP version you recommended. After botting into this recovery, I can "factory reset" the phone and the sideload the HK 12.2.0.3 rom you provided. The sideload flashes to the phone with no errors, but phone still doesn't boot past the MIUI logo
Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.
Hey all!
I've been trying to install TWRP on my google pixel (32 GB/ 4GB). It runs Android 10, has an encrypted filesystem and the boot loader is unlocked. I booted into fastboot mode, then used fastboot boot twrp.img to boot into TWRP and it worked perfectly fine. Then, after decrypting, I tried flashing the TWRP zip I had on my phone. But it failed to do so, giving these errors - Failed to mount /system_root (invalid argument); Failed to mount /vendor (invalid argument). When I checked the mounted partitions in TWRP, system and vendor were unchecked and I couldn't check them.
Next, I tried to use fastboot flash recovery to flash the TWRP image directly from fastboot but this didn't work either.
Finally, I tried to flash a TWRP image after booting to TWRP. I chose the install to recovery ramdisk option but it didn't install, giving me the same failed to mount errors.
So right now I'm stuck at this point. Any help will be really appreciated
Thanks
-Keith
keith-james said:
Hey all!
I've been trying to install TWRP on my google pixel (32 GB/ 4GB). It runs Android 10, has an encrypted filesystem and the boot loader is unlocked. I booted into fastboot mode, then used fastboot boot twrp.img to boot into TWRP and it worked perfectly fine. Then, after decrypting, I tried flashing the TWRP zip I had on my phone. But it failed to do so, giving these errors - Failed to mount /system_root (invalid argument); Failed to mount /vendor (invalid argument). When I checked the mounted partitions in TWRP, system and vendor were unchecked and I couldn't check them.
Next, I tried to use fastboot flash recovery to flash the TWRP image directly from fastboot but this didn't work either.
Finally, I tried to flash a TWRP image after booting to TWRP. I chose the install to recovery ramdisk option but it didn't install, giving me the same failed to mount errors.
So right now I'm stuck at this point. Any help will be really appreciated
Thanks
-Keith
Click to expand...
Click to collapse
You should indicate which image you are booting and flashing. There are several and from what I gather, not all are compatible with 10.
Tulsadiver said:
You should indicate which image you are booting and flashing. There are several and from what I gather, not all are compatible with 10.
Click to expand...
Click to collapse
Hello! Thank you so much for the reply. I was flashing and booting twrp 3.5.1_9-0 for sailfish.
keith-james said:
Hello! Thank you so much for the reply. I was flashing and booting twrp 3.5.1_9-0 for sailfish.
Click to expand...
Click to collapse
Try 3.3.0 instead (for both). The last I can find on my records that I used is 3.1.0.
Edit:
fastboot boot image
Flash twrp zip
Flash magisk zip
Reboot
Should be rooted with twrp installed.
This is how it used to work at least.
Okay I will try that out thank you!
Tulsadiver said:
Try 3.3.0 instead (for both). The last I can find on my records that I used is 3.1.0.
Edit:
fastboot boot image
Flash twrp zip
Flash magisk zip
Reboot
Should be rooted with twrp installed.
This is how it used to work at least.
Click to expand...
Click to collapse
Hey! I tried what you said, booted into twrp using fastboot. But when I entered my password to decrypt data it says "password failed, please try again". This did not happen when I used the other img.
keith-james said:
Hey! I tried what you said, booted into twrp using fastboot. But when I entered my password to decrypt data it says "password failed, please try again". This did not happen when I used the other img.
Click to expand...
Click to collapse
I read through the twrp thread. I don't think they ever got deception working on 10. Not by installing, just booting.
Tulsadiver said:
I read through the twrp thread. I don't think they ever got deception working on 10. Not by installing, just booting.
Click to expand...
Click to collapse
So should I install the img via fastboot?
keith-james said:
So should I install the img via fastboot?
Click to expand...
Click to collapse
I don't think you can on Android 10. You can try but I think people just booted twrp when they wanted to use it.
I think I'm having the same problem or at least a very similar one, I get the same errors in TWRP (started with ""fastboot boot twrp.img") saying unable to mount /system_root and /vendor but i am still told installation was successful anyway. Unfortunately, when I reboot to recovery, it seems to try and start TWRP but the phone restarts after the google boot logo and this will happen every time.
You can get the older verson of (temporary) TWRP Tulsadiver suggested using past the decrypting stage simply by removing your password/pin in settings > security > screen lock but using this version didn't help me at all.
I have tried going back to an earlier stock rom using google's images and trying to install TWRP again but this didn't work either.
Please let me know if you get anywhere with this.
I also have the same problem. It just saying unable to mount /system_root (Invalid argument)
And the /system is read-only,
I need to modify the files on /system partition, what should I do?
I've tried 3.4.0.0 and 3.3.0.0 and 3.6.9.0-9-0 but all failed.
Thank you all!
the-blind-bandit said:
I think I'm having the same problem or at least a very similar one, I get the same errors in TWRP (started with ""fastboot boot twrp.img") saying unable to mount /system_root and /vendor but i am still told installation was successful anyway. Unfortunately, when I reboot to recovery, it seems to try and start TWRP but the phone restarts after the google boot logo and this will happen every time.
You can get the older verson of (temporary) TWRP Tulsadiver suggested using past the decrypting stage simply by removing your password/pin in settings > security > screen lock but using this version didn't help me at all.
I have tried going back to an earlier stock rom using google's images and trying to install TWRP again but this didn't work either.
Please let me know if you get anywhere with this.
Click to expand...
Click to collapse
I have this problem too. Pixel sailfish on Android 10, tried to install TWRP zip file using the TWRP temp boot, and it will say unable to mount system_root and vendor but still successful, but unable to boot to recovery (restarts after Google boot logo).
Any idea how to install TWRP on Pixel with Android 10?
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.