Related
Hi guys,
I know there are many similiar threads to this one and I'm sure I've read most of them. Either my issue is different, or, if the answer was in one of them, I was too stupid to realize it.
With my S4 Active GT-I9295 I had to go back to stock ROM for the Samsung S-Health and Gear related apps.
I came from spegelius' (absolutely awesome) Google Edition for SGS4A (int'l) v0.9.9.-od2 and flashed the Samsung Stock 4.4.2 with Odin (*). The procedure was: Flash -> Factory Reset -> Flash again to be absolutely sure all files are updated. Currently, I rooted the phone.
My problem persists:
After a reboot I (usually; not always) am able to make normal phone calls.
After some time (sometimes minutes, sometimes hours) I no longer have sound.
I do not hear ringing, the callee can't hear me, I can't hear the callee.
Same problem if I'm being called
Establishing a connection though works always.
Mobile Data is not affected.
WiFi works
Also observed after factory reset -> re-flash, only enter WiFi PW and Google Login Data -> try phone call
I know this problem often arises from a baseband/modem mismatch. So I investigated my CWM backup of the pre-installed 4.2.2 ROM.
That's what was pre-installed:
Bootloader: I9295XXUBMK3
CSC: I9295OXXBMK3
Modem: *I did not find the info in my backup*
This corresponds to the Romanian 4.2.2: http://www.sammobile.com/firmwares/download/22586/I9295XXUBMK3_I9295OXXBMK3_ROM.zip/
That's why I flashed the direct successor http://www.sammobile.com/firmwares/download/37083/I9295XXUCNI1_I9295OXXCNI1_ROM.zip/
PDA: I9295XXUCNI1
CSC: I9295OXXCNI1
MODEM: I9295XXUCNI1
I tried everything I could find online, nothing helped. I am really running out of ideas. Is it possible to go back to 4.2.2 to see if the problem persists?
I do have logcat logs of the radio module before and after the problem occured. But its thousands of lines. If it helps I can upload it!
Thank you guys for your help
(*): I did some intermediate flashing of several other firmware versions (especially different baseband / CSC versions of the same 4.4.2). But I assume this does not affect the result. I used Odin v3.07 & v3.09
Edit: PS: I still think that I might have the wrong CSC Version. I know the 4.2.2 PDA/CSC matches, but I am not from Romania. I'm actually from Germany. And what makes me wonder is that I cannot select the German Keyboard Style without downloading it first. I can't remember doing something similar after unboxing the phone and setting it up for the first time.
Are you aware of this thread?
http://forum.xda-developers.com/showthread.php?p=56955843
Bevare the Thanks Button
Thanks for the answer O-T!
Yes, I was aware of that thread. However, I never made it until here
http://forum.xda-developers.com/showthread.php?p=50787570
Although I did the things basically as described in that posts I have a new question:
Which country is relevant for the search on sammobile? I mean, do they ask me "Where do you live" or "For which country was your device produced?".
Edit: Okay actually they ask me for the 'product code', so it's probably the latter question.
I realized that my 4.2.2 PDA and CSC also match the French version. That would match the language of my original packaging. I already flashed the French 4.4.2 once but heard only noise when calling someone. So I gave up on that one quickly. But I'll give it another shot now.
Is it possible that I had a factory installation of the firmware for country A, and when I first registered with my local carrier I received a modem update OTA for country B?
That would really surprise me. But it could explain my issues, since there is no 4.4.2 for o2 Germany, i.e. I probably wouldn't receive another modem update OTA.
(I never looked into the carrier specific firmwares because I figured they are for sim-locked devices.)
If the above is true, I understand that the only option would be to somehow downgrade my device back to 4.2.2.
I know I'm asking a lot of questions that have been asked and answered elsewhere. But by now I tried so much and nothing worked that I'm really confused and need your guidance.
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
hyperion89 said:
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
Click to expand...
Click to collapse
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
JASONRR said:
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
Click to expand...
Click to collapse
Yes, I always did a factory reset. Most of the times I even flashed the firmware a second time after the factory reset. (This was recommended somewhere else.)
JASONRR said:
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
Click to expand...
Click to collapse
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
hyperion89 said:
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
Click to expand...
Click to collapse
You can flash only the modem & non-holos from the 4.2.2 firmware and check
JASONRR said:
You can flash only the modem & non-holos from the 4.2.2 firmware and check
Click to expand...
Click to collapse
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
hyperion89 said:
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
Click to expand...
Click to collapse
Identify the bootloader version and Knox state:
http://forum.xda-developers.com/showthread.php?p=57332718
Knox is not a counter - it's a like a fuse.
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
hyperion89 said:
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
Click to expand...
Click to collapse
There's 3 stock 4.2.2 TW ROM I9295XXUBMK3 to choose for flash by Odin. All have different Germany CSC (Carrier Specific Code) - Generic, O2, T-Mobile. PDA=MODEM=I9295XXUBMK3 for all of them. Not sure if O2 or T-Mobile versions are locked, but they usually have operators bloat apps.
Remember to power OFF before entering download mode, flash ROM in Odin, factory reset.
https://www.samdownloads.de/download/i9295xxubmk3-dbt-4-2-2-germany/
https://www.samdownloads.de/download/i9295xxubmk3-via-4-2-2-germany-o2/
https://www.samdownloads.de/download/i9295xxubmk3-dtm-4-2-2-germany-t-mobile/
Your choice.
O-T I'm so sorry. My post from yesterday was a lie; I can't read my own OP. :crying: :angel:
I9295XXUBMK3 was preinstalled
Now I'm on I9295XXUCNH2, which implies 4.4.2 and makes a downgrade to 4.2.2 impossible (afaik).
Please note that I already tried the generic German (4.4.2) firmware. I never had operater bloat apps and I bought a simlock-free version of the device. Thus I never tested the o2 / T-Mobile ones. (I did, however, once flash the o2 modem over the generic 4.4.2, which turned out to be a bad idea).
I would love to extract the modem info from my CWM backup. The bootloader / CSC strongly suggest I have a French phone, but the modem would ultimately clarify that.
What is your opinion on trying a different custom-ROM? I never built one so I have no idea from where designers obtain their NON-HLOS and modem files. I know many don't come with any of those and require an already working ROM before flashing so these drivers can be kept. On the other hand, Darkman's StockyROM has an additional modem pack.... which, in my case, didn't help.
I simply cannot believe that it's a hardware issue. Everything worked fine until the update to 4.4.2 and new radio drivers should be thoroughly tested before distribution.
Hi
I have gone through the forums and can't seem to find solution for my problem with my Optimus L90 phone.
I have recently flashed the CM13 on my phone without any errors but below are the issues that I am facing
1. No cellular network signal after inserting SIM card.
2. I read in a different forum that this could happen due to using a wrong version of TWRP, so installed a newer version 2.8.7.0 but things worse.
3. Now I am not able to boot into recovery mode and phone just stays idle with the LG logo screen and few commands appearing like fastboot_iniy() and udc_start().
4. I have tried hard reset and soft reset and both are not successful.
5. I cannot root my phone either. Tried all ways like towelroot, purpledrake, lg root by avicoh etc but in vain
Now my phone, even though has a latest CM version I cannot use it for anything else.
Any help is greatly appreciated.
No SIM is hardly related to TWRP, probably you needed a different bootstack (there is a thread about it).
On CM you don't need anything to root, it's already rooted just not visible to common users, you need to activate Developer Options (it's also explained elsewhere)
Finally, if you cannot reach recovery but still can boot CM13 simply use adb, Flashfy or Hashr to flash another version or TWRP. 2.8.7 is kinda old and not recommended for Marshmallow, you can try 3.0.2 by SlimShady or DarkBlue version from shoxxy's thread.
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
hvramanan said:
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
Click to expand...
Click to collapse
I was able to unblock my phone finally and loaded the stock ROM but the phone is still isn't recognizing cellular network . I am on T-MOBILE. I have tried to insert different SIM, turned off wifi calling but still the phone is not catching any cellular network.
[lfom]: you indicated earlier that a different bootstack might be needed. I am not that knowledgeable about bootstack so can you help me through this or point me to different thread where users might have a similar issue.
Sorry, I meant to say unbrick above
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
lfom said:
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
Click to expand...
Click to collapse
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
hvramanan said:
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
Click to expand...
Click to collapse
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
lfom said:
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
Click to expand...
Click to collapse
[lfom]: thank you for responding. My phone model is LG-D415 . Actually my phone was bricked but I was able to get into download mode and then I used the L90 Hardbrick tool to flash stock ROM (KDZ) to latest kitkat like you have specified above. Then with the OTA update I was able update it to latest lollipop. Then I followed this forum below to to change the bootstack to KK 10C version as the issue specified in the below thread was similar to mine.
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-12-lg-l90-t3049512/page235
Image of the label inside my phone attached.
Do you think I should have used the LG flash tool to flash stock ROM. Should I repeat the steps with the LG flash tool ?
Thank you again for helping me on this.
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
lfom said:
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
Click to expand...
Click to collapse
Yes I checked and it matches. There two fields IMEI which has the number and then there is another field which says IMEI SV and it has a value of 02 in it.
Hello everyone!
I just bought an used P9 (EVA-L19) in pristine condition. It arrived with the nougat update but it is missing all Huawei apps. I don't think I really mind not having those (less bloat, hurray!), but I really want at least the camera app! What should I try? This thing is full stock (unrooted), and I'd rather keep it that way... Should I just flash the full stock firmware? HiSuite claims my phone is up to date, but I've got no idea how to check what build my current firmware is.
Thanks!
Oooh... the build seems to be NRD90M "test-keys", which appears to be an old beta build from my googling. Do I have to go back to MM and then upgrade to Nougat? Hopefully I can do all that without a custom recovery...
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Shymmy said:
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Click to expand...
Click to collapse
I'm from Brazil, but I know for a fact this phone isn't brazilian. It comes with a bunch of stuff written in spanish rather than portuguese, and a warranty certificate citing a bunch of spanish-spekaing latin american countries. I'm browsing through the forums and trying to find out what is my Cust yet. But thanks for the response.
Also, if I have to flash something, is it better to stick with Nougat or is Marshmallow more hassle-free?
(I've attached a screenshot of the status screen from Huawei P9 Tool, this is all the data I could gather so far)
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Shymmy said:
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Click to expand...
Click to collapse
All it says on "Version number" is "NRD90M test-keys". I've read that thread, but to downgrade you need a ROM, and without knowing my Cust ID I'm not sure which ROM I should get.
The screenshot shows my serial number (XVV7N16425001010), the model (EVA-L19 - Dual Sim 32GB Rom 3GB RAM) and a weird build string (eng.jenkin.20161230.130431)
absynte said:
Hello,
do you have dual sim , or single sim and NFC ?
Dual sim: EVA-L19 ou L29
Single sim and NFC EVA-L09 (Européan version)
Click to expand...
Click to collapse
Dual SIM EVA-L19 - No idea if I've got NFC or not. Can't find anything NFC-related on the menus, but it might be that I do not know where to look. Long time Windows Phone user here, just migrated back to Android :laugh:
absynte said:
NFC is an connectivity option.
If you don't have, you have dual sim
Click to expand...
Click to collapse
It does have dual SIM, and is the EVA-L19. So no NFC then. Does it help? I'm currently looking for debranding guides because I can't find what branding this phone originally had.
Oooh well... so far:
1- *#*#2846579#*#* doesn't work (nothing happens), can't enable Manufacturer mode for DC Unlocker
2- The HUAWEI EMUI site doesn't give me a bootloader unlock code, so can't unlock the bootloader with the official method
So, so far, I can't install TWRP, so I can't flash a C432 oeminfo.bin
Also, the Rollback instructions at https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091 fail, as the rollback intermediate firmware just fails at 5% claiming to be incompatible with my device.
Aside from blindly trying to flash random firmwares with the three button method, do you guys have ANY ideas at all? I need a rest, just wasted the whole day trying to get this damned thing fixed
Sad thing: even with a borked firmware install this is still orders of magnitude better than my old Lumia 930.
EDIT: GODDAMMIT, BLUETOOTH ALSO DOESN'T WORK!
absynte said:
Ok so you've got to google this or to find on xda some answers.
https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
For exemple....2 or 3 clicks....
bye
Click to expand...
Click to collapse
I'll give the instructions of the first post a try, though they did not work for the OP.
EDIT: AAAAAND the 800mb file is downloading at 28kbps... this won't be fun
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
alexanrsousa said:
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
Click to expand...
Click to collapse
how u downgrade to MM?
spring80 said:
how u downgrade to MM?
Click to expand...
Click to collapse
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
alexanrsousa said:
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
Click to expand...
Click to collapse
thanks for your answer my friend , i will try and update u
---------- Post added at 01:56 PM ---------- Previous post was at 01:25 PM ----------
working my friend , but be sure to backup first because u will lost everything
I'm in Korea and bought a P9 (L09-for Korean market).
I was so frustrated cause it stucked on android M (Huawei Korea didnt even care to give it an upgrade to android N) I tried to do it on my own. I followed a number of instructions here on XDA which I had no idea what they are about and whether I did the right thing, I basically unlocked bootloader, debranded the phone, installed custom TWRP and nougat packages. As a result I got android N (B386 probably) on my phone, no keyboard, no fingerprint, and no service when inserting sim. Is my phone bricked? How do I fix it or make it go back to stock android M.
Quanla said:
I'm in Korea and bought a P9 (L09-for Korean market).
I was so frustrated cause it stucked on android M (Huawei Korea didnt even care to give it an upgrade to android N) I tried to do it on my own. I followed a number of instructions here on XDA which I had no idea what they are about and whether I did the right thing, I basically unlocked bootloader, debranded the phone, installed custom TWRP and nougat packages. As a result I got android N (B386 probably) on my phone, no keyboard, no fingerprint, and no service when inserting sim. Is my phone bricked? How do I fix it or make it go back to stock android M.
Click to expand...
Click to collapse
Your phone is not bricked since it still boots...
If you want a keyboard, download the google keyboard apk, transfer it to your phone and install it in file manager.
https://www.apkmirror.com/apk/google-inc/google-keyboard/
To rollback to mm, flash this using dload: https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091
Hi,
I hope you could help me.
I have Samsung Note 8 SM-950N and I am unable to make any calls after flashing stock ROM.
When I received it I checked the model first and it showed SM-N950N in the download mode and SM-950F/DS in the menu. That seemed weird but after reading a bit I concluded that one in the download mode is more accurate so I downloaded and flashed SM-N950N_SKC_N950NKSU5DUG1 ROM. Now I can't make any calls and IMEI has changed and it turned into single SIM phone.
I would like to restore the phone to its original state and have a call functionality. Maybe you could help me.
I have attached pictures that I made before flashing.
After flashing stock ROM it looks like this.
What happens if you decide to flash back to n950f rom?
LR7875 said:
What happens if you decide to flash back to n950f rom?
Click to expand...
Click to collapse
I think initially phone came as N950N, but someone tried to make it dual SIM N950F/DS. If I try to flash N950F stock ROM SM-N950F_SEE_N950FXXS5DSC6 it fails in Odin.
When it was converted to dual SIM network was working I have taken a screenshot of IMEIs as well but I wanted to revert it to stock. Now it shows single IMEI even though when I enter this IMEI online it says it can't find it.
I even removed the back cover to check IMEI number on the battery but it is different there as well (it might be that the battery has been replaced?).