Database Develop

i9000 bricked or something like that.

Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?

Bezeq said:
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Click to expand...
Click to collapse
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine

foggydisaster said:
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
Click to expand...
Click to collapse
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!

Bezeq said:
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Click to expand...
Click to collapse
Well you cant flash roms onto sdcard... But if your partition is broken, then sorry but im a noob
Sent from my GT-I9000 using xda app-developers app

Have you tired using a pit file?

flash a stock rom from samfirmware.com with ODIN.(eg. jw5)
to extract the password is "samfirmware.com"
tick repartition and use 512 pit file(included in rom from samfirmware).
check youtube for "flash with odin" if u dont know how.
edit:u are trying to flash from from samsungs 3 recovery.u need cwm(clockworkmod) to flash.
go to CF-ROOT(for i-9000) thread and follow instructions and read all in the OP(1-2-3 posts)
again u need ODIN to flash it.

hey
there is the best wasy to do that...just go to sammobile.com
there sign up first and then download the firmware (in firmware tab) and flash-programs...
the make sure to use oidn3_v1.0 only...
you can also download the flash-guide if you need it...
its simple..:laugh:

Thanks to everyone for replays, but nothing helped me x_x
if i flash 2.2.1 or 2.3.6 i receiving this error:
https://www.box.com/s/4d4b108a0246f9f56c7c
If i flash 2.3.3 or 2.3.4:
https://www.box.com/s/f09fd945620c03daffa9
And then it keep showing me GT 9000 logo......
yes i used 512pit and using 1.82 odin
I know there is way to install in to external SDcard: http://www.youtube.com/watch?v=zdMhYYdMB08
I had such error and successfully installed rom in to sdcard but i had issue with phone signal, so tried to re install rom and now its keep teling me cant mount data..
What can i do?

Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?

mystic324 said:
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
Click to expand...
Click to collapse
Yep, keep shows only gt-9000 logo..

I had a very similar problem earlier this year.
From what I could see the partitions on the phone's internal storage weren't able to be accessed. In adb I tried using parted and rm but the partitions there (/dev/block/mmc/blk0) didn't ever change. I also tried various .pit files and Android versions through Odin but nothing worked.
I took my phone in for repairs after flashing a really old version; as close as possible to what it came with, and they fixed it. The repair was due to 'mechanical fatigue' according to them. I assumed the internal storage was some how broken or corrupted and couldn't be written to.

Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.

Captain_17
Yes Captain_17, i have exactly same problem, cant give it to repair since purchased it from abroad.
erpurohit said:
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Click to expand...
Click to collapse
3e recovery because i`ve flashed 2.2 and 2.2.1 or any other official roms, i can flash CWM easy but as Captain_17 said i can see but cant touch
files or partitions.
If flash CWM then phone will boot to CWM only, and i cant flash any rom from CWM because i cant copy files to internal storage and external (sdcard) cwm doesn't see it.

Sorry man, wish I could be of more help. I tried every available option I could find online but nothing worked.
Seems to be a hardware problem and replacing the damaged part is the only solution.

Silly question, but you ticked re-partition? try flash 2.2.1 or 2.3.3 with 512 pit and repartition

Also, you could try to flash Darky ressurection via odin, not completely stock rom. I know that this is just tweaked stock, but you could try do that.
And, you could try to use Heimdall instead of odin - http://forum.xda-developers.com/showthread.php?t=1196179
I have read somewhere that heimdall is more preferable than odin in some cases.

Bezeq said:
Yep, keep shows only gt-9000 logo..
Click to expand...
Click to collapse
I once also a similar problem and flash2.1 Eclayr. But then I had to restore recowery to flash. as with you, I do not know if it helps.

[Q] can't mount /data

form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:

USE TWRP AND TRY FORMATTING WITH MAKE EXT4fs AND DON'T USE RM RF AND IF STILL DOESN'T WORK TRY REBOOTING SYSTEM AND TRY TO FORMAT AGAIN STILL GOT ERRORS TRY FLASHING A NEW ROM

tsrajput said:
form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:
Click to expand...
Click to collapse
flash the stock userdata.img by:
fastboot flash userdata userdata.img
the image file will br ir SP tools flashable rom/firmware.

tsrajput said:
form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:
Click to expand...
Click to collapse
If you are on 5.1+ then use twrp 2.8.6.0... Thats the latest official build for sprout

Yes, the latest recovery solves the issue of many zips which were not flashing......

Unable to mount /vendor /product /version

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 might need some assistance. (EVA-L19)

After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.

EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros

zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..

I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)

zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.

People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html

I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.

christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?

Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:

So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.

christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!

Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.

Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..

Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.

Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.

christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing

Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?

/data is indeed on EXT4, and I was installing the one that was on the room section.

Note 8 phone not booting after EFS restore (Brick?) [Solved]

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