Database Info

Bricked S7 - Imei lost

I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

darkalez said:
Click to expand...
Click to collapse
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?

MAX 404 said:
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
Click to expand...
Click to collapse
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp

darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)

darkalez said:
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
Click to expand...
Click to collapse
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?

darkalez said:
I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
Click to expand...
Click to collapse
DroidHackeR said:
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
Click to expand...
Click to collapse
MAX 404 said:
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
Click to expand...
Click to collapse
Looks like OP has tried ODIN already

/data is likely encrypted, so it's not surprising that it doesn't mount, but it looks like you may have corrupted your EFS somehow. This is actually really REALLY bad. The EFS is device unique and by design irrecoverable. Previous Samsungs could regenerate it if you wiped it from recovery and then flashed stock with Odin, but AFAIK this hasn't worked since the S5. If you decide to wipe it make sure you dd your existing partition first, but if that doesn't fix it you may need to take it to a service centre and pay for a repair
Always backup the EFS first before flashing ROMs

flashing stock won't fix IMEI. Looks EFS is broken.
Try to find some1 with box.

*Detection* said:
Looks like OP has tried ODIN already
Click to expand...
Click to collapse
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did

MAX 404 said:
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
Click to expand...
Click to collapse
BTW, to address that error he needs to format data. But backup his stuff 1st.

starche_old said:
BTW, to address that error he needs to format data. But backup his stuff 1st.
Click to expand...
Click to collapse
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)

MAX 404 said:
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
Click to expand...
Click to collapse
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.

starche_old said:
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
Click to expand...
Click to collapse
Hi
No really , as long as you dont use the data partition with TWRP is not necessary , check their thread , that step is no longer listed on the OP
1 In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2 Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
3 Extract Odin_3.12.3.zip to your computer.
4 Install Samsung Mobile Phone Drivers for Odin to find your device.
5 Download a .tar image of TWRP for herolte.
6 Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + v[Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
7 Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
8 Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
9 At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
10 If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
11 Go to [Reboot] -> [System].
12 Wait 2-5 minutes for your device to finish setting itself up
As i said in stock ROM , custom roms may vary
Regarding IMEI you are totally right if he does not have a EFS back up

Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.

starche_old said:
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
Click to expand...
Click to collapse
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.

As I SAID I can't flash stock firmware with odin, because of efs folder problem.... I already tried it.
I haven't got a rom installed on my s7 and I can't flash any, it'll not boot.
I gived it to a local shop.... I wait for his reply

darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
Try this guide to repair your efs.
Might be worth looking into re-partitioning here
If you can get into download mode, then there is always hope! Please excuse me if I missed any info, didn't read through the whole thread. Good luck! :good:

MAX 404 said:
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
Click to expand...
Click to collapse
Agreed.
And sorry everyone for off-topic

@darkalez: Since you have TWRP, you can flash other ROMs without any problem. I guess there are .ZIP files with stock ROM, although that won't reflash the recovery.
Why do you want to flash stock? If it's just to use that ROM, then do so via TWRP. Else you are in loss.

SM-G930x Retail Phone Secure Check Fail : (PIT), help please?

So I got a hold of a retail G930x and was successfully able to install TWRP and factory reset with a stock image, only problem was that I never turned off the FRP lock, and when the phone was restarted while updating SuperSU my recovery was blocked. OK, no problem, just flash a stock ROM through Odin mode right? Well for some reason G930AATT1APB5, and G930FXXU1APB4, do not seem to work. At one point I was able to partialy boot into the stock recovery, but at another flash attempt my computer blue screened and I received the error message "An error has occured while updating the device software. Use Emergency recovery function in the smart switch PC software", but Smart Switch returns an error message of "Device Not Supported". I can still boot into Download mode and attempt flashes, but I can't seem to find a working ROM for this phone or a solution to the stock Recovery issue (which is most likely corrupted by now). Any help would be greatly appreciated, thank you.

edit:
edit: so I flashed a recovery image file from ROM.G93xF.XXU1DQFM-v18.0.by.ambasadii.zip and was able to get to the stock recover screen. Unfortunately i get an error message saying "Failed to mount E: /system (Invalid Argument)
Update from external storage is disabled.

Installing system update fail after Odin flash. Boot into recovery mode.

Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No 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)
dm-verity verification failed...
E:failed to clear BCB message: failed to fin /misc partition
Click to expand...
Click to collapse
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!

normsrayn said:
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
Click to expand...
Click to collapse
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Just download the latest version of the file (6.0)
Now wait until rom boots
-----------------------------------------------------------------------------------
Please donate and like if you think i deserved it,
If it didnt work you don't have to do it
Happy flashing and good luck
Dont forget to update me after following the steps

I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!

normsrayn said:
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
Click to expand...
Click to collapse
Flash the stock firmware again but from download the firmware from Samfirm application. Please use the HOME_CSC too or your device is wiped. If you need the firmware just post modelnumber or name idk and CSC code and i can post a link with the firmware for you. TWRP can't mount /data and you will need to format your phone with means you lose everything.

getting dark error in galaxy j4 smj400F after system update failing
Picklewickle said:
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
but i have done factory reset so how to enable oem /unlock bootloader to flash via odin
HELP
-----------------------------------------------------------------------------------
Click to expand...
Click to collapse

Same issue
I have the same issue. I cant boot into download mode at all to even attempt to flash anything

Galaxy S7 G930F stuck on "No Command" screen after trying to flash back stock

Galaxy S7 G930F stuck on "No Command" screen after trying to flash back stock
Hello All,
First of all thank you all for your posts. I'm reading XDA forums for years and use rooted phones with custom ROMs thanks to the info you are all posting here
I've recently received a brand new S7 SM-G930F.
First thing out of the box I wanted to get rid of Google and Samsung bloatware and flash LineageOS (like I've done with previous phones), but ended up as a hopeless lady stuck in a boot loop
This is what happened:
Flashed a brand new S7 SM-G930F (Android 8.0 installed) with TWRP (3.2.3), LineageOS (14.1-20181011-nightly), Magisk (17.1), Xposed.
I then restored a TWRP backup from a S7 SM-G930FD (same LineageOS, but from a dual sim version phone).
Initially everything worked fine, then I noticed the SIM card is not recognised and that the baseband version is "unknown".
Also, every time I connected to my Wifi network while the other S7 SM-G930FD was connected as well, the last was disconnected.
Diving into XDA forums! Reading and reading, I figured the only way to fix it is to run a TWRP backup, wipe everything and flash a stock firmware on my device. Then flash TWRP again and either restore LineageOS backup or starting from scratch (without wiping system to keep the baseband version).
Things went down south when I tried to flash stock with Odin 3.12.3 (never did I ran into trouble doing this before!).
Flashing did not pass.
Downloading a different stock image from SamMobile and flashing, this time it did pass, but had another problem:
After flash the phone showed an "Installing software update" on a blue screen for about 30 seconds.
Then the message has changed to "Erasing" for about 5 seconds more.
Eventually received a blue "No Command" screen with a yellow warning symbol.
Tried to reboot. Then clear cache and reboot. Then wipe data. Tried to flash another stock image from SamMobile (different carrier), again getting to "No command" screen.
Did that with several stock images from different carriers, both with Android 8.0 and 7.0. All resulted with a "No command" screen.
I then flashed TWRP once again through Odin.
Wiped the phone and install LineageOS. Works! :victory:
LineageOS boots fine, just not recognising the SIM (as before). Also when I go to Settings → SIM cards, I have SIM 1 and SIM 2. Both are not recognised, but this is not a dual SIM phone
Relaxing that the phone can still function, I tried once more to flash stock through Odin.
Flashing did pass, phone rebooted, got an "Installing software update", message which changed to "Erasing", then I've received an "Error" screen. Looks exactly as the "No command" screen.
Now whenever I'm rebooting the phone it is stuck on boot screen. Although I can still get into recovery or install TWRP via Odin.
This is Odin's message when flashing stock fails:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a photo of the message I see when booting into recovery.
Text of this message here:
Code:
Installing system update
Error!
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File-Based OTA
Supported API: 3
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
When I click Mount /system and reboot nothing changes.
Device technical info:
Device out of the box:
Android version: 8.0.0
Baseband version: G9730FXXU2ERD6
Kernal version: 3.18.14-13438344-QB18292513; [email protected]#1, Sat May 26 15:53:42 KST 2018
Build number: R16NW.G930FXXU2EREM
Knox version: Knox 3.1, Know API level 25, TIMA 3.3.0
Device after flashing TWRP/Magisk/Lineage:
Android version: 7.1.2
LeneageOS version: 14.1-20181011-NIGHTLY-herolte
LineageOS API level: Guava (7)
Device after flashing stock firmware again:
samsung/heroltexx/herolte
8.0.0/R16NW/G930FXXS3ERI1
Hope there is a genius here that understand how I can fix this. I was assuming that going successfully back to stock will sort the baseband version/kernel and the phone will read the SIM card again, but I may be wrong?
Please share your insights!
Thank you :angel:

I have the same problem
To get back phone you flash original firmware and after that flash
no-verity-opt-encrypt-6.0.zip from somewhere on this forum.
Probably your /efs is damage
After flashing some firmware original/ and roms I've get working phone but not for long. After some time once it was 2 weeks once after 2h I get network error and no sim errors like you did.

Odin is shown flashing U2 firmware to S3. The firmware should be U3, S3, or higher (newer)
New firmware might require Odin 3.13.1.
Unzip the firmware with a different archiver.
Ensure the firmware download hadn't been interrupted.
I do not recommend anything EFS (backup is ok) unless sure (a data wipe or firmware change should be enough).

Thanks you both for responding!
@jaqjacek, I have flashed no-verity-opt-encrypt-6.0.zip after installing TWRP. These problems occurred after.
Could it be that the SIM problem started do to restoring a LineageOS image from a Galaxy S7 Dual SIM (G930FD)?
@Bryan48765, all U3 firmware are from South America countries. I have tried before S3 firmware, and have tried it once again, using Odin 3.13.1.
The result was the same.
Here are some details:
Flashing stock through Odin 3.13.1 - PASS :victory:
Phone reboots, blue screen with "Erasing" message, then "No command" screen:
Screenshot of recovery right after (DMVerity success):
Phone stuck on boot screen. Only can reboot into download mode, then rebooting into recovery. While reboot I get a blue screen with "Installing system update" message:
"Installing system update" changes to an "Error" message (wasn't fast enough to get a screenshot). But this is a screenshot of the recovery after (DMVerity fail):
Does this makes any sense?

Try smart switch!

jackherer72 said:
Try smart switch!
Click to expand...
Click to collapse
Yeah tried that but Smart Switch doesn't seem to pick up the fact that my device is connected. I can only get to recovery/download modes so I guess that's why..
Any idea if I can switch back to LineageOS and flash modem/baseband only?
Or do you think that after switching back to LineageOS and booting the system Smart Switch will then be able to read the phone?

OK made some progress and posting here just in case anyone else will ever run into this mass
To get myself out of this mass I:
- Flashed TWRP, mounted system and EFS, flashed no-verity and cleared dalvink/art cache. BTW data wouldn't mount so changed data file system to FAT and then to EXT4, data then mounted OK.
- Then Samsung screen appeared and system booted (yay!).
- Phone didn't read sim just like Lineage couldn't. When checking the device information I now see my other phone (s7 dual sim) model number, serial number, no IMEI and no baseband.
So in short, my issue here all seem to have started when I (stupidly) flashed S7 Duo (SM-930FD) TWRP recovery file on my new non-duo S7 phone (SM-930F). The fact that both use the same file of LineageOS firmware doesn't mean I could do that and expect the rest of the phone to work properly.
Questions for you:
- I have a TWRP backup of before flashing the Duo restore file, do you think that will revert back to original model & serial?
- If no, I guess I will now need to root the device and manually change back to my model number (from SM-930FD to SM-930F) and serial number so that my phone won't have identity issues anymore
Did any of you guys do it before?
Found this tutorial: https://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
Does that make sense or am I about to brick my phone again?

hello;
plz did you foundany solution??? i have the same probleme ...
- cannot flash stock firmware
- imei: 00000000000000
- sim card don't works
however i can flash costum rom
g930f u3 bricked after trying to flash combination file to get duel sim , and finaly i gget no sim looool
any solutions?

Guys, I have the same issue, can someone help me ?
Stuck on NO COMMAND after flashing stock rom .
Please help !

Had the same "No command" problem (and a corrupt recovery) and installing Samsung firmwares via Odin did not help.
But after I installed a TWRP-x.y.z.herolte.img.tar on AP with Odin I could boot into Recovery and install Lineage normally.

e: failed to mount /efs (invalid argument) on Samsung Galaxy NOTE 4 MODEL: N910H

Hi Geniuses!
Please save a soul!
At first, i was trying to fix my Samsung sm-N910H imei and baseband version.
I downloaded and flashed all sort of Samsung official firmwares of N910H of different versions including 5.0.1, 5.1.1 and latest 6.0.1 still to no avail.
I came across efs repair file online flashed it to my rom BOOM!!! that is the beginning of the end.
Now i try installing official ROM it fails on hidden.img.
I sorted it out by extract and removing the hidden.img file.
It flashed successfully. But guess what? it stocks on samsung boot logo before then, see attached d recovery mode log before attempting to boot.
DOWNLOAD MODE, samsung firmware: official, system status: custom
e: failed to mount /efs (invalid argument)
have installed CWM Custom recovery tried all sort nothing positive.
Please i need help as i want to boot to my system even without the imei and baseband saga, i would just use the phone as phablet with just wifi connection.
Your response is anticipated with much thanks!!

Seems /EFS partition where IMEI and all network related stuff is stored, doesn't no longer exist or got corruped.
Because original Android OS got tampered DM-Verity check must fail.

jwoegerbauer said:
Seems /EFS partition where IMEI and all network related stuff is stored, doesn't no longer exist or got corruped.
Because original Android OS got tampered DM-Verity check must fail.
Click to expand...
Click to collapse
Exactly, i agree with you.
It has a solution or the phone is permanently damaged!?