Hey, so I somehow bricked my phone. I wanted to root my phone and I got stuck in download mode. So i flashed it with odin. It passes perfectly everytime, but then I get stuck in android recovery mode, where at the bottom I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.
What version did you flash on your phone? And what version were you trying to root
G920FXXU5DQA7_G920FBTU5DQA2_BTU works just fine for me to get at least in recovery mode. I can't tell you what version i used to root my phone, because I don't remember now and I deleted that fille. When I flash it, blue screen with "installing system update" and loading android logo shows up for a few seconds and then immediately recovery mode comes back. And the same 4 errors show up at the bottom.
Kingkhone said:
G920FXXU5DQA7_G920FBTU5DQA2_BTU works just fine for me to get at least in recovery mode. I can't tell you what version i used to root my phone, because I don't remember now and I deleted that fille. When I flash it, blue screen with "installing system update" and loading android logo shows up for a few seconds and then immediately recovery mode comes back. And the same 4 errors show up at the bottom.
Click to expand...
Click to collapse
Well this is the AT&T forum so I'm assuming that you have the AT&T model, after the underscore where it says G920F it should be G920A. Go back and get the correct firmware and it should work.
Sorry about that, wrong forum. I'm new in this web. I'm using G920F
Kingkhone said:
Hey, so I somehow bricked my phone. I wanted to root my phone and I got stuck in download mode. So i flashed it with odin. It passes perfectly everytime, but then I get stuck in android recovery mode, where at the bottom I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.
Click to expand...
Click to collapse
Sounds to me like you would need to get a kernel with dm-verify removed or flash magisk, which does that for you.
The_scam said:
Sounds to me like you would need to get a kernel with dm-verify removed or flash magisk, which does that for you.
Click to expand...
Click to collapse
Thank you for your help, but I get the same problem. I tried to to emergency recovery with smart switch, but again I get stuck in recovery mode. When I try to reboot system, it gets stuck on black screen. In TWRP when I select backup, writes 0MB on the efs. Did I somehow wiped my efs partition? Is there any way I can fix it?
Kingkhone said:
Thank you for your help, but I get the same problem. I tried to to emergency recovery with smart switch, but again I get stuck in recovery mode. When I try to reboot system, it gets stuck on black screen. In TWRP when I select backup, writes 0MB on the efs. Did I somehow wiped my efs partition? Is there any way I can fix it?
Click to expand...
Click to collapse
Yes , you can use Odin to flash firmware 5.1.1 or greater
The_scam said:
Yes , you can use Odin to flash firmware 5.1.1 or greater
Click to expand...
Click to collapse
I try to flash 5.1.1, but I get sboot fail in odin. But I think I have bigger problem - I have lost my efs partition without doing any backup of it. Can I somehow reset my efs?
Kingkhone said:
I try to flash 5.1.1, but I get sboot fail in odin. But I think I have bigger problem - I have lost my efs partition without doing any backup of it. Can I somehow reset my efs?
Click to expand...
Click to collapse
No, try using Samsung software instead of Odin ?
The_scam said:
No, try using Samsung software instead of Odin
Click to expand...
Click to collapse
I don't understand what do you mean. Should I do this with smart switch or what?
Kingkhone said:
I don't understand what do you mean. Should I do this with smart switch or what?
Click to expand...
Click to collapse
I believe it was called Kies, if not that, try smart switch
The_scam said:
I believe it was called Kies, if not that, try smart switch
Click to expand...
Click to collapse
I'll try it
samsung galaxy s6 SM-G920A ayuda!!!
Tengo ese mismo problema pero en el samsung SM-G920A at&t soy de REP.DOM. mi whatsapp por si quieres ayudarme 829-367-7120
I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.[/QUOTE]
Related
i am now using the ZSJPG 2.2.1 version.
i use this version for few weeks already and there is no problem...
but yesterday i failed to turn it on and it stayed in "S" logo and vibrated....
so far i know 3 ways to solve this...factory reset, flash a rom or flash the original kernel...
but i want to keep my data and files!! which one is better??
thanks to everyone!
many thanks!!
I too have a similar problem ! I tried re-flashing. it doesn't help. When I go into recovery mode, It says " update media, please wait E:cant mount /dev/block/stl10 ( invalid argument) E:copy_dbdata_media : Can't mount DBDATA :
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed. "
manosijmukherjee said:
I too have a similar problem ! I tried re-flashing. it doesn't help. When I go into recovery mode, It says " update media, please wait E:cant mount /dev/block/stl10 ( invalid argument) E:copy_dbdata_media : Can't mount DBDATA :
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed. "
Click to expand...
Click to collapse
you mean you failed in both re-flashing rom and kernel??
Now it works.. Peculiar!
I was on I9000XWJV1 .. wanted to go back to I9000XWJS8. Tried JPY as well .. Was having the above mentioned problem. Now I flashed it again with JV1, now it works fine.
Could someone explain this ?
manosijmukherjee said:
Now it works.. Peculiar!
I was on I9000XWJV1 .. wanted to go back to I9000XWJS8. Tried JPY as well .. Was having the above mentioned problem. Now I flashed it again with JV1, now it works fine.
Could someone explain this ?
Click to expand...
Click to collapse
you flashed rom or kernel??
does your data still exist in your phone?
all gone.. I flashed my kernel
Hello good night, my problem is the following, I have a huawei P9 EVA L09 and I can not install official firmware C432B136 I have no rom installed in the terminal, I have unlocked the bootloader, twrp 3.0.2.0 installed, cust432 installed with error across Of the twrp, it does not enter to install the firmware with the method of 3 buttons, they do not appear any red letters, nor appears emui installing the firmware, only the symbol of huawei without entering to install, I do not have emui recovery, some expert can lend a hand to me? Thank you for your cooperation in advance.
¿Can someone please help me?
Flash OEMinfo with TWRP to get emui recovery back.
http://nigella.modaco.com/files/oeminfo-huawei-p9-eval09-c432.zip
Thanks for helping me walk, the phone unlocked y frp unlock, having prepared in the card the dload b136, when I flash the c432 oeminfo from the twrp 3.0.2.0 b361-b378 Appears on the screen:
*
Full selinux support is present.
Mtp enabled
Installing zip file '/ sdcard / oeminfo-juawei-p9-eval09-c432.zip'
Checking for md5 file ...
Skipping md5 check: no md5 file found
Flashing oeminfo ...
Done!
Script succeeded: result was [1.000000]
Updating partition details ...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
is left without twrp And locked bootloader, I try to install with the method 3 buttons and does not go out emui installation.
What I can do?
Try to find a solution through the program SRKToolHuawei-Lod-Chong-V2.0-20161002 (ALREADY I SAW IN A VIDEO THAT ENTERS THE EMUI RECOVERY)
1st method twrp 3.0.2.0 b361-b378 (correct)
2º meto the update.app I try with several, Rollback_Nougat_a_MMEVA-L09C900B300, or the update EVA-L09_B136, or the EVA-L09_C432B378_v74832 with its information, or the C432B182 in the folder dload (WITH NO EMPLOYEES EMUI recovery)
3º flasheo el oeminfo-huawei-p9-eval09-c432.zip error:
*Full selinux support is present.
Mtp enabled
Installing zip file '/ sdcard / oeminfo-juawei-p9-eval09-c432.zip'
Checking for md5 file ...
Skipping md5 check: no md5 file found
Flashing oeminfo ...
Done!
Script succeeded: result was [1.000000]
Updating partition details ...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
(Even so it flashed because it blocks the bootloader and is left without twrp)
4º meto the Stock Recovery L09-EVA (correct)
5º I use the program SRKToolHuawei-Lod-Chong-V2.0-20161002 with the step 1 to unlock the bootloader since with that step it directly enters emui recovery in a video that I saw, (BUT TO ME MEET TWRP 3.0.2.0) (WITH THE 3 BUTTONS DOES NOT ENTER, IT IS ON THE HUAWEI LOGO)
Other data that do not explain if I am not mistaken .. in the bootloader appears depending on whether I enter the from the twrp:
Android rebboot reason:
Bootloader
NA
Rebboot_enter_fastboot_common_func
After flashing the oem if I enter with low volume and usb output:
Android rebboot reason:
AP_S_COLDBOOT
NA
Volumnkey_down_press_process_func
After flashing the twrp if I enter with low volume and usb comes out depending on how you give it:
Android rebboot reason:
AP_S_abnormal
NA
Volumnkey_down_press_process_func
or
Android rebboot reason:
AP_S_PMU
Press8s_restart
Volumnkey_down_press_process_func
What am I doing wrong because of my lack of experience and knowledge, can you help me?
First flash the same firmware that you had to restore ur phone to a working stat.
In srk tool flash stock recovery.
Find the firmware for ur phone and extract the zip,you will get a file update.app ,copy this file to a folder name 'dload' on ur SD card.
With the phone off,press 3 buttons,power volume up and down till the update start.
I already did it, it does not want to enter, it does not decide to enter, it must be damaged recovery, it does not enter for much that I try with the mode of 3 buttons, it must be wrong recovery emui, no Never comes the emui symbol, only the symbol of huawei, desperate, helps, Can post me some kind of complete help to follow, miss recovery miui
What is not entering?
To boot into recovery,you need to hold volume up + power till you see the huawei logo than remove power key and keep pressing volume up.
Remove any usb before doing this.
Not enter, I already did without usb, turning it off, many times, waiting for the vibration to release the power, and also with the 3 at the same time, there is no way to get the miui logo, the huawei continuously, no I have android start to work ... when I put the dload it well, in the sd card, I feel alone in this problem .. And there where the problem (internal), related to the twrp, must be interfering, my Lack of knowledge, any other method to follow? How to completely erase recovery and re-flash?
Sorry I don't understand what you did and what you use and which firmware.
Do you have unlocked bootloader? Do you have twrp installed? Can you boot twrp?
I have unblocked the bootloader and twrp 3.0.2.0 b361-b378, I explain something important about what twrp 3.0.2.0 b361-b378 shows, once having the twrp, when I unlock with the SRKToolHuawei step 1 instead of going to Logo de miui, it is directed to the twrp, when it is done with 3 buttons it never enters, it stays in huawei logo
1-First boot to twrp, wipe format data,it will ask you type yes.
2-aftet wiping data in twrp go to first page and press reboot and reboot recovery.
3 Flash this in twrp ,copy this 2 files to sd card so you can install.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3574/f1/full/hw/eu/update_data_full_hw_eu.zip
I really appreciate it, this aside, inside wipes in the twrp comes this when doing wipes
formatting cache using make_ext4fs...
qipping data without wiping/data/nedia...
done.
updating partition details...
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
I will follow his indications to the letter of what he said to me before, I will communicate you here.
Formatting and say if this appears ...
formatting cache using make_ext4fs...
you may need to reboot recovery to be able to use / data again.
updating partition details
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
...done
In twrp " format data "not wipe cache. It should ask you to type yes to confirm.
Leave this... I already did
Formatting and say if this appears ...
formatting data using make_ext4fs...
you may need to reboot recovery to be able to use / data again.
updating partition details
Failed to mount '/ product' (invalid argument)
Failed to mount '/' vendor '(invalid argument)
Failed to mount '/' version '(invalid argument)
...done
Ok reboot to twrp recovery and flash the 2 files above.
Agree to take time to proceed.. it is downloading, is slow.. you are being of great help to the community and laggards that can happen this
One file has 10 min and the other 20 to proceed
HP96 said:
One file has 10 min and the other 20 to proceed
Click to expand...
Click to collapse
Good luck
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
If you can still get into TWRP then try flashing the backed up (or stock, extracted from a stock ROM) boot.img first. This will bring those partitions back (I think). Don't do this with the restore method in twrp, instead use the install button then change from .zip to .img.
Have you tried the dload method to flash back to stock or the huawei updater and hisense? Then redo everything from unlocking the bootloader to installing twrp and root. From there try to restore your backup. As far as i know this should work if all else fails, having done the exact same thing myself as you previously.
In the future when installing a custom rom the only partitions you need to wipe for a clean install are
Dalvik/ART
Cache
System
Data
Internal Storage (optional)
lostunsunghero said:
If you can still get into TWRP then try flashing the backed up (or stock, extracted from a stock ROM) boot.img first. This will bring those partitions back (I think). Don't do this with the restore method in twrp, instead use the install button then change from .zip to .img.
Have you tried the dload method to flash back to stock or the huawei updater and hisense? Then redo everything from unlocking the bootloader to installing twrp and root. From there try to restore your backup. As far as i know this should work if all else fails, having done the exact same thing myself as you previously.
In the future when installing a custom rom the only partitions you need to wipe for a clean install are
Dalvik/ART
Cache
System
Data
Internal Storage (optional)[/Q
Hey, thank u for the answere,
I tried the dload methode, I just booted to the stock recovery for about 2 hours...
About the boot.img: I didnt found any boot.img based on the stock rom on the internet... Should I try the pre-rooted img form this Thread ?
Click to expand...
Click to collapse
Bluesyle said:
Hey, thank u for the answere,
I tried the dload methode, I just booted to the stock recovery for about 2 hours...
About the boot.img: I didnt found any boot.img based on the stock rom on the internet... Should I try the pre-rooted img form this Thread ?
Click to expand...
Click to collapse
Only if you were on b378 before you messed up the phone or plan on flashing a b378 based ROM. Otherwise you will have to download a stock firmware and extract the boot.img from there. You can find stock firmwares in this thread:
https://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
Bluesyle said:
Hello everyone,
Click to expand...
Click to collapse
Reflash stock rom Boot into stock recovery after flash and wipe data factory reset.
Sent from my NATASHA using Tapatalk
Same Problem with Huawei Honor 8 FRD-L04
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
chemicalfx said:
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
Click to expand...
Click to collapse
were you able to find a fix?
Failed to mount
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
cfrisen said:
Hi everyone,
I did a disaster :
Click to expand...
Click to collapse
Man, i am in same problem like you did. If you find solution please pm me, i will do the same.
džejms din said:
Man, i am in same problem like you did. If you find solution please pm me, i will do the same.
Click to expand...
Click to collapse
Guy please tell me how you solved this problem!!!
Bluesyle said:
Guy please tell me how you solved this problem!!!
Click to expand...
Click to collapse
Sorry to say you but there was no solution for it. I did send my phone to servise and still wait for call.. in theory fix should be easy (with their tools etc..) but i am still not sure will they fix it or not.
When they call me i will tell you how much it cost and what they did to it..if they could. Worst case scenario i will sell my phone in parts and get some money back.
chemicalfx said:
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
Click to expand...
Click to collapse
Every few days somebody opens such a thread, having the phone similarly bricked. When asking what did you do, it turns out that he was on some of the AOSP based custom ROMs (there are couple of them), and he wanted to go back to stock, or he wanted to try/flash to the other custom ROM, etc.
I really wonder (I never tried those AOSP based custum ROMs - AFAIK, drivers for camera are not published and all those AOSP ROMs cannot utilize the main strength on this phone, the camera. Besides, I'm happily using another custom ROM that is stock based [hence havint the stock Camera app] but debloated, prerooted by Magisk, etc) do the corresponding AOSP custom ROM threads provide FAQ or information how to go back to stock (maybe they do but people don't bother to read)?
If they don't provide such info, why people do not first ask there (before bricking the phone)? IMO, developers of those custom ROKs would know the answer, if asked (supposidely they test their custom ROMs on various configurations and they have to go back to stock and forth to custom).
It will be helpful to ask and to get the answer in those threads for future users who will similarly come to try the ROMs, but maybe then also want tto go back to stock - to prevent that they similarly brick the phones.
---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
džejms din said:
Sorry to say you but there was no solution for it. I did send my phone to servise and still wait for call.. in theory fix should be easy (with their tools etc..) but i am still not sure will they fix it or not.
When they call me i will tell you how much it cost and what they did to it..if they could. Worst case scenario i will sell my phone in parts and get some money back.
Click to expand...
Click to collapse
DC Phoenix (15 EU) might be cheaper than service shop:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Chrome will automatically translate:
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and extract the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
---------- Post added at 09:45 AM ---------- Previous post was at 09:22 AM ----------
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and take oou the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
Thank you!
King_of_Android said:
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and extract the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
---------- Post added at 09:45 AM ---------- Previous post was at 09:22 AM ----------
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and take oou the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
Click to expand...
Click to collapse
Thank you :good: @King_of_Android.. I had a same issue in my Honor-5c Indian variant for Vendor and System.. Followed your simple steps and it worked flawlessly. BTW few applications are missing like Clock, themes, file explorer..... Do you any idea ?
When I try to flash the system.img, it comes the following message:
Code:
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460631 KB)...
OKAY [ 12.205s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.241s
When I try to check the unlock status it comes:
Code:
fastboot getvar unlocked
getvar:unlocked FAILED (remote: Command not allowed)
finished. total time: 0.008s
And at last:
Code:
fastboot oem unlock *code*
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.005s
Any idea? :silly:
did u found a fix??
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
did you found the correct metheod to fix it.
TWRP builds for P9 Android MM, N, O
TWRP must be ported to the particular device and firmware to support its partitions set-up, encryption, etc
No wonder that installing inappropriate TWRP and using it to flash something can brick your device
For Huawei it means that different ports of TWRP are required for different EMUI versions (4, 5 or 8)
In other words, depending on your P9 stock Android version, the following TWRP builds are proven (and AFAIK the newest)
- For Marshmallow, P9-EVA-TWRP-Android-6 from this post:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
- For Nougat, twrp-3.1.1-1-eva_extended from this post:
https://forum.xda-developers.com/showpost.php?p=75787111&postcount=1
- For Oreo, P9-EVA-8.0.0-TWRP-v4 from this post
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
I managed to fix this. My P9 was bricked, fastboot display an erro(11) and the above when trying to flash a rom in TWRP.
First download a stock rom, if possible the rom version that came with your phone, unzip update.zip to get update.app. Download app extractor and extract vendor.img, product.img, verlist.img, system.img then flash all img in fastboot, i.e., fastboot vendor vendor.img..
Erecovery mode will now be possible, connect to wifi and recover phone.
dimsum888 said:
I managed to fix this. My P9 was bricked, fastboot display an erro(11) and the above when trying to flash a rom in TWRP.
First download a stock rom, if possible the rom version that came with your phone, unzip update.zip to get update.app. Download app extractor and extract vendor.img, product.img, verlist.img, system.img then flash all img in fastboot, i.e., fastboot vendor vendor.img..
Erecovery mode will now be possible, connect to wifi and recover phone.
Click to expand...
Click to collapse
Does you need to re-unlock your phone after this ?
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
Bro today i found solution for this problem i was also getting error i was very frustrated
first of all download the original firmware from the manufacturer and unzip all the files you will find many images file such as boot.img,vbmeta.img...etc extract all the img files from the rom and place it in your desktop.
then whatervr invalid arguments you were getting such as vendor product etc this all comes inside the SUPER.IMG file you have to do only one thing go to fastboot mode and flash super.img file while booting your phone in fastboot mode
command:
fastboot flash super super.img
then it will take a while and congtrats all errors fixed after struggling and searching almost two hour i didnt gat a way out i wan not able t copy super.img file directly into storage i dont know why but after this the phone became normal
if you face any issues then tell i will send screenshots of everything
I just bought a P9-L19 International that comes with MM. I do not what I did while trying to root the thing, but I end up with the following problem:
Every time I try to install something from TWRP, it always says:
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
Since I do not know which version of MM it comes with, I tried many roms. Right now, I have EMUI-A168-L19C900B040SP11. Although it seems to work, I do not for sure whether it is the really the right rom. I can install and use TWRP, but every time I try to root it with SuperSu, TWRP always returns the above error messages and the flashing fails. So, I can't root my phone now. Any help with fixing the problem/id the right rom/root is greatly appreciated!
Thanks!
After restoring a backup, Includes EFS I am not able to reboot my phone anymore.
I tried flashing stock, a few combinations..
Combinations bootloop on Factory Binary logo, Stock ROMs on Samsung logo.
Download mode:
ODIN MODE
DOWNLOAD SPEED: FAST
Product name: N950F (My model is N950F/DS but it's normal it says N950F)
Current Binary: Samsung Official
System Status: Custom
RMM State: Prenormal
FRP Lock: OFF
OEM Lock OFF
Secure download enabled.
Also my Knox is 0x030c.
In recovery I get this:
Code:
#Fail to open recovery_Cause (No such file or directory)
Stock/Combinations flash fine. But on reboot they boot into stock recovery and gives this error:
Reboot Recovery Cause is Unknown
Support SINGLE-SKU
File based OTA
E:Failed to mount /efs (Invalid argument)
Supported API: 3
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
Dm-verity verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
Remove failed dir '/system/carrier/att/priv-app invalid directory
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
(A lot of times)
Any ideas? I really miss this phone.
Thanks in advance!! I'm on CRGA if that helps, So I can flash ARG1 combination, CRG1 firmware, CRGA firmware.
I had no issues with EFS before at all, All issues came after this backup restore.
Flashing custom recovery gives me this: imgur.com/a/zKcoJVp
Errors in stock recovery: imgur.com/a/ywIXfx7
Samsunguser932 said:
I had no issues with EFS before at all, All issues came after this backup restore.
Flashing custom recovery gives me this: imgur.com/a/zKcoJVp
Errors in stock recovery: imgur.com/a/ywIXfx7
Click to expand...
Click to collapse
Have you tried formatting data, where you have to type yes? I believe TWRP still has mounting issues, so you have to format like I said, then TWRP should mount properly.
You will have to flash stock with Odin to get rid of the binary issue., I believe.
stonedpsycho said:
Have you tried formatting data, where you have to type yes? I believe TWRP still has mounting issues, so you have to format like I said, then TWRP should mount properly.
You will have to flash stock with Odin to get rid of the binary issue., I believe.
Click to expand...
Click to collapse
I can't flash TWRP at all, Please read my whole post.. I tried flashing stock and this is as far as I get right now.
Samsunguser932 said:
I can't flash TWRP at all, Please read my whole post.. I tried flashing stock and this is as far as I get right now.
Click to expand...
Click to collapse
I was just trying to make sense of your post if I'm honest.
If you can not flash stock with Odin, contact Samsung for repair.
stonedpsycho said:
I was just trying to make sense of your post if I'm honest.
If you can not flash stock with Odin, contact Samsung for repair.
Click to expand...
Click to collapse
I can't , Solution now?
Samsunguser932 said:
I can't , Solution now?
Click to expand...
Click to collapse
Why can't you contact Samsung for repair?
sefrcoko said:
Why can't you contact Samsung for repair?
Click to expand...
Click to collapse
He does not want to take it, because it's a n950x live demo unit :silly::silly:
sefrcoko said:
Why can't you contact Samsung for repair?
Click to expand...
Click to collapse
SebastianSNRL said:
He does not want to take it, because it's a n950x live demo unit :silly::silly:
Click to expand...
Click to collapse
Because it's bought through work, It is a lease.
Samsunguser932 said:
Because it's bought through work, It is a lease.
Click to expand...
Click to collapse
Well, take it to your work for them to sort it out, just don't tell them what you tried to do.
Surely they would get you a replacement?
How did you restore your efs partition?
Bootloader 4?
PM me.
stonedpsycho said:
Well, take it to your work for them to sort it out, just don't tell them what you tried to do.
Surely they would get you a replacement?
Click to expand...
Click to collapse
I am starting to think it's a hardware issue and this might be how it should be done..Problem is it says System Status: Custom, And I can't change it to Official without booting :crying:
Samsunguser932 said:
I am starting to think it's a hardware issue and this might be how it should be done..Problem is it says System Status: Custom, And I can't change it to Official without booting :crying:
Click to expand...
Click to collapse
Your bootloader states prenormal, maybe this post will help you with that.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
stonedpsycho said:
Your bootloader states prenormal, maybe this post will help you with that.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
I can't boot at all..
Samsunguser932 said:
I can't boot at all..
Click to expand...
Click to collapse
Ok stupid question.
Since your on bootloader v4 since your on crga
1) did you flash any firmware with 4 in like N950FXXU"4"CRGA because you can't flash bootloader v. (3 or 2 or 1)
2) Have you tried the latest Odin?
3) have you flashed the CSC file (this one erases files and set up like new phone) instead of home_CSC?
And since Knox is Tripped there is no going back! So hope your company doesn't mind a rooted phone.
You'll need combination files that's for N950FXXU4CRGA (pay attention to the 4) if your going to flash combination files.
Sent from my SM-N950F using Tapatalk
Samsunguser932 said:
I can't boot at all..
Click to expand...
Click to collapse
What is current status?
Havethi you read esf mount Error fix in gen section sticky thread by me?
BluePhnx said:
Ok stupid question.
Click to expand...
Click to collapse
dr.ketan said:
What is current status?
Havethi you read esf mount Error fix in gen section sticky thread by me?
Click to expand...
Click to collapse
You 2 read my post entirely, I am limited on only stock recovery and stock ROM, I can't even boot stock ROM. So that fix if it's the data one is useless
Samsunguser932 said:
You 2 read my post entirely, I am limited on only stock recovery and stock ROM, I can't even boot stock ROM. So that fix if it's the data one is useless
Click to expand...
Click to collapse
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
dr.ketan said:
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
Click to expand...
Click to collapse
I tried that, I got many solutions I want to try first, I still don't know what exactly went wrong for my device to do this, What will Service station say to "System Status: Custom", I can't reset it to official when I can't boot.
dr.ketan said:
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
Click to expand...
Click to collapse
The pit file included into the CSC file don't will be used while the firmware flash process?
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts