Database Users

[SOLVED] BASEBAND "unkown" EMEI "unkown" - EFS Backup available

Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4

Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
...
Click to expand...
Click to collapse
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.

xclub_101 said:
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
Click to expand...
Click to collapse
ok thank you - bad news
Ill try this guide: (Can this guide be used with KK 4.4.2 ?)
http://forum.xda-developers.com/showthread.php?t=2567133
What about the "unkown baseband"? How can this be fixed?

Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again

Bro whats a twrp efs backup?

Team win recovery Project. Its a revovery and a twrp efs Backup is a Backup from the 3 efs partitions in twrp
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Will a TWRP boot ,data and system backup work as well for restoring baseband? I have the same problem -> http://forum.xda-developers.com/showthread.php?t=2796948&page=6

No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
So have I run out of options? Please have a look at my thread. The last few posts especially . Any help would be appreciated.

Please help sm-n900
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
just went to the above mentioned link but none of the multiupload files link work.
could you upload the NOTE 3 - Fix soft bricked.rar and the Samsung drivers.
I want to extract the NOTE 3 - Fix soft bricked.rar and modify it for use in sm-n900

Sorry I don't have these files anymore try to get them from the thread owner
Gesendet von meinem SM-N9005 mit Tapatalk

Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Hi, I have the same problem as you did, my baseband is showing unknown and the imei is showing null. This happened when I was installing a different modem via ODIN. I do have a EFS backup, however, it was done with philz recovery instead of TWRP and has 4 files ('efs.ext4.tar'; 'efs.ext4.tar.a'; 'nandroid.md5'; and 'recovery.log'). Are these the same that you would get with a TWRP?
I also have another efs backup that I did which is one file only, 'efs_20140531_122400.img'. Would I be able to use this for anything?
The phone is an N9005 on Kitkat.
Thanks for any help in advance and please let me know if you need any other info.
Cheers
--------------------------
Just to let you know,
I had tried flashing flash latest full UK NF4 system before and it didn't work. However, desperate as I was, I went again and gave it another shot and incredibly enough, it worked!!!! Phone is back together again!!!! Yeeahh!!! There goes an incredible load off my shoulders. I guess I did something in between that actually helped, we may never know.
Cheerio

Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Click to expand...
Click to collapse
Hi Hundsbuah,
I upgraded my Note 3 9005 Hong Kong Version 32 GB from Jelly Bean to KitKat without taking backup of EFS and now I have IMEI Null and Baseband unknown. I found backup of other user's note3 EFS at "http://forum.xda-developers.com/showthread.php?t=2447342". So, if I tried EFS restore from above link will it resolve my IMEI null and baseband unknown issue?
Regards,
Asif

[Q] SM-N900 EFS nv_dat.bin corrupt EFS etc Pease HELP!!!!

I have a sm-n900 exynos and I have lost my imei and baseband during a Samsung flash. I have a TWRP backup, efs.img backup by dr.ketan's backup tool but nothing is able to restore my efs. I have scanned emmc blocks for bricked blocks and all blocks come back as non-corrupted. may be the partition is corrupted .how do I erase my efs partition to rebuild it. I have tired to flash PIT from ODIN but that too doesn't work.
tried this post http://forum.xda-developers.com/show...567133&page=36
but need a guide to identify the partitions and how to rebuild them. by any chance anyone know if I could extract twrp backup to files to restore efs or from efs.img so I can use the nv_data.bin, since tried restoring the backups and it didn't restore I feel the partition might be corrupt and hence not being re-written. so might be I have to rebuild the partitions by formatting as explained in this thread. but I don't know exactly the steps for exynos variant. I tried using terminal on twrp but mkef2 command shows mmbcblkp03 doesn't exist which as I have read in posts is the efs partition on this phone and reboots to twrp recovery. and mmbcblkp12 show filesystem too small and reboots to twrp recovery
Can some one upload sm-n900 efs folder may be can try and edit nv_data in hex editer

mithudas28 said:
I have a sm-n900 exynos and I have lost my imei and baseband during a Samsung flash. I have a TWRP backup, efs.img backup by dr.ketan's backup tool but nothing is able to restore my efs. I have scanned emmc blocks for bricked blocks and all blocks come back as non-corrupted. may be the partition is corrupted .how do I erase my efs partition to rebuild it. I have tired to flash PIT from ODIN but that too doesn't work.
tried this post http://forum.xda-developers.com/show...567133&page=36
but need a guide to identify the partitions and how to rebuild them. by any chance anyone know if I could extract twrp backup to files to restore efs or from efs.img so I can use the nv_data.bin, since tried restoring the backups and it didn't restore I feel the partition might be corrupt and hence not being re-written. so might be I have to rebuild the partitions by formatting as explained in this thread. but I don't know exactly the steps for exynos variant. I tried using terminal on twrp but mkef2 command shows mmbcblkp03 doesn't exist which as I have read in posts is the efs partition on this phone and reboots to twrp recovery. and mmbcblkp12 show filesystem too small and reboots to twrp recovery
Can some one upload sm-n900 efs folder may be can try and edit nv_data in hex editer
Click to expand...
Click to collapse
Could you provide more details about the backup you have:
- What files do you have? What is the name of these files, and also the file sizes?

vndnguyen said:
Could you provide more details about the backup you have:
- What files do you have? What is the name of these files, and also the file sizes?
Click to expand...
Click to collapse
I HAVE efs.img created my Dr. Ketan's EFS tool and which had worked succefully so presume it's a good copy, I have a completeTWRP backup of installed VNROM 13.1 which doesn't have the new baseband problem of NE3 in vnrom 14, and have used to rstore efs earlier and has worked successfully.
files I have
efs.img 20 Mb
attached screenshot of twrp backup

Deleted

georgesmh said:
Did u try to flash the previous modem?
Anyways this is an EFS backup
removed
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
If that's your EFS back up, I'd remove it, or someone else is gonna enjoy your IMEI

radicalisto said:
If that's your EFS back up, I'd remove it, or someone else is gonna enjoy your IMEI
Click to expand...
Click to collapse
Haha damnn thanks dude I didnt know
Sent from my SM-N900 using Tapatalk

georgesmh said:
Haha damnn thanks dude I didnt know
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Keep your EFS info as private as you do your ATM card Pin number my friend :good:

georgesmh said:
Deleted
Click to expand...
Click to collapse
I know its risky but could you please please send me the efs, once my device gets its base band and is up and running i will restore my own efs backup. I dont need to use your iemi and trust me i wont. I would be grateful for to you pleade help me . Tou xould pm me the upload please. A beey veey himble and desperate request.

mithudas28 said:
I HAVE efs.img created my Dr. Ketan's EFS tool and which had worked succefully so presume it's a good copy, I have a completeTWRP backup of installed VNROM 13.1 which doesn't have the new baseband problem of NE3 in vnrom 14, and have used to rstore efs earlier and has worked successfully.
files I have
efs.img 20 Mb
attached screenshot of twrp backup
Click to expand...
Click to collapse
So it seems you have the correct backup for your device. Some more questions:
1- Can you show the link to the EFS tool you have used to make a backup?
2- What is your difficulty now? You don't know how to restore? Cannot restore? Or you already restored but the problem still persist?
Please be noted that you have to restore ALL efs-related partitions, NOT only 1 partition.
At the moment, my app 'IMEI Backup ★Samsung★' can only restore from the backup that has been made by it. But I will add the ability to restore from the backup which was made by other apps, may be in the next release.

vndnguyen said:
So it seems you have the correct backup for your device. Some more questions:
1- Can you show the link to the EFS tool you have used to make a backup?
2- What is your difficulty now? You don't know how to restore? Cannot restore? Or you already restored but the problem still persist?
Please be noted that you have to restore ALL efs-related partitions, NOT only 1 partition.
At the moment, my app 'IMEI Backup ★Samsung★' can only restore from the backup that has been made by it. But I will add the ability to restore from the backup which was made by other apps, may be in the next release.
Click to expand...
Click to collapse
yes i tried to restore both the baxkups and even the whole twrp backup but unfortunatly the system gets restored but not the imei. The link for the tool
https://play.google.com/store/apps/...+tool&pcampaignid=APPU_ALKrU4PHMMy5uAS4yYDYDA

mithudas28 said:
yes i tried to restore both the baxkups and even the whole twrp backup but unfortunatly the system gets restored but not the imei. The link for the tool
https://play.google.com/store/apps/...+tool&pcampaignid=APPU_ALKrU4PHMMy5uAS4yYDYDA
Click to expand...
Click to collapse
That means the above-mentioned app does not work correctly with the restoring job?
Has your phone been rooted? If yes, I will guide you some steps to restore manually.

Yes its rooted and has twrp recovery . It would be just great if you xould guide me
Sent from my SM-N900 using XDA Free mobile app

Hi , i have One question , is there a way to send the nv_data. Bin by adb command ?

request
Hi, please, can someone upload his efs.IMG from sm-n900 ?
I want to write it inside my phone to try with a box if it possible to write after my imei loosed.
I have null/null and no backup from telephone!

Calling Dr.Ketan need to reach you

Dear Dr.Ketan
since I have recently registered I am unable to post anything on the development thread. I am facing a serious problem. and I am asking you this because I had backed up efs.img 20 Mb and it has helped me restore earlier. but now it's failing to restore my efs. I am explaining the problem below.
I have a sm-n900 exynos and I have lost my imei and baseband during a Samsung flash. I have a TWRP backup, efs.img backup by dr.ketan's backup tool but nothing is able to restore my efs. I have scanned emmc blocks for bricked blocks and all blocks come back as non-corrupted. may be the partition is corrupted .how do I erase my efs partition to rebuild it. I have tired to flash PIT from ODIN but that too doesn't work.
1. could you tell me if it's possible to extract the efs.img to the efs files and will it help.
2. do you think there is a way I could retore from your tool using some other method.
i have tried the following things too
tried this post http://forum.xda-developers.com/show...567133&page=36
but need a guide to identify the partitions and how to rebuild them. by any chance if you know if I could extract twrp backup to files to restore efs or from efs.img so I can use the nv_data.bin, since tried restoring the backups and it didn't restore I feel the partition might be corrupt and hence not being re-written. so might be I have to rebuild the partitions by formatting as explained in this thread. but I don't know exactly the steps for exynos variant. I tried using terminal on twrp but mkef2 command shows mmbcblkp03 doesn't exist which as I have read in posts is the efs partition on this phone and reboots to twrp recovery. and mmbcblkp12 show filesystem too small and reboots to twrp recovery

Backup / Restore EFS

How to Backup / Restore EFS for Galaxy Grand Prime ????
PLEASE HELLLLLP

If you phone is rooted, With phillz touch recovery you can backup modem and efs. And off course restore that backup.

syverman said:
If you phone is rooted, With phillz touch recovery you can backup modem and efs. And off course restore that backup.
Click to expand...
Click to collapse
No , my devise is not rooted yet .
Is there any way 2 do that before rooting ??

Im Stuck on the Google Logo with non stop reboots after TWRP Restore.

Problem previously posted here has been fixed! Here is the official fix!
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users.
Users on other phones with the same problem await instructions!

This thread details what happened to a lot of us:
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I and a couple others managed to recover because we had a nandroid backup made with TWRP 3.0.2-0, and following a particular variation of restoring:
flash stock of whatever version your nandroid was -> flash TWRP 3.0.2-0 -> repair all partitions that are possible -> flash nandroid backup -> reboot -> flash stock (if still not fixed) -- full details in the (long) thread.
Not sure if anyone without a previous backup reported success.

vacaloca said:
This thread details what happened to a lot of us:
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I and a couple others managed to recover because we had a nandroid backup made with TWRP 3.0.2-0, and following a particular variation of restoring:
flash stock of whatever version your nandroid was -> flash TWRP 3.0.2-0 -> repair all partitions that are possible -> flash nandroid backup -> reboot -> flash stock (if still not fixed) -- full details in the (long) thread.
Not sure if anyone without a previous backup reported success.
Click to expand...
Click to collapse
As It turns out I think I might have found the ROOT of the problem. For me personally it turns out TWRP CORRUPTS the EFS partition! The 2 EFS backups it makes are wrong! When you restore it it ****s them up and it makes you unable to boot. I talked with some really in depth people and we did full Kernel log search through and it turns out that TWRP corrupts my EFS partition and causes the problem! The solution above might work since the old backups have the correct EFS. This is MY situation and might be others too! If anyone else has this problem please tell them to check their EFS partition!

bogomil4e said:
As It turns out I think I might have found the ROOT of the problem. For me personally it turns out TWRP CORRUPTS the EFS partition! The 2 EFS backups it makes are wrong! When you restore it it ****s them up and it makes you unable to boot. I talked with some really in depth people and we did full Kernel log search through and it turns out that TWRP corrupts my EFS partition and causes the problem! The solution above might work since the old backups have the correct EFS. This is MY situation and might be others too! If anyone else has this problem please tell them to check their EFS partition!
Click to expand...
Click to collapse
Not convinced that TWRP produces incorrect EFS backups (at least not 3.0.2-0, anyway) because I subsequently restored those after being soft bricked... if you meant that 3.0.2-1 corrupts EFS after restoring, then yes, that might make sense.
BTW, if you have a chance, could you assist me in this thread?
http://forum.xda-developers.com/nexus-6p/help/formatted-nexus-6p-persist-partition-t3453035

Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!

bogomil4e said:
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Click to expand...
Click to collapse
I never restored EFS partitions, I just bricked going from an Android N ROM back to a clean flash of a 6.0.1 ROM.
Hopefully this will help some users though, thanks for the update.
I already shipped my phone off to Huawei -_-

Hey guys, I just had this problem and thanks for this thread it got me all fixed up. Will TWRP 3.0.2-2 be good?

DeathmonkeyGTX said:
Hey guys, I just had this problem and thanks for this thread it got me all fixed up. Will TWRP 3.0.2-2 be good?
Click to expand...
Click to collapse
Decide for yourself by reading post #64 in this Announcement thread:
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119/page7
Sent from my Nexus 5X using Tapatalk