K TOOL doesnt work
yakirz said:
K TOOL doesnt work
Click to expand...
Click to collapse
for I9500 ONLY
download terminal emulator to your I9500. open it and type (enter, after each command)
for backup:
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
to restore if something goes wrong :
Code:
su
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
NB Beware! make sure you type it exactly!
samersh72 said:
for I9500 ONLY
download terminal emulator to your I9500. open it and type (enter, after each command)
for backup:
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
to restore if something goes wrong :
Code:
su
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
NB Beware! make sure you type it exactly!
Click to expand...
Click to collapse
Will this also work for the I9505 model of the Galaxy S4? I've attempted to run /efs backups using the terminal emulator (with root access) with a different set of commands, but I keep getting the error message "tar: not found"...
samersh72 said:
for I9500 ONLY
download terminal emulator to your I9500. open it and type (enter, after each command)
for backup:
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
to restore if something goes wrong :
Code:
su
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
NB Beware! make sure you type it exactly!
Click to expand...
Click to collapse
dd command is great for that purpose... Actually it can backup any partition... I would do them all and store them in my hard drive...
the best way to back up ur efs
yakirz said:
K TOOL doesnt work
Click to expand...
Click to collapse
Your phone must be rooted..
download TWRP recovery (flash right twrp version for your version of phone
Install it then reboot to recovery
then
in menu
Go to back up
and
Check the efs
thx
Please post upload EFS!!
I cant to boot complete!!! EFS Invalid Argument... please upload your backup brother for to test with me....I need that sdcard/efs.img
Regards
Efs Backup App
http://forum.xda-developers.com/showthread.php?t=2379400
Please follow the link, This app does a pretty good job for EFS Backup & restore
Note : root is required
To do terminal emulator trick root is needed?
Sent from my GT-I9500 using Tapatalk 4 Beta
You can use cwm or simple is flash some rom which can backup efs as crash, phoenix,etc
Sent from my GT-I9500 using Tapatalk 4
arolopez said:
To do terminal emulator trick root is needed?
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yes you need root to use terminal emulator
samersh72 said:
yes you need root to use terminal emulator
Click to expand...
Click to collapse
please help even after using terminal emulator my s4(i9500) is not registering to network. i have already backed up my efs using emulator but after flashing another rom & restoring via android terminal my phones not working. what to do now?
shahriarthe1 said:
please help even after using terminal emulator my s4(i9500) is not registering to network. i have already backed up my efs using emulator but after flashing another rom & restoring via android terminal my phones not working. what to do now?
Click to expand...
Click to collapse
On what rom, firmware you are now? And what did you flash?
Sent from my Galaxy Nexus using xda premium
samersh72 said:
On what rom, firmware you are now? And what did you flash?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
let me explain in details.....i flashed MH1 few days ago, after then i flashed back to my previous MG5 firmware & lost my IMEI. anyway when i flashed MH1 again & my IMEI was back again, then i backed up EFS using android terminal & andromizer both. then i flashed back to MG5 & restored the EFS but stil failed to got my IMEI so (not registered to any network starts again) really help me somebody?
shahriarthe1 said:
let me explain in details.....i flashed MH1 few days ago, after then i flashed back to my previous MG5 firmware & lost my IMEI. anyway when i flashed MH1 again & my IMEI was back again, then i backed up EFS using android terminal & andromizer both. then i flashed back to MG5 & restored the EFS but stil failed to got my IMEI so (not registered to any network starts again) really help me somebody?
Click to expand...
Click to collapse
efs is fine, but it is just not detected.
i guess you can not downgrade.
flash MG9 modem twice as "phone" with odin http://forum.xda-developers.com/showthread.php?t=2192025 (first flash untick "auto-reboot" when it pass, remove battery, insert it, re-flash modem)
samersh72 said:
efs is fine, but it is just not detected.
i guess you can not downgrade.
flash MG9 modem twice as "phone" with odin http://forum.xda-developers.com/showthread.php?t=2192025 (first flash untick "auto-reboot" when it pass, remove battery, insert it, re-flash modem)
Click to expand...
Click to collapse
thanks for all the help
What to do if i want to upgrade? why do i have to flash mg9 modem since i already have the IMEI intact in my MH1? sorry i'm kinda noob at this.
what will happen if i flash MG9 modem?
please answer
shahriarthe1 said:
thanks for all the help
What to do if i want to upgrade? why do i have to flash mg9 modem since i already have the IMEI intact in my MH1? sorry i'm kinda noob at this.
what will happen if i flash MG9 modem?
please answer
Click to expand...
Click to collapse
sometimes efs partition is not detected when moving from new to old modem.
so if you flash a newer modem, efs will be detected.
you are moving from MH1 to MG5, from new to old so you need a newer modem to read efs partition.
you can flash MH1 modem or other new modem, but MG9 is working fine and tested with newer firmware
why would you revert to MG5 and not still on MH1?
samersh72 said:
sometimes efs partition is not detected when moving from new to old modem.
so if you flash a newer modem, efs will be detected.
you are moving from MH1 to MG5, from new to old so you need a newer modem to read efs partition.
you can flash MH1 modem or other new modem, but MG9 is working fine and tested with newer firmware
why would you revert to MG5 and not still on MH1?
Click to expand...
Click to collapse
thanks a ton...now i understand. I tried back to MG5 coz i didnt like "claro" to be shown up every time i reboot.
What if i try flashing a new rom? will it detect my modem? i already tried MH2 (correct me if i'm wrong. isnt it upgraded than MH1) & failed.
shahriarthe1 said:
thanks a ton...now i understand. I tried back to MG5 coz i didnt like "claro" to be shown up every time i reboot.
What if i try flashing a new rom? will it detect my modem? i already tried MH2 (correct me if i'm wrong. isnt it upgraded than MH1) & failed.
Click to expand...
Click to collapse
usually it must work. and as i said earlier, it happen sometimes. (moving from new to old and sometimes vice versa)
you have always the option of flashing the new modem (twice) of the new firmware alone when efs is not detected.
people think that efs partition is corrupted but in fact it is not detected
samersh72 said:
usually it must work. and as i said earlier, it happen sometimes. (moving from new to old and sometimes vice versa)
you have always the option of flashing the new modem (twice) of the new firmware alone when efs is not detected.
people think that efs partition is corrupted but in fact it is not detected
Click to expand...
Click to collapse
it worked!!!! thanks.....
learned a lot from you & hope to learn more in the coming future....
samersh72 said:
for I9500 ONLY
download terminal emulator to your I9500. open it and type (enter, after each command)
for backup:
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
to restore if something goes wrong :
Code:
su
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
NB Beware! make sure you type it exactly!
Click to expand...
Click to collapse
Does this work for the Latest Indian firmware???
Related
Galaxy note 3 sm-n900 kk 4.4.2 n900xxudnc1 official problem imei null/null
are there a solution ??
Repair is possible ??
I readed here in this forum that there's soluttion to make dowgrade to jb 4.3 some one can write the steps to do that if it's possible ??
Please heeeelp !! Thanks to all... :good: :good:
:crying: :crying:
Sorry bro I have no idea what u are talking about. But one thing I can answer the downgrade from 4.4 to 4.3 is not possible by now if. What exactly happened?
4aces said:
Sorry bro I have no idea what u are talking about. But one thing I can answer the downgrade from 4.4 to 4.3 is not possible by now if. What exactly happened?
Click to expand...
Click to collapse
baseband version unknown after upgrade to 4.4.2 via odin (1 month a go), no gsm network no sim detect, imei lost.
wissàm1981 said:
Galaxy note 3 sm-n900 kk 4.4.2 n900xxudnc1 official problem imei null/null
are there a solution ??
Repair is possible ??
I readed here in this forum that there's soluttion to make dowgrade to jb 4.3 some one can write the steps to do that if it's possible ??
Please heeeelp !! Thanks to all... :good: :good:
:crying: :crying:
Click to expand...
Click to collapse
Did you backup efs? If you did restore it. If not then try flashing this in recovery.. Or try flashing stock again.
http://forum.xda-developers.com/showthread.php?t=2507403
4aces said:
...But one thing I can answer the downgrade from 4.4 to 4.3 is not possible by now if...
Click to expand...
Click to collapse
Actually it IS possible for the n900, the knox reset also let's users downgrade if they so choose to.. But he doesn't need to downgrade, he lost his efs/imei and that can be fixed if he made a backup or by using the other options that I listed.
http://forum.xda-developers.com/showthread.php?p=52329946&nocache=1
Thanks 4 correcting me, I didn't know. I have the N9005 so... learned something
Khizar said:
Did you backup efs? If you did restore it. If not then try flashing this in recovery.. Or try flashing stock again.
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
thanks bro, no backup efs.
Actually it IS possible for the n900, the knox reset also let's users downgrade if they so choose to.. But he doesn't need to downgrade, he lost his efs/imei and that can be fixed if he made a backup or by using the other options that I listed.
http://forum.xda-developers.com/showthread.php?p=52329946&nocache=1
Click to expand...
Click to collapse
please how to make a safe downgrade?? i think that can fix the problem, i have not an efs backup & flashing roms don't solve (i did that many time) same result "unknown baseband version"!! thanks bro, knox warranty void 0 samsung official.
Downgrade to jb 4.3 successful!! thanks you RuchRha you are great man!
http://forum.xda-developers.com/showthread.php?t=2642207&page=9
but my phone still baseband unknown & imei null/null
wissàm1981 said:
Downgrade to jb 4.3 successful!! thanks you RuchRha you are great man!
http://forum.xda-developers.com/showthread.php?t=2642207&page=9
but my phone still baseband unknown & imei null/null
Click to expand...
Click to collapse
Do not try to recover EFS...
It is not the problem, the problem is that you have unknown baseband (Modem damage)... Please check if it can mount /EFS folder (Check in recovery)
It it fails to mount /EFS, then you will probally need to find someone with a Asansam box to fix it...
Remember to backup you EFS folder
Best regards
Ratata82 said:
Do not try to recover EFS...
It is not the problem, the problem is that you have unknown baseband ()... Please check if it can mount /EFS folder (Check in recovery)
It it fails to mount /EFS, then you will probally need to find someone with a Asansam box to fix it...
Remember to backup you EFS folder
Best regards
Click to expand...
Click to collapse
please how to do that (mount /EFS), i have not an efs backup
Modem damage that mean phone does not accept any modem version via odin or via recovery ??
Thanks a lot,
Best regards,
wissàm1981 said:
please how to do that (mount /EFS), i have not an efs backup
Modem damage that mean phone does not accept any modem version via odin or via recovery ??
Thanks a lot,
Best regards,
Click to expand...
Click to collapse
IMEI null/null comes from modem failure. It is not because your EFS is wiped, if your EFS was wiped, then you would get a generic IMEI number 0044.....
But try to go to recovery, do you get "failed to mount /EFS"
But your IMEI null/null could also be a hw failure...
But I would try to flash a 4 part 4.4.2 firmware
Remember to backup your EFS, it is not corrupted...
Ratata82 said:
IMEI null/null comes from modem failure. It is not because your EFS is wiped, if your EFS was wiped, then you would get a generic IMEI number 0044.....
But try to go to recovery, do you get "failed to mount /EFS"
But your IMEI null/null could also be a hw failure...
But I would try to flash a 4 part 4.4.2 firmware
Remember to backup your EFS, it is not corrupted...
Click to expand...
Click to collapse
i did a mount /EFS from recovery but no msg "failed to mount /EFS" no thing,
i think my EFS is corrupted or wiped !! how to verify that ?? thanks
wissàm1981 said:
i did a mount /EFS from recovery but no msg "failed to mount /EFS" no thing,
i think my EFS is corrupted or wiped !! how to verify that ?? thanks
Click to expand...
Click to collapse
IMEI null/null has nothing to do with a wiped EFS. It is modem problem, or HW failure. I would start flashing a 4 part firmware, eg this one
https://mega.co.nz/#!f9BxWSzK!O-3wPSJIeuhuIfwRYaPPmjxc4w1OmKxBE826sSCdAz8
Keep us updated
Best regards
fix imei note 3 n900
My phone is note 3 kk sm-n900
I faced this problom and i found solution
Throug tool named (((GSII-REPAIRE))))
in google play first you have to :
1. Root your phone
2.install busybox
3.downlaod and install GSII-REPAIER
4.CLICK REPIER IN THE APP (MOUNT)
5.Hoha now enjoy your imei the real one is back and the network
Best regards
Amara
Libya
worked like charm
7moda said:
My phone is note 3 kk sm-n900
I faced this problom and i found solution
Throug tool named (((GSII-REPAIRE))))
in google play first you have to :
1. Root your phone
2.install busybox
3.downlaod and install GSII-REPAIER
4.CLICK REPIER IN THE APP (MOUNT)
5.Hoha now enjoy your imei the real one is back and the network
Best regards
Amara
Libya
Click to expand...
Click to collapse
thanx a lot saved me and my note 3
i cannot it say
you dony have .nv_data.bak and his md5 files , canceled
what i do???????
please help
No anyone to help me?
Hi friends. I am new to xda. I have same problem last 4 months. I have tried flash different stock roms but no use. When i check phone info it showing
Original CSC is INU. But showing other CSC is THL (wrong). Modem is blank. SW Version is unknown. My guess is modem and csc related issue. I have tried flash modem, but not affected. CSC also not affected. Why this happen?
IMEI. Restore backed up EFS folder .
Sent from my SM-N930F using XDA-Developers mobile app
Hi guys I have just rooted my i9505 black edition using towel root. I only have mobile Odin for flashing so I am looking for a rom close to neatrom on the s3 as that is what I am used to could somebody please help with pointers
Sent from my GT-I9505 using Tapatalk
You can use cwm recovery
I used towel root to root my phone so no cwm recovery I only have mobile Odin
Sent from my GT-I9505 using Tapatalk
You can flash TWRP recovery from Terminal Emulator.
http://teamw.in/project/twrp2/182
Download the .img
In Terminal Emulator type:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p21
Make sure to do it correct.
is it possible o downgrade succesfully the firmware from ng1 o nd2? when i tried it, i got no signal. tried to flash the modem.bin that i found in the original firmware, but i just can't have signal. how can i solve?
Jager23 said:
is it possible o downgrade succesfully the firmware from ng1 o nd2? when i tried it, i got no signal. tried to flash the modem.bin that i found in the original firmware, but i just can't have signal. how can i solve?
Click to expand...
Click to collapse
Downgrade the Bootloader may brick your device.
Can you check if your IMEI and Baseband are still valid?
You can use Phone INFO ★Samsung★ app to check for the Baseband and Bootloader version.
imei and baseband are UNKNOWN with the firmware nd2
Jager23 said:
imei and baseband are UNKNOWN with the firmware nd2
Click to expand...
Click to collapse
How about the Bootloader version?
Try to reflash the NG1 firmware.
vndnguyen said:
How about the Bootloader version?
Try to reflash the NG1 firmware.
Click to expand...
Click to collapse
if i reflash the NG1 firmware,averything works fine, but i lose root.
the app info phone, says that my booloader is ND3 (sorry,always read wrong number)
Jager23 said:
if i reflash the NG1 firmware,averything works fine, but i lose root.
the app info phone, says that my booloader is ND3 (sorry,always read wrong number)
Click to expand...
Click to collapse
Or try to extract modem.bin + NON-HLOS.BIN file from the firmware and reflash them.
vndnguyen said:
Or try to extract modem.bin + NON-HLOS.BIN file from the firmware and reflash them.
Click to expand...
Click to collapse
i'm trying to reflash over and over [ odin 3.09-flash modem.bin (in CP) - reboot - flash NON-HLOS.BIN (in CP) -reboot ] it doesn't seem to work for now
Jager23 said:
i'm trying to reflash over and over [ odin 3.09-flash modem.bin (in CP) - reboot - flash NON-HLOS.BIN (in CP) -reboot ] it doesn't seem to work for now
Click to expand...
Click to collapse
Try to boot into Download Mode by turn off the phone completely, then boot into Download Mode with the key-combination.
vndnguyen said:
Try to boot into Download Mode by turn off the phone completely, then boot into Download Mode with the key-combination.
Click to expand...
Click to collapse
doesn't work...i have an old efs backup (efs.img)...is it of any help?
Jager23 said:
doesn't work...i have an old efs backup (efs.img)...is it of any help?
Click to expand...
Click to collapse
What is phone model? N900 or N9005?
And how many backup files? Only 1 file efs.img?
Sent from my SM-N9005 using Tapatalk
vndnguyen said:
What is phone model? N900 or N9005?
And how many backup files? Only 1 file efs.img?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
n9005 and yes, only one
Jager23 said:
n9005 and yes, only one
Click to expand...
Click to collapse
What tool did you use to backup? one file is not enough for N9005.
If you use IMEI Backup ★Samsung★ app, you will see there are 3 backup files: efs.img, modemst1.img and modemst2.img.
In N9005, efs.img does not contain the IMEI. The IMEI is stored in modemst1.img and modemst2.img.
Anyway, try to restore with the tool that you have used to create the backup.
vndnguyen said:
What tool did you use to backup? one file is not enough for N9005.
If you use IMEI Backup ★Samsung★ app, you will see there are 3 backup files: efs.img, modemst1.img and modemst2.img.
In N9005, efs.img does not contain the IMEI. The IMEI is stored in modemst1.img and modemst2.img.
Anyway, try to restore with the tool that you have used to create the backup.
Click to expand...
Click to collapse
no i didn't use programs if i remember correctly i used adb to backup the efs
Jager23 said:
no i didn't use programs if i remember correctly i used adb to backup the efs
Click to expand...
Click to collapse
Hummh, 1 file is not a valid backup. As I have said, for N9005 the backup must be 3 files.
vndnguyen said:
Hummh, 1 file is not a valid backup. As I have said, for N9005 the backup must be 3 files.
Click to expand...
Click to collapse
so for now i'm stuck with an unrooted note 3?
Jager23 said:
so for now i'm stuck with an unrooted note 3?
Click to expand...
Click to collapse
Here is the modem flashing instruction. Try to follow it step-by-step to reflash the modem:
Code:
• Switch off your device completely.
• Connect to PC and power on your phone in Download Mode (Volume Down + Home + Power).
• Start Odin v3.09 (be sure it recognised your phone and show ID:COM port number).
• Untick Auto Reboot.
• Flash MODEM.BIN (CP slot - unzip it first).
• Reboot once again into Download Mode using Vol Down + Home + Power.
• Tick Auto Reboot and flash NON-HLOS.BIN.
• If this doesn't work, try repeating the flash process again while rebooting manually and with Auto Reboot option turned off.
Thanks for the help...after loosing some time i tried to flash only the nd3 kernel, rebooted and finally got the signal...than rooted and flashed again the ng1 kernel...so now i'm rooted with the original firmware and knox 0x0
sent from my Note 3
Jager23 said:
Thanks for the help...after loosing some time i tried to flash only the nd3 kernel, rebooted and finally got the signal...than rooted and flashed again the ng1 kernel...so now i'm rooted with the original firmware and knox 0x0
sent from my Note 3
Click to expand...
Click to collapse
Is your IMEI ok now?
So the solution is just flashing the kernel? Not the modem?
Flashing the modem wasn't working, so i don't think the modem was at fault...now my imei is correct and everything is fine
sent from my Note 3
Jager23 said:
Flashing the modem wasn't working, so i don't think the modem was at fault...now my imei is correct and everything is fine
sent from my Note 3
Click to expand...
Click to collapse
Can you share the experience, how to flash the kernel?
Hello Fellas, am posting here as I haven't found help elsewhere. Kindly Respond to my woes. I have a rooted Galaxy Note 3 N900 running official Lollipop with IMEI Null/Null and No Baseband version. The IMEI just disappeared totally out of the blue as no custom ROM has been flashed on the device!! This has happened 2 months after updating from 4.3 Jelly bean. With no prior EFS Backup here's what I have tried:
1. EFS Professional (backup&restore complete but no luck)
2. EFS Restore express ( backup.bat>Odin restore)
3. GSII Repair tool
After hitting no luck with the above tools and without any "/EFS mount errors" in recovery either and WIFI working fine, I came to a conclusion that most probably the EFS folder partition on my Note 3 is still intact and most probably this could be a case of a bad modem which would explain the loss of Baseband Version and thus the Null IMEI. So I tried flashing back to KitKat with N900XXUENG1 firmware and separately flashed a few modems compatible with Samsung's new EFS System: N900XXUENG1_MODEM, N900_XXUENF2_MODEM_CWM and also gave a shot at recommended N900_XXUENE1_MODEM_CWM.ZIP which seems to restore baseband for many users with this issue but this failed as well. After much searching I found a 4file_N900XXUGBNL8 Lollipop Firmware with PIT from Dev-Host, flashed all files in Odin&even repartitioned the device but still no baseband!!! WIFI&everything else runs smooth except the damn baseband/Null IMEI! Almost Exhausted my options...
Now I trust we have some informed members and developers here, NEED YOUR VALUABLE IDEAS HERE mates! Someone, anyone.....Thanks!
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
try flashing stock rom from sammobile via odin. you need to backup efs folder everytime you flash a new rom, that's my opinion. may be wrong.
I think I used to had this problem with my Note 2 as well. If you come from 4.3 you should flash stock ROM Jelly bean 4.3 from Sammobile or Samsung-updates website. Then flash lollipop 5.0 over 4.3 when you can see your IMIE. Maybe it will work.
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
m6112 said:
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
Click to expand...
Click to collapse
All EFS folder files are present including nv_data.bak&.bin Am a bit reserved to go the JTAG way just yet.
white7561 said:
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
Click to expand...
Click to collapse
Thanks for that but as I already said I was lucky to find a 4file partitioned Lollipop ROM with separate modem. Flashed that through Odin and even repartitioned the device but that hit a rock as well!
longcoming said:
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
Click to expand...
Click to collapse
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Did you try downgrading to 4.3 with official stock files?
If not,give it a shot.
Droidsan said:
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Click to expand...
Click to collapse
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
UPDATE:
dr.ketan said:
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
Click to expand...
Click to collapse
Thank you Dr.Ketan for that information. You have been a great help to many. I have followed your posts about this issue and I feel there is still hope.
UPDATE:
I WAS ABLE TO RESTORE THE BASEBAND AND NOW THE IMEI IS GENERIC, READS 004999010640000. [/B] I was able to restore nv_data backup from /Efs folder and deleting bad nv_data. Here's what I did:
Using root Explorer in /EFS:
Deleted corrupt files;
nv_data.bin ( 18 April 2015)
nv_data.bin.md5 (18 April 2015)
Renamed backup files (dated 31 Jan 2015) to apply;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
Using ADB shell:
Code:
adb shell
su
umount /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
Reboot
However, the baseband and generic IMEI come&go across reboots and seems not to stick permanently. Any possible steps from here???
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
Try this out
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option Odin. Tell me if it works.
Muthumbi said:
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option in odin mode. Tell me if it works.
Click to expand...
Click to collapse
If flashing modem via Odin you MUST turn off the phone then start it in DL mode. Simply doing a 'reboot' into DL mode will not let the modem be flashed.
Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.
macoX13 said:
Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.
Click to expand...
Click to collapse
Its the same procedure for all devices
Rajada said:
Its the same procedure for all devices
Click to expand...
Click to collapse
thanks. can you link a particular thread or site for doing the that.
macoX13 said:
thanks. can you link a particular thread or site for doing the that.
Click to expand...
Click to collapse
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows
Rajada said:
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows
Click to expand...
Click to collapse
im in windows. is there a thread for doing that so i can follow the procedure.