Hello my freindes
i rooted my sm-c7000 and after download a custom rom it stuck on logo so i back to stuck rom but when i go to recovery mode it said "E:failed to mount /efs (Invalid argument)" and after search on google i found that i should flash esp by odin
so i need the EFS for C7000ZH please
+------------------------+
Thanks in advance
Best regards
@misyo.nour
EFS isn't a file but is a partition on your Android device that stores all the important data associated with your phone. For instance, these data include the IMEI number, Mac address of Wireless devices, important files of internet and product code, etc. Hence the EFS partition holds data to a specific phone, isn't generic, will say can't simply get transferred from one phone to another one.
jwoegerbauer said:
@misyo.nour
EFS isn't a file but is a partition on your Android device that stores all the important data associated with your phone. For instance, these data include the IMEI number, Mac address of Wireless devices, important files of internet and product code, etc. Hence the EFS partition holds data to a specific phone, isn't generic, will say can't simply get transferred from one phone to another one.
Click to expand...
Click to collapse
is there any way to fix it so i can open wifi and blutooth ??
btw sim card working fine
Related
TLDR: Phone was bricked revived it now stuck with generic IMEI
Ok so basically my GS3 got bricked dont know exactly why but in recovery it said e: failed to mount /efs (Invalid argument) i was able however to revive it with this thread post #4 ( http://forum.xda-developers.com/showthread.php?t=2204960 ) but now my IMEI is "generic" 004999010640000 and now i cant connect to the network. Im on a mac and the only tutorials ive seen are for windows. my question is is there anyway to change it from the phone itself or on a mac? Sorry if this has been asked before but if anyone can point me in the right direction that would be great.
PS i know changing your IMEI is HIGHLY illegal but i just want to change it back to the original one on the back of the phone.
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Im on a mac...
oh im sorry but if you read the whole thing IM ON A MAC so anyway to fix this would be great...
djembey said:
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Click to expand...
Click to collapse
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Ok so i have a backup but its the coorrupted one... anyway to open up the .img and copy the files manually on a mac? sidenote when i restore the corrupted one im in a boot loop
JJEgan said:
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Click to expand...
Click to collapse
Sorry not a clue don't even know how to switch a Mac on .
jje
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
so i tried that and wasnt able to boot past the i9300 screen. any other suggestions?
d4fseeker said:
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
Click to expand...
Click to collapse
ugh
Ok so i havent updated this in awhile but here it goes...
First i installed ubuntu on my mac and converted my corrupted EFS partition to .iso and opened it in linux. Anyway no files in there.
Second the samsung service center here in alaska is only for TVs...
Third ill call samsung on monday but dunno what i can do besides save up for another phone or a octopus box or what you call it.
OK so I'm sure this would be of benefit to many I605 users. Does anyone have the factory EFS folder minus the device specific info.
In an attempt to regain lost storage during the install of Linux on android I had erased and cleared EFS during a re flash of the Kies factory mj9 image. This was before anyone had posted that anyone wanting to install custom roms should not Flash this version.
I am aware that the EFS folder contains all of the device specific info required to provide proper cellular connectivity, and that people will not share this folder not wanting to give away their own devices identity.
What I'd like to know is what files exactly contain what device information. I may be mistaken but many of the files are provider specific and not device specific which would help me in repairing the Baseband Version. UNKNOWN. Apparently with the baseband unknown many of the I'm either repair tools will not properly connect to the phone to write the proper Imei.
Cmon guys with this wealth of knowledge here on this board I would think this wouldn't be such a hard thing to repair. Besides the Imei what other private device specific info is found in the EFS. It's already well known that that the Imei is found at the 550 memory address with this being the case this could be deleted and added after the EFS has been restored.
Some one please help.
Hi guys.
Disclaimer:
Changing or messing up with IMEI may be banned in your area or country of residence. Please check with your local regulations before attempting to modify the IMEI and related information of your phone. I take no responsibility whatsoever for your attempts to change any such information. This thread does not support in anyway to deliberately modify the identity of the phone.
Click to expand...
Click to collapse
1. PDS partition does not determine IMEI.
As you know PDS is actually at /dev/block/mmcblk0p26 or /dev/block/platform/msm_sdc.1/by-name/pds. When the phone boot it mounts this partition at /pds. After blowng up my IMEI, this partition was still mounting at /pds and had data untouched in it. So this partition is really not important. Also i read on another thread, people with backup also cud not restore their IMEI.
2.When giving command "fastboot erase all", the following partitions are erased:
a. hob (located at /dev/block/platform/msm_sdcc.1/by-name/hob)
b. dhob (located at /dev/block/platform/msm_sdcc.1/by-name/dhob)
c. fsc (located at /dev/block/platform/msm_sdcc.1/by-name/fsc)
There are other partitions erased as well such as fsg,modemst1, modemst2 etc. But these partitions are restored when we flash stock ROM. So they can be taken out of picture.
Possible solutions:
1.Restoring a QCN backup through QPST after putting the phone in BP Tools mode.
Unfortunately this doesn't work as the NV area of the Moto E2(possibly all motos) is write protected.i.e,we won't be able to restore the modified qcn file.
So no luck here.
2.Restoring fsc,hob and dhob files from a working Moto E 2015.
This is something that could work.
As confirmed by many users,restoring these partitions from a working device gives back the radio functionalities but not the IMEI.
If any has more info,they are more than welcome.
Let's get these babies working again.
Sources:http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970 and ofcourse me(solutions part).
Hi guys,
I'm still owning an old i9300 and would like to flash CM14.1 to it (already have the same model running CM14).
This particular device is.. well kind of soft bricked - I think. I'm running out of ideas.
It shows the developer IMEI 00049... and no valid serial #
Not a single howto/patched kernel/app is solving this. I searched not only the xda-developers forum but all parts of g**gle I can handle the language
What I tried already:
- Installed the stock FW with ODIN (even after a full wipe of the internal eMMC partitions with CM13 as root )
- Downgraded to 4.0.4 ICS (and in this step I was able to re-create the serial # by manually patching nv_data and .nv_data)
- Removed /efs with mke2fs and let the device re-create it (it re-creates all the necessary files including nv_data.bin etc.) - without showing the IMEI
- Built a serial cable to talk to the modem (nice - but no solution for my problem)
- Maybe my biggest mistake: Tried (by accident) to restore an entire OS from a similar phone - INCLUDING /efs - to this phone. After that step my phone displayed a while the wrong serial #
My questions are:
- If I delete all the partitions of the internal eMMC (dd if=/dev/zero of=/dev/block/mmcblk0 - DON'T TRY THIS AT HOME). From *where* is /efs re-created? Where exactly is serial รค and IMEI stored?
- Is there a chance to bring this device back to live? I really want to bring this device to a repair shop, but the repair shop in my village does not even know what /efs or UART is - they are replacing just glasses and stuff
And: No, I don't have an /efs backup of this phone....
Have you tried flashing via kies?.
Yes you did brick it by cross flashing another devices identity.
If the device is an international btu you can try flashing the stock rom twice with a factory reset in between. If no joy then try kies again. The phone has lost who it is. You have to get it to remember.
The stock btu rom: https://drive.google.com/file/d/0B4vTiHTBB629OVlvY0pkcXN4ak0/view?usp=drivesdk
Beamed in by telepathy.
Hello shivadow,
shivadow said:
Have you tried flashing via kies?.
Click to expand...
Click to collapse
Yes - *plenty* of times (like 20..30) to rest the device to a defined state after a non-working [patched modem|EFS-repair|differnent firmware|...]
shivadow said:
The stock btu rom: [...]
Click to expand...
Click to collapse
Thanks a lot - but even this firmware does not help (I tried this - oh, before Christmas holidays, I think)
In the meantime I have learned a lot about the EFS folder:
- Never, ever restore a foreign EFS folder - it will not work
- Manually fiddling around with the nv_data bin is hard work (although I'm now able to switch the serial number back to the one printed under the battery)
- The device is fixable, but most probably not without a box - just because the necessary information is not freely available. With a free trial of a software I was able to reset the IMEI to a fake one and all of sudden I had network and was able to make calls
- With some AT+MSLSECUR/AT+IMEITEST stuff I'm not able to set the IMEI - it seems some certificate is missing (maybe the protection from Samsung for modifying the IMEI?). I was always stuck in the last step: actually write/set the IMEI does not work.
I think tomorrow I will bring the device to a repair shop in a larger town (they will have the knowledge I hope) and then I will compare broken EFS/fixed EFS (i.e. nv_data.bin) to learn even more.
So, you flashed another devices nvram and didn't have a backup of your own?.
Beamed in by telepathy.
shivadow said:
So, you flashed another devices nvram and didn't have a backup of your own?.
Click to expand...
Click to collapse
Exactly - it restored by mistake the backup to the wrong device. So not even parts of the original EFS folder - not even one single bit - is available. (Of course, the EFS folder of the wrong device is also not working...)
Looks like the phone will need to be repaired by a cell shop.
Hi guys,
the people in a repair shop were able to restore the original IMEI although undelete/forensics in an ext4 FS is not what I do every day it looks like:
- "they" replaced the nv_data.bin with another one (maybe some "empty" one?)
- the IMEI is definitely properly integrated (*#0011# menu is telling "IMEI CERTI: PASS and AT+MSLSECUR is now requesting a proper certificate)
Now I will start some investigation with the two (well, three) different versions of nv_data.bin
I'm still wondering *where* an i9300 is storing the identity after i.e. an eMMC replacement..
Has somebody particular informations of the RPMB area of the eMMC? Maybe I'm going to JTAG that device to find out...
Hello guys, first of all: thank you very much for your Forum; I'm learning a lot even if I remain a complete noob!
I'm trying to use LineageOS 17.1 (lineage-17.1-20210118-UNOFFICIAL-a3y17lte, recovery OrangeFox 11.01) on Galaxy A3 2017 (SM-A320FL), and I did something really stupid trying to make Link2App work.
I had problems to format properly the miniSD using Android's apps, and I could not remove the card from the phone (the slot's opening is damaged). So then I tried to format the card using ADB + BusyBox + fdisk, BUT I did it while I was distracted by other job's issues, and I didn't realize I was working on the internal SD instead of on the removable card (yes, complete idiot...).
Result: a brand new empty partition table in my phone, permanently stuck in Download mode (impossible even to power off it).
I tried to restore the phone using this procedure, but it failed midway. By the way, I could Odin-flash TWRP and then restore the partitions using the repartion script. Eventually, I fleshed my OrangeFox and LineageOS: the system is now perfectly working, but the phone doesn't recognize any more my SIM and IMEI (dialing: *#06#) is blank.
I had a Fox's "light" backup, but it didn't solve anything.
I'm still having the original box with the IMEI number on the label, but I didn't find a suitable procedure to use it.
Kies3: the SM-A320 phone seems too old to allow the Initialization procedure described here (yes, the phone was unplugged)
There are many apps promising miracles (for instance: ToolHero, MTK Engineering Mode, IMEI Generator Pro, EFT Dongle...); however, I tried some, and they seem to me just ****ty pieces of software, requiring the original system or dubious paid services.
Dialing codes* procedure (like Method 1 here). I cannot remove SIM or battery to complete the procedure. Besides, my phone doesn't react to the code; probably they are country or SIM specific...
Line command (terminal emulator or ADB): this seems to be the most promising method; however, the line
Code:
echo 'AT +EGMR=1,7,"MY_IMEI_NUMBER"'>/dev/pttycmd1
doesn't do anything on my device
IMEI generator: I tried to generate a new MP0B_001 file using this guide. The download link is broken, then I downloaded the files from another source, and I prefer to add to my system just the MPB_001, without flashing the "repair" tool. Besides, I don't have any /nvram folder in my $root/data/ directory... (the only IMEI related folder is in $root/eps/).
Any suggestion to solve this mess? Thank you very much!
Daniele
* EDIT: after typing *#*#197328640#*#* the phone window closes.
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
jwoegerbauer said:
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
Click to expand...
Click to collapse
Thank you very much for your answer! The 2-3 methods seem promising; however, I isolated the problem and solved it before receiving your message.
The problem: after messing with the partitions, I tried to restore my system, downloading the files via Freja. However, I select the wrong CSC, using my SIM provider code (TIM) instead of the generic code for Italy (ITV).
I noticed it exploring the light backup I had done in TWRP (only System partition): a CSC_version.txt was there, pointing to A320FLOXA9CTK1 (ITV version, while I restored using A320FLTIM8CTH1, TIM carrier version). ITV was also mentioned in the file $ROOT/eps/imei/mps_code.dat (dunno if this is relevant)
Solution: Odin + the right firmware did the trick. I had my IMEI back and the phone working, then I came back flashing TWRP, Orangefox and, eventually, LineageOS.
Everything is working now, and, of course, I backed up EPS partition (now).
Many thanks!
daniele