Database Users

[Q] IMEI null and Baseband Unknown, No SIM detected on Samsung Galaxy Note 3 sm n900

Hello developers,
I found the exact same problem posted on xda developers fourm but none of the posts were answered completely or solved.
I rooted my Sm n900 without any problems, installed CWM recovery, installed SuperSu and installed VN Rom for galaxy note 3 (referred this from some Chinese guy on web (since i cant post third party links) its galaxynote3root dot com.
At first i didnt check efs backup option and installed VN rom without any problems (no imei loss or baseband unknown) on my own phone.
But when rooted one of my friends SM n900 with exact same method as i did earlier (but i checked create efs backup this time), i got screwed.
I tried EFS professional, but when i try to put his phone in RMNET + DM + MODEM by pressing *#0808#, and run efs software, and click either qualcommn or efs professional button, it doesnt recognise the device and says not connected.
I tried various other options as well such as rerooting, reinstalling the rom, reinstalling OEM rom, and other roms as well. Every thing is fin except IMEI and baseband null/unknown.

I had a problem like that. On my note 2 .i flashed patition file in odin and it was fixed.

bonebeatz1234 said:
I had a problem like that. On my note 2 .i flashed patition file in odin and it was fixed.
Click to expand...
Click to collapse
Which partition? EFS? Problem is, now i dont have any backups of EFS partition or folder. I am trying to flash modem via odin from phone mode. After that i will have tried everything and will be stuck with a bricked cell forever

rabinpro said:
Which partition? EFS? Problem is, now i dont have any backups of EFS partition or folder. I am trying to flash modem via odin from phone mode. After that i will have tried everything and will be stuck with a bricked cell forever
Click to expand...
Click to collapse
you should bring to the service center to record the IMEI number.

root your device and flash xxuene1 modem from recovery.
Modem is available on xda..search
I did the same and it worked for me

Not worked

Install Recovery and CM on Locked I9500

Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL

The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.

Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL

Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)

No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.

Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!

Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....

Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.

Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,

N910F lost OS, urgent help please

Hi, I have a N910F in the UK. I was on stock BOC5 rom loaded via OTA. I then rooted via cf root and loaded twrp all succesfully. I took a back up and stored on external sd card and internal. I then saw stock BOC5 deodex so thought i would try. Downloaded the file and it failed to flash. I then used my ext SD backup and that failed, so flashed internal, all was good.
Then the crap hit the fan. I then thought if I went official BOD2 from sammobile then flash the deodex maybe better. Downloaded BOD2 and went through odin, it failed saying the file was too large. i then did a search and found a Pit file, so used that in odin too and failed at the same. went to recovery, it booted into download mode saying to connect to kies. Tried that and my comp didn't recognise phone. Reflashed cf root and twrp, all worked but can only see ext SD. internal says 0mb. i get boot with both samsung logos but then says decrypt and to reset phone. i have since downloaded a couple of sammobile roms and a couple of roms flashable in twrp and no luck.
anyone have any ideas or suggestions? I know this is probably back to samsung repair.

quick update. downloaded newest version of odin< downloaded 3mobile uk version and went through odin with this pit file http://forum.xda-developers.com/attachment.php?attachmentid=3135354&d=1422307712. this worked, rooted, installed trwp, installed my ext sd back up and all worked fine.

Ok, another update, I have lost efs. i used kies to go back to stock rom and used my twrp back up to restore efs. it passed in 1 sec but nothing in the efs folders.
i do however, have correct imei, connect to wifi, etc it does however have the wrong serial number showing. does anyone know why twrp isnt restoring EFS?

littleracer said:
Ok, another update, I have lost efs. i used kies to go back to stock rom and used my twrp back up to restore efs. it passed in 1 sec but nothing in the efs folders.
i do however, have correct imei, connect to wifi, etc it does however have the wrong serial number showing. does anyone know why twrp isnt restoring EFS?
Click to expand...
Click to collapse
Just I read this, may help you.
http://forum.xda-developers.com/showthread.php?p=61127397

[Q] HELP NOTE 3 N900 UNKNOWN BASEBAND, NULL IMEI completely out of Nowhere!

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.

New $600 paper weight

So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.

Have you tried using ODIN and flashing back to a fresh, stock ROM?

I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.

Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880

It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.

Flash using ODIN not FlashFire or anything else.

I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS

Did you Flash the pit file on the page I linked earlier? That should repartition everything.

Still the same problem

So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone

Eventually the NI2 + .pit file being flashed together fixed the problem.