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
Related
I have a Samsung Captivate that was running 2.2 flashed by Keis.
I could not see all of my internal sd space so I wanted to flash a custom rom.
I have used Titanium Backup to back up my phone.
I then Tried to use AIO Captivate Toolbox 2.5 to flash back to stock.
Now every time that I try to boot my phone it goes into system recovery <2e>
at the bottom it says
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.
Please Help
Just to add to the last post I can still get into download.
download the file in my sig. Flash it with odin 1.3
http://dl.dropbox.com/u/20958367/Odin3 v1.3.exe
I can walk you through it if you like.
I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?
windburn said:
I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?
Click to expand...
Click to collapse
theres the new URL for 2.1
http://dl.dropbox.com/u/20958367/I896UXJI2-homebinary.tar
Thank you so much.
I am downloading it now.
Just a few questions.
When I do odin what do I select pit, PDA or what?
Also do I have to change any of the options like re-partition?
Don't change any options at all. Open odin and leave it as is.
The file goes into the PDA section, no pit file is required.
odin did it's thing said pass 1:51.
Then it re-booted into android system recovery <2e>
What would you like me to do?
Exit recovery, and attempt to boot the phone.
I thought we had it but no luck.
it is still going into recovery
with this error
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.
try flashing the 2.2 one it has a different recovery 3e.
I am downloading now.
I will let you know what happens
Once it reboots it should go into recovery and install a bunch of files and then boot back up by itself.
It re-booted into recovery but got the same error.
It did not install any files or reboot again.
windburn said:
It re-booted into recovery but got the same error.
It did not install any files or reboot again.
Click to expand...
Click to collapse
Its by me at this point. That method has always worked for me.
Sorry I couldn't get you any further than you were.
I was reading this does it make sense to you
http://forum.xda-developers.com/showthread.php?t=788850
It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?
windburn said:
It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?
Click to expand...
Click to collapse
Reading that, its sounds exactly like what happened.
I don't know of any pit file for Rogers.
Thanks for your help nickm50
I will keep looking and see if I can find any way to fix this.
Maybe someone who has fixed the problem before will let us know how they did it.
Hello
So I got a phone from a friend wich doesn't boot. In recovery it says:
"Copying media files..
E:failed to mount /sdcard (File exist)
E:copy_dbdate_media: can't mount /sdcard
your storaged not prepared yet, please use UImenu for format and reboot actions."
Tried an full wipe reset through recovery. Tried installing firmware through Odin. Tried with a 512 pit file (repartition). Didn't work yet. Any ideas?
See here http://forum.xda-developers.com/showthread.php?t=1841250
compacity said:
See here http://forum.xda-developers.com/showthread.php?t=1841250
Click to expand...
Click to collapse
Thanks, will try. Hope it works. 1 hour remaining for the download.
sybe1986 said:
Thanks, will try. Hope it works. 1 hour remaining for the download.
Click to expand...
Click to collapse
It didn't work. ;[
Will look into flashing a rescue kit?
Hi.
Have you tried full restore to GB? Original Stock Firm.
-Get your stock from http://samfirmware.com/ & Odin (with pit file).
Don't forget the WIPE! ( you can restore to stock and after that wipe and restart )
For me, at any problem i have... i use the GB Flash Kit from Here: http://forum.xda-developers.com/showthread.php?t=1637966
And folow that 5 steps.
Don't forget to have a Backup of EFS (IMEI)
Search here on XDA, you will find the right way to bypass your problem, it always happened, don't panic.
Hello everyone,
First, excuse me because of my bad English, I have a big problem on my SM-800H and i hope someone will help me.
Before this problem i had a pre-rooted version of the G800HXXU1ANGD and the TWRP recovery, when i knew that Samsung released an 5.1.1 update of the OS, i decided 3months after to install a pre-rooted version, unfortunately it seemed that it was really unstable, WiFi and call didn't work and the UI was too laggy. So i decided to reinstall the ROM after a clean uninstall to see what it will do but i got a boot-loop on boot(Sorry if i seem stupid). I wanted to install my old ROM via Odin but it didn't work, it was telling about an issue with ext4 or something like that... After some searches, i found this topic (http://forum.xda-developers.com/galaxy-s5-mini/general/pit-files-t3064921) so i flashed the pre-rooted ROM (the old) in addition to the PIT File via Odin, at the beginning i thought it worked but in reality, it just booted, i could hear just a part of Samsung boot sound then it stopped roughly and there was a boot-loop. I went again in recovery to flash an another ROM (An unofficial version of Bliss Pop, pretty stable) but it said at the end something like unable to mount /data and unable to find crypto footer. After a reboot just to check it didn't want to boot into system, i had to wait a few minutes before it automatically reboot intro recovery but, surprise... I had something like a recovery boot-loop, it showed Team Win boot screen then it turned black and it showed me the boot screen another time and it returned black and it happened again like that infinitely.
I can boot into download mode so please if someone could help me, it'll be really nice
Thanks!
DyorenZ said:
Hello everyone,
First, excuse me because of my bad English, I have a big problem on my SM-800H and i hope someone will help me.
Before this problem i had a pre-rooted version of the G800HXXU1ANGD and the TWRP recovery, when i knew that Samsung released an 5.1.1 update of the OS, i decided 3months after to install a pre-rooted version, unfortunately it seemed that it was really unstable, WiFi and call didn't work and the UI was too laggy. So i decided to reinstall the ROM after a clean uninstall to see what it will do but i got a boot-loop on boot(Sorry if i seem stupid). I wanted to install my old ROM via Odin but it didn't work, it was telling about an issue with ext4 or something like that... After some searches, i found this topic (http://forum.xda-developers.com/galaxy-s5-mini/general/pit-files-t3064921) so i flashed the pre-rooted ROM (the old) in addition to the PIT File via Odin, at the beginning i thought it worked but in reality, it just booted, i could hear just a part of Samsung boot sound then it stopped roughly and there was a boot-loop. I went again in recovery to flash an another ROM (An unofficial version of Bliss Pop, pretty stable) but it said at the end something like unable to mount /data and unable to find crypto footer. After a reboot just to check it didn't want to boot into system, i had to wait a few minutes before it automatically reboot intro recovery but, surprise... I had something like a recovery boot-loop, it showed Team Win boot screen then it turned black and it showed me the boot screen another time and it returned black and it happened again like that infinitely.
I can boot into download mode so please if someone could help me, it'll be really nice
Thanks!
Click to expand...
Click to collapse
I think you need to re partition the storage
Then flash the latest kitkat ROM from sammobile via Odin it will show a fall message its fine
Now flash the stock lollipop ROM
Hope it works
sasukesama said:
I think you need to re partition the storage
Then flash the latest kitkat ROM from sammobile via Odin it will show a fall message its fine
Now flash the stock lollipop ROM
Hope it works
Click to expand...
Click to collapse
Thanks man for your quick reply, i'll test that as soon as possible
DyorenZ said:
Thanks man for your quick reply, i'll test that as soon as possible
Click to expand...
Click to collapse
When flashing KitKat stock ROM it didn't say fail, it just rebooted to system and i got a boot-loop. I removed the battery to reboot into download and flash the lollipop ROM but it showed me that after flashing (http://image.noelshack.com/fichiers/2016/06/1455453314-capture.png) and after rebooting to system, another boot-loop :/
sasukesama said:
I think you need to re partition the storage
Then flash the latest kitkat ROM from sammobile via Odin it will show a fall message its fine
Now flash the stock lollipop ROM
Hope it works
Click to expand...
Click to collapse
At least thanks to flashing the ROM I successfully flashed the TWRP recovery and now recovery works so i if u have any tip to repair this issue from recovery, it'll be nice
DyorenZ said:
At least thanks to flashing the ROM I successfully flashed the TWRP recovery and now recovery works so i if u have any tip to repair this issue from recovery, it'll be nice
Click to expand...
Click to collapse
Go to wipe>>>advance wipe
And try to repair all the partitions
Then try to wipe them
After that flash any custom ROM (PAC is recommended as I'm using it right now)
sasukesama said:
Go to wipe>>>advance wipe
And try to repair all the partitions
Then try to wipe them
After that flash any custom ROM (PAC is recommended as I'm using it right now)
Click to expand...
Click to collapse
Could u plz send me the link for ur custom ROM?
sasukesama said:
Go to wipe>>>advance wipe
And try to repair all the partitions
Then try to wipe them
After that flash any custom ROM (PAC is recommended as I'm using it right now)
Click to expand...
Click to collapse
I tried first to repair the first data partition (there is two) but it failed, here's the logs:
Code:
E : Could not mount /data and unable to find crypto footer.
E : Unable to mount '/data'
E : Unable to recreate /data/media folder.
Updating partition details...
E : Unable to mount '/data'
E : Unable to mount storage.
E : Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E : Unable to mount /data/media/TWRP/ .twrps when trying to read settings file.
E : No valid storage partitions found for MTP
E : Unable to mount '/data'
E : Unable to mount '/data'
Repairing Data using e2fsck...
E : Unable to repair '/data' .
E : Error repairing file system.
DyorenZ said:
I tried first to repair the first data partition (there is two) but it failed, here's the logs:
Code:
E : Could not mount /data and unable to find crypto footer.
E : Unable to mount '/data'
E : Unable to recreate /data/media folder.
Updating partition details...
E : Unable to mount '/data'
E : Unable to mount storage.
E : Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E : Unable to mount /data/media/TWRP/ .twrps when trying to read settings file.
E : No valid storage partitions found for MTP
E : Unable to mount '/data'
E : Unable to mount '/data'
Repairing Data using e2fsck...
E : Unable to repair '/data' .
E : Error repairing file system.
Click to expand...
Click to collapse
Are you using rvr twrp? Or jackeagles one?
sasukesama said:
Are you using rvr twrp? Or jackeagles one?
Click to expand...
Click to collapse
I'm using RVR one
DyorenZ said:
I'm using RVR one
Click to expand...
Click to collapse
Use jack one and try to change the partitions system to ext4
Start with data then system
You know how to do that right?
sasukesama said:
Use jack one and try to change the partitions system to ext4
Start with data then system
You know how to do that right?
Click to expand...
Click to collapse
alright but could you first send me a link to jackeagle twrp plz?
DyorenZ said:
alright but could you first send me a link to jackeagle twrp plz?
Click to expand...
Click to collapse
Herehttp://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-qualcomm-twrp-2-8-7-0-t3245256
sasukesama said:
Herehttp://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-qualcomm-twrp-2-8-7-0-t3245256
Click to expand...
Click to collapse
btw is it normal that in my case the /data partition have an 0mb size?
DyorenZ said:
btw is it normal that in my case the /data partition have an 0mb size?
Click to expand...
Click to collapse
Yes
Sometimes my cach partition get corrupt and it shows 0mb
Repair usually fixes it
sasukesama said:
Yes
Sometimes my cach partition get corrupt and it shows 0mb
Repair usually fixes it
Click to expand...
Click to collapse
Changing system files in /system and /data to ext4 just fails. Moreover, when i try to repair /data it fails with ERROR=8
No idea?
Did you try the steps in the thread bellow?
http://forum.xda-developers.com/galaxy-s5-mini/general/to-stock-t3353824/
If you messed up your partitions you may need to use an updated version of a PIT table for your phone and firmware version, or use the ROM related to the available PIT file.
lfom said:
Did you try the steps in the thread bellow?
http://forum.xda-developers.com/galaxy-s5-mini/general/to-stock-t3353824/
If you messed up your partitions you may need to use an updated version of a PIT table for your phone and firmware version, or use the ROM related to the available PIT file.
Click to expand...
Click to collapse
No I haven't tried these steps, in fact I think i messed up my data partition (E: failed to mount /data (invalid argument)), what can I do please?
Reinstalling the firmware using Smart Switch solved the problem, thanks for those who tried to help me
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]
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