Serves me right for not writing down product code before reflashing to fake froyo (the 2.1.1, officially, kies with spoofing).
I had to do spoofing again to get official 2.2 froyo through kies.
Before i started messing with my phone i didnt really know about product codes. Hence the messup.
Now i hear the 2.2.1 is out in uk and i cant het it through kies.
Used SGS toolbox to see my product code, but i get two actually.
nv_data.bin shows I9000HKDKOR
nv_data.bak shows I9000HKDTMU
Some more data about the phone:
Firmware Version: 2.2
Baseband: I9000XXJPP
Kernel: 2.6.32.9
Build: FROYO.XXJPO
Rooted.
The phone was initially T-Mobile UK branded, now runs official samsung froyo.
At a loss on how to proceed to get 2.2.1.
Same for me. I used XEU reg trick but somehow ended with KOR. Also should I use Odin or Kies for the update?
Sent from my GT-I9000 using XDA App
Well change the code to XEU? (But from the looks of it, every UK brand got the update or?)
Anyway its up to you but XEU is for JPY golden
I used only Kies to update it(I came from IRD Eclair to JPX with spoofing XEU (changed to KOR since I had XEU) I changed it via the code + imei to XEU and to JPY it stayed on XEU)
If the nv_data.bak has the product code you want, you can just delete the nv_data.bin and .md5 while in offline mode, reboot and the phone will restore to the product code you want
That's what backups are for
Sent from my GT-I9000 using XDA App
Then how do i change my code to XEU permanrently ?
TMU may brand the phone again to T-Mobile. (do samsung dish out branded roms as per code ?)
Well TMU wont help him much. As the latest is JP5 for it ?
Try this one, I think I did the automatic method http://forum.xda-developers.com/showpost.php?p=8220521&postcount=1
read the warnings too... and changing the code = factory reset
sliex said:
Then how do i change my code to XEU permanrently ?
TMU may brand the phone again to T-Mobile. (do samsung dish out branded roms as per code ?)
Click to expand...
Click to collapse
You can't have it permanently, as flashing will change the product code to KOR sometimes. If you don't flash, it will stay of course. If you have XEU as a backup, you can do what I said in my last post. If not, there is a way to change it by entering some numbers in the dialer, which I don't remember from the top of my head. Search for it. This method will result in a factory reset though. But, for later easy access, after you have got the product code you want, you can delete the backup in /efs, so a new one of the product code you want will be created. That way you won't have to factory reset everytime. And no, as far as I kn ow no roms so far has been branded. At least for the GT-I9000.
Sent from my GT-I9000 using XDA App
I did manage to get JPY with spoofing just fine (did not flash it, just verified if update is available), however...
1. Phone is unlocked, will it relock after reflash/update? How do i get unlock key if SGS Unlock doesnt work (worked on 2.1). Is XEU update network lock free ?
2. Learned that this may get fixed by deleting nv_data.bin and nv_data.bin.md5 (there are bak files in EFS folder and crc/md5 is different from bin file). What is actually stored in nv_data file ? what would happen if EFS folder is erased (not planning on doing that, but would be good to know, still studying android innards ) Both bin and bak files are 2mb in size (2097152 bytes).
Related
Hi im new to these forums as i have just bought a galaxy s second hand,
anyways the problem is when i connect it to kies to try and update the firmware it says the current firmware is: blank <as in nothing>
tried kies 1.5 and 2.0 same thing it picks up the phone but wont pick up the firmware,
im guessing somethings been done to this phone, all i want is the stock firmware and to be able to update in the future, nothing fancy. please help.
Find what version your stock firmware is and flash it with odin. You can download the firmware from samfirmware.
Sent from my GT-I9000 using XDA App
i dont know if this helps but it says
pda: i9000xxjpo
phone: i9000xxjpp
csc: unknown
build info: 2010, 10
firmware version
2.2
baseband version
i9000xxjpp
kernel
2.6.32.9
[email protected] #1
build
froyo.xxjpo
now which one is my stock firmware and can this be updated via kies once ive done it through odin?
Stock firmware = basic unbranded unaltered firmware as supplied by Samsung .
Network firmware is above plus any network branding plus add on that the network have added .
So you have stock firmware .
now which one is my stock firmware and can this be updated via kies once ive done it through odin?
No if you use Kies it will look for the phones product code to update product code is tied to seller/network of original phone .
What is your product code .
Question has to be what do you want on your phone re firmware and are you willing to use flashing methods or not .
jje
thanks for the reply,
now how do i find the product code?
from what i know about the phone is that it used to be on vodaphone and is now sim free, the guy who sold it to me told me he had 2.3 on there but reverted it before selling, i dont see how he managed to do this using kies?
what i would like is to be able to update it through kies to 2.2.1 which is what my gf has on her phone, and make it readable for future updates, if i have to use flashing methods to achieve this then so be it, or is there another way if i can get the product code?
kingofpain69 said:
thanks for the reply,
what i would like is to be able to update it through kies to 2.2.1 which is what my gf has on her phone, and make it readable for future updates, if i have to use flashing methods to achieve this then so be it, or is there another way if i can get the product code?
Click to expand...
Click to collapse
Enter *2767*4387264636# in your dialer.
Then there will be a line that says:
[2] PCode:"your phone model type"
http://forum.xda-developers.com/showthread.php?t=835628&highlight=Kies+Registry+Patcher
You are best to try above and see how you get on .
As its non stock firmware you may need to spoof the product details etc .
If the download of the firmware works take the opportunity to save the rom as in instructions .
jje
pcode: gt-i9000hkaxee
There is no such sales-code, just flash to the latest JPY and you are set..the phone you have has been flashed to Nordic firmware sales-code XEE at some point, the sales-code for Voda is GT-I9000HKDVOD or GT-I9000HKAVOD.
After flashing enter in phone-dialer the following: *#272*IMEI_NUMBER# and choose XEU.
9000 [Sweden] = GT-I9000HKAXEE
Product code for Sweden.
jje
ok this is disappointing news, i am sorry i am really new to all this, but does this mean il never be able to update through kies, and will need to keep flashing to update the phone?
do i still try the kies registry patcher thing or forget about it?
Are you swedish in sweden or where what product firmware do you want .
jje
kingofpain69 said:
ok this is disappointing news, i am sorry i am really new to all this, but does this mean il never be able to update through kies, and will need to keep flashing to update the phone?
do i still try the kies registry patcher thing or forget about it?
Click to expand...
Click to collapse
Ofcourse you can use kies in the future, but after you have corrected the sales-code. You might be able to do it now, just enter *#272*IMEI_NUMBER# and try to see if you can choose XEU.
i am from the uk london to be exact, and i just wanted the latest kies firmware, like my gf has 2.2.1 i will try the code you gave me now and post back
ok i tried that with the imei and it said rejected
kingofpain69 said:
ok i tried that with the imei and it said rejected
Click to expand...
Click to collapse
Check the IMEI number under Settings>About phone>Status , see if it is correct. You must enter the number without slashes or spaces.
kingofpain69 said:
i am from the uk london to be exact, and i just wanted the latest kies firmware, like my gf has 2.2.1 i will try the code you gave me now and post back
Click to expand...
Click to collapse
The latest Kies firmware for your phone is Swedish .
Kies reads your phone and servers sees Swedish product code and wrong firmware so it does not proceed .
Choice is one use Odin and put the latest stock non network Firmware on phone
problem will be its not going to update in the future via Kies as Kies will be trying to update the firmware thats Swedish .
two change your product code
three use Kies registry patcher to spoof your phone to a UK branded phone
same as one you wil not get a further update but need to spoof again .
Example current )2 uk firmware with very little branding/ad ons by O2 .
Using Kies registry hack
SoftwareRevision
was
I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1
ProductCode
Was
GT-I9000HKDO2U
HIDSWVER
Was
"I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1"
DEVCONINFO
Was
" MN(GT-I9000);VER(I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1);HIDVER(I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1);PRD(GT-I9000HKDO2U);SN();IMEI(***********);PN(*********** );CON(AT,
Firmware may need downgrading via Odin to Eclair for this update to work .
four flash latest generic unbranded firmware to phone via odin again no upgrade via kies .
jje
hmm strange the imei under status is different to the one on the box i will try that now,
and the more complicated thing if it does not work lol
thanks guys really appreciate the help
ok so i did the imei number on the status and it has sales code xee a blank box below it with a circle at the end that turns green if clicked and below that install or cancel, i tried clicking the xee it doesnt change just can click the circle to turn it green, should i press install?
JJEgan said:
The latest Kies firmware for your phone is Swedish .
Kies reads your phone and servers sees Swedish product code and wrong firmware so it does not proceed .
Choice is one use Odin and put the latest stock non network Firmware on phone
problem will be its not going to update in the future via Kies as Kies will be trying to update the firmware thats Swedish .
two change your product code
three use Kies registry patcher to spoof your phone to a UK branded phone
same as one you wil not get a further update but need to spoof again .
Example current )2 uk firmware with very little branding/ad ons by O2 .
Using Kies registry hack
SoftwareRevision
was
I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1
ProductCode
Was
GT-I9000HKDO2U
HIDSWVER
Was
"I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1"
DEVCONINFO
Was
" MN(GT-I9000);VER(I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1);HIDVER(I9000ADJM1/I9000O2UJM1/I9000ADJM1/I9000ADJM1);PRD(GT-I9000HKDO2U);SN();IMEI(***********);PN(*********** );CON(AT,
Firmware may need downgrading via Odin to Eclair for this update to work .
four flash latest generic unbranded firmware to phone via odin again no upgrade via kies .
jje
Click to expand...
Click to collapse
kingofpain69 said:
thanks for the reply,
now how do i find the product code?
from what i know about the phone is that it used to be on vodaphone and is now sim free, the guy who sold it to me told me he had 2.3 on there but reverted it before selling, i dont see how he managed to do this using kies?
what i would like is to be able to update it through kies to 2.2.1 which is what my gf has on her phone, and make it readable for future updates, if i have to use flashing methods to achieve this then so be it, or is there another way if i can get the product code?
Click to expand...
Click to collapse
He did state that the phone was on vodaphone, GT-I9000HKDO2U is an O2 sales code, I did suggest XEU because vodaphone codes are GT-I9000HKAVOD or GT-I9000HKDVOD, in this case he has GT-I9000HKAXXX, and while changing the sales code only the last three letters would change. If he does change that to O2 code then it will change to GT-I9000HKAO2U then keis will not recognize the phone again, because there is no such sales-code.
kingofpain69 said:
ok so i did the imei number on the status and it has sales code xee a blank box below it with a circle at the end that turns green if clicked and below that install or cancel, i tried clicking the xee it doesnt change just can click the circle to turn it green, should i press install?
Click to expand...
Click to collapse
My friend, download JPY from here: http://www.multiupload.com/UHJNT0K1F2 Extracting code is samfirmware.com
Flash using odin 1.7 : http://www.multiupload.com/JMBJGDN00I
Load the extracted tar file in odin as PDA and flash, after that enter the recovery mode and do a factory reset.
Use the images here http://forum.xda-developers.com/showthread.php?t=846913 as reference if you did not use odin before, but you must start odin, load the tar file as PDA and then put the phone on download phone before connecting the phone and flashing.
Entering download mode is by pressing and holding Volume down key + Home key and then pressing and holding Power on key till you get to download mode.
Entering recovery mode is by pressing and Volume up key + Home key and then pressing and holding Power on key till you get to recovery mode, navigate using Volume op/down keys and select using Home key.
Good luck..
Hi Guys,
I have a meteor (ireland) carrier brand galaxy s2 csc is KD1(met).
I successfully flashed over the ke7 XEU firmware I found by searching these forums.
HOWEVER... after flashing... in kies I get the following message :
This version of the device cannot be updated.
I've read up more and found out that it is because the version of the CSC that I have does not match what kies would be expecting. In this case I would imagine it is a multi-csc XEU.
How should I proceed if I want to make this a full retail generic galaxy s2 that is correctly identified by kies ? Shoudl I reflash with the pda again and with a specific csc file (as I used to do on my older galaxy s 1).
Any advice is much appreciated.
thanks
r1_2010
Just flash with the XEU KE7 file. then do a factory reset for the CSC to change.
KE7 is the latest version for XEU so it will show as latest firmware
Its not the CSC its product code and other codes that may change .
Basic rule is ODIN flash = no upgrade via KIES .
jje
JJEgan said:
Its not the CSC its product code and other codes that may change .
Basic rule is ODIN flash = no upgrade via KIES .
jje
Click to expand...
Click to collapse
Not the case mate. Odin flash and everything works normally if you're not changing CSC's for the device.
To the OP. Do a hard reset of the device and then flash the firmware again.
Thanks guys for the suggestions. I did a hard reset and reflashed however I still have the prob with the CSC being identified as KD1(met) , baseband XXKE4 and kernel XWKE7 which is fine... with the exception of the csc...
There was only a tar file in the firmware that i downloaded and extracted (which is expected). I remember with my older galaxy s 1 to change the csc I had to actually enter a code and manually change the csc to multi xeu...
Do i need to do something similar with the S2 ?
-- r1_2010
dunno if this help but you can change the CSC using this code after youve flashed
type this into your dialer - *#272*<your IMEI>#
and then select the one you need
Thanks I that but when the preconfig menu opens I can see a 'Sales Code' label beside a textbox , prepopulated with 'XEU' (correctly).
At the bottom of the screen there is an 'install' and 'cancel' options.
I click install but it gives the following error 'Must be THREE chars'
But I cannot edit the text of the sales code , select it or anything else (there is just XEU prepopulated in that text box).
Any more suggestions ?!
I must be missing something....
Ok I've tried flashing again and the same prob... Would our be worthwhile flashing ke2 XEU first and then going to ke7 ?!
Sent from my GT-I9100 using XDA App
Intratech said:
Not the case mate. Odin flash and everything works normally if you're not changing CSC's for the device.
To the OP. Do a hard reset of the device and then flash the firmware again.
Click to expand...
Click to collapse
All i can say is i know some say that but posts are littered with cannot update via Kies after stock flash.
On SGS1 and SGS2 i have failed to update any stock rom even with the original CSC in place and thats after many tries .
jje
Hello S3 Users, i`m the developer of https://play.google.com/store/apps/details?id=com.manniakk.cscselector
As you know in the new XXELLA rom Samsung changed the security policy and there is no way to change the CSC without root permissions.
I made a new version that should do the work but it is still not on the market. I need your help to test if it working on all XXELLA roms and then i`ll update the market version. It is signed with the same signature so you can just update the old version with this one.
It will require root only if the normal way fails, remember that you need to have root and tick the checkbox
thanks, will try later,
I think it will be better if you move this thread to Apps and Themes Sub Section..Here it will get lost in the hullaballooo..
Awesome
Works perfectly in XXELLA
Thank you very much. Is seems to be worked on rooted XXELLA.
Have recently installed I9300XXELLA and its generally working well. I downloaded and installed your attached .apk and get the same error as the play store version:
"com.android.Preconfig not found on your device. Manual mode..."
Then displays *#272*0105# in the phone app.
I have not rooted the phone so cant check that.
greg796 said:
Have recently installed I9300XXELLA and its generally working well. I downloaded and installed your attached .apk and get the same error as the play store version:
"com.android.Preconfig not found on your device. Manual mode..."
Then displays *#272*0105# in the phone app.
I have not rooted the phone so cant check that.
Click to expand...
Click to collapse
sorry, as stated in the first post, currently there is no way to invoke the csc changer without root. If i found a way the app will be updated
Working with root. Thanks
Sent from my GT-I9300 using Tapatalk 2
I will be testing ..
Does changing csc will wipe data in root mode also?
Edit: it changed my csc from btu to inu but it changed it to kor, I had selected inu, I tried multiple times but csc remains kor.
Sent from my GT-I9300...
binYaqoob said:
Does changing csc will wipe data in root mode also?
Edit: it changed my csc from btu to inu but it changed it to kor, I had selected inu, I tried multiple times but csc remains kor.
Sent from my GT-I9300...
Click to expand...
Click to collapse
the tool is invoking the built-in configurator for the CSC Select. It can`t change the csc by itself.
And yes.. the process of changing the CSC will always wipe data
Not working for me: I choose CSC, phone reboots and when restarts CSC is BTU, not the one selected...
Seems that it works like other tools and this one froem terminal window. One solution is to flash with CSC.XXX.zip with only one region and then run app and reboot - look at Perka thread
gpvecchi said:
Not working for me: I choose CSC, phone reboots and when restarts CSC is BTU, not the one selected...
Click to expand...
Click to collapse
the app doest not change your csc itself, It runs the build in preconfigUI, that is shipped with your rom...
manniakk said:
the app doest not change your csc itself, It runs the build in preconfigUI, that is shipped with your rom...
Click to expand...
Click to collapse
I have found out that for the multi CSC to be applied successfully, you have to be on stock recovery. I flashed CF auto root by chainfire and suddenly the CSC is applied successfully. Before that, the CSC just would not change.
not work
hi to all
this csc changer not work on xella at all
when install says
com.android.confi....
my phone info is :
ap : i9300xemf6
cp : i9300xxema5
csc : i9300jvmf1
or move you to root the phone
we want an csc changer to xxela without root
plzzzz replay me
Hello all,
I would like to share a method that solved this tricky issue with my S4 GT-I9500. While flashing with some new ROMs, I ended up with a generic IMEI on my S4. I read everything I could find here in XDA foruns, and no method worked for me. This one below, from fellow colleage douglasgalves at brasildroid foruns saved my phone. Here the link to the original post (portuguese only, sorry)
http://brasildroid.com.br/discussoe...efs-resolver-esse-problema-11.html#post299796
The method is quite simple, and althogh it does not make complete sense (why Trinida Tobago for example) it worked for me! Here it is.
1. You have a I9500 with a generic IMEI.
2. Install a official stock ROM with ODIN. Not any Stock ROM, but specifically Trinida & Tobago April 2013 ROM. You can browse it on Sammobile, or also get it from this link on XDA -> http://forum.xda-developers.com/showthread.php?t=2257645
The ROM I used is:
Build Date: 24.04.2013
Region: TTT (Trinidad and Tobago)
PDA: I9500UBUAMDK
Changelist: 534999 Android: 4.2
3. Once installation is finished, disconnect the cable;
4. Reboot to recovery and wipe data and cache;
5. Install KIES on your PC and let it update to its latest version.
6. Once KIES is updated, connect your S4 to the PC, no need for USB Debug, etc, just connect it.
7. KIES will detect it and say a new version of firmware is available. Perform the update. It takes a long time.
8. Once the update is finished, you get a dialog in KIES asking you to disconnect and connect the cable again, with a confirm button "Confirm". This is the moment it fixes your IMEI. One more reboot and voilà, your IMEI should be back.
I have no idea how/why this worked, if someone more experienced can explain, I would like to understand.
Also, no idea if this would work on other models, with a different ROM, or on a Mac instead of a PC, or with steps on different order. All I know is that, by doing exactly this, I gave life back to my beloved S4.
Now, off to make some 5 backups of the /efs folder before flashing ROMs again.
Good luck there with your generic-IMEIed S4s!
Did some more tweaking to try to understand what happened. Hope some guru can jump in and help me.
1. After I recovered my IMEI, I installed Philz Touch 5.11.2. It went well, I rebooted in CWM recovery, then chose Reboot->Root. It rebooted the phone. Then I went to make a backup of the /efs folder with Root Explorer, and discovered that despite it looking as rooting went well, the phone was not rooted.
Question 1: Why does Philz did not get to root the device? At that stage the firmware version was MG9 for region TTT (Trinidad & Tobago). Is that firmware somehow imcompatible for Philz to root?
Then ...
2. I flashed Firmware for Colombia with ODIN (my phone was bought in Colombia) from April, version UBUAMDE. Got Generic IMEI again. Then followed the same procedure from post 1, and got my IMEI back with KIES. The strange thing is that on KIES, my phone still shows as TTT (Trinidad) after that.
Question 2: It looks like more than the ROMs, it is the last step on KIES that recovers the IMEI. Is it so tha ODIN may be screwing up the IMEI?
Question 3: why I keep with my phone showing as TTT? Is that a problem?
3. Then I flashed the ChainFire recovery. Strangely, this went well and rooted my phone, so it may be something with Philz. I again flashed Philz and it installed well.
Question 4: may I get any problems by using Philz but having rooted with Chainfire?
Thanks a lot for any clarification you gurus out there can give me!
Thanks
You've given a considerable amount of hope to those that are stuck on the genereic imei. Thank you for providing this solution.
However, I am stuck:
After using ODIN 3.07; clicking nothing other than PDA for selecting the firmware you said to download: Hotfile:GT-I9500-TTT-I9500UBUAMDK-1366814146.zip The firmware was successfully installed.
Then before the boot completed, I went into recovery and wiped data and cache. The phone restarted and it booted up, Kies was already updated to the latest version. So once the phone booted up, I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
As I said in the second post, I also got successful using the ROM for Colombia from April.
I would sugesst you to go to sammobile's firmware database. Download any older ROM which supports firmware via KIES (there is an icon showing that over there) and do the same procedure. It looks like what really solves it is the final step in KIES.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I think this is due to flashing Previous Version of Modem (Its Including in Stock Firmware). When You flash Previous Version of Modem, Somehow IMEI retains. Here are some facts:
1) When we try to Flash any MOD of any dev then its depend on which Modem (i.e country's Firmware) the dev is using.
2) After flashing the MOD, Our IMEI becomes Fake.
3) Flashing Previous Version of Modem take back the IMEI.
In your above method you did the same. You flashed the Whole stock firmware but too old by date. After flashing, it retains.
BTW, have you checked your IMEI after flashing the Firmware using ODIN.? It was there.? was it Generic.?
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Disturbed™ said:
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Click to expand...
Click to collapse
It is indeed strange Disturbed, but I can reproduce it. I flash for example, April ROMs (happened with all countries that I tested, Trinidad, Colombia and Brazil), the IMEI gets generic. It is not that the /efs folder is deleted. It is there, it is just that somehow, the IMEI does not get correctly read from the files that are there.
It only gets fixed after KIES updates the ROM for the latest one, and only at the very last stage where KIES ask to disconnect/reconnect the cable.
I first get into trouble when after flashing CWM Philz, I tried to restore stock ROM.
I live in Brazil, but travel very often on business to Colombia, and bought the phone on a good sale. That is why I am trying different countries, but the problem first happened when re-installing Stock ROM for the first time, and at that time I was just using the ROM for Colombia.
Only when things got bad (generic IMEI) I tried other countries ROMs, modems, etc, and finally got to this method that fixed it for me.
[/QUOTE]
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app
exclaimed said:
I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
Click to expand...
Click to collapse
*FIX*
I had the same problem, so I did the following to fix the problem:
Root the device,
Install CSC Changer,
Select the CSC which matches the firmware you are trying to update,
Then start the guide above again from the beginning (including reinstalling the firmware through Odin, even if you are currently using it - to remove the root...)
and now Kies is updating my device!
*UPDATE*
IMEI is not fixed...
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
exclaimed said:
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
Click to expand...
Click to collapse
Please note that KIES does not require Download mode, just connect the phone to the PC running KIES. Maybe it is that, I don`t know.
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app[/QUOTE]
Hey 123hiten, I had no lockscreen issues, only Generic IMEI. Solve it with KIES.
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
SmilerOnline said:
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
Click to expand...
Click to collapse
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
partimers said:
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
Click to expand...
Click to collapse
I did exactly as you said but the Kies button said "OK" not "Confirm"...
and the only reason the CSC change was required for me was to allow my device to be updated by kies (if your device was from Columbia & you updated it with that fw that may be why you didn't need to change the csc... as the csc was already the Columbia csc)
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@partimer, I am curious, what app or program did you use to backup your IMEI after restoring it to its original form or did you just copy the efs folder.
Thanks.
Copy the efs folder using root Explorer to the Sd card. From there I created a tarball and backed it up to my file server and cloud.
Sent from my GT-I9500 using XDA Premium 4 mobile app
From my time on the S2 I had efs problems too. It was established that the IMEI number is individual to each device and is not included on any firmware be it stock or custom. Several roms now automatically create backups when being flashed so it's worth exploring your system to find any backups.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hi guys,
so I own a non rooted Galaxy S7 edge (exynos) and I am trying to change it's CSC.
Prehistory:
I live in Bulgaria and bought it (back in 2016) from one of the carriers here - Telenor, so naturally it had a Telenor branded firmware (CSC GBL I think). I immediately downloaded the unbranded firmware for Bulgaria (CSC BGL) from Sammobile and flashed it. Phone started in Polish, but didn't have any extra apps or uncotabilities, so I left ti this way.
The problem:
With the new versions of Android the Polish CSC, which the MULTI-CSC for Bulgaria defaults to started having some apps (like samsung pay) that just crash when opened and started having some menus in the settings (like T mobile roaming) which just crash the settings app when clicked. I tried downloading several ROMs (The first Andorid 8.0 and several older Android 7.0) in an attempt to make the phone switch to BGL SCS, but unfortunately whatever I do it just defaults on the Polish one. I tried wiping the cache and factory reset after flash, tried having a Bulgarian SIM card inserted both during flash, cache wipe & reset, and startup, but I cannot change the CSC to BGL.
Notes:
1. Flashing Android 8.0 caused the bootloader to be updated to U2, so I cant flash firmwares with bootloader of U1, unless I flash them without the their bootloader, but this doesn't work everytime (I think)
2. I haven't rooted my phone yet and prefer not to. If I absolutely must I ask for a guide on how to do it without triggering Knox & with option to unroot it after in such a way that it is like it has never been rooted.
3. The Dialer codes for IMEI and CSC change no longer work. I only managed to make the IMEI one ( *#06#) work using a firmware from 07.2017 (flashed without its bootloader), but the one for changing CSC (*#272*<IMEI>#) doesn't work on it.
I'm stuck guys I don't know what else to do. I only want the phone to have a BGL CSC and to receive OTA updates. No root, no nothing.
Thank you for your time.
P.S. I searched the forums all day, but couldn't find a solution
Do you know when oreo to s7 edge with CSC SEE users?
Sent from my H2 using Tapatalk
sharcevic said:
Do you know when oreo to s7 edge with CSC SEE users?
Sent from my H2 using Tapatalk
Click to expand...
Click to collapse
I' not sure if I understand that? Are you asking me if I know when Oreo comes out with CSC SEE?
yeah, that's what I'm interested in
stunito0o0 said:
I' not sure if I understand that? Are you asking me if I know when Oreo comes out with CSC SEE?
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
stunito0o0 said:
Hi guys,
so I own a non rooted Galaxy S7 edge (exynos) and I am trying to change it's CSC.
Prehistory:
I live in Bulgaria and bought it (back in 2016) from one of the carriers here - Telenor, so naturally it had a Telenor branded firmware (CSC GBL I think). I immediately downloaded the unbranded firmware for Bulgaria (CSC BGL) from Sammobile and flashed it. Phone started in Polish, but didn't have any extra apps or uncotabilities, so I left ti this way.
The problem:
With the new versions of Android the Polish CSC, which the MULTI-CSC for Bulgaria defaults to started having some apps (like samsung pay) that just crash when opened and started having some menus in the settings (like T mobile roaming) which just crash the settings app when clicked. I tried downloading several ROMs (The first Andorid 8.0 and several older Android 7.0) in an attempt to make the phone switch to BGL SCS, but unfortunately whatever I do it just defaults on the Polish one. I tried wiping the cache and factory reset after flash, tried having a Bulgarian SIM card inserted both during flash, cache wipe & reset, and startup, but I cannot change the CSC to BGL.
Notes:
1. Flashing Android 8.0 caused the bootloader to be updated to U2, so I cant flash firmwares with bootloader of U1, unless I flash them without the their bootloader, but this doesn't work everytime (I think)
2. I haven't rooted my phone yet and prefer not to. If I absolutely must I ask for a guide on how to do it without triggering Knox & with option to unroot it after in such a way that it is like it has never been rooted.
3. The Dialer codes for IMEI and CSC change no longer work. I only managed to make the IMEI one ( *#06#) work using a firmware from 07.2017 (flashed without its bootloader), but the one for changing CSC (*#272*<IMEI>#) doesn't work on it.
I'm stuck guys I don't know what else to do. I only want the phone to have a BGL CSC and to receive OTA updates. No root, no nothing.
Thank you for your time.
P.S. I searched the forums all day, but couldn't find a solution
Click to expand...
Click to collapse
Morning,
I hope you have found a solution to this already. If not.. You need to download a combination file which is the same version as the main firmware you have. eg. XXU2 firmware requires a XXU2 combination file.
Flash the combination file. When the device is rebooted in to factory binary perform a factory reset. now flash the "home csc" file from your main firmware pack. when the handset is powered on again open up the factory imei shortcut/app, this has a keypad type *#243203855# this will bring up the csc codes for your multi-region firmware. select the one you require and the handset will reboot. now just flash your main firmware and it will be the CSC you need.