Related
This is my first Samsung phone so I was unaware of the precautions I should take before rooting and flashing TWRP. I am still on my stock ROM that was shipped on the phone but I am rooted and my phone doesn't recognise any SIM cards and the IMEI is not stored in the phone.
I took a backup of my efs the first time using twrp however after restoring this, the problem remains
Is there anything that I can do?
coolkodz said:
This is my first Samsung phone so I was unaware of the precautions I should take before rooting and flashing TWRP. I am still on my stock ROM that was shipped on the phone but I am rooted and my phone doesn't recognise any SIM cards and the IMEI is not stored in the phone.
I took a backup of my efs the first time using twrp however after restoring this, the problem remains
Is there anything that I can do?
Click to expand...
Click to collapse
I also have this problem.
I recommend that you reset your flash counter and return to stock rom/kernel and book it into a service repair by Samsung.
also i think on qualcomm based devices the NV DATA is stored somewhere else not in the efs folder.
jay7862 said:
I also have this problem.
I recommend that you reset your flash counter and return to stock rom/kernel and book it into a service repair by Samsung.
also i think on qualcomm based devices the NV DATA is stored somewhere else not in the efs folder.
Click to expand...
Click to collapse
Okay thanks, I'll probably try my phone seller first aswell.
Good luck to you!
Flashed my stock ROM and now my SIM card is recognised and my IMEI on device now matches that of the one on my box.
First thing I am going to do now is backup my efs!
In all my foolishness and ignorance I have managed to lose my IMEI number while changing my firmware... Now my phone does not have a IMEI number...
An somebody help me??
EDIT: OK I realised my IMEI is written at the back of my phone all along... How do I get it to work in my phone?
rocker128 said:
In all my foolishness and ignorance I have managed to lose my IMEI number while changing my firmware... Now my phone does not have a IMEI number...
An somebody help me??
EDIT: OK I realised my IMEI is written at the back of my phone all along... How do I get it to work in my phone?
Click to expand...
Click to collapse
Have you tried flashing stock?
Not yet. I will get it done now. Will report any results
Flashing stock doesn't help. I have flashed the N9005DXUGNH1 firmware, both the imei and baseband remain unknown.
Now I'm using the mokee rom
rocker128 said:
Flashing stock doesn't help. I have flashed the N9005DXUGNH1 firmware, both the imei and baseband remain unknown.
Now I'm using the mokee rom
Click to expand...
Click to collapse
Try flashing this: http://forum.xda-developers.com/showthread.php?t=2507403
nicholaschum said:
Try flashing this: http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?
rocker128 said:
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?
Click to expand...
Click to collapse
It tries to restore your corrupted efs folder.
rocker128 said:
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?
Click to expand...
Click to collapse
if that is not work your IMEI is on the BLAKLIST of samsung.
Nico231995 said:
if that is not work your IMEI is on the BLAKLIST of samsung.
Click to expand...
Click to collapse
Uhm. NO. Samsung does not blacklist any IMEI's just because we are rooting/flashing our handsets.
A blacklisted IMEI will not be null/null, a blacklisted IMEI will be the original IMEI.
This is some kind of software fault (Or ofcause HW)
Try to reboot into recovery, do you get failed to mount /EFS?
Best regards
Ratata82 said:
Uhm. NO. Samsung does not blacklist any IMEI's just because we are rooting/flashing our handsets.
A blacklisted IMEI will not be null/null, a blacklisted IMEI will be the original IMEI.
This is some kind of software fault (Or ofcause HW)
Try to reboot into recovery, do you get failed to mount /EFS?
Best regards
Click to expand...
Click to collapse
you and me have desame problem but my phone have IMEI NULL and BASEBAND unknown i restore my imei and baseband but NO SIGNAL that's my POINT. the only way to fix my phone is to change IMEI from the original one to have Signal. and now my phone is working.
nicholaschum said:
It tries to restore your corrupted efs folder.
Click to expand...
Click to collapse
Nope it does not work. I reflash the mokee rom, gapps then this and now it still says baseband and imei unknown
rocker128 said:
Nope it does not work. I reflash the mokee rom, gapps then this and now it still says baseband and imei unknown
Click to expand...
Click to collapse
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350
nicholaschum said:
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350
Click to expand...
Click to collapse
That instruction is for T-Mobile Note 3.
On Note 3 International version the partitions may be different, so doing that may mess up with partitions and may brick the device.
Be careful.
vndnguyen said:
That instruction is for T-Mobile Note 3.
On Note 3 International version the partitions may be different, so doing that may mess up with partitions and may brick the device.
Be careful.
Click to expand...
Click to collapse
Partitions are the same. You can install N900T ROMs on N9005 devices easily.
nicholaschum said:
Partitions are the same. You can install N900T ROMs on N9005 devices easily.
Click to expand...
Click to collapse
Yes, but the EFS partition may be different.
In that instruction, I see the EFS partition is mmcblk0p12.
But on my Note 3 N9005, the EFS partition is mmcblk0p11.
So just a warning.
vndnguyen said:
Yes, but the EFS partition may be different.
In that instruction, I see the EFS partition is mmcblk0p12.
But on my Note 3 N9005, the EFS partition is mmcblk0p11.
So just a warning.
Click to expand...
Click to collapse
It's quite an old post, it could have been for 4.3...not sure though.
nicholaschum said:
It's quite an old post, it could have been for 4.3...not sure though.
Click to expand...
Click to collapse
I believe that updating from 4.3 to 4.4.2 will not change the partition structure.
The partition structure is device-dependence, and vary from model to model (N900T vs N9005).
@ OP: you can follow that instruction, but you may need to replace its efs partition (mmcblk0p12) to your efs partition (mmcblk0p11, if your device is N9005 international version, as mine).
vndnguyen said:
I believe that updating from 4.3 to 4.4.2 will not change the partition structure.
The partition structure is device-dependence, and vary from model to model (N900T vs N9005).
@ OP: you can follow that instruction, but you may need to replace its efs partition (mmcblk0p12) to your efs partition (mmcblk0p11, if your device is N9005 international version, as mine).
Click to expand...
Click to collapse
Yeah try that.
4.3 Bootloaders can't boot KK ROMs, which is how I came to that conclusion - and vice versa.
nicholaschum said:
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350
Click to expand...
Click to collapse
Ok, im downloading an international firmware now (XXUEND3), will try that method once it flashed it. One question though... how do i do an "adb shell"?
Thank you both of you for helping a noob like me...
rocker128 said:
Ok, im downloading an international firmware now (XXUEND3), will try that method once it flashed it. One question though... how do i do an "adb shell"?
Thank you both of you for helping a noob like me...
Click to expand...
Click to collapse
Enable USB debugging, connect your phone to the computer.
Install adb using the 15 second adb installer (Google it) and in the directory adb is installed in, hold down shift then right click on a blank area, click on Open command window here, then type adb start.
Sent from my OnePlus One using Tapatalk VIP
Hey guys,
So I am a beginner here, had no idea what I was doing and somehow I ended up messing up/bricking my S4. Long story short, after several days of messing around with it, I was finally able to take firmware through ODIN back to stock.
The issue is: The phone still does not recognize my sim card, when I check baseband it says Unknown, and IMEI is Null/Null. After further research, it seems that this has something to do with EFS. Unfortunately, I did not back up any such files since I have no real idea what I am doing.
Can anyone help me out with this? Galaxy S4- SGH-I337, NB1.
I just need the most simple fix to get phone working again.
Thanks.
Get a s4 from a friend and make a back up of the EFS. That's how I have heard people make it work
Maybe this can help you.
churapa said:
Maybe this can help you.
Click to expand...
Click to collapse
The only issue with that is they want me to back up and restore the EFS. I did not back up my EFS initially so I feel it is too late for that.
moiramd said:
Get a s4 from a friend and make a back up of the EFS. That's how I have heard people make it work
Click to expand...
Click to collapse
This may be hard, But if I did find an EFS for I337 online.. How would I go about putting this on my phone?
With EFS restorer Express
I thought each phone's efs were unique to that phone?
Airtioteclint said:
I thought each phone's efs were unique to that phone?
Click to expand...
Click to collapse
Yea thats what I thought, Which is why im confused.
tigerx88 said:
Yea thats what I thought, Which is why im confused.
Click to expand...
Click to collapse
Did you ever make a nandroid backup at all? I know twrp backs up the efs hopefully you have that somewhere.
There is an app in the playstore that will give you your efs info using other info. It's called meid converter. Good luck.
Airtioteclint said:
Did you ever make a nandroid backup at all? I know twrp backs up the efs hopefully you have that somewhere.
There is an app in the playstore that will give you your efs info using other info. It's called meid converter. Good luck.
Click to expand...
Click to collapse
Unfortunately, I dont think I backed up anything... not that I know of anyway.
What can I do with this app? Am I able to restore the baseband and IMEI?
tigerx88 said:
Unfortunately, I dont think I backed up anything... not that I know of anyway.
What can I do with this app? Am I able to restore the baseband and IMEI?
Click to expand...
Click to collapse
It will tell you your imei, and other info that you might be missing. From there you will have to try and figure out a way to reinput them manually. There was an app called anycut that worked great for things like this back in the gingerbread days. I'm sure there are ways to do it in terminal emulater now hopefully a more knowledgeable user can help out with that part.
Still cant figure out what I should do here. Any further ideas?
I have tried changing the firmware via Odin several times, and I am still having the same issue! Can someone please instruct on how to get the baseband and IMEI back if it was never backed up in the first place.
Thanks!!
tigerx88 said:
I have tried changing the firmware via Odin several times, and I am still having the same issue! Can someone please instruct on how to get the baseband and IMEI back if it was never backed up in the first place.
Thanks!!
Click to expand...
Click to collapse
Last bump before I give up on this
i have galaxy s5 (SM-G900F) with no imei
the imeisv is 04
i didnt backup it or anything there is a way to restore it?
ben.anter said:
i have galaxy s5 (SM-G900F) with no imei
the imeisv is 04
i didnt backup it or anything there is a way to restore it?
Click to expand...
Click to collapse
Have you tried flashing stock with Odin?
Have you still got a radio signal (Make calls / text etc) ?
If not, you might have lost your EFS partition, which afaik, needs a professional repair to fix unless you backed up that partition first
RuffBuster said:
Have you tried flashing stock with Odin?
Click to expand...
Click to collapse
yep i have tried to update it with stock frimware but didnt help.
*Detection* said:
Have you still got a radio signal (Make calls / text etc) ?
If not, you might have lost your EFS partition, which afaik, needs a professional repair to fix unless you backed up that partition first
Click to expand...
Click to collapse
i have the signal bars working but no imei. no backup.
there is no other way to restore it somehow?
ben.anter said:
yep i have tried to update it with stock frimware but didnt help.
i have the signal bars working but no imei. no backup.
there is no other way to restore it somehow?
Click to expand...
Click to collapse
Before you try anything, I strongly advise you to backup your EFS partition or you could end up with no signal at all
IMEI and Radios are both contained in the EFS partition, lose that, your screwed
http://forum.xda-developers.com/showthread.php?t=2696153
*Detection* said:
Before you try anything, I strongly advise you to backup your EFS partition or you could end up with no signal at all
IMEI and Radios are both contained in the EFS partition, lose that, your screwed
http://forum.xda-developers.com/showthread.php?t=2696153
Click to expand...
Click to collapse
i have signal but when i try to make a call it says "not registered in the network"
and i have backup my efs partition to my sdcard as you said.
what now?
ben.anter said:
i have signal but when i try to make a call it says "not registered in the network"
and i have backup my efs partition to my sdcard as you said.
what now?
Click to expand...
Click to collapse
Might be too late if the EFS partition is corrupted and you don't have an IMEI and can't make calls
There are a couple of threads kicking about on XDA S5 forums where people have managed to recover their phones with similar problems, have a read through the Q&A forum and see if you can find them, some fixed by flashing stock, not sure how that worked, but apparently it did
Read others saying they backed up a working S5 EFS and restored it to the broken one
Have a read and see what you can find
*Detection* said:
Might be too late if the EFS partition is corrupted and you don't have an IMEI and can't make calls
There are a couple of threads kicking about on XDA S5 forums where people have managed to recover their phones with similar problems, have a read through the Q&A forum and see if you can find them, some fixed by flashing stock, not sure how that worked, but apparently it did
Read others saying they backed up a working S5 EFS and restored it to the broken one
Have a read and see what you can find
Click to expand...
Click to collapse
so you saying the only thing i can do is to flash a new imei with octoplus or some other kind of boxes.
and if i recover imei from other phone it will not cause network problem becuase there is two phones with the same imei ??
The law in most countries states that the only IMEI number you can use in your phone is the one it came with.....
Nobody here on XDA is going to give you advice on how to change your IMEI for that reason......it's against the law..... *and* as such, it's against XDA rules as well......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
The law in most countries states that the only IMEI number you can use in your phone is the one it came with.....
Nobody here on XDA is going to give you advice on how to change your IMEI for that reason......it's against the law..... *and* as such, it's against XDA rules as well......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
^^This.
Thread closed.
Hello everybody,
What can I do if my Axon 7 has lost the IMEI by restoring a backup through TWRP? My baseband version is unrecognized.
I have tried to save on this thread the mobile phone, but the problem "IMEI Changer" does not recognize DIAG port.
Windows only shows:
Sry for my bad english. I use Google Translate.
I hate to say this, but you're out of luck. If you restored your EFS partition via a bad version of TWRP, you're stuck. Send it back to ZTE.
Controllerboy said:
I hate to say this, but you're out of luck. If you restored your EFS partition via a bad version of TWRP, you're stuck. Send it back to ZTE.
Click to expand...
Click to collapse
Damn and I was hoping through the program IMEI Changer could save the phone ...
I have the A2017G model and the bootloader has been unlocked. The device was bought at Amazon in Germany. Is it possible to send the device to the manufacturer because of the warranty?
logimowl said:
Damn and I was hoping through the program IMEI Changer could save the phone ...
I have the A2017G model and the bootloader has been unlocked. The device was bought at Amazon in Germany. Is it possible to send the device to the manufacturer because of the warranty?
Click to expand...
Click to collapse
I encountered the exact issue you told me. I restored a TWRP backup that I had made through a faulty TWRP version and it made me lose my IMEI and baseband. Tried just about anything. Nothing worked.
Restored everything to stock, reflashed stock recovery and locked bootloader and sent it back. Got a new one, only had to pay the shipping costs of my device to Germany. I hope you're as lucky as I have been. Thumbs up.
How can we make a backup of imei?
SilentEYE said:
How can we make a backup of imei?
Click to expand...
Click to collapse
Folks need to stop messing with the EFS partition. The only things you should be backing up with twrp is boot, system, and data. Nothing else.
Have you tried the zadig tool?
http://zadig.akeo.ie
Also, I've found this Qualcomm Driver to always work for me in the past. Surprising. It's the ONLY one that could help my device get detected by certain tools.
I uploaded it to my AFH for safekeeping: https://www.androidfilehost.com/?fid=817550096634746189
If you haven't tried any of this yet, just give it a whirl. I used the IMEI tool to rewrite my IMEI when I accidentally wiped it, and it was perfect.
My imei is shown as unknow i have a US phone but its working fine so i dont really pay much atention to it lol, but i will try the app kwesi posted to see if i can get it working