Dear Fellows,
After a bad upgrade in a SGS I9000b, my phone does not recognize your own imei (bad efs).
I had made a backup of my EFS using only RootExplorer, and now I can´t change files permissions.
My system uses /dev/block/stl3 to mount /efs
I cannot change /efs (not have permissions to change when its mounted and if I umount folder, changes aren´t saved).
I need a solution to make a new stl3 using my efs backup to be used on ODIN.
It is possible to build a new efs using my data (imei number, bluetooth mac, etc,etc) of Samsung Galaxy I9000b?
Thanks for any help.
i want an efs backup in img format without nv-data.bin i have my imei so no problem is in giving it as it does not leak your personal information like imei
Hello guys, so i have a problem with my s3 i9305 I lost my IMEI and my phone is on factory mode the problem is that i don't have a QPCT nor a EFSPRO backup, I have an efs created by amcha rom when i was installing it with aroma i had the option to chose to backup the efs in my SDcard , i don't know how to restore it its a .tar.gz i tried to copy the files in the Efs folder using rootexplorer but still the same problem no imei or signal any help would be appreciated.
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
(°_o) said:
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
Click to expand...
Click to collapse
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
MYEUHD said:
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
Click to expand...
Click to collapse
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
MYEUHD said:
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
Click to expand...
Click to collapse
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
xc-racer99 said:
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
Click to expand...
Click to collapse
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
(°_o) said:
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
Click to expand...
Click to collapse
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
xc-racer99 said:
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
Click to expand...
Click to collapse
The mtd doesnt interface the whole NAND storage.. so i'm gonna have to rebuild the kernel exposing the original efs partition..
Let's see how it goes.
@xc-racer99
I dumped the 10mb parition but it wasnt mountable by any means..
Then I hex viewed it and it showed.. FSR_STL in beginning..
Which lead me to, https://github.com/Benjamin-Dobell/Samsung-Read-Only-FSR/blob/master/Inc/FSR_STL.h
So unless I check out the STL implementation or use one that is I guess I have to go back to stock :\
I cannot get any valid data from the dump.
I've attached the dump of it, if youre intrested.
hi
i have a730f efs damaged i dont have backup the device is stay on logo in recovery show efs directory error and frp & ome is on android 8 oreo i flashed combination but the problem is not solved any body can help??? ineed efs file
Efs
Up
a730f efs
you found it A730F EFS?