Backup Note 3 imei and restore it using adb
Backup Note 3 imei and restore it using adb – tools needed
Backup Note 3 imei – step by step
- Open command prompt and cd to folder where adb tools was extracted
- Make sure you have rooted your Samsung Galaxy Note 3 and usb debugging activated
- Check if your Note 3 detected in adb by execute this command :
adb devices
- Enter to android shell and get superuser right:
adb shell
su
- Find EFS’s partition block:
cd /dev/block/platform
ls
cd dw_mmc.0
ls
cd by-name
ll
This is ll command output:
root@ha3g:/dev/block/platform/dw_mmc.0/by-name # ll
ll
lrwxrwxrwx root root 2015-01-26 10:48 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-26 10:48 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-26 10:48 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-26 10:48 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-26 10:48 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-26 10:48 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-26 10:48 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-26 10:48 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-26 10:48 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-26 10:48 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-26 10:48 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-26 10:48 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-26 10:48 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-26 10:48 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-26 10:48 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-26 10:48 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-26 10:48 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-26 10:48 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs3 -> /dev/block/mmcblk0p6
- Now we know that EFS partitions is /dev/block/mmcblk0p3
- Backup note 3 imei / EFS using dd command:
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.backup
- Copy Note 3 EFS backup file into PC (exit from shell first):
adb pull /sdcard/efs.backup
Now we have Backup note 3 imei / EFS, keep this file.
- Open command prompt and cd to folder where adb tools was extracted
- Make sure you have rooted your Samsung Galaxy Note 3 and usb debugging activated
- Check if your Note 3 detected in adb by execute this command :
adb devices
- Enter to android shell and get superuser right:
adb shellsu
- Find EFS’s partition block:
cd /dev/block/platformlscd dw_mmc.0lscd by-namell
This is ll command output:
root@ha3g:/dev/block/platform/dw_mmc.0/by-name # ll
ll
lrwxrwxrwx root root 2015-01-26 10:48 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-26 10:48 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-26 10:48 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-26 10:48 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-26 10:48 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-26 10:48 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-26 10:48 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-26 10:48 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-26 10:48 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-26 10:48 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-26 10:48 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-26 10:48 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-26 10:48 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-26 10:48 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-26 10:48 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-26 10:48 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-26 10:48 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-26 10:48 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-26 10:48 m9kefs3 -> /dev/block/mmcblk0p6
- Now we know that EFS partitions is /dev/block/mmcblk0p3
- Backup note 3 imei / EFS using dd command:
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.backup
- Copy Note 3 EFS backup file into PC (exit from shell first):
adb pull /sdcard/efs.backup
Now we have Backup note 3 imei / EFS, keep this file.
Restore Note 3 imei – step by step
In case your note 3 EFS corrupted so the phone’s baseband version become unknown and imei become null or imei become 0049xxxxxxxxxxx, you can restore the backup note 3 imei /EFS file:
- Copy the efs backup file from pc to device
adb push efs.backup /sdcard/
- Restore it
dd if=/sdcard/efs.backup of=/dev/block/mmcblk0p3
- Reboot the phone
reboot
Now the phone’s imei and baseband version back to normal 
In case your note 3 EFS corrupted so the phone’s baseband version become unknown and imei become null or imei become 0049xxxxxxxxxxx, you can restore the backup note 3 imei /EFS file:
- Copy the efs backup file from pc to device
adb push efs.backup /sdcard/
- Restore it
dd if=/sdcard/efs.backup of=/dev/block/mmcblk0p3
- Reboot the phone
reboot
Now the phone’s imei and baseband version back to normal
http://www.androidunbrick.com/17-baseband-unknown-problem-samsung-phones
Baseband unknown problem on Samsung phones
Baseband unknown problem – What is baseband and how it works in Samsung phones
Baseband is a system that handle radio / RF in Samsung phones. Most of Samsung phones use 2 processor. One is AP or application processor (exynos, nvidia, omap, novathor, qualcomm) and the other is CP or Communication processor / baseband processor (most of it using Intel chipset). To make the baseband system works, it need both of working hardware and software that related to baseband it self.
Baseband is a system that handle radio / RF in Samsung phones. Most of Samsung phones use 2 processor. One is AP or application processor (exynos, nvidia, omap, novathor, qualcomm) and the other is CP or Communication processor / baseband processor (most of it using Intel chipset). To make the baseband system works, it need both of working hardware and software that related to baseband it self.
Baseband unknown problem – Hardware of baseband system
We will use Samsung Galaxy S4 I9500 for this hardware example. Some hardware part related to baseband system :
- Baseband chipset : Intel PMB9820, this part is main processor of baseband system.
- AP chipset : Exynos 5410, the main processor need to communicate with baseband processor using IPC. IPC are used to transfer Voice data, SMS data, Net (browser) data between CP and AP.
- PMIC / Power Management IC : S2MPS11, provide voltage supply and 32KHz clock source for baseband processor.
- RF IC : Intel PMB5745, provide main clock for baseband processor.
- eMCP / eMMC : Samsung KMV3W000LM-B310, storage used by application processor and DDR / RAM used by baseband processor
We will use Samsung Galaxy S4 I9500 for this hardware example. Some hardware part related to baseband system :
- Baseband chipset : Intel PMB9820, this part is main processor of baseband system.
- AP chipset : Exynos 5410, the main processor need to communicate with baseband processor using IPC. IPC are used to transfer Voice data, SMS data, Net (browser) data between CP and AP.
- PMIC / Power Management IC : S2MPS11, provide voltage supply and 32KHz clock source for baseband processor.
- RF IC : Intel PMB5745, provide main clock for baseband processor.
- eMCP / eMMC : Samsung KMV3W000LM-B310, storage used by application processor and DDR / RAM used by baseband processor
Baseband unknown problem – Software of baseband system
Below are software part of the baseband system :
- Modem firmware, in Samsung firmware file, there is modem.bin file that will be flashed to the modem partition in firmware upgrading / updating. This softwre part used to communicate with the baseband system hardware.
- EFS partition, used to store imei certificate, and other security related parameter.
Below are software part of the baseband system :
- Modem firmware, in Samsung firmware file, there is modem.bin file that will be flashed to the modem partition in firmware upgrading / updating. This softwre part used to communicate with the baseband system hardware.
- EFS partition, used to store imei certificate, and other security related parameter.
Baseband unknown problem – The Symptoms
- The Phone can enter the menu, and when we go to about phone on the settings menu, the baseband version is unknown. The phone can’t registered to any network, can’t make a call, and when we type *#06# on dialer, it show imei null / null.
- The phone can’t enter the menu, just stuck on Samsung logo. The phone can enter recovery mode by pressing power + home + volume up button while in off state, and in recovery mode there is red words “can’t mount /efs”.
- The Phone can enter the menu, and when we go to about phone on the settings menu, the baseband version is unknown. The phone can’t registered to any network, can’t make a call, and when we type *#06# on dialer, it show imei null / null.
- The phone can’t enter the menu, just stuck on Samsung logo. The phone can enter recovery mode by pressing power + home + volume up button while in off state, and in recovery mode there is red words “can’t mount /efs”.
Baseband unknown problem – Solutions
After we know how the baseband system works either hardware part and software part, we can try some method to fix baseband unknown problem.
- Baseband unknown problem solutions by software part :
- Try to flash only modem firmware part using lower modem version.
- Try to repair EFS using odin or ADB or eMMC direct method.
- Baseband unknown problem solutions by hardware part :
- Check the baseband processor supply voltage, replace problematic part if any.
- Check the 32KHz clock from PMIC to baseband processor, replace PMIC if no 32KHz clock.
- Check the main clock from RF IC to baseband processor, replace RF IC if no main clock supply.
- Try to change eMCP / eMMC in case of broken DDR inside it.
After we know how the baseband system works either hardware part and software part, we can try some method to fix baseband unknown problem.
- Baseband unknown problem solutions by software part :
- Try to flash only modem firmware part using lower modem version.
- Try to repair EFS using odin or ADB or eMMC direct method.
- Baseband unknown problem solutions by hardware part :
- Check the baseband processor supply voltage, replace problematic part if any.
- Check the 32KHz clock from PMIC to baseband processor, replace PMIC if no 32KHz clock.
- Check the main clock from RF IC to baseband processor, replace RF IC if no main clock supply.
- Try to change eMCP / eMMC in case of broken DDR inside it.
Baseband unknown repair on Samsung S3 I9300 and Note II N7100
Baseband unknown problem is one of the most common problem affected to Samsung Galaxy SIII I9300 and Note 2 N7100. You can try to fix it by using software method because one thing that causes it is EFS corruption. First thing first we need to know the symptoms of EFS corruption on I9300 and N7100 :
- The Phone can enter the menu, and when we go to about phone on the settings menu, the baseband version is unknown. The phone can’t registered to any network, can’t make a call, and when we type *#06# on dialer, it show imei null / null.
- The phone can’t enter the menu, just stuck on Samsung logo. The phone can enter recovery mode by pressing power + home + volume up button while in off state, and in recovery mode there is red words “can’t mount /efs”.
How to fix baseband unknown on Samsung Galaxy S3 I9300 and Note 2 N7100
We need some file and software:
Here’s the steps to fix baseband unknown on Samsung Galaxy S3 I9300 and Note 2 N7100
- Open Odin3 v1.85 software
- Choose correct efs file depend on the phone type in PDA file
- Put the phone into download mode by pressing power + home + volume down button and then choose continue and plug the usb cable until odin software detect it
- Press start and wait until it finished.
If the phone’s condition still haven’t changed, then we can’t fix baseband unknown problem by this software method because the causes is not an EFS corruption. But if the baseband version is shown and if we type *#06# on dialer it show 0049xxxxxxxxxxx, the phone’s EFS has been fixed but can’t registered to network and make a call yet. We need to repair the phone’s imei first using Z3X box or Octoplus box software
ไม่มีความคิดเห็น:
แสดงความคิดเห็น