Develop Bugs

[Help] Phone won't detect sim. Unknown Baseband and IMEI

So... I seem to be having the efs corruption issue with my co-worker's phone. I've been searching all over and have found how others have solved the problem, but it seems that our nv_data.bin is not located in our efs directory.
Does anyone have any idea where these files are? I need to check the last modified dates of their backup files to see if I can restore them >.<
Any help is greatly appreciated!!

Bump.. If anyone knows where these files are this could help us from running into the corrupt efs problem that many people have had. Usually backing up your efs prevents your phone from becoming unable to function as a phone.
I do remember reading something about our unlock code not being present in our nv_data.bin.. And when I check my efs folder in both my, as well as my co-worker's phone there is no nv_data.bin so maybe it has been relocated??
Anyone with knowledge on this subject.. your input would be greatly appreciated! I'm also gonna read over the unlock threads to see if there is any relevant info there.

I am having this problem now, I know you posted this over a month ago, but please tell me you know the location of the backup files or any other solution for this?'
Thank you,

[Q] T989 - Baseband and IMEI Unknown
I have searched and read many threads already. I understand the i9100 uses a file called nv_data.bin and requires its .bak file for a fix.
But, I dont think the t989 is the same because these files dont seem to exist, or at least not in the locations the threads for i9100 state. I am wondering if anyone has had this problem and/or how they fixed it. I know it was caused because of trying to unlock, but I'm looking for a solution.
Thanks!

just buy one of those $20 online unlock or go to your local phone kiosk to have it unlocked
any one with a machine to unlock Samsung phones can get this phone unlocked easily
there's no software unlock yet, as you have found on your searches

I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"

svahora said:
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
Click to expand...
Click to collapse
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!

KillaHurtz said:
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
Click to expand...
Click to collapse
What does the (d) stand for?
And, how can I make sure this never happens again in the future? I know there are backup options out there (CWM, Nandroid), but are there any that make a complete clone of the phone's image? In case I mess up the efs or IMEI files again I can restore and be ok.
Thanks!

T989D = Canadian release of T989
they are identical, the just use the D for Canadian

AllGamer said:
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
Click to expand...
Click to collapse
Would a Nandroid backup fix this in the future?

is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder

AllGamer said:
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
Click to expand...
Click to collapse
I wonder if the new Galaxy Nexus has its IMEI files stored similarly. If so, we can join forces with that forum group.

If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.

-Mr. X- said:
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
Click to expand...
Click to collapse
Did it twice, the stock rom, modem, and kernel.

The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).

cyberjam said:
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
Click to expand...
Click to collapse
Would the KL1 work any different than the older one? I tried ODINing the original one, and it didn't work and increased the count so I didn't try the KL1.

I just got my replacement phone yesterday for this same problem. Flashed the stock kernal, and also the modem just to be safe and nothing would fix it. From what I know its just a hardware issue, not software. I was chatting with samsung and t-mobile people about this trying all kinds of fixes to nothing left but hardware defect.

Repairing IMEI and serial number? Samsung Galaxy S3

Hi can someone please provide a step by step tutorial to using this tool: https://www.youtube.com/watch?feature=player_embedded&v=i_tKiM7aQPU
I have a Samsung Galaxy S3 i9300. It produces an error 'not registered on the network'. The IMEI is 0049 and the serial number is 00000... Which means they are unreadable. I have restored the /efs folder from a back up using officially recommended tools, I have reflashed to stock firmware, I have reset the flash counter, I have set the correct CSC country and carrier code. I have tried everything imaginable to try to get the phone working again. But nothing has worked.
This is the last of all of the methods left for me to try. However, as a n00b, I don't quite understand what's going on in the video? When the person in the video clicks "select DB", where does he get these files from and what are they?
Also how do I get a valid serial number? There is no serial number on the underside of the phone underneath the battery, or anywhere else for that matter.
I should make it clear that this is not a stolen phone. I bought the phone off eBay and the IMEI on the sticker matches the IMEI on the box it came in.
I have completely ran out of options on how to fix this, so this is my last possible option.

As an update, the site hosting this app also states that these files are also required: http://download972.mediafire.com/g2...All+Mtk+BPLGU+Modem+files+for+Imei+change.rar
As you can see it says All Mtk BPLGU Modem files for Imei changer. But what are these files and how do I use them? Forgive me for being a n00b. We were all n00bs at one point.
There is another tool called WriteIMEI which looks simpler to use, but for some reason it can't connect via USB to my phone. When I look at the list of ports my USB ports aren't even listed.

Anyone?

Fixed
jebus197 said:
Anyone?
Click to expand...
Click to collapse
I've used the chimera tool to fix it .... costs €13 but it fixed my problem

Thank you Imnoa!
I had the same problem that the imei was a developer imei with 0049...
I spent hours to repair my phone. But nothing helped. My ESF folder was gone. I read your post, that you repaird your phone with Chimera and downloaded it. First it failed because i took the new method to repair my imei. After three hours of trying other solutions, i tried the old one and it works! Thank you so much! After 10 hours of searching you were my key! My phone is risen from the dead! So, a last time: THANK YOU
Nice greetings
astertz

What did you do?

Bell S3 Unlocking Issues

Hey guys,
I've been trying to unlock my phone for a few days now. Long story short, I moved from Canada to Japan and now I want to unlock my S3 to use a Japanese SIM.
I bought an unlock code from eBay. I was previous running cyanogenmod but then I was told that rooting will cause issues, so I unrooted my phone after an unsuccessful SIM unlock attempt. (wiped the phone, installed stock TW)
Even after unrooting I still had issues, and was given directions for the Service mode. That did not work either. I have tried many different methods and troubleshooting tips and nothing seems to have worked.
Here are some screenshots of the debug mode, my phone details, and a simple root checker app I installed.
puu.sh/dPN0p.png
Here are some specs: SGH-i747m Samsung Galaxy S3 on Bell running official firmware 4.4.2
Thanks for reading, and I really hope someone can help ;_;

Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?

audit13 said:
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
Click to expand...
Click to collapse
Yes it displays the same IMEI on the label of the phone, and when using *#06# on the dial pad.
Despite my flashing back to stock, multiple sellers I have been through on eBay believe my phone is still rooted. One of my friends believed the people on eBay are at fault.
I then bought a code from a somewhat reputable looking website (cellunlocker.net) and received the exact same code. They had provided some additional troubleshooting methods but they did not work.

So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?

audit13 said:
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
Click to expand...
Click to collapse
The prompt appears on screen no problem. It won't accept the code. Please refer to the screenshots I posted in the OP (the puu,sh link)
Is there some extra step I can do to get my phone back to normal? I thought just flashing stock and wiping data/cache would do it but I'm still having problems and I can't figure them out.
I'm aware downgrading firmware is out of the question, but I really have no options left.
I haven't technically activated the Japanese SIM card yet. Could that be an issue?

Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.

audit13 said:
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
Click to expand...
Click to collapse
Yes I grabbed firmware from sammobile and flashed with Odin. I made sure to match the last four digits in the baseband of my phone which is FNH2 so I downloaded this one from sammobile
sammobile /firmwares/download/34795/I747MVLUFNH2_I747MOYCFNH2_BMC.zip/

On the Odin "Downloading..." screen, my warranty bit is 1. Could that be causing the issue?
If so how do I fix that

The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.

audit13 said:
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
Click to expand...
Click to collapse
Still no luck unfortunately ;_;
Blah. Might just sell this phone and buy a Japanese one.

The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?

audit13 said:
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
Click to expand...
Click to collapse
First time I've ever heard of that. Backup/restore?
I just did a quick google search and couldn't find a solid guide. Did you have a certain process in mind?
I appreciate all of your help.

http://forum.xda-developers.com/showthread.php?t=1804117

audit13 said:
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thank you for providing the guide. Unfortunately it's still not working. I uploaded a video just in case that might help, I also have to get a refund from an unlock website, lol.
https://www.youtube.com/watch?v=anrfCgMvBrw&feature=youtu.be

This is really weird as it looks like you are doing everything right.

audit13 said:
This is really weird as it looks like you are doing everything right.
Click to expand...
Click to collapse
Then you can understand why I am incredibly frustrated, hahaha.
It's cool. I just ended up buying a Japanese phone.
Thank you for all your help, hopefully no one else runs into thee issues in the future

Null serial number

Hello guys! I buy sgn4 from ebay. Problem is that imei and phone model on sticker and from phone "about" is different. Network is good, i can make calls, etc. Ok, i think that motherboard was changed. But serial number is only "0" as i know it is factory s/n. What should i do with this device. What happens if i flashed it with custom? I`m afraid that my imei will broke and i can use it only in "iPod touch" mode

Altair7610 said:
Hello guys! I buy sgn4 from ebay. Problem is that imei and phone model on sticker and from phone "about" is different. Network is good, i can make calls, etc. Ok, i think that motherboard was changed. But serial number is only "0" as i know it is factory s/n. What should i do with this device. What happens if i flashed it with custom? I`m afraid that my imei will broke and i can use it only in "iPod touch" mode
Click to expand...
Click to collapse
I understand your worries. I hate even giving advice on touchy matters like this, because depending on why the imei doesn't match. But I'll go over a couple senerios. For one the samsung serial number is all zeros. Mine is to.
Now the big concern is why the imei doesn't match. It's either the mother board was replaced or someone hacked it. Is the model number the same? Cause that's gonna make a big difference as to what to do.
Lets say someone replaced the mobo, but its not a Sprint mobo, then that's gonna effect how and what roms you flash on the device.
Before we move on, give me more info. In About phone, what does it say for the following:
Software version
Hardware version
Model number
Baseband version
Also do you have Twrp? And/or root?
Get me that info, and i wouldn't flash anything until you figure exactly what hardware the device is and have a full backup plus Efs backup.

aaron74 said:
Before we move on, give me more info. In About phone, what does it say for the following:
Software version
Hardware version
Model number
Baseband version
Also do you have Twrp? And/or root?
Get me that info, and i wouldn't flash anything until you figure exactly what hardware the device is and have a full backup plus Efs backup.
Click to expand...
Click to collapse
Thanks for your reply! The phone about says that i have:
Software version: N910PVPS4DQB3
Hardware version: N910P.05
Model number: SM-N910P
Baseband version: N910PVPS4DQB3
I have no root and stock recovery with ticked Knox counter

the same as my phone, my SN number is array of 0, but the phone is working flawless without any problem. You can try many roms for N910P

zRoNz said:
the same as my phone, my SN number is array of 0, but the phone is working flawless without any problem. You can try many roms for N910P
Click to expand...
Click to collapse
Ok, i try them) Tell me one more thing. I have a grid in center of screen like chess deck. Its visible only on white background. Is that normal? There was nothing like this on my previous Note 3

Altair7610 said:
Ok, i try them) Tell me one more thing. I have a grid in center of screen like chess deck. Its visible only on white background. Is that normal? There was nothing like this on my previous Note 3
Click to expand...
Click to collapse
oops, i think your phone maybe have some parts that were replaced from the seller. so why don't you contact him and ask about the phone for more information and got the refund if he sold you a bad quality phone ? the normal phone doesn't have any ghost image or blur grid on the screen. And you tell that your IMEI from system is differented from it's sticker ? Your phone maybe hard-bricked and lost IMEI, and the seller used tools to write another Phone's IMEI to your phone.

Altair7610 said:
Thanks for your reply! The phone about says that i have:
Software version: N910PVPS4DQB3
Hardware version: N910P.05
Model number: SM-N910P
Baseband version: N910PVPS4DQB3
I have no root and stock recovery with ticked Knox counter
Click to expand...
Click to collapse
That all looks good.
Now the back of phone says it's a SM-N910P? Correct?
But the IMEI's just don't match, Correct?
If this is the case, it seems that the mobo was replaced.
The main thing here to know, is if that this is indeed N910P hardware. You should be fine flashing or using Odin!
If you decide to start flashing custom roms, the first thing i would do is Flash TWRP and do a Full Backup (boot,system,data,EFS,modem,cache). And save it in a safe place (like off device, on a pc).
I believe you should be fine, either mobo was replaced or someone hacked the imei so it didn't show as stolen. Either way as long as you don't mess with your EFS, everything should be fine.
FYI, there are no guarantees with flashing! Make sure you research what your doing!
Edit: I just seen your other post about grid. I agree with @zRoNz , the screen could have been replaced with cheaper parts (digitizer) or is a burn in effect.
Edit : 1 more thing you can do. Is install 1 or more Device Info apps. And compare the hardware info they state your phone has. Just to make sure it's truely Note4 hardware!

@aaron74 thank you very much for helping. I just asked seller about this. I think that screen was replaced with no original one. And last questuon: I cant press left sensor button with s-pen. It's should work i think?

Altair7610 said:
@aaron74 thank you very much for helping. I just asked seller about this. I think that screen was replaced with no original one. And last questuon: I cant press left sensor button with s-pen. It's should work i think?
Click to expand...
Click to collapse
That all makes sense now. It's probably because of the digitizer installed. Not sensing in that region. I'm no expert on this, but that all adds up!
If you just bought this, you could try to see about a replacement. But if you can't get one, i would say how much is there to really worry about it. As long as everything is correct except that, how often will you need the spen for just that? It works everywhere else, i assume.
Good luck!

Question [fixed] rooted a325m suddenly no imei, no sim

I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!

flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.

UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram

Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.

edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?

Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it

edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too

myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store

Unroot before update and unlock

wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .

did you fix it?

applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"

For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.

very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe

i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523

applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?

well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month

applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?

applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.

applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw