Vendor and Product partition error - Huawei P9 Questions & Answers

Hi,
I have à problem with my P9 EVA-L09 when I 've wanted install renovatio rom.
Installation stopped. I ve restarted the phone and when i wanted wipe data i had errors:
Failed to mount /cust (invalid argument)
Failed to mount /vendor (invalid argument)
Failed to mount /product (invalid argument)
Now i can't install any rom ( before i had installed linear os) I can not boot to stock recovery or erecovery. I can just start boot on twrp.
On twrp terminal i format cust partition(/dev/block/mmcblk0p42) this solved cust partition error.
But i no found partition for /vendor /product
I ve downloaded full huawei firmware.
I ve extracted update.app with huawei extractor software.
I ve copied vendor. Img and product. Img on p9 memory
On p9 memory :
Cd /dev/block/bootdevice/by-name
Dd if=sdcard/vendir. Img of=vendor
Now i ve vendor file system in bootdevice but when i do a ls-l I've :
Cust-> mmcblk0p42
Vendor
Vendor has not link to partition.
I try make4_fs -l 512M vendor
Mke2fs -O journal_dev vendor (on bootdfvice directory)
But still not vendor partition and when i try wipe ive now
Failed to mount vendor (such on device)
I wanna ask you how to repair vendor and product partition. And if you can send me a tree of your mmcblk0 (fdisk /dev/block/mmcblk0 and p command) for see if i have the same.
Sorry for my bad english
Thank you

What version of twrp are you using?

Did you ever find a fix for this?

>Reaper< said:
Did you ever find a fix for this?
Click to expand...
Click to collapse
Hi, you've been able to work it out.
I don't see the Vendor partition either, after a bad flashing, I lost CUST, with the commands you use I was able to recover it, but it seems that the 3rdmodem and Vendor folders are not correct either, the first one is empty, and Vendor is not directly found.
With all this I haven't been able to start the system yet, I guess that's why.
See if it's possible that we can help each other.
A greeting.
P.S. my terminal is the p9 plus
P.S.2 By the way, if I try to start the recovery mode, a screen similar to the bootloader one appears, and if I try to recover the system with the 3 buttons protocol, I start TWRP, I don't know if it happens to you too, the fact is that even though I flash the original Recovery 1 and 2, they don't work as expected.

Related

Failed to change /cache file system from ext4 to f2fs

Hi guys... i want to ask whether anyone know how to solve this error,....i was succeed to change file system of /system and /data from ext4 to f2fs but i've got this error message after i'm trying to change file system of /cache by using twrp v2.8.70 :
E: mkfs.f2fs -t 1 /dev/block/mmcblk0p4 process ended with ERROR=255
E: Unable to wipe '/cache'
E: Error changing file system.
Thanks in advance for your attention

K01A ME70C I can only accesso to fastboot

I all I have an old memopad that I would like to revive for using I in a project. Afetr upgrading to lollipop for mistake I tried to boot in recover through rom manager and obviously it failed
Now I am stuck , I can load fastboot mode and it show unknow bootloader. How Can I revive it?
update:
I followed this tutorial https://forum.xda-developers.com/memo-pad-7/general/downgrade-asus-memo-pad7-me70c-t3735665
I managed to install the temp recovery but I am unable to mount the sd card.
The error seems in the partition structure.
I: Can't partiton unknown volume : /emmc
I Can't patition non-vfat : datamedia
W: failed to mount /dev/block/platform/intel/by-label/ fata ( invalid argument)
Can't partition device : /sdcard
Click to expand...
Click to collapse

Asus ROG 2 stuck in boot Loop

Hey guys, i have encountered a weird problem i got stuck in boot loop. i have tried to install the firmwares from fast boot, edl and TWRP mode. nothing is working
while trying to factory reset/wipe data i am getting error for BCB messaged alerts for failed to open dev/block/bootdevice/by-name/misc: no such file or directory found.
while from twrp i am getting unable to mount storage. i will highly appreciate if anyone can help me. mostly i have tried all of the firmware's.
Wiping Data...
Done processing script file
Wiping Cache...
Unable to find partition for path '/cache'
Done processing script file
Wiping Dalvik Cache...
Failed to mount '/data' (Invalid argument)
Done processing script file
Pushing First Zip...
D:\UL-ASUS_I001_1-CN-16.0631.1910.63-1.1.252-user.zip: 1 file pushed. 36.4 MB/s (2608518787 bytes in 68.420s)
Flashing First Zip...
Installing zip file '/UL-ASUS_I001_1-CN-16.0631.1910.63-1.1.252-user.zip'
Checking for Digest file...
Unmounting System...
Flashing A/B zip to inactive slot: B
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
First Zip Flashed
Deleting First Zip...
Press any key to continue . . .

Failed to moutn '/system_root' (invalid argument) A71 TWRP

I was follow this tutorial to install a custom ROM.
I flashed the ROM as 'Super (system, vendor, product...)' as I didn't see any 'System' option, now it looks like I broke everything.
It says "Failed to moutn '/system_root' (invalid argument)" when I try to Format Data and flash anything
Help
Super image is supposed to be system, vendor, product and odm all into one
You replaced it with a singular system.img and are now missing vendor, product and odm. You should either flash a super.img that will restore those partitions (like NcX or Swx for example) or you can just flash stock with Odin and then re-install your custom recovery.
I think you're supposed to use the new OrangeFox recovery that can flash system images by itself.

Question Every custom ROM I flash is stuck on their bootscreen

Hello.
I have a Redmi Note 10 Pro (8GB RAM Version) with an official unlocked bootloader.
I have managed it to install TWRP, TWRP works, that means, I can boot into it, and use it.
But if I flash a ROM ZIP file over TWRP, every custom ROM gets stuck at its bootscreen. It shows the
bootscreen of the offending custom rom, then nothing happens anymore, its just stuck there.
Does anyone here know, wht I do wrong?
Regards
Try flashing the fastboot firmware using pc so that it may fix corrupt partitions, if any.
or maybe the universe is conspiring against you
Can you tell me how I do that (Flashing over pc?)
ME20001 said:
Hello.
I have a Redmi Note 10 Pro (8GB RAM Version) with an official unlocked bootloader.
I have managed it to install TWRP, TWRP works, that means, I can boot into it, and use it.
But if I flash a ROM ZIP file over TWRP, every custom ROM gets stuck at its bootscreen. It shows the
bootscreen of the offending custom rom, then nothing happens anymore, its just stuck there.
Does anyone here know, wht I do wrong?
Regards
Click to expand...
Click to collapse
Try to format data with yes before and after you flash a ROM via twrp
Tried to format data with yes, shows following errors:
Failed to mount `/system_ext´(Invalid argument)
Failed to mount `/product`(Invalid argument)
Updating partition details...
Failed to mount ´/system_ext`(Invalid argument)
Failed to mount `/product`(Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Done.
You may need to reboot recovery to be able to use /
data again.
TWRP will not recreate /data/media on an FBE device.
Please reboot into your rom to create /data/media [Note from the narrator: Thats not possible, every ROM stucks on boot]
Formatting Metadata using mke2fs...
Done.
Updating partition details...
Failed to mount ´/system_ext´(Invalid argument)
Failed to mount ´/product´(Invalid argument)
...done
ME20001 said:
Tried to format data with yes, shows following errors:
Failed to mount `/system_ext´(Invalid argument)
Failed to mount `/product`(Invalid argument)
Updating partition details...
Failed to mount ´/system_ext`(Invalid argument)
Failed to mount `/product`(Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Done.
You may need to reboot recovery to be able to use /
data again.
TWRP will not recreate /data/media on an FBE device.
Please reboot into your rom to create /data/media [Note from the narrator: Thats not possible, every ROM stucks on boot]
Formatting Metadata using mke2fs...
Done.
Updating partition details...
Failed to mount ´/system_ext´(Invalid argument)
Failed to mount ´/product´(Invalid argument)
...done
Click to expand...
Click to collapse
Try to flash stock ROM via PC with mi flash (important don't lock bootloader in miflash)

Categories

Resources