hi everyone
i have problem with my phone note 4 i flashed orignal firmware from sammobile when device restart i get this error
failed to mount efs invalid argument
The phone is very slow and hang many
what is the solution for this
a_s_a_o said:
hi everyone
i have problem with my phone note 4 i flashed orignal firmware from sammobile when device restart i get this error
failed to mount efs invalid argument
The phone is very slow and hang many
what is the solution for this
Click to expand...
Click to collapse
There's a stock tar thread in general forum with md5 to verify against the downloaded zip. If you have a download that you can verify md5 for then use it verified good.
Once you verify the md5, extract the tar.md5 by opening the archive and dragging tar.md5 to Odin folder. Flash that in latest Odin with Odin defaults.
You should backup keepsakes, wipe everything but extSdCard, factory reset and format data partition and then power down your phone and pull battery before Odin. Let it auto boot and go through the setup wizard. If you're not Sprint, I'm not sure what you do but maybe just a data zip flash in recovery and deleting the Sprint activation application is all that is required. Dunno because I'm on Sprint, myself.
If you're downgrading from Marshmallow, there's been recent reports of having to factory reset in stock recovery after flashing stock tar. For those reporting that, they reported phone not booting after tar flash. I've downgraded with success but factory reset and wipe internal memory and used bootloader and TWRP backup to restore. Wasn't a problem.
It's also been reported in Nexus forum that efs partition shouldn't be restored. I don't think this works for Note 4 either. Don't restore efs partition.
Sent from my SM-N910P using Tapatalk
samep said:
There's a stock tar thread in general forum with md5 to verify against the downloaded zip. If you have a download that you can verify md5 for then use it verified good.
Once you verify the md5, extract the tar.md5 by opening the archive and dragging tar.md5 to Odin folder. Flash that in latest Odin with Odin defaults.
You should backup keepsakes, wipe everything but extSdCard, factory reset and format data partition and then power down your phone and pull battery before Odin. Let it auto boot and go through the setup wizard. If you're not Sprint, I'm not sure what you do but maybe just a data zip flash in recovery and deleting the Sprint activation application is all that is required. Dunno because I'm on Sprint, myself.
If you're downgrading from Marshmallow, there's been recent reports of having to factory reset in stock recovery after flashing stock tar. For those reporting that, they reported phone not booting after tar flash. I've downgraded with success but factory reset and wipe internal memory and used bootloader and TWRP backup to restore. Wasn't a problem.
It's also been reported in Nexus forum that efs partition shouldn't be restored. I don't think this works for Note 4 either. Don't restore efs partition.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
thanks for your help
my note is 910p- and i use my phone out USA
same problem any other idea
a_s_a_o said:
same problem any other idea
Click to expand...
Click to collapse
Which stock tar are you trying to update to? Did you verify the md5?
Does the flash complete without error?
Are you managing any connection to your carrier? Could be hardware failure or a corrupt partition. I've seen suggestions to use a tar with PIT included. For Android 5.1, that would be OG5 stock tar. For Android 6, PC1 has PIT. Have you tried either of those?
Sent from my SM-N910P using Tapatalk
samep said:
Which stock tar are you trying to update to? Did you verify the md5?
Does the flash complete without error?
Are you managing any connection to your carrier? Could be hardware failure or a corrupt partition. I've seen suggestions to use a tar with PIT included. For Android 5.1, that would be OG5 stock tar. For Android 6, PC1 has PIT. Have you tried either of those?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
yes i flashed this rom N910PVPU4DPE1_N910PSPT4DPE1_SPR and it flashed with no error then the device rebot in recovery and get the same error massage , i made wipe for everything and factory reset after flash TWRP , but also the phone is very slow and hang, and still this message shown
a_s_a_o said:
hi everyone
i have problem with my phone note 4 i flashed orignal firmware from sammobile when device restart i get this error
failed to mount efs invalid argument
The phone is very slow and hang many
what is the solution for this
Click to expand...
Click to collapse
Questions belong in the Help/Q&A section, not General.
THREAD MOVED
efs fail
i have this Problem same you and i have collect 4 N910P efs.img user please add my facebook name（cai fa Hork）
I haven't had this issue. I don't know if the thread below is relevant for Note 4 but if you don't have a backup try the easy fix first (CM):
Some in the thread have noted that flashing CM nightly resolved this issue for them.
http://forum.xda-developers.com/showpost.php?p=55040882&postcount=1
Sent from my SM-N910P using Tapatalk
Related
Hi All,
I stupidly (by accident) attempted flashing a n7100 CM10.1 ROM to my n7105. Basically I soft-bricked the phone but when I used Odin to restore the stock rom my baseband is showing up as unknown and my internal sdcard storage shows up in stock as having 0 bytes.
Anyone have any idea how to recover from this? I have read alot and it seems reflashing the stock rom has helped some people and not others. I even tried a kies restore with no luck
Regards,
Phoenix
flash stock ROM including pit file
if your device is 7105
here is thread you can find pit and stock ROM
http://forum.xda-developers.com/showthread.php?t=2032849
dr.ketan said:
flash stock ROM including pit file
if your device is 7105
here is thread you can find pit and stock ROM
http://forum.xda-developers.com/showthread.php?t=2032849
Click to expand...
Click to collapse
Tried that one already with no luck
try just flashing pit file only
then flash pit + stock ROM
does your odin log was showing successful?
have you tried factory reset after flashing?
As well your IMEI is displaying correctly?
dr.ketan said:
try just flashing pit file only
then flash pit + stock ROM
does your odin log was showing successful?
have you tried factory reset after flashing?
As well your IMEI is displaying correctly?
Click to expand...
Click to collapse
Tried pit alone, didnt make any difference.
Followed by PIT + Stock ROM, didnt make any difference.
Always factory default after a flash and it hasnt helped.
Odin did not give me an error either time that I flashed.
IMEI is null/null when using *#06#
Thanks for your help
PhoenixMage said:
Tried pit alone, didnt make any difference.
Followed by PIT + Stock ROM, didnt make any difference.
Always factory default after a flash and it hasnt helped.
Odin did not give me an error either time that I flashed.
IMEI is null/null when using *#06#
Thanks for your help
Click to expand...
Click to collapse
It seems your efs is corrupt.
Try this. This is your last and best bet
http://www.cvxcvx.pl/podstrona-0/naprawa-efs-w-i9100-n7000?lang=en
PhoenixMage said:
Tried pit alone, didnt make any difference.
Followed by PIT + Stock ROM, didnt make any difference.
Always factory default after a flash and it hasnt helped.
Odin did not give me an error either time that I flashed.
IMEI is null/null when using *#06#
Thanks for your help
Click to expand...
Click to collapse
try flashing baseband only
In odin select ROM file for 'Phone' tab instead 'PDA'
OR get modem.tar from here and flash using odin for phone tab
http://forum.xda-developers.com/showpost.php?p=31986738&postcount=6
zeeshanonlyme said:
It seems your efs is corrupt.
Try this. This is your last and best bet
http://www.cvxcvx.pl/podstrona-0/naprawa-efs-w-i9100-n7000?lang=en
Click to expand...
Click to collapse
I backed up my existing efs then tried this. Didnt help and the phone got stuck in Factory Mode until I restored the efs image I backed up. I had to change the partition from mmcblk0p1 to mmcblk0p3 as that is my efs partition.
I suspect you are right and if I could get someone elses efs image then I may have a hope but considering if contains the IMEI I doubt anyone would be willing to do that.
I tried billard412's Sprint ROM restore to stock and something went haywire.. It rebooted and then it would just boot loop. Ok I thought I'll just Odin back .. but everytime I tried any TAR to Odin it would just stop at cache.img.. I am able to get into TWRP and when I tried a restore, it restored fine, but then it would say
E: Unable to mount /efs
E: Unable to mount /preload
E: Unable to mount /carrier
I've tried various operations, megawipes and such and it would still give me that error on my Sprint Galaxy Note 2 at the end.
Can anyone help me please?
This is scary! I was about to use that so I could do the full ma7 update but now I'm not so sure.
Maybe you should ask billard for ideas since he knows what actions his zip takes and *should* have clues about what parts could go wrong.
Sent from my SPH-L900 using xda premium
KEYofR said:
This is scary! I was about to use that so I could do the full ma7 update but now I'm not so sure.
Maybe you should ask billard for ideas since he knows what actions his zip takes and *should* have clues about what parts could go wrong.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I think if I had backed up my EFS folder I might be OK, but alas. I didn't .. This is my first Samsung phone, coming from HTC.... I asked in his thread but it's probably one of those one in a million chance type of things that happened to me
well if that didnt work i just had the same issue
due to upgrading to stock MA7 and flashing an LK8 rom with an MA7 stock kernal
i had to odin twrp recovery and run the restore zip from there since i cant mount preload
also if the zip dont work load a custom rom then go back to recover and try it then you should be able to odin again
*also when i went back to stock LJC i went to manual recovery and cleared cache and dalvik because when i did a factory reset E: failed again*
Tha_Dynasty2049 said:
well if that didnt work i just had the same issue
due to upgrading to stock MA7 and flashing an LK8 rom with an MA7 stock kernal
i had to odin twrp recovery and run the restore zip from there since i cant mount preload
also if the zip dont work load a custom rom then go back to recover and try it then you should be able to odin again
*also when i went back to stock LJC i went to manual recovery and cleared cache and dalvik because when i did a factory reset E: failed again*
Click to expand...
Click to collapse
billard was able to point me into the direction of a PIT that I used to re-partition the phone.. Now I just have the mouning /efs problem, which if I read correctly, I should have backed up.. that's where I am now. I was able to go back to stock but it boot loops and when I go into recovery I have the unable to mount ./efs error
jyan_osu said:
billard was able to point me into the direction of a PIT that I used to re-partition the phone.. Now I just have the mouning /efs problem, which if I read correctly, I should have backed up.. that's where I am now. I was able to go back to stock but it boot loops and when I go into recovery I have the unable to mount ./efs error
Click to expand...
Click to collapse
wow so the repartition didnt work?
i mean like i said you can try after doing stock you
can reboot go in to stock recoevery and clear things they may help
and also when loopinng i used twrp 2.4.0.1 i think thats the newest 1
Tha_Dynasty2049 said:
wow so the repartition didnt work?
i mean like i said you can try after doing stock you
can reboot go in to stock recoevery and clear things they may help
and also when loopinng i used twrp 2.4.0.1 i think thats the newest 1
Click to expand...
Click to collapse
Yea using the newest TWRP.. cleared everything.. tried multiple roms both rooted and stock.. i think it's a lost cause
jyan_osu said:
Yea using the newest TWRP.. cleared everything.. tried multiple roms both rooted and stock.. i think it's a lost cause
Click to expand...
Click to collapse
i dont think so i swear
i got same issue it even told me to connect to kies due to odin not working nor the restore for 1 click
you have to make sure when you went to recoevry and flashed the stock ljc
http://forum.xda-developers.com/showthread.php?t=2086769
it will take you back to stock period when your phone boots
you will have to shut it down and then go to recoveryt which it will be stock and then
wipe factory 2 times and then cache 2 times and that should repartition your phone
reboot it and then use a stock tar and then repartition you should be good to go and you even have 0 reset counts with stock LJC
I was going to upgrade to kitkat, and was in the process of just doing a factory wipe using teamwin. The issue is, I was a work doing this at my desk and trying to just breeze through it and deleted the OS. I have all of the files I need to throw kitkat on it, but the .PIT file. I was reading some of the forum posts and I came across one where someone was running into a similar download mode issue using Odin and was able to get his note 3 to work again after adding in the PIT file. My issue is, Ive scoured for my particular PIT file, but to no avail. can someone please help. Thanks in advance. :fingers-crossed:
According to your post, all you did was format the system in TWRP? Do you still have TWRP installed? If so, you can just flash another rom. Otherwise, have you tried just flashing the stock tar file in Odin? I'm assuming I'm missing a big detail, as to why you went from wiping the system in recovery, to having a bigger issue.
Sent from my SM-N900T using Tapatalk
Towle said:
According to your post, all you did was format the system in TWRP? Do you still have TWRP installed? If so, you can just flash another rom. Otherwise, have you tried just flashing the stock tar file in Odin? I'm assuming I'm missing a big detail, as to why you went from wiping the system in recovery, to having a bigger issue.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
That worked. I just flashed a new ROM. I was over complicating it. What happened is i was manually selecting wipe criteria and checked the box for the OS to wipe with the cache and such. When i was going through the process before it was giving me a partition error.
Thanks for the help =)
I am trying to fix my friends phone. I believe the partitions are out of whack. The data partition is displaying an abnormally huge size as you can see in the attach picture. I have tried ODIN back to stock and can actually get 4.2.2 MDL to load but I encounter issues from there. Its highly unstable. I have tried to install several custom roms off from TWRP, CWM, and OUDHS and not a single one boots. I definitely can't make backups since the partition is so huge. I think I PIT file will solve the problem but it seems like PIT file for TMobile variant is available. Is there any way to extract one? Is there any other way I can fix this?
So far I haven't seen a pit file posted for this device anywhere.
And from my knowledge it is not included in the stock firmware files that we would flash from sammobile.com
What happens when you try to format the partitions in the recovery like that.
I had a similar problem before with my s3 and using twrp and formating the partitions was able to fix it in that case.
When you Odin back to MDL and don't root it right away, how does it work then?
When you say format partition in recovery, I assume you mean wiping the partition. Wiping the partition, although it appeared the procedure completed successfully, the size of the partition did not change. Very strange.
As far as ODIN to MDL, the phone does boot into 4.2.2. Its a little quirky but it works. I can always get it back to MDL. Doing any installing from recovery does not work. He may be stuck with a quirky 4.2.2 system.
How could I in Odin insert a PIT file to remap my filesystem.
Is there one for the TMO S4 or could I simply use one from the gt9505?
Stoowyguy said:
How could I in Odin insert a PIT file to remap my filesystem.
Is there one for the TMO S4 or could I simply use one from the gt9505?
Click to expand...
Click to collapse
You don't.
Remapping the file system is not a current mod and is not recommended to try. One of the 95xx variants had a remapped PIT file done to add a little bit of usable space. (You can't use that one. It will break your 919 device) The risk was high and the benefit was low. It's just so cheap and easy to buy a 32 or 64 GB external SD card that accomplishes the same thing.
I guess basically what I'm trying to achieve is for my phone to be able to install custom roms again. Randomly one day I was unable to install any, for it would just install a few apks from each CustomRom installation zip.
I've tried reinstalling stock and it doesn't fix my issue that most likely lies in the file system of my phone.
Stoowyguy said:
I guess basically what I'm trying to achieve is for my phone to be able to install custom roms again. Randomly one day I was unable to install any, for it would just install a few apks from each CustomRom installation zip.
I've tried reinstalling stock and it doesn't fix my issue that most likely lies in the file system of my phone.
Click to expand...
Click to collapse
That is weird. Did you try to reflash back to stock using Odin? Or by flashing a nandroid of a stock ROM?
If using Odin to flash a stock image doesn't work I'm not sure a pit file would help. The stock .tar image for Odin contains the proper PIT file. So it's getting the PIT file anyway.
I'll try again..
I've tried coming back from Odin many times but I've noticed Odin is pretty sketchy because honestly most of the time oI get FAIL status near the end of stock installation but I keep going until it passes and I've tried going back from NAND. I was going to see this phone because no one on XDA nor me could figure out this tricky issue. Someone pm'd me claiming he has the same issue and I told him I haven't solved it yet. I think tomorrow I'm going to maybe try stock install and then wipe data factory reset after and then boot and then go back to download mode and install recovery and try install wicked or maybe gpe. Btw the last ROM I was running was Gpe by Kot49h danvd I think the name is
I'm The Second Person Who Claimed it Wasn't work
Sent from my SGH-M919 using Tapatalk