Database Users

It is not possible to *repair* a lost IMEI on GS4 i9500

For reasons of brevity on this post, I ended up with a generic IMEI on my Samsung S4 i-9500 while flashing Philz CWM and then the stock ROM back. After extensiverly combing all possible threads on the subject, my conclusion is that there is no way to repair a lost IMEI on this phone when one does not have a working backup of the /efs folder.
I tried all possible methods:
- Flash stock ROM back
- Delete /efs and reboot
- Try to fiddle with copying .nv_data to .nv_data.bin
- EFS Pro to recover from an /efs I had. I noticed this was already the one with the generic IMEI
- Flash the modem twice
- etc.
Is that really the conclusion? It is not possible to repair a lost IMEI on GS4? On other phones people usually get it back when reflashing stock.
Does GS4 has some trick done by Samsung so that IMEI is not recovered?
I thank upfront whoever can enlighten me on this topic.

Either buy a RIFF box & A) Pay for something you'll never use again & B) Bork your phone to the point of requiring a motherboard replacement if you get it wrong or take it to a local mobile repair shop/someone who already has one & knows how to use it and have it fixed properly for half the price of you buying your own/without the risk.
Do the smart thing.

MistahBungle said:
Either buy a RIFF box & A) Pay for something you'll never use again & B) Bork your phone to the point of requiring a motherboard replacement if you get it wrong or take it to a local mobile repair shop/someone who already has one & knows how to use it and have it fixed properly for half the price of you buying your own/without the risk.
Do the smart thing.
Click to expand...
Click to collapse
Thanks for the reply, so then it is really impossible to recover. Is that always the case with other models or firmwares? Can a Samsung service center repair it, even with a cost out of warranty?

partimers said:
Thanks for the reply, so then it is really impossible to recover. Is that always the case with other models or firmwares? Can a Samsung service center repair it, even with a cost out of warranty?
Click to expand...
Click to collapse
From all the posts I have read in the last two days, this one gave me more hope, as it keeps saying that restoring an older ROM may help.
It is not that I have an empty /efs. I have an /efs that I backed up, but after I noticed the fake IMEI issue. Can it be that somehow this /efs still contains what I need and is just not recognized by the stock ROM I am using?
This is the data about the stock ROM I am currently using, my phone is a GT-I9500 bought in Colombia, from carrier Claro, factory unlocked, no contract (I suppose all 9500 are like that). I flashed the Stock ROM following this guide, using the stock ROM files listed there http://forum.xda-developers.com/showthread.php?t=2265477
Colombia
GT-I9500 Galaxy S 4
PDA: I9500UBUAMDE
CSC: I9500UWMAMDE
MODEM: I9500UBUAMDE
Added: 2013-04-18

Yep. Sometimes flashing stock roms restores the IMEI where it's a case of it disappearing temporarily. But you've already tried that, and if this was the case with your situation, you would have fixed it already. I mean, you can flash a bunch of stock roms & maybe you'll get lucky, but it almost always returns with the first stock rom you flash in these cases.
If you have an EFS backup that you know is 'good' (I.E you verified its integrity with something like kTool when you made the backup), then you should be able to restore it with kTool/similar. If you've tried that & it doesn't work for whatever reason, the backup is obviously bad.
I would be very surprised if a Samsung service centre didn't fix it if you paid them. However, you will possibly find that a local mobile repair shop who isn't an authorised Samsung repairer will fix it more cheaply (that's certainly the case where I live).
I noticed you tried to restore the backup with EFS Pro (don't know why people insist on using this app, maybe it's the 'Pro' in the name ? I don't think I've seen anyone on here successfully restore with it), try with kTool (search here/Google Play).
What you do from here is up to you, but if it were me (having tried the things you've already tried), I'd be biting the bullet & getting it fixed tomorrow, because you can try a bunch of things that won't work & you'll still have to get it fixed in a week/whenever.

This works! http://forum.xda-developers.com/showthread.php?t=2432758
Sent from my GT-I9500 using XDA Premium 4 mobile app

[Q] What can I do with my I9500

My carrier seems to have flashed there own custom rom and rooted this I9500. I even found a TWRP
folder with a tiny .twrps file modified 2 days before I got the phone but recovery mode doesn't say anything about TWRP. They even tripped knox, I think. Pictures are attached at the bottom.
Now that I have studied up a bit I would like to know if I can just back up there rom and kernel with TWRP then flash a bloat free, hopefully smoother running combo and just flash back to theirs if need be and remove TWRP like they seem to have done?
They used TTT as a base for whatever reason if that matters. Actually that's the part I'm unsure about. Do I have to update to a different firmware and if I do can I go back to theirs?
PDA: I9500UBUFNB3
CSC: I9500UUBFNB3
MODEM: I9500UBUFNA2
Version: Android 4.4.2
Added: 2014-03-02

Bumping after total rewrite.

Bram Skull said:
Bumping after total rewrite.
Click to expand...
Click to collapse
Hi mate
Your carrier gave you a phone with knox bit tripped?? that is odd , i can tell you right now the phone is not new...
If you decide to keep it , you have a few options , flash a stock rom and leave it with the original firmware , or go custom , flash new recovery , new custom rom ..........

I been with them for years so I went for contract and got it for bumping my bill up $10 for two years. Effectively paying $240 for a $350 phone. I just didn't know about knox and that it had been tripped. Pretty sure it is new they just flash it with there own logo on the bootscreen+rom, just not sure if they did anything else to the rom. Still has the little plastic strips along the sides, no scratches, and accessories in the box are unopened. Suppose it could be a refurb but the Samsung stickers on the box don't say anything about being a refurb.
I just thought the fact is just said 1 and not 0x1 was weird to since all the pics i see posted here have two lines related to know with 0x0 or 0x1. Thought maybe they had used one of the methods that doesn't trip knox since I haven't studied enough about it.
I just want to see if it runs better on different rom=kernel and be able to switch it back if I decide to and can return it. Then again I might just take it back and get out of the contract if I can on the simple fact they gave me phone they have already voided the warranty on. My plan was to rely on it the first year then pay for insurance after that. If all else fails my sister has been wanting a new phone but stuck in a contract she shared with here ex so I might just give it to her on a $10 month payment plan lol.
And if anyone is curious the carrier is "Cellular One of East Central Illinois"

I grabbed TWRP Manager and they already had 2.8.0.0 installed, so I backed up there custom version of TWRP and installed 2.8.1.0. I then made a full backup, wiped Data ,Cache Partitions and Preload as instructed in the thread for the rom I grabbed. I even factory reset and made a backup of that too. I flashed the latest version of Prism Barebone and all seemed good until I realized I had WiFi but no mobile data connection. I had already manually entered the APN info so I double checked it then checked efs folder and even pasted in a backup, rebooted and still no data. Flashed back to the factory reset backup and data was back so I grabbed an EFS backup app and an APN one and tried Prism again but still no data other than WiFi. Didn't really use the APN backup tool since it said something about not being able to load a backup on 4.x but I did look at the xml it produced and the settings were the same as I had manually entered.
I would try updating the modem but cant find a copy of I9500UBUFNA2 to flash back to if I decide to take the phone back and I'm really starting to think about doing that now, if I can. I just want this thing to run smooth, as of now my I927r runs Terra Battle smoother and loads it faster than this S4. Music even stutters when the screen is off unless I set the min cpu to 400 instead of the stock 250.
Terra Battle did run smoother on the prism rom but Injustice was no different. It seems like textures are slow on the first load but sometimes it freezes for a 1ms on particle effects and on rare occasion just randomly. Is this normal on the I9500's or did I just get a dud?
Almost forgot but with the carriers rom loaded I cant edit the APN's at all, if that means anything.

S4 i337M - No sound on calls (in/out) after flashing Stock 5.01 Loliipop ROM

Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.

Try flashing the latest stock from sammobile.com.

Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse

What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?

Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse

After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?

Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse

Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.

Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.

You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.

@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.

Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.

Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw

Okay, try flashing with a pit file and the latest stock rom from sammobile.

audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?

Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?

audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone

I attached a 16 GB pit file from my i337m.

Help! Help! Help! Please!

Bought a OTG from China, used one, left plugged into the phone as I slept...don't know if it's the cause of my troubles to start happening, or if the Twitter app I installed at the same time is the cause.
The phone became TROUBLE and I eventually decided to try going back to stock. I did manage to get stock on but couldn't use because the phone immediately would display the dreaded "Unfortunately.......", which pops up so often that you cannot do anything. So I decided to do a full wipe from factory recovery. Since then, the phone wont power on at all! I have left it to charge overnight, all day, NO POWER!!!! I have read many similar accounts. I lost as what to do! I had ZERO power issuses before. Saw a vid where a guy says the power switch is faulty. He ordered one from eBay and replaced it. 1) I don't think it's the case. 2) don't think I wanna try soldering, etc.
Any help would be appreciated!!!

I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.

Wow! NOBODY?!
kojam said:
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Click to expand...
Click to collapse
Cannot believe nobody has replied. I did get one of the usb things from a very nice member (i have to register myself as someone who now has one) but the phone is still not working.
Having done some confusing reading to try to fix mine but don't think i can.
Wondering if there's a good, reliable, store in the GTA (north end preferrably) that can do repair with JTAG? Wondering if there's any hope in recovering this phone. I get the impression that there's a good chance JTAG repair can bring it back to life.

"Unfortunately" error after IMEI repair

Hello everyone,
Couple of months ago I was trying something with my SM-N900 and I really messed things up and didn't backup my efs back then, I ended up visiting a repair shop that was able to fix it and restore my IMEI. Now I notice that I get Unfortunately [app name] has stopped, especially with Facebook Messenger and Google services. I am really terrified of flashing anything, and repair shops are crazy expensive here. I tried cleaning apps' cache, rebooting, factory reset. Please, is there a way to fix this?

HeroTK said:
Hello everyone,
Couple of months ago I was trying something with my SM-N900 and I really messed things up and didn't backup my efs back then, I ended up visiting a repair shop that was able to fix it and restore my IMEI. Now I notice that I get Unfortunately [app name] has stopped, especially with Facebook Messenger and Google services. I am really terrified of flashing anything, and repair shops are crazy expensive here. I tried cleaning apps' cache, rebooting, factory reset. Please, is there a way to fix this?
Click to expand...
Click to collapse
Have you tried a fresh Odin flash to stock?

ShaDisNX255 said:
Have you tried a fresh Odin flash to stock?
Click to expand...
Click to collapse
I am worried that it will mess up my IMEI, I don't know why.

Flashing a stock rom has never messed up the imei on any Samsung phone I have used. It’s usually a custom rom or kernel that messed up my imei.

audit13 said:
Flashing a stock rom has never messed up the imei on any Samsung phone I have used. It’s usually a custom rom or kernel that messed up my imei.
Click to expand...
Click to collapse
How can I know the right stock rom? Because I really don't know the exact region of my phone so it's a bit confusing for me.

Do you where where the phone came from? If it is running a stock ROM now, install samsungphoneinfo from the Play Store to find the csc which will tell you carrier.
Stock firmware is here for the sm-n900: https://www.sammobile.com/firmwares/galaxy-note3/SM-N900/