Hi,
These are probably newbies questions but I could not find a definitive answer for them. Basically, I think I am having some mismatch between my CSC code and my location.
I bought my GT-N7000 in Senegal (where I live) a bit more than a year ago, with a GB ROM. A couple of weeks afterwards, I received an OTA update (pushed) without any issue, apparently the last one on GB. Then the Note was caught in a storm and the motherboard was fried. The local after-sales service ordered a new motherboard, which was installed in August. Since then, I have not received a single OTA notification.
A few weeks ago, I tried to force OTA to check updates, but I keep getting a Server connection error. I installed Kies but am then getting the Device not supported error, though I have not rooted the phone or changed anything from the stock base. I also tried both processes while visiting in France, using a French (Bouygues) sim card but with a similar result.
The *#1234# maneuver gives the following:
PDA: N7000UBKK8
Phone: N7000UBKK3
CSC: N7000CHOKK3
The CHO CSC code is confirmed on Kies. Apparently, this is a code for Chile, so I don't quite understand why I would have it for a Senegalese phone. When using the 272 + IMEI code, I also get the CHO code, with no alternative choice.
I tried looking through various sources, here and on SM, but cannot find any confirmation as to what the CSC code for Senegal should be (i.e some national code or a regional / open one), as I did not check this with my initial motherboard.
The local after sales service has no idea about any of this ("you should not try to update too much via OTA, your will fry your motor") and they suggest the current GB 2.3.6 ROM is indeed the latest one available here. So my questions are:
1. Is there a way to confirm this latter assertion?
2. In case there is in fact a newer stock ROM but the CHO "discrepancy" (provided it is indeed a mismatch) prevents it from being reachable on OTA and Kies, to which code should I change my CSC to make them available again?
3. Should this change not be possible (or the CHO code be the correct one), which ROM (most likely JB) should I use via Odin to be sure I will still be able to use any and all of my local setup. Since there is no reliable Wifi here, I have to rely on 3G (this gets all the more tricky since I am using a small operator (Expresso) instead of the large Orange one) so losing the expresso APN in the flashing process is not an option (I understand crashing APNs can be a drawback of flashing non-national ROMs on Odin, maybe I'm wrong).
Sorry if this is all very basic, but not finding any specific, local info is getting a bit frustrating
Thanks
You can try CSC Changer from play store but i doubt that you will find csc for your country there, even if you do and you choose it, it will format your phone. JB update is available in Africa but not in your country, nearest one being south africa and kenya. You can flash firmware for any of these countries. Regarding APN Settings: if you are rooted used TBP to backup your APN settings or even My Backup Pro can also backup your APN Settings which you can restore after flashing firmware for any of the 2 countries mentioned above.
Make sure to format everything from recovery (ofcourse after backup) and flash JB using Odin.
Good Luck!!!
Cheers!!!
Related
Dear all
I write this post as I hope to get some input and some expert suggestions on the course of action I should take with my phone.
For many years I have been supplied with a phone through my company but it seems to be always the crappy old Nokia. Good for making telephone calls but worthless for anything else.
So recently I bought a Galaxy S on a business trip to China. I love the phone, it works and by now I have almost no Chinese letters and applications left anymore. This is really something else; I'll never go back to the company Nokia. Never!
I think most of the applications are working and I have access to the Android Marked. However, Youtube is not installed or working and I think that the GPS is a little off.
Now I read a lot about Froyo and I bet I would want to get that on my phone, I am also pretty sure that I want to get the phone totally de-Chinese and preferably into something Danish or at least English.
What do I do next?
I have been reading so much on this site that I am getting dizzy. Flashing, rooting, updating, kies(hey, I actually got it working now (again) ) Odin, JM1, JPK etc.
Now my phone has the following;
ProductCode: I9000HKDVD2
PDA: I9000XXXXX
Phone: I9000BUJG1
CSC: I9000GVD2JG1
SalesCode: VD2
Reading through posts on this forum I never saw anyone with the same codes as mine.
Model number: GT-I9000
Firmware version: 2.1-update1
Kernel version: 2.6.29 [email protected] #2
Build number: ECLAIR
As mentioned, I bought the phone in China and I have no idea if it is branded (with Google printed on the back cover) has been unlocked, but I suspect it has. It has been rooted (I have a little black ninja guy giving Superuser Permission) and there is a folder-like icon named "root(and some Chinese letters)"
Well, as I said I have Kies running again. First it was running fine then it stopped connecting to the phone and now after unmounting the external SDcard I can again access the phone from my PC.
Through Kies I can do a firmware update. But should I?
Will it be re-locked?
Will it get all the Chinese stuff back?
Will it somehow be converted into a European phone?
Should I wait for the official Froyo or just go ahead and update?
I can update again when the Froyo finally arrive?
Do I need to make backup of any of my "system" files before doing anything?
Any help suggestions and/or warnings will be appreciated.
If you can do an upgrade through Kies it will aslo tell you what the update is (JG2 for example) since you have what I gues is a chine salescode, you will probably get a chinese update .. What you can do, is goint to the devlopers section and read the topic about spoofing your productcode in the registry so Kies thinks you have phone from another provider / country than that what you have now
I am almost certain that if you can enter an old danish firmware in the registry and a danish productcode you will get offeren a new new danish firmware through kies ..This will not relock your phone ( if it was locked before) as far as I know only the froyo builds will do that.
I have been reading some more on the forum and found that the phone is actually branded.
Model [Country of Origin](Branded Phone Carrier) = Code
I9000 [Germany](Vodafone) = GT-I9000HKDVD2
I have also checked out the 3-button combo which seems to be disabled on my phone. I'll get this fixed before doing anything.
So I want to update to the froyo release and will probably be uding the Kies hack to do this. I'll use the XEE code which I believe will give me the danish language as an option.
Do I need to make backup of some of the system files before doing this?
In some poste there is talk about backing up some system files before upgrading as there is some information which is needed to unlock the phone again.
Well. I am still investigation this issue.
Now I am looking into using odin and firmware from samfirmware . com. Probably to JPA or JPO? Then I have been reading about the DocRambone ROM and will probably try that.
However they suggest to "- Check Simlock and Network lock is OFF *#7465625#". When I do this I am promted with a "Rejected" message.
Can anybody please tell me what this means?
I do not want to start messing with it before I know that the phone will not be locked after flashing to new firmware?
If it will be locked then what is the procedure of unlocking anagin. I have already made backup of the "nv_data.bin.md5" and the "nv_data.bin". Having these files is the same as having backup of the /efs? Reason for asking is that I cannot find /efs on the root of my phone.
Please help!
I have a Samsung Galaxy S original model number GT-I9000HKAOPS. Like many others I jumped the gun and used Kies Registry Patcher 1.6.0.0 to upgrade to Froyo. The firmware version I upgraded to was XEU which I understand is the UK unbranded ROM. Also like many others doing so has changed my Product Code to KOR. With the recent release of the official Optus 2.2 Froyo version I decided to flash this firmware, again using the Kies Registry Patcher. On completion I noticed my product code is still KOR. This has a number of side effects such as Kies continuously prompting that a firmware upgraded is available, plus indicating the wrong market area.
My objective is to restore my Galaxy S back to how it was when it was supplied or how it should be if I had only flashed the official Optus Froyo ROM. I have a rough idea how to do this though I have a few questions:
1. What is the best way to restore my product code? I have seen references to deleting your nv_data.bin as well as entering in a code via your dialler.
2. If rooting your phone to delete nv_data.bin is the best way, this installs an updated kernel as well as other files. If I restore my product code then upgrade to the official Optus Froyo firmware will this replace the updated kernel and remove the other files added through rooting?
3. What other things may have changed upgrading to the XEU ROM that may reside after flashing to the official Optus Froyo ROM?
4. What else may I need to do to achieve my objectives?
Please note I have searched for many hours trying to find solutions and answers to achieve what I want to achive without much luck, any advice would be appreciated.
How to Restore my Galaxy S
Hi - I'm also looking for the same solution but didn't get any. Did u get a chance to get any results ?
I found a solution in regards to the repeated prompt to update firmware through Kies. The fix is, if you have used Kies Registry Patcher 1.6.0.0, to run this again and set enable spoof to false, then click ‘Write Registry’. Next time you run Kies the prompt to upgrade firmware is gone. A residing problem is that if you try to manually do a firmware update through Kies, it comes up with a message stating ‘This device’s version cannot be update’. I imagine this is due to the mismatch between the currently installed firmware, (PDA: I9000DTJP5, PHONE: I9000DTJP3, CSC: I9000OPSJP4) and the current device product code(GT-I9000HKAKOR).
Another interesting question, if anyone has upgraded direct to the official Optus Froyo ROM using Kies without any hacking, have they got the same PDA, PHONE, and CSC details as I have.
http://forum.xda-developers.com/showthread.php?t=787163 go to this page i used the automatic method takes like 2 mins.
Thanks a lot for the post. It was really helpful
Thanks again
--Durai
I have had great success, all without rooting or any other complicated steps, though it wasn’t all smooth sailing.
The steps I took were to use the Kies Registry patcher ver 1.6 to cross grade my phone to the XSA Froyo ROM which is the Australian Telstra, Virgin and etc ROM. Given I’m on Telstra this is ideal ROM for me. The problem I ran into though is the ROM would ‘fail to convert to upgrade mode’. Kies would then report a failed upgrade and would prompt to attempt recovery. I ignored this message a number of times then decided to run with it. Doing so gave me step by step instructions to put the phone into download mode, from there the installation of the ROM began. Once the ROM was fully installed I formatted the internal SD memory, did a factory restore and all is sweet. Product code is XSA, sales code is XSA as well. This is a better outcome to what I was hoping to achieve.
Hi
I have a Galaxy Note bought from Handtec in the UK. They shipped me a Polish device. This Polish device has a CSC set to 'KOR'. The device is being used in the UK. The device is stuck on XXKJ4 2.3.5. I have no interest in either rooting the device, or trying out custom firmwares, but I do wish it to receive the official updates via either OTA or Kies.
From reading these forums, 'KOR' is not a valid CSC. So I use the *#272*Device IMEI# method to change the CSC. I select XEU as the new CSC which I believe to be for the UK where the phone is used.
I now get an OTA update which I download, but the phone refuses to flash it (tried several times). I try via Kies (downloaded from Samsung UK), it says "your device does not support software upgrading via Kies".
I wish to end up with a bog standard UK note at the end of the process, or at least something that will find/get the ICS update when it turns up.
Last time I order anything from Handtec. Updating a phone should not consume this much time, it never did on my iPhone. I love the Note, but need it to 'just work' due to a lack of time to muck about with it.
Can anyone offer a solution that does not involve ODIN, rooting, custom roms or any other non-Samsung provided solutions?
Kind Regards
Nigel (rather peeved with his Note!)
Just tried XEO (polish) CSC, and tried to update the phone again. Failed in the same way. Looks like I am going to have to send the pile of dung to Samsung and have them fix it up with a UK (English) ROM/CSC on my behalf. Kies still reports that it cant upgrade it either.
Waste of time
Rooting and flashing the latest stock ROM on my Handtec Note was rather simple and pain free. In the time you've already spent, you probably could've done it several times now with a time allotment added in for flashing ICS when it's released. LA4 was even a non-wipe ROM, so I didn't have to re-do all of my apps and settings.
And there are so many benefits to rooting, I don't see why anyone would go without. Full usage of Titanium Backup is in and of itself enough reason, let alone Ad-free Android, LBE Privacy Control, and several other great root only apps.
Well, I finally got it to flash by setting the CSC to DEU. It still would not update OTA, but at least Kies would finally see that it was an updatable device.
I used to spend many-a-happy hour fidding with my many WinMo phones and trying out various roms. These days I just need it to work (like my iPhone4 did!). That includes seamless major revision updates that see all my apps/config automagically put back on the phone after the update! It should not really be necessary to root a phone just so that you can do a full backup (incl settings) of it.
I love the note, its far more practical/versatile than my iPhone ever was, and the screen is superb.
Risk of a bricked device, too many custom firmwares, and custom firmwares that change every few days etc are the reasons I have not rooted/flashed with ODIN. I also do not know where to find a stock UK LA4 rom to flash to the device.
Due to the CSC being KOR, and having to change this, The phone wiped its self, that would have been the deal with or without root afaik.
The only stock UK rom listed on the sticky here: http://forum.xda-developers.com/showthread.php?t=1424997 is UK carphone warehouse. Which I imagine means I would get all of their crud on the phone too.
Nigel
thanks
This is probably a very common problem but I have unusual circumstances. I have a Galaxy Mini that I bought in Thailand, I flashed CWM and installed the "Democracy" ROM and had no problems at all with the GPS. I decided to go back to the stock firmware, only problem was I didn't have it! So I went here (http://forum.xda-developers.com/showthread.php?t=1551586) I didn't see the code that's printed on my phone's box on this page so I FOOLISHLY downloaded a European firmware (I figured it would be better to have writing in English than Thai).
Ever since I flashed that via Odin my GPS can't even find satellites even without locking on. I can only figure that this change to European firmware has changed a necessary file for the GPS. I went back to the Democracy ROM and still no GPS.
I just can't seem to find my original firmware that is printed on my phone's box (GT-S5570AABTHL), I didn't get the original PDA or CSC code (LESSON LEARNED!). The closest I can find is here:
http://www.sammobile.com/firmware/?page=8&view=4933
I do remember when I was running original firmware it was S5570B and that is the only result under the S5570B Thailand option. I can't figure out why under "Region" it says Cyprus, Greece when it's titled Thailand.
I just don't know if simply flashing back to the Thai firmware is going to solve my problem or not, I don't even know if this is the right firmware! I would download it and try it but I'm currently on 2G speeds so it will take me 3 hours to download the file just to test it, so I was hoping for a response from this site before I put myself through the agony of the long wait.
Am I on the right path here? Any help will be severely appreciated.
Flash the original country's software i.e. from where you bought it. B'coz if you flash another country's firmware, your GPS wont work. Kies also creates problem (in updates...) in most of these cases.
Sent Via XDA™ Premium
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
Try to flash this firmware : http://www.sammobile.com/firmwares/3/?download=18114 via odin3 it's a i8190XXAMG4 (DBT) firmware it also include modemfs (modem) then try to upgrade your baseband to XXAMG4.
bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
I8190XXAMG4 / QXXAMH1 is a German La Fleur firmware. I have no idea why your CSC seems to be messed up. It should probably be DBT.
What does it say if you dial *#1234# in dialer?
Thanks for the infos so far.
I did not intend to link to the LaFleur version in the first post.
Do I need the root recovery for the baseband update?
With the 1234 code I get:
AP: I8190 XXAMG4
CP: XXXX
CSC: I8190 QXXAMH1
I think this is the same as mentioned before. I checked the origin of the files I used before on this mobile and it is possible that I used this a recovery file which may be for a 8190N (I cannot post the outside link yet). I did not read careful enough the thread linking to this file.
Can this be the origin for the messed CSC version and the missing product code?
Looks like you're without baseband.
Take a look at this thread and flash a modem for i8190.
http://forum.xda-developers.com/showthread.php?t=2526831
Sent through time and space from my s3mini/CM11
Happy end
Hello again,
firstly: Problem is solved - phone works properly. Thanks for the replies and to tys0n for the work with the files and the support - acutally doing the job of Samsung and google.
For the sake of completeness, I will tell what I did, if any unexperienced user (as I still am) will ever come across this thread:
I tried first just the standard firmware AMG4 from Sammobile (which is linked above) and afterwards the baseband files - but both did not help as expected.
I installed CWM and used the file from here and miraculously it was working (The phone is used only in 2G). Later I wiped the data and flashed again with the AMG4 firmware to have a clean version now.
AP, CP, CSC say all XXAMG4 now, Kies recognizes it as DBT (as supposed to). But the product code, which came back and was read out with CheckFus, says I8490 RWA XSE. This should be Indonesia, correct? Is there still an inconsistency somewhere?
Thanks again for the help
Robert