My recovery says all the time
E:failed to mount /efs (Invalid Argumen )
E:failed to setting up dirty target
dm-verity verification failed
Pls help me anybody out this thing thank you
After flashing Android 4.4.2. IMEI changed and network signals gone. How can i fix this problem ?
TalhaMoazSarwar said:
After flashing Android 4.4.2. IMEI changed and network signals gone. How can i fix this problem ?
Click to expand...
Click to collapse
If you have old twrp backup of any rom which is earlier(in yout mobile not other mobile only your mobile don't try backup of other mobile if the mobile is same then also not try only your mobile backup) then to goto twrp hit restore and restore efs only
Or try to reflash ypur rom using this method
Use this method
1- swithoff your galaxy grand 2
2- power on to download mode( volumedown+download+power)
3- open Odin choose tar file(stock framware)
4-(most important) unmark auto Reboot, mark F. Reset time & Nand Erase All & phone bootloader update & phone EFS clear. see attached image
5-connect your grand 2 to your pc it will be shown in odin like com?
6-start odin to flash firmware to your grand 2
7-when odin finish don't reboot just remove battery for 20 sec.
8- re-insert battery and power on in recovery mode( volume up+home+power)
9-leave it do its work till samsung logo appears on screen remove battery again.
10- re-insert battery power on to recovery mode.
11 - in recovery do factory restore twice then reboot.
You can download the firamware from samobile google it and search for girmware of your model number with country code of country
Hope this will help you
Hit thanks button if i help
And ya i am not responsible for anything happens your mobile.
I have done all steps but after booting into recovery the following error occur (in red color) and phone doing bootloop on samsung logo.
E: failed to mount /data (invalid argument)
can't mount '/data' (invalid argument)
E: failed to mount /data (invalid argument)
can't mount /data/log/recovery_log.txt
E: failed to mount /data (invalid argument)
E: can't mount /data/log/emmc_checksum_log.txt
TalhaMoazSarwar said:
I have done all steps but after booting into recovery the following error occur (in red color) and phone doing bootloop on samsung logo.
E: failed to mount /data (invalid argument)
can't mount '/data' (invalid argument)
E: failed to mount /data (invalid argument)
can't mount /data/log/recovery_log.txt
E: failed to mount /data (invalid argument)
E: can't mount /data/log/emmc_checksum_log.txt
Click to expand...
Click to collapse
Factory reset 4 to 5 time and wipe cash also
May work if not to your phone to service center
Still not working
TalhaMoazSarwar said:
Still not working
Click to expand...
Click to collapse
May this help you
https://m.youtube.com/watch?v=Pai4BH3AWq8
Or open trminal emulator and type
Su
Grand permission
echo ‘AT+EGMR=1,10,”IMEI_NUMBER”‘ >/dev/pttycmd1
And reboot
In place of imei number enter your imei number
Found backside of your mobile where battery is placed
Or box of your mobile and its bill
And again do at your own risk. I am not responsible for any liability occur or any thing happen with your mobile
As you using this method your and only responsible for it not anyone else...
This trick only work on Chinese MTK mobile..
I just recently flash a stock rom with PIT file. Then I went to stock recovery and factory reset. But i got a error which is
"E: failed to mount /preload (Invalid Argument)"
Is there a way to fix my problem? I don't want to trip knox warranty. Any help will do :good:
SM-G530t FRP LOCK - Stuck at Galaxy Splash screen
Hi All, Im really stuck here. I have ODIN installed on my phone and have tried to install every ROM and image out there and am having trouble with the FRP . I need to unlock it to install a stock rom image ... i have tried the kies method, the smart switch method and they all run fine, but my e: partition is hosed
tried OF8_full.tar.md5
result to android system recovery <3e>
lmy47x.g530tuvu1a0f8
reboot system now
apply update from adb
" from external storage
" from cache
wipe/factory reset
wipe cache partition
reboot to boot loader
power down
recovery logs
--------------------------------------------------------------------
E: failed to mount /efs (invalid argument)
e: failed to mount /efs (invalid argument)
e: failed setting up dirty target
dm-verity failed...
e: failed to mount /system
PLEASE HELP WITH THE FRP LOCK WITHOUT BUYING A BOX
this is seriously affecting my business and cutting into my playing Destiny time!!
thanks in advance Mike
Help! My phone is now stucked on a boot logo. I tried rooting and flashing via odin on Oreo, after then, it stucks on boot loop, on which I know how to fix, going back to stock rom works, but then signal is gone (boot loop wasn't expected, didn't managed to see bandbased version) I then, flashed this: https://forum.xda-developers.com/showthread.php?t=2420881 through odin via AP, which is a wrong method on which I know I am stupid enough, right after then, OS won't boot up but stuck on boot logo, also tried using TWRP and Official Lineage OS 14.1 and the same thing happened, it starts to boot up, it rebooted after a few mins, then it goes back to TWRP.
HELP, I think the wrong method of flashing of this: https://forum.xda-developers.com/showthread.php?t=2420881 file is the mistake, idk what did I messed up with it, it was supposed to be used for EFS restore app not flash through Odin, what should I do? Any OS just stucks on boot logo but download menu and recovery mode (official/twrp) is still there, also the phone is still viable to be flashed.. Please help.. I just got this phone not even 24 hours ago.. Lol, I know stupid me, that I didn't checked the file carefully, I learnt my lesson, criticize me or anything.. But please, help if you can.
I had not known that the Marshmallow, Nougat and Oreo was pretty harder to do things on, I'm quite new with this new OS release, I was pretty confident because I was doing this all over the years (I only know step by step, not really in-depth information). Way back, odin only requires AP, now it requires 4 columns on which I cannot reflash without unchecking the Bootloader.
P.S. Before boot loop starts to happen I tried rooting on Oreo, downloaded my own country region openline version(I am openline, yes) and also tried Lineage OS 14.1, Now, I am trying to download Russia(not my country) Stock Rom Oreo, it might be the case that it doesn't allow me to flash bootloader as this was the downgrade, and I skipped right through it. But I am worrying about the wrong flash file and after the download finishes, the same thing happens and I won't be able to get passed out of boot
EDIT: I've did everything and ODIN works for the flashing the whole columns including bootloader with russian full stock ROM, but its still stuck on boot logo, EFS not detected on recovery. I'm losing hope, this is not recoverable yeah?
Here's the error code on recovery mode:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [Unknown]#
No Suppport SINGLE-SKU
E:Failed to mount /efs (Invalid argument)
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-verify verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
... and so on.
E:failed to clear BCB message: failed to find /misc partition
i have this problem too