CSC - XXX Issue - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I had recently got my Note's board replaced. When i got back my phone from the Samsung Service Center and i tried connecting it to Kies it showed the current firmware was the LRB/LR4 version but the CSC code which is displayed in parenthesis was XXX and not INU. Also on little bit of further checking i found that the serial number of my phone which is found in the Settings->About Phone->Status menu was 00000000000 instead of the serial number given under the battery. When i went back to the service center,the person there blabbered some god damm excuse which did not convince me. He said that the serial number is written but is not displayed and will be displayed when the next update comes for my phone. Please help me get out of this issue.

Not sure about the serial number but the CSC can be changed using the code *#272*IMEI#. Then choose INU. This will reset the phone and wipe data. So make sure you are on a safe kernel.

I have already tried the CSC change code but its not working!!

After this repair you should have warranty again. So do not change anything, go back to the Samsung Service Center and if the person makes his "blabla" again, simply ask for his boss.

Thanks ThaiDai ill try it today and let you know!!

phalgunlodaya said:
I had recently got my Note's board replaced. When i got back my phone from the Samsung Service Center and i tried connecting it to Kies it showed the current firmware was the LRB/LR4 version but the CSC code which is displayed in parenthesis was XXX and not INU. Also on little bit of further checking i found that the serial number of my phone which is found in the Settings->About Phone->Status menu was 00000000000 instead of the serial number given under the battery. When i went back to the service center,the person there blabbered some god damm excuse which did not convince me. He said that the serial number is written but is not displayed and will be displayed when the next update comes for my phone. Please help me get out of this issue.
Click to expand...
Click to collapse
I also had similar problem. Note's board was replaced and after that Kies was showing CSC as XXX, however serial number shown in phone settings app was correct. Kies was showing an error message that the device's firmware can not be upgraded. After 4.1.2 was released, I went to service center again and got the firmware updated to 4.1.2. Now the CSC code is INU. Kies detects the phone correctly. Phone interface is very smooth on Jelly bean and there is no lag in dialer/contacts application.

Related

[Q] Imei trouble

Hey, i messed up my efs files awhile back when froyo was first getting leaked onto I9000 and flashed to my samsung captivate. So i have the generic fake samsung EMEI code of 004999010640000 so that i can use the AT&T network. I never made any back up of efs files and i recently tried to restore my emei using the two methods in android development but still no luck getting my original IMEI. I need get a warranty exchange through samsung due to search button randomly engages on its own and am worried that samsung will see that the EMEI code is different and try to void my warranty since it would be evidence that i messed with the software. I have my original box so i know my original IMEI code so is there a way to manually enter my code or any other way to restore my EMEI. Or do u think samsung would even notice anything with the android software?
Fix IMEI
OP, ODIN3 One-Click Master Clear will get it all back 4 U. I just posted on another thread about this same issue. I went through hell trying anything I could find, was ready to go to AT&T for a swap out. I gave ODIN3 One-Click Master Clear a try and it did it for me. So give this a try, you'll kiss your phone after You done
Just flashed back to stock and turn in your phone. Don't think the warranty dept are gonna be that anal for the exchange.
If they have questions on the IMEI number, tell them all you did was the kies update to JH7.
You shouldn't have any problems. It's been done before
edit: Btw, make sure you have JH7 installed
People assume that the rep at at&t has any clue what they are looking at.
Put a sticky note that says "phone" on it before you pack it up so the AT&T people will know what it is.
lol ok ill be sure to do that when i exchange it. But ill be dealing with samsung warranty on this one. I tried AT&T when my imei got messed up the first time, and i needed an network unlock code to use my captivate that didnt exsist and they wouldnt exchange me phones cause i was past 30 day return by 2 weeks, assholes.
If i do the master clear with odin will all the at&t network settings be erased and have to input them manually? Hopefully i can find the settings online if thats the case. A smart phone with no network is an expensive paper weight, lol.
Are you not able to get on the ATT network with the generic IMEI number? I have the generic IMEI number running on my phone now with it ending 40000 and I'm having no trouble getting on the the ATT network.
Edit: I do have a backup of my efs with the correct IMEI number too, just lazy sometimes on restoring the original efs. Just make sure your product code is correct and you should be able to update through kies to get back to JH7.

Help--kies: This version cannot be updated--help??

i just downgraded from kp9 to ddkb2(my original) so that i can have official update but
kies shows device cannot be upgraded
pda:kb2 phone: ka5 csc:ka6(glb)
i am from india
plz help
dawinner said:
i just downgraded from kp9 to ddkb2(my original) so that i can have official update but
kies shows device cannot be upgraded
pda:kb2 phone: ka5 csc:ka6(glb)
i am from india
plz help
Click to expand...
Click to collapse
Try re-installing Kies....Kies is like devil! I Hate it !
flash wice ur problem will be solved.!!!
I flashed twice but not solved my problem. I then re-installed Kies after twice-flashing and it solved my problem.
great now delete this thread......
For future reference:
The problem is that your locale was changed from INU (more likely) or INS to something else, in your CSC.
To access the settings to change your CSC, you need your IMEI number.
Get this by using the code : *#06# , in the phone dialer.
It should be 15 digits. Write it down someplace for this next step.
Open the dialer and input : *#272*<enter 15 digit IMEI>*
It should instantly display a menu. If you get an error, make sure the code is correct and that you have taken down your IMEI correctly.
Now choose your locale from the options presented.
For your locale, check this thread:http://forum.xda-developers.com/showthread.php?t=787163
Credits to bloodrider for the original, and detailed, post!
Cheers!

Imei number problem

Hi, People, here is my problem. I have a s3 mini i8190..after battery problems, i update it by KIES, to 4.1.2 I saw that when i did it, the baseband change...After that, i never had put sim inside.. I keep trying with the battery problem due to a "copsdaemon" process...I install recovery, root, instal a few rooms, and the problem keep... Now reading , i see my IMEI NUMBER, is not same that on the back, the last 4 NUMBER; is not correct, so i tried a process like this:
http://forum.xda-developers.com/showpost.php?p=47452726&postcount=1
http://forum.xda-developers.com/showpost.php?p=47969448&postcount=1
But any of these work, also, the baseband change to XXXX, but again is OK.
What can i do? Before come back to stock to see.
How i change the baseband!???and if i do, how i come back ??because i have not seen any other file with thath number.
Here is my information
BASEBAND I8190XXAMA3
Nucleus version 3.0.101-novafusion.pl
Version carbon CARBON-KK-UNOFFICIAL-20101001-1631
LINUX STATE PERMISIVE
Hope for your help...thanks
I again, no one have any idea?now i am on stock 4.1.1 rooted, but nothing change, the last 3 digit of the imei are not correct, when i update to 4.1.2 i dont get baseband or imei....helppp

Bought a Note 5 n920T with a different imei in software than on the back glass.

Hello, I have done much research about this issue and I have come to the conclusion that this Note 5 our cell phone repair store bought has two different imei's. I believe that it has been previously rooted and had the t-mobile imei spoofed to a working metro-pcs imei.
The imei on the back glass is a valid t-mobile imei that has been blacklisted. Which is fine, because we can pay for a service to remove the blacklist.
The imei in the software of the phone (found in settings and from using the #*06# code) is not recognized by t-mobile, even though there is a t-mobile splash screen. The only network that recognizes the imei is metro-pcs. Although they cannot confirm what device this imei is connected to.
The phone came with a metro-pcs sim card when the phone was bought, which was recognized by the metro-pcs network and said (Metro-Pcs) on the unlock screen. The Knox counter has been tripped by 1. The phone had android 5.1 installed and the firmware was marked 'Custom' in the settings.
Since then I flashed the latest official firmware (android 6.0.1, baseband version N920TUVS4DQA2) using odin. Then I was able to update the software from the update menu in the phone to the latest security patch. Yet the imei stays the same and does not revert to the one on the back. It appears as though it is the original back glass, but I have not taken it off to verify.
So, I flashed a custom kernel and recovery (Stock modified kernel, and TWRP) in attempt to find a way to manually change the imei back to its Original state. Which shouldnt be illegal, since I am reverting back to the original imei? From my research, it appears as though I might be able to flash a deodexed stock rom for the note 5 and then install the xposed framework, then use their imei changer. But will this actually work to change the imei from the one in the settings to the correct one on the back glass? Is there any other way to revert back to the original imei which would show in the settings?
Any help would be much appreciated.
-cpr_centerville
[email protected]_centerville said:
Hello, I have done much research about this issue and I have come to the conclusion that this Note 5 our cell phone repair store bought has two different imei's. I believe that it has been previously rooted and had the t-mobile imei spoofed to a working metro-pcs imei.
The imei on the back glass is a valid t-mobile imei that has been blacklisted. Which is fine, because we can pay for a service to remove the blacklist.
The imei in the software of the phone (found in settings and from using the #*06# code) is not recognized by t-mobile, even though there is a t-mobile splash screen. The only network that recognizes the imei is metro-pcs. Although they cannot confirm what device this imei is connected to.
The phone came with a metro-pcs sim card when the phone was bought, which was recognized by the metro-pcs network and said (Metro-Pcs) on the unlock screen. The Knox counter has been tripped by 1. The phone had android 5.1 installed and the firmware was marked 'Custom' in the settings.
Since then I flashed the latest official firmware (android 6.0.1, baseband version N920TUVS4DQA2) using odin. Then I was able to update the software from the update menu in the phone to the latest security patch. Yet the imei stays the same and does not revert to the one on the back. It appears as though it is the original back glass, but I have not taken it off to verify.
So, I flashed a custom kernel and recovery (Stock modified kernel, and TWRP) in attempt to find a way to manually change the imei back to its Original state. Which shouldnt be illegal, since I am reverting back to the original imei? From my research, it appears as though I might be able to flash a deodexed stock rom for the note 5 and then install the xposed framework, then use their imei changer. But will this actually work to change the imei from the one in the settings to the correct one on the back glass? Is there any other way to revert back to the original imei which would show in the settings?
Any help would be much appreciated.
-cpr_centerville
Click to expand...
Click to collapse
This is such a grey area and from my understanding isn't to be discussed by any means on xda so not going to comment on changing imeis whether valid or not but can give you this link.
https://swappa.com/esn?hc_location=ufi
Run the imei thru that and will tell you valid/invalid/blacklisted/etc but give you a result of what it possibly belongs too.
Keep in mind too someone could of broke the back of their phone, bought a blacklisted and swapped the mother board out so could be correct to begin with.

not registered on network

Hey guys,
since i went to rome last week i got the "not registered on network" error. Here are some details about my phone:
model: SM-G800F
android: 6.0.1
rooted? yes! i rooted the phone yesterday to follow some guides to repair it. didn't work
baseband: g800FXXU1CPL1
kernel: 3.4.39-8954887
build: MMB29K.G800FXXU1CPL1
warranty? expired early 2017
It's my first android phone, so i got really low skills with repairing it.
What I already did:
test another sim in the S5 Mini
test the sim from the S5 Mini in another phone
facotry reset
Tried to do a manual OTA Update: I always get the error that there is a network or server error
smart switch emergency recovery: doesnt't recognize my phone
flash 6.0.1 without repart via ODIN
coincidentally i saw that the IMEI in the phone (*#06#) differs from the one behind the battery :/ I think this could be the error, but i don't know how to fix it.
Thanks in advance for your help
That wrong IMEI even remains after i deleted the EFS Folder oO
Not registered on network imei issue
Hi There,
Did you ever get a fix for this issue as I have exactly the same problem, my SM-G800F IMEI now also shows as - IMEI 350695200123951-01 which is for a blacklisted NOKIA 6310. If anyone can supply an absolute beginners guide for me as to how I can get my original Imei back that would be fantastic.
I am just a user of an android phone and have zilch experience of tinkering with them.
I have seen reference to things like Odin and flashing firmware and am quite happy to give it a go myself and learn
I will post this on a few other threads that list the same issue as I am desperate to get this fixed now as is a waste of a perfectly good phone !!
Cheers.

Categories

Resources