Database Develop

[Q] Samsung galaxy note shows conflicting device number

I recently bought the Unlocked Galaxy note 1 from eBay(India). It has conflicting device numbers written on back of the device and one on the "About Phone" menu. On back of the device its written as n7000 and "About Phone" menu shows it as "SHV-e160K", I need some help in identifying whether the device is fake? (From build of the device it looks genuine Samsung ),
This phone also has some other issues as below
1. It does not display the the career range although I was able to register to local Vodafone network and I am able to have incoming and outgoing calls. Also 3G works pretty well.
2. About phone menu sows Baseband version :-Unknown
3. NFC unable to detect the NFC tags
4. Samsung kies software not able to detect the device
5. Many Samsung softwares installed on the device fail to update saying software not signed by Samsung
I have replacement of the phone in transit, Once I receive the new device, are there any steps which can help me confirm genuineness of the device ?
Also is there any way to confirm if 4G works ,without having to insert 4G sim card?

You are the owner of a korean versison of the Samsung Galaxy Note now. Different hardware. No own forum here. Search for "e160K" and you'll find a lot of threads related to "SHV or SHE e160K".

What does it say unknown base-band version
ThaiDai said:
You are the owner of a korean versison of the Samsung Galaxy Note now. Different hardware. No own forum here. Search for "e160K" and you'll find a lot of threads related to "SHV or SHE e160K".
Click to expand...
Click to collapse
Thanks, I had misspelled the number,
How can I know if this is really SHV-e160K instead of n7000, because back of the phone shows number as n7000, When I search with IMEI number on google , it shows device number as n7000 although phone info shows 1.5GHz processor(which is specific to SHV). Does this device carry IMEI number registered against n7000?

SXinus said:
Thanks, I had misspelled the number,
How can I know if this is really SHV-e160K instead of n7000, because back of the phone shows number as n7000, When I search with IMEI number on google , it shows device number as n7000 although phone info shows 1.5GHz processor(which is specific to SHV). Does this device carry IMEI number registered against n7000?
Click to expand...
Click to collapse
Use quadrant standard app to check the cpu info. If it's a qualcomm based cpu then it's a Korean note. If the back cover has n7000, then it could be possible that the motherboard inside might have changed.

GPU is Qualcomm
nokiamodeln91 said:
Use quadrant standard app to check the cpu info. If it's a qualcomm based cpu then it's a Korean note. If the back cover has n7000, then it could be possible that the motherboard inside might have changed.
Click to expand...
Click to collapse
As I checked using quandrant standard app, it shows details as below
GPU [Screenshot attached GPU.jpg]
Vendor: Qualcomm
Renderer Adreno(TM) 220
Vresion: OpenGL ES 2.0
CPU [Screenshot attached CPU.jpg]
Name: Armv7 Processor rev2(v7l)
Current Freq: 1512MHz
Max frex: 1512Mhz
Min Freq: 192 MHz
Cores : 2
Architecture: 7
BogoMIPs:13.54
Hardware: QCT MSM8X60 FUSION FFA
Revision: 2
GPU looks inline with the Qualcomm processor, I am not sure about CPU version as Samsung website do not mention the version of CPU for SHV-e160K.
Maybe its the false label behind the device, but it looks suspicious..?

Korean

IMEI on Galaxy S6 doesn't match the backing

Bought this phone off Craigslist come to find out the software IMEI shows a different IMEI than the backing. I spoke with a Samsung rep and they told me the IMEI from the status menu shows a SM-G925A. Strange because i looked up that IMEI on http://www.imei.info/ and it says it's a SM-920F, I'm inclined to believe the Samsung rep. The IMEI on the backing shows it's a SM-G920A which is what the phone physically is.
Phone works via voice and data, text, apps, etc. Everything works but Samsung Pay. In my fit of impatience (prior to my knowledge of the IMEI dependency) i flash my 5.0.2 to 5.1.1 and it froze after ODIN was completely and only after a AP reflash it booted.
So this looks like why my Samsung Pay is not working perhaps? I am so confused right now, any advise on what I should do?

How do I positively identify my mainboard?

I went to a local 'store' and bought an 'unlocked' AT&T S6 for my wife to use on our T-Mobile account last year.
She wanted a new phone, so I got her one and went to sell this one, but found out that the IMEI in the OS doesn't match the one on the back of the phone. My first thought was that the mainboard was replaced...but here's the odd part:
1. The phone says it's an SM-G920A in the 'About' section of the settings.
2. The phone says it's an SM-G920A in the bootloader. Shows as 'official' and everything. Knox is NOT tripped.
3. The rom is AT&T branded.
4. The phone works with both AT&T and T-Mobile sims.
5. The IMEI shows that it is either an SM-G920F or SM-G920T (I get different reports, depending on which IMEI checker I use)
Is it even possible to put AT&T firmware on a T-Mobile mainboard, and still keep Knox official? Or was the IMEI of this model hacked?
How do I know for SURE (without opening the phone) what mainboard I have?

What Is This?

This is a running journal covering my attempts to stabilize a secondhand Note 5 prone to crashing. This first post summarizes the progress, and links to the current state of affairs below.
I've just acquired a second hand Note 5. It was sold as problematic, restarting continuously after loading the stock Marshmallow. 20 seconds or so, and it reboots.
After performing a factory reset the first time, Marshmallow loaded the configuration interface without any issue at all. Select region/language, choose WiFi network, give password, choose email account, give password, etc. Eventually it loaded into Marshmallow itself, no problem. It worked fine for half an hour or more. Then it froze and rebooted, during the automatic (app) updating process. After that, the screen would freeze after 20 seconds or so.
I tried another factory reset. This time it froze and restarted twice during the configuration interface, right when entering the WiFi password. After I got through it, and eventually loaded into Marshmallow, I turned off WiFi. It has been working without issue for an hour now.
I noticed a "dm-verity error" message at the bottom of the Marshmallow stock recovery screen. Perhaps importantly, eventually I recall that on the download screen the image and binary are identified as custom, not official.
See post #3 for more details.
By post #14 the phone has stabilized somewhat. Both WiFi and cellular function and the sudden restarts have been much less frequent. I successfully flash the Russian (SER) Nougat (7.0) firmware of November 2017. The restarts end completely, the battery performance is spectacular (1% per hour on idle) but l lose the cellular network.
By post #19 I suspect either a hardware or persistent data issue is involved, and find with *#0011# that the IMEI Status is NG. I am considering how to unbork the situation, as I didn't make an EFS backup.
By post #23 I have restored network service, but no matter how thoroughly I wipe and flash stock firmwares I'm left with the original issue: constant freezes and restarts. Then, without any discernable reason everything is smooth for days. This odd behavior leaves me wondering whether it's not a hardware issue, but the previous owner borked partitions that aren't affected by flashing firmware. I decide to try and make a full backup, including all hidden partitions normally not included. And see what happens if the next time the phone starts crashing, I restore that backup. But how do I make and restore a full EMMC backup?
It turns out the internal storage of a Note 5 is actually UFS, not EMMC and XDA turned out to be a dry well on full (EMMC) backup and if Google had answers, persistent searching for a week or so didn't turn anything up. Android backup seems an ill defined and ill standardized field. Many options, many superficial. What imaging there is, is spotty and generally incomplete, "proprietary" and not easily restorable.
When after a month smooth operation things go pear-shaped again (post #24) I've got no backup to restore. Not that it would have mattered probably. I suspect it's probably a NAND/EMMC/UFS issue at the back of it all. Now, with Note 5 not officially marketed or supported in the EU, how do I find the parts that I need and fix them?
In the end I replaced the motherboard with one I bought on eBay. The process was simple, using a YouTube video to walk me through the steps. I did walk into a peculiar circuit sticker which was partly stuck to the top of the inside of the cover, and tore. The switch out worked without a hitch but I'm trying to figure out what the sticker is. See my last post.

You bought it rooted and with stock android? To my knowledge not everything is stable with stock android on the note 5! If this phone is your daily you should flash a Samsung based Rom to avoid those reboot issues... or even returning the phone back to stock via Odin!

Well. The print on the back says SM-N920F, but the Odin menu says "product name: SM-N920C". As the IMEI and serial numbers printed on the back also do not match those reported by *#06# I'd say it's a reasonable guess the phone is a fake. The device information in settings indicates the Note 5 is running baseband N920CXXU3BQA1, Android 6.0.1.
So. If the fake would work well, I wouldn't mind. It doesn't for now, though. Given the issues described in the first post, I'm thinking it may have a corrupt stock ROM or a conflict between it's actual (or compatible) model and the ROM that's either installed or it's getting updates for. As a fake, it may even have mixed components of various models SM-N920C and SM-N920I, for example.
How does one get the right ROM for a fake? How does one figure out which parts are actually in the phone, that determine which ROM is needed?

However much you paid for your note 5 can easily determine if its fake or not! Right Now a like new/mint Note 5 (according to swappa) goes for about $220 or less. There are many signs to that hint at a chinese knock off. Simply youtube search "fake v real" note 5.
If your phone is a fake Note 5 theres not much you can do software wise. Not even something like nova launcher will help you. I've seen these knockoffs in person. They are unbearable to use as a daily. The hardware in the knockoff versions aren't even close to what the real Note 5 has.

Crike said:
Well. The print on the back says SM-N920F, but the Odin menu says "product name: SM-N920C". As the IMEI and serial numbers printed on the back also do not match those reported by *#06# I'd say it's a reasonable guess the phone is a fake. The device information in settings indicates the Note 5 is running baseband N920CXXU3BQA1, Android 6.0.1.
So. If the fake would work well, I wouldn't mind. It doesn't for now, though. Given the issues described in the first post, I'm thinking it may have a corrupt stock ROM or a conflict between it's actual (or compatible) model and the ROM that's either installed or it's getting updates for. As a fake, it may even have mixed components of various models SM-N920C and SM-N920I, for example.
How does one get the right ROM for a fake? How does one figure out which parts are actually in the phone, that determine which ROM is needed?
Click to expand...
Click to collapse
It doesn't necessarily mean it's fake, it just have motherboard from other phone, download rom for n920c and flash it using odin and you should be working fine.

El Solido said:
It doesn't necessarily mean it's fake, it just have motherboard from other phone, download rom for n920c and flash it using odin and you should be working fine.
Click to expand...
Click to collapse
I can see how that might be, and why the IMEI on the back and the one reported by *#06# would then be different. The thing is, the 15 digit IMEI printed on the back (357XXX/XX/XXXXXX/X) is invalid according to www.imeipro.info, imei24.com and www.imei.info. How could that be the case on a genuine Samsung? (I tested the IMEI as a single string of numbers, without the slashes printed on the back, as given above.) Also, the IMEI reported by *#06# is resolved by the above-mentioned sites as a 2005 Philips 960. That doesn't square with the idea of a cannibalized motherboard, I'd say.
That said, the build quality is very high if it is a fake: excellent manufacture; 16MB camera; well working, slickly spring loaded, pressure sensitive S-Pen with functioning button; fingerprint reader that works (correctly distinguishing the scanned finger from others); high resolution AMOLED screen.
It's an odd duck.

Crike said:
I can see how that might be, and why the IMEI on the back and the one reported by *#06# would then be different. The thing is, the 15 digit IMEI printed on the back (357XXX/XX/XXXXXX/X) is invalid according to www.imeipro.info, imei24.com and www.imei.info. How could that be the case on a genuine Samsung? (I tested the IMEI as a single string of numbers, without the slashes printed on the back, as given above.) Also, the IMEI reported by *#06# is resolved by the above-mentioned sites as a 2005 Philips 960. That doesn't square with the idea of a cannibalized motherboard, I'd say.
That said, the build quality is very high if it is a fake: excellent manufacture; 16MB camera; well working, slickly spring loaded, pressure sensitive S-Pen with functioning button; fingerprint reader that works (correctly distinguishing the scanned finger from others); high resolution AMOLED screen.
It's an odd duck.
Click to expand...
Click to collapse
I would say thats stolen phone with random imei put on it, but I can't be sure.
PS Fake won't have working s pen

El Solido said:
I would say thats stolen phone with random imei put on it, but I can't be sure.
PS Fake won't have working s pen
Click to expand...
Click to collapse
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?

Perhaps you could upload a few pics of the device or even a video of it? That will be a better way to get help.

Crike said:
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?
Click to expand...
Click to collapse
To know for sure do geekbench 4 then we will now is it fake or not. And for rom you can't sim lock by installing firmware.

Crike said:
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?
Click to expand...
Click to collapse
Also, maybe it was stolen before being registered on the network, and had imei changer beforehand activating.

El Solido said:
Also, maybe it was stolen before being registered on the network, and had imei changer beforehand activating.
Click to expand...
Click to collapse
Like being from a container of original phones that fell from a ship? Not a single one lifted by a pickpocket.
Whatever the case may be, geekbench 4 reports the same hardware as on Wikipedia. Unfortunately the CPU test keeps crashing the phone at around 60% - about a minute or two into the test. So I don't have a benchmark to compare with established Note 5 performance.
How would you recommend I pick a ROM with the best chance of functioning in the region?

Crike said:
Like being from a container of original phones that fell from a ship? Not a single one lifted by a pickpocket.
Whatever the case may be, geekbench 4 reports the same hardware as on Wikipedia. Unfortunately the CPU test keeps crashing the phone at around 60% - about a minute or two into the test. So I don't have a benchmark to compare with established Note 5 performance.
How would you recommend I pick a ROM with the best chance of functioning in the region?
Click to expand...
Click to collapse
Use russian firmware, only european rom i saw.

El Solido said:
Use russian firmware, only european rom i saw.
Click to expand...
Click to collapse
Tried flashing but Odin 3.07 seems to hang on "NAND writing started!" After 30 minutes I examined the Odin process in Windows' Task Manager, and it seemed completely inactive (0% CPU). Tried again, same result. Restarted the phone, and it booted straight into the existing ROM, which appeared completely unaltered.
I'd like to try another Odin version. Is there a trustworthy site?

El Solido said:
Use russian firmware, only european rom i saw.
Click to expand...
Click to collapse
Downloaded the latest Odin from the thread on XDA: PASS. Upgraded successfully to the latest Russian Nougat release.
Unfortunately, now I have "Emergency calls only", and I get an "Error while searching for networks" when trying Settings\Mobile Networks\Network Operators\Search Networks. Available network modes are LTE/3G/2G.
Also, geekbench 4 still crashes at around 60% as it did before.
The upgrade wasn't clean, the previous apps and settings still remained after flashing.
Perhaps a full wipe and a clean flash, perhaps again a United Arab Emirates variant? That ROM did work with my mobile network.

Crike said:
Odin: PASS. Upgraded successfully to the latest Russian Nougat release.
Unfortunately, now I have "Emergency calls only", and I get an "Error while searching for networks" when trying Settings\Mobile Networks\Network Operators\Search Networks. Available network modes are LTE/3G/2G.
Also, geekbench 4 still crashes at around 60% as it did before.
The upgrade wasn't clean, the previous apps and settings still remained after flashing.
Perhaps a full wipe and a clean flash, perhaps again a United Arab Emirates variant? That ROM did work with my mobile network.
Click to expand...
Click to collapse
Ok now first thing go flash that united arab emirates rom, after that go to stock recovery do factory reset.

El Solido said:
Ok now first thing go flash that united arab emirates rom, after that go to stock recovery do factory reset.
Click to expand...
Click to collapse
There are two UAE (United Arab Emirates) ROMs: LYS and XSG. Both fail in Odin, while the Russian ROM succeeds. I've tried multiple times.
I noticed that while the order of images (boot.img, recovery.img, system.img, etc) differs between all three ROMs, both UAE ROMs fail shortly after hidden.img.
The Russian Nougat ROM works well and is apparently stable. The only issue is that the phone can't connect to or find mobile networks and emergency calls only are possible.
Can the Russian ROM be patched with the appropriate modules from another ROM? How would I determine what kind of network module is required in the EU, and from which ROM to pilfer it?
I'm thinking about flashing the United Arab Emirates modem.bin file over the existing Russian ROM modem.bin with ADB/Fastboot. How bad of idea is that?
Another idea would be to extract a United Arab Emirates ROM, remove the hidden.bin (possibly replace it with the one from the Russian ROM) and the compress the files into a new .md5 file with Universal Android Toolkit.

Crike said:
There are two UAE (United Arab Emirates) ROMs: LYS and XSG. Both fail in Odin, while the Russian ROM succeeds. I've tried multiple times.
I noticed that while the order of images (boot.img, recovery.img, system.img, etc) differs between all three ROMs, both UAE ROMs fail shortly after hidden.img.
The Russian Nougat ROM works well and is apparently stable. The only issue is that the phone can't connect to or find mobile networks and emergency calls only are possible.
Can the Russian ROM be patched with the appropriate modules from another ROM? How would I determine what kind of network module is required in the EU, and from which ROM to pilfer it?
I'm thinking about flashing the United Arab Emirates modem.bin file over the existing Russian ROM modem.bin with ADB/Fastboot. How bad of idea is that?
Another idea would be to extract a United Arab Emirates ROM, remove the hidden.bin (possibly replace it with the one from the Russian ROM) and the compress the files into a new .md5 file with Universal Android Toolkit.
Click to expand...
Click to collapse
You could try that, but first try factory reset then try flashing rom.

El Solido said:
You could try that, but first try factory reset then try flashing rom.
Click to expand...
Click to collapse
I've checked the SIM and it's in good condition. I've tried a number of firmwares, none of which resolves the "No service" issue. I've spoken to several Dutch Note 5 owners and they seem to have a variety of Iraqi, UAE and Russian firmwares and those all work.
It would seem it either ~ is ~ a hardware issue after all or there's some borked data which isn't affected by flashing, either on the phone's own memory (like the /efs folder) or in the modem/radio itself, if that has programmable memory.
Edit: *#0011# shows "IMEI Status NG".
I do not have an EFS backup.
I need some serious guidance beyond this point.
Is there software to determine if there is a hardware issue with the modem board? What else could I do beyond this point? I'm not ready to hand it over to a repair service.
Also, if the phone does have bars and call emergency services, doesn't that mean the modem/radio itself is working? Is there a forum I should look to for more help on this issue?

Crike said:
I've checked the SIM and it's in good condition. I've tried a number of firmwares, none of which resolves the "No service" issue. I've spoken to several Dutch Note 5 owners and they seem to have a variety of Iraqi, UAE and Russian firmwares and those all work.
It would seem it either ~ is ~ a hardware issue after all or there's some borked data which isn't affected by flashing, either on the phone's own memory (like the /efs folder) or in the modem/radio itself, if that has programmable memory.
Edit: *#0011# shows "IMEI Status NG".
I do not have an EFS backup.
I need some serious guidance beyond this point.
Is there software to determine if there is a hardware issue with the modem board? What else could I do beyond this point? I'm not ready to hand it over to a repair service.
Also, if the phone does have bars and call emergency services, doesn't that mean the modem/radio itself is working? Is there a forum I should look to for more help on this issue?
Click to expand...
Click to collapse
Ok since you can't flash firmware you want, extract it from .tar and select it in CP in Odin 3.12.xx and maybe it will work then. gl

Can't change the Service Provider CSC on my note SM-N960F

So I bought a brand new Sim-free sealed note 9 from eBay last week here in Germany. Take it from the box turn the phone on and see the OPTUS logo when I power it on and then I was thrilled like WTF is this a fake phone? (didn't know what that logo is) so I searched on google and found out that is just an Australian service provider so was relaxed and then I put different SIM card in the phone and I can do phone calls and use mobile data without any problems. The only problem is that the service provider SW is Locked on Optus Australia (OPS). I downloaded different stock firmware's from SamMobile for Germany (DBT), UK (BTU) Even Australia (XSA) and still in settings at the software info/service provider is shown: OPS/OPS,OPS/OPS and every time when I turn the Phone ON/OFF the annoying OPTUS logo is shown... I tried just only flashing the CSC in Odin but still no changes... I contact the buyer on eBay and he is willing to take the phone back and full refund me. But I want to keep the phone really like the Note 9. Please help me :angel:

You have to change the CSC using a combination file ROM, as they use a multi-CSC now. In some ways, it's better than the old system but in others, it's worse.
This took me ages to figure out but after finding a guide and the right combination ROM (must match the current bootloader version else it won't boot), it worked.
Here's the thread that helped me: https://forum.xda-developers.com/t/...9-s9-csc-only-same-model-numbers-csc.3870836/
Look through all the comments if you have issues. I believe I mentioned, somewhere in that thread, the exact steps I took to make it work.
Newer versions of SamFirm have a combination ROM download option to simplify finding one (new SamFirm builds don't seem to be on the website yet but the guy who maintains it now also has a YouTube channel where he posts links. Seems to be fine except the very latest version seems a bit ad-filled).
Just so you're aware, the N960F shouldn't be carrier-locked. You just can't change the CSC like older phones could. S7 and Note 7 were the last Samsung phones that used the old CSC system, if I remember correctly. Getting rid of the carrier logo is worth it, though, in my opinion.