Failed to mount .../vendor - Huawei Mate 9 Questions & Answers

Hello Guys,
Right now i think my Problem is well beyond my reach...
I wanted to install LineageOS on my recently bought second hand Huawei Mate 9 (MHA-L29) with the help of the instructions from this Thread: https://forum.xda-developers.com/mate-9/development/alpha-t3835072
that worked to one certain point...
I got a key for unlocking my phone from an internet site called funkyhuawei, which worked great
Whit the key I had no problems to unlock my phone and flash twrp
I also managed to boot into twrp but now I'm stuck because every time when I install the ROM it boot loops until eRecovery asks for wipe/system update.
When I install LineageOS it says :
mount: Failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: Device or resource busy
script succeeded:result was [1.000000]
Updating partition details...
...Done
Right now it's still possible to go back to stock android although the last time I tried I had to do several atempts until it worked.
Thanks to everyone who is willing to help out a total IT-Noob who does this for the first time in his life :silly:

Did you try OpenKirin's OmniROM Pie Alpha 3? No need to mess with TWRP. You can get root with Magisk

Related

Bricked honor 8 please help

Hello, today while trying to get back to stock i wierdly bircked my honor 8
I flashed the stock recovery and stock boot img
Then i flashed a rollback package and a marshmallow package which i used for this same thing before.
Now the phone didnt start for a solid 30 minutes and ive decided to reflash the rollback and marshmallow package, but after i flashed the rollback got stuck at the boot logo, not even the stock bootanimation showing up.
The phone doesnt reboot neither in any of the recoveries nor in bootloader.
Any help would be appreciated.
Stephen
Okay so after all of this i managed to reboot to bootloader and get my hands on one of my previous unlock codes. So now ive got an unlocked bootoader, but after fashing twrp the phone is stuck at the 'your device is booting now' when im trying to get in it
I thing you have flashed the wrong TWRP, check for the latest version or at least the one for your build
uh well, hello there again.
i've tried to do the dload method which failed(i used lots of versions tho none worked)
and i've tried flashing marshmallow twrp, which at the moment, well, it cannot mount anything. no partition can get mounted.
Does any of you guys have an idea of what i could try?
thanks in advance
Does it mean that you have access to TWRP ? if TWRP cannot mount a partition, go into mount section, tick system, data, boot, vendor and then reboot to TWRP again. Then try your previous operation. If it cannot mount data, go into wipe, advanced wipe, and click on format data, then restart TWRP and try again
seems like i somehow broke the partition table, cause it shows every storage as 0 mb and mounting isn't available, cant tick the option. Looks like i will have to find some service center to repair it by my own cost, by the end of the month. Though im giving it around the 25th so i got some more time till then, so maybe i find some solution to this problem.
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
ØG_SQUAÐ said:
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
Click to expand...
Click to collapse
You tried only once? Maybe you should now try to flash TWRP recovery and restore a backup made by TWRP. I can provide you one but for FRD-L09, not another. Another method would be to flash the rollback package and then retry flashing an EMUI 4.X ROM (dload method for both), hope you'll figure it out
I think i expressed myself wrong.
That was how i got the phone to work.
Oh lol I misunderstood because of the "it failed at 99%" and I thought the phone wasn't rebooting , no matter I'm glad you succeeded

Stuck in "Your device has been unlocked and can't be trusted" screen.

Hi everybody, I've been trying to unlock root on my Honor 6x BLN-L21 with Android 7 EMUI 5 (updated from Android 6) and I found myself following this guide. At first something went wrong as I got this error: "failed to mount /system (Invalid argument)", so I went under Advanced Wipe section of TWRP 3.1.1.0 and changed system partition format from EXT4 to FAT and then back to EXT4, and it solved. The installation of SuperSU didn't show any error message but as soon as I reboot my mobile from that screen, I get the screen in the title. Of course it won't let me run any update, meaning Volume UP + Volume Down + Power would just let me stick in the "Honor" blue screen with no progress showing. I need help to solve, thanks in advance.
PS: The only thing I get is: "No OS installed!". I'm astonished....
Use this guide to fix your phone. If you have any questions about the steps just ask.
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
TIP: If the version number you download wont flash using dload then try a lower version. For example. Even though my phone was on BLN-L24C567B366 when i messed it up i could only flash the BLN-L24C567B360 files. I updated once the process was complete.
Tip 2: Instead of Super Su. Try magisk instead. It allows you to root your phone and still use apps that refuse to work on rooted devices(pokemon go for example but theres many more.) You simply flash magisk with twrp and install the magisk manager apk. Everything is here. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This is gonna fail for sure, as every kind of update I try using dload method will permanently stick at 5%.
EDIT: I could solve installing via TWRP this custom ROM.
Baffol2asta said:
Hi everybody, I've been trying to unlock root on my Honor 6x BLN-L21 with Android 7 EMUI 5 (updated from Android 6) and I found myself following this guide. At first something went wrong as I got this error: "failed to mount /system (Invalid argument)", so I went under Advanced Wipe section of TWRP 3.1.1.0 and changed system partition format from EXT4 to FAT and then back to EXT4, and it solved. The installation of SuperSU didn't show any error message but as soon as I reboot my mobile from that screen, I get the screen in the title. Of course it won't let me run any update, meaning Volume UP + Volume Down + Power would just let me stick in the "Honor" blue screen with no progress showing. I need help to solve, thanks in advance.
PS: The only thing I get is: "No OS installed!". I'm astonished....
Click to expand...
Click to collapse
Use team mt multi tool
Provide required file from update.app
siddhrsh said:
Use team mt multi tool
Provide required file from update.app
Click to expand...
Click to collapse
I had solved already (look at the previous EDIT). Thanks anyway.

failed to mount vendor (invalid argument) -- SOLVED

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

Fastboot loop in already rooted OnePlus 7 Pro

I've done a bit of digging but I'm on a time crunch, and frankly I don't want to dig myself in a deeper hole.
I was attempting to make a backup of my OnePlus 7 Pro prior to doing an OTA update while preserving root.
I was getting a "failed to mount" and "0mb storage" so I looked into fixes and found this:
How to Fix TWRP Unable to Mount Storage, Internal Storage 0MB - Appuals.com
Some TWRP users, especially those who install custom ROMs, sometimes run into an issue where TWRP will an error that reads “Unable to mount storage”. The
appuals.com
.
I followed this and got to the point where I attempted to change file system from ext4 to ext2 and back again.
After doing this however I got stuck in a bootloop.
I entered TWRP recovery and tried to mount and boot? to system, and now I'm totally stuck on a fastboot loop -- unable to access TWRP.
I have several tools on my laptop saved from the initial root process such as the Tool All In One and the MSM download tool.
I would just like some clear direction to proceed. I'd rather not have to essentially reset my device, as I'm pretty sure all my data is in the device but I think I'm in the wrong partition. I'm just not savvy enough to know how to get it without causing further issues.
Any help would be great. I'm leaving for a 12 hour shift now, so I can't do any more digging on my own.
Thanks in advance.
Lower TWRP version.. is the fix, but.. i dont known anything about the OnePlus serie

Help Rooting

Spend the whole day looking through websites such as Magisk and TWRP as well as bunch of YouTube videos. I have unlocked the bootloader via DC Unlocker (Paid $4.50). For the most part, I have Magisk Manager installed but have no idea how to get Magisk itself installed via a boot image from their website.
Specs on Magisk shows Ramdisk: Yes, A/B: No, SAR: No.
Skipping that part, I did try a few of the img files on TWRP for Huawei Honor 8. Used the Minimal ADB and Fastboot steps. On the last step to "adb reboot recovery", it gets stuck on the loading screen and never reaches the TWRP screen. Any idea?
My end goal is to only use this phone for spoofing on Pokemon Go. That's all.
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
CHECK_123 said:
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
Click to expand...
Click to collapse
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
etsai3 said:
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
Click to expand...
Click to collapse
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
CHECK_123 said:
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
etsai3 said:
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
Click to expand...
Click to collapse
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
CHECK_123 said:
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
Click to expand...
Click to collapse
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
etsai3 said:
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
Click to expand...
Click to collapse
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
CHECK_123 said:
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
Click to expand...
Click to collapse
Thank you. The Power + Volume Up worked. Got Magisk installed. Just haven't figured out the last steps to get Pokemon Go spoofing to work.

Categories

Resources