[REF] Manually change "sales code" (CSC selection) when multi-CSC won't allow you to - Galaxy S II General

[REF] Manually change "sales code" (CSC selection) when multi-CSC won't allow you to
I've recently been getting annoyed with how, whenever I updated a firmware, on first boot the phone would still look for an invalid CSC code, which I had "removed" from the phone.
For example, none of the XEU CSCs currently available will allow you to change to / from XEU as those CSCs don't include other options. ... so if you've manually set your CSC to XEE using the *#272*IMEI# trick; there's no way to get back to XEU.
The solution is as follows: (yes, you need root)
1) Ensure the product code in your nvram.bin file is set how you want it, in this case XEU. (it's in the file twice, once on it's own and once at the end of the "I9100LKA" string. Both those should be at the end of line 215 of the file)
2) (and this is the new bit) - there's another file on the phone which stores the "Sales Code" - its the file that tells the phone what CSC to look for on first boot after flashing a firmware. This file doesn't change unless you can successfully use the *#272*IMEI# trick!
2a) Using a file browser that has root privileges, navigate to /efs/imei/ then look for the file "mps_code.dat"
2b) Open this file as a text document (making sure you're mounted R/W) and edit the string to whatever you want (in this case XEU). Note, you should only put in the 3 letter code, not the rest of the product code.
2c) Save the file and reboot the phone. Hey presto you're on a different CSC!
(and I *think* this trick works to change CSC (without actually installing one, obviously), without wiping the /data partition.

wow great work

ok maybe it's just me but I cannot locate the nvram.bin file anywhere????
I'm on ke7 cf rooted and using script manager to browse system, could u direct me pls as I am running around in circles here.
I found efs/imei and that is xeu but i'm stuck on abr somewhere and it's causing me a few probs.

what and where is this "nvram.bin" file ? thanks

c19932 said:
what and where is this "nvram.bin" file ? thanks
Click to expand...
Click to collapse
Anyone can point to where is this nvram.bin file is located please? i am searching for it using root explorer till my eyes are blurry now...still cant find it
Thanks

^^
You cannot see the contents of efs unless you are rooted!

reb73 said:
^^
You cannot see the contents of efs unless you are rooted!
Click to expand...
Click to collapse
With all due respect sir..yes I have root..but still can't locate the nvram.bin file. I found the rest but as per my understanding is...I need to change the value in the nvram.bin file aswell to make all this work.
Thanks again for all the help.
Sent from my GT-I9100 using Tapatalk

My method on SGS1 was to use custom rom from rom kitchen open that and just change the required CSC folder and files with new folder and files zip back up and install .
Does not work yet on SGS 2 due to being unable to rezip and install custom roms .
Work around has just been to copy the relevant \CSC folder and two CSC files + SW conf file to phone deleting originals . Files have been ripped from original firmware nandroid backup .
Factory reset and all changed .
jje

Ok dokie...thanks for the explanation.
Sent from my GT-I9100 using Tapatalk

iznee said:
Anyone can point to where is this nvram.bin file is located please? i am searching for it using root explorer till my eyes are blurry now...still cant find it
Thanks
Click to expand...
Click to collapse
No, because there is no "nvram.bin" inside the latest (-> KE2, KE7, KF1) stock firmwares!
And changing only "mps_code.dat" won't do the trick as this will only create a new "nv_data.bin" after next reboot.
And if you would delete this new "nv_data.bin" (hoping that the files will be recreated/replaced at next reboot, this worked with SGS like this) you will end up with NO ProductCode and an fake IMEI too! So you should be VERY careful modding anything inside of /efs!

I edited the nv data.bin as well from KOR to BTU is this not a wise thing to do on GS3?
Sent from my GT-I9300 using Tapatalk 2

Solution to Change sales code
How to change CSC sales code on Samsung Galaxy S2?
1.Just type *#272*Device IMEI# at Phone dial pad.
2.Select the CSC that you want.
3.Click Install.
4.Phone will be rebooted by itself.
5.That’s all.

goodie said:
I edited the nv data.bin as well from KOR to BTU is this not a wise thing to do on GS3?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I need to change my CSC on GS3 too, that has been locked using *#272*Device IMEI# method.
Did you have any success? If so are you able to please share instructions?

Related

Need Desperate Help nv_data.bin corrupted

Hi guys, I was trying to change my product code back from KOR, to OPS, but have now stuffed my phone
It can't receive calls, and or make them.
I copied the file out using Root Explorer, and then edited it using notepad, then copied it back using Root Explorer, and deleted the md5 file
I made a copy of the bin file, but even when I put the original file back in, it still doesn't work.
The only file I never made a back up of was the md5 file.
What am I doing wrong here ?
Help is most appreciated, as I am really stuffed
Cheers
Put your copy of the bak file in the efs folder and delete the bin and md5 and reboot. As long as your bak file is ok it will load a bin file from it on boot. Dont delete the md5 of the bak file or it wont work.
Edit: did u reboot after copying the bin file back? U never mentioned.
Sent from my GT-I9000 using Tapatalk
Will try that now, but thought I had already tried that.
I still have my IMEI, what are the chances of recovering my phone from this.
In case my nv_data.bin file can't be recovered ?
Cheers
If you still have your imei then you should not be having this trouble
Sent from my GT-I9000 using Tapatalk
You may need to change the file owner to 1001:1001
Sent from my GT-I9000 using Tapatalk
By 1001:1001 you mean in Root Explorer, and file permissions ? If so exactly what do I do to get 1001:1001 ?
I can't make or recieve calls, my APN's are missing, would that stop me from making calls, I thought that only had to do with internet ?
Apn is internet we can fix the in a bit. Plug the phone into the computer with debug enabled. Then abd shell then su then chown 1001.1001 /efs/nv_data.bin
Sent from my GT-I9000 using Tapatalk
Thanks heaps, deleting the files and leaving the backups worked.
I am so grateful for your help.
One last question, changing the Product Code, should be as simple as changing the nv_data.bin file, and replace the old one, and delete the MD5 file ?
When using Root, do I need to be aware of file permissions etc ?
Cheers
My file permissions are rwx------ i changed my product code the same way and all worked fine.
Sent from my GT-I9000 using Tapatalk
Never mind the last question.
The Backup files replaced the KOR product code with the original ones.
So I am now back to where I wanted to be in the first place.
You sir are a true gentleman
Thanks Again
It may be something as simple as the owner was incorrect. Now that you know you can fix it you can try that
Sent from my GT-I9000 using Tapatalk
You are must welcome
Sent from my GT-I9000 using Tapatalk
can anyone confirm the proper product code for a
Captivate on ATT in USA
thanks
thank you for sharing your ideas.

Galaxy s3 getting HD VOICE

S3 getting HD VOICE http://m.techradar.com/news/phone-a...k-telecom-s-hd-voice-over-lte-service-1091435
Sent from my GT-I9300 using xda premium
Poker gypsy said:
S3 getting HD VOICE http://m.techradar.com/news/phone-a...k-telecom-s-hd-voice-over-lte-service-1091435
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
it already has HD voice - just that it is network dependent!
Yeah I had HD Voice enabled with Telstra but since I flashed the stock LG8 ROM, the feature is disabled. Only currently works with Telstra's ROM and the stock XSA (unbranded aus) ROM. Call quality is superb when your speaking to someone else with HD Voice enabled.
Hopefully this means we can enable it with future stock UK firmware as well.
Sent from my GT-I9300 using xda premium
Simmo3D said:
Yeah I had HD Voice enabled with Telstra but since I flashed the stock LG8 ROM, the feature is disabled. Only currently works with Telstra's ROM and the stock XSA (unbranded aus) ROM. Call quality is superb when your speaking to someone else with HD Voice enabled.
Hopefully this means we can enable it with future stock UK firmware as well.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
so what dose it do?
Sent from my GT-I9300 using xda premium
Its basically a higher bandwidth audio codec that makes the calls sound much more clearer.
Sent from my GT-I9300 using xda premium
hd voice works for me on LG8
-flash back to your stock rom
-root your phone
-with root explorer, extract your carrier CSC folder and the SWConfiguration file to your extSDcard
-flash back to LG8
-root your phone
-copy the CSC folder(***) and the SWConfiguration file to where it should be
-open dialer
-use code *#272*YOURIMEI# to change your CSC (it will factory reset your phone)
-when phone will reboot, you will have HD voice working!
(***) if you do not want bloatware from your carrier, just remove the apk from this folder
Use this myself and I now have HD voice working with LG8
Mopral said:
hd voice works for me on LG8
-flash back to your stock rom
-root your phone
-with root explorer, extract your carrier CSC folder and the SWConfiguration file to your extSDcard
-flash back to LG8
-root your phone
-copy the CSC folder(***) and the SWConfiguration file to where it should be
-open dialer
-use code *#272*YOURIMEI# to change your CSC (it will factory reset your phone)
-when phone will reboot, you will have HD voice working!
(***) if you do not want bloatware from your carrier, just remove the apk from this folder
Use this myself and I now have HD voice working with LG8
Click to expand...
Click to collapse
Wish i had known how to do this, had made a few posts on various forums and no-one had a clue what i was on about apart from one poster on here who i couldnt pm. I was on stock Three firmware and when i flashed to latest UK unbranded, the HD voice feature was removed.
I contacted Samsung who said they would open a case for me but the advisor i spoke to asked me what HD Voice was and as soon as i mentioned WB-AMR he didnt have a clue. Needless to say i wont hold out much hope. It should be automatically set to on and it isnt which is a big bugbear of mines.
I have it on the mine in the UK on T Mobile. haven't checked my latest firmware though
Mopral said:
hd voice works for me on LG8
-flash back to your stock rom
-root your phone
-with root explorer, extract your carrier CSC folder and the SWConfiguration file to your extSDcard
-flash back to LG8
-root your phone
-copy the CSC folder(***) and the SWConfiguration file to where it should be
-open dialer
-use code *#272*YOURIMEI# to change your CSC (it will factory reset your phone)
-when phone will reboot, you will have HD voice working!
(***) if you do not want bloatware from your carrier, just remove the apk from this folder
Use this myself and I now have HD voice working with LG8
Click to expand...
Click to collapse
Hi,
I tried this but the change does not take place.
I'm using the Custom Omega Rom - latest build - but it will not let me change/update the CSC.
When I replace the files and do the *#272 thing - there are no other CSC's listed.
I then test to see if WB-AMR is enables and its not...
What am I doing wrong, have reverted back to stock rom for time being...
Is it possible to use another CSC file with the OMEGA rom? I tried flashing the CSC file via odin and still wont work.
Please help
J
JACKERL360 said:
Hi,
I tried this but the change does not take place.
I'm using the Custom Omega Rom - latest build - but it will not let me change/update the CSC.
When I replace the files and do the *#272 thing - there are no other CSC's listed.
I then test to see if WB-AMR is enables and its not...
What am I doing wrong, have reverted back to stock rom for time being...
Is it possible to use another CSC file with the OMEGA rom? I tried flashing the CSC file via odin and still wont work.
Please help
J
Click to expand...
Click to collapse
Are you sure that your carrier support WB-AMR?
Some CSC are a little bit tricky...
Post a link to what you have extracted from your stock carrier rom (CSC folder + SWconfiguration file) and I will try to find what could be done to make it work...
Mopral said:
Are you sure that your carrier support WB-AMR?
Some CSC are a little bit tricky...
Post a link to what you have extracted from your stock carrier rom (CSC folder + SWconfiguration file) and I will try to find what could be done to make it work...
Click to expand...
Click to collapse
Yep - my carrier is THREE and WB-AMR works with stock rom.
J
JACKERL360 said:
Yep - my carrier is THREE and WB-AMR works with stock rom.
J
Click to expand...
Click to collapse
Ok!
Now that I have this answer, Just give me a link to what you have extracted from your stock three rom
I will take a look at it...
Mopral said:
Ok!
Now that I have this answer, Just give me a link to what you have extracted from your stock three rom
I will take a look at it...
Click to expand...
Click to collapse
I have extracted the folder 'csc' that contains: -
contents
customer
defaut_Workspace
language
others
sales_code.dat
And also extracted the file: -
SW_Configuration
Thanks
J
JACKERL360 said:
I have extracted the folder 'csc' that contains: -
contents
customer
defaut_Workspace
language
others
sales_code.dat
And also extracted the file: -
SW_Configuration
Thanks
J
Click to expand...
Click to collapse
SO it is a "straight" CSC and this is why the *#272* thing does not work
try that:
-make a backup of your app and data
-erase all files in your CSC folder on your phone
-put the files extracted from your CSC carrier rom in this empty CSC folder
-put SW_configuration to /system folder on your phone
-restart in recovery
-make a factory reset (will erase your data and app so that is why I ask you to make a backup) from recovery
-restart your phone
WARNING: I know nothing about omega rom (I am still on full stock...) so no guarantee that it will work. there is a risk that you will have to reflash your rom if it does not work properly but there is no risk to brick your phone
Mopral said:
SO it is a "straight" CSC and this is why the *#272* thing does not work
try that:
-make a backup of your app and data
-erase all files in your CSC folder on your phone
-put the files extracted from your CSC carrier rom in this empty CSC folder
-put SW_configuration to /system folder on your phone
-restart in recovery
-make a factory reset (will erase your data and app so that is why I ask you to make a backup) from recovery
-restart your phone
WARNING: I know nothing about omega rom (I am still on full stock...) so no guarantee that it will work. there is a risk that you will have to reflash your rom if it does not work properly but there is no risk to brick your phone
Click to expand...
Click to collapse
WORKS!!!!
I also copied the file CSCVersion as well - dont know if this made any difference.
Now using Omega 11.1 with HD Voice...
Thanks very much...
J
JACKERL360 said:
WORKS!!!!
Now using Omega 11.1 with HD Voice...
Thanks very much...
J
Click to expand...
Click to collapse
Glad that it works for you.
Only drawback: you will have to do this each time you flash a new rom that change the CSC...
Why the heck isnt HD Voice enabled by default? I know not all networks support it but surely even if it was on then the network that doesnt support it just wouldnt be able to use it. Madness.
JACKERL360 said:
WORKS!!!!
I also copied the file CSCVersion as well - dont know if this made any difference.
Now using Omega 11.1 with HD Voice...
Thanks very much...
J
Click to expand...
Click to collapse
Is it possible you could post a zip with the csc files etc needed to activate HD Voice ? I am on three also only my s3 is an unbranded BTU phone
Cheers
c0manche said:
Is it possible you could post a zip with the csc files etc needed to activate HD Voice ? I am on three also only my s3 is an unbranded BTU phone
Cheers
Click to expand...
Click to collapse
+1
Sent from my GT-I9300 using xda premium
Would also appreciate a flashable CWM image which can enable HD-Voice on Three for the unbranded phones.

[HOWTO] Change CSC region code without losing data

Hello,
I had to make a video for a noob girly friend (hum...) who needed to change her CSC region code but didn't want to lose time to copy her sd card partition to her PC, then back to phone... And the problem is recursive on XDA's threads, so I made the video in english to let people understand. Sorry for my bad unpracticed english...
As everyone know, changing CSC from a custom ROM wipes everything on sd card partiton. So the point is to change it directly in te .zip file of the ROM.
How to do it, easy as 1, 2, 3 :
- Extract your ROM .zip in a new folder
- Go to system / csc
- Here's a list of available CSC region codes
- Choose your CSC (XEF for me - France)
- Go to XEF (replace by your CSC) / system / csc
- Copy all files : contents.db, customer.xml, feature.xml, others.xml, sales_code.dat
- Paste it and replace files in the main CSC folder : ROM / system / CSC
- Repack all the folders in a .zip file
Here' s the video :
http://youtu.be/RqplhCYQdPI
PS : I don't get how to integrate youtube video, I paste embeded intergrated link (<iframe width=....) wraped by [YOUTUBE] tags, but video isn't showing...
gamin92 said:
Hello,
I had to make a video for a noob girly friend (hum...) who needed to change her CSC region code but didn't want to lose time to copy her sd card partition to her PC, then back to phone... And the problem is recursive on XDA's threads, so I made the video in english to let people understand. Sorry for my bad unpracticed english...
As everyone know, changing CSC from a custom ROM wipes everything on sd card partiton. So the point is to change it directly in te .zip file of the ROM.
Click to expand...
Click to collapse
How does this write to the EFS partition? The CSC is in there as well.
Kangburra said:
How does this write to the EFS partition? The CSC is in there as well.
Click to expand...
Click to collapse
Is It ????????????????
jje
JJEgan said:
Is It ????????????????
jje
Click to expand...
Click to collapse
Yes, take a look in /efs/imei/mps_code.dat
Kangburra said:
How does this write to the EFS partition? The CSC is in there as well.
Click to expand...
Click to collapse
Hmm, didn't know that. But doing this gives chosen CSC in "CSC selector" of different ROMs, and correct access in market.
gamin92 said:
Hmm, didn't know that. But doing this gives chosen CSC in "CSC selector" of different ROMs, and correct access in market.
Click to expand...
Click to collapse
I would find out, your fix may break something quite significant, there must be a reason you can't just edit the user accessible bits or they would have done it for SGS2.
Kangburra said:
I would find out, your fix may break something quite significant, there must be a reason you can't just edit the user accessible bits or they would have done it for SGS2.
Click to expand...
Click to collapse
I've been doing this since 3 months, everything's going fine, and apps I couldn't see or install from market are back. Probably not the best way to do, but it doesn't break stuff.
Kangburra said:
Yes, take a look in /efs/imei/mps_code.dat
Click to expand...
Click to collapse
Doubt if that's relevant to phone use as it just gives the Samsung letter code like XEO .
Plus i have copied CSC files over for years with no problem and don't even bother with CSC now .
jje
JJEgan said:
Doubt if that's relevant to phone use as it just gives the Samsung letter code like XEO .
Plus i have copied CSC files over for years with no problem and don't even bother with CSC now. jje
Click to expand...
Click to collapse
Agree, have edited 'CSCVersion.txt' and 'SW_Configuration.xml' without even changing CSC files and 'kies' shows my region.
02xda2 said:
Agree, have edited 'CSCVersion.txt' and 'SW_Configuration.xml' without even changing CSC files and 'kies' shows my region.
Click to expand...
Click to collapse
What is the ROM status? Modified or normal?
Kangburra said:
What is the ROM status? Modified or normal?
Click to expand...
Click to collapse
Normal !
(Vikingway v4 / recovery 6.0.2.7 touch)
So one noob question: is it possible to do that with root explorer on phone too?
mondeo-rs said:
So one noob question: is it possible to do that with root explorer on phone too?
Click to expand...
Click to collapse
How will you edit the files with 'root explorer' ?
I understood this so: i copy the CSC files from the csc i need and paste it in the csc from the rom default (from dbt to eur) and reboot. Maybe i am on the wrong way.
mondeo-rs said:
I understood this so: i copy the CSC files from the csc i need and paste it in the csc from the rom default (from dbt to eur) and reboot. Maybe i am on the wrong way.
Click to expand...
Click to collapse
I did that once with my SGS2 and it work, but don't forget to reboot the phone after copying .. Now i'm not sure if it would work with SGS3
Press "Thanks" if i helped.
Yes, something like that, copy the csc you need to the device replacing the csc there.
And also the two files mentioned earlier (edit if required) to the '/system' folder.
What could be if it not works? Bricked? No booting?
Sorry for my bad english.
---------- Post added at 08:27 PM ---------- Previous post was at 08:12 PM ----------
So i am on omega ella, default is eur, but i wanna dbt. the file you sad, there is in :
cscversion.txt I9300oxaella
sw-configuration.xml cscname i9300oxa/cscversion ella.
So what must i chage to get dbt? Omegarom is multicsc, so dbt is there
greets mike
mondeo-rs said:
What could be if it not works? Bricked? No booting?
Sorry for my bad english.
---------- Post added at 08:27 PM ---------- Previous post was at 08:12 PM ----------
So i am on omega ella, default is eur, but i wanna dbt. the file you sad, there is in :
cscversion.txt I9300oxaella
sw-configuration.xml cscname i9300oxa/cscversion ella.
So what must i chage to get dbt? Omegarom is multicsc, so dbt is there
greets mike
Click to expand...
Click to collapse
ELLA show you're on OXA (europe) but if you were in DBT before flashing ELLA you still keep your CSC , just go to recovery (VOL + , menu , power) and there it will show your real CSC
Press "Thanks" if i helped.
Sorry, can`t see this in recovery.
Hey, this was an idea of mine! :crying:
http://forum.xda-developers.com/showthread.php?p=36348391#post36348391

[GUIDE]How to change your region.

Always make a backup before changing / on your device!
Q. What is this?
A. A way to change your region. More manufacturers in QRemote, Russian/Greek/etc T9 in dialer, working 4G, no wifi frequency restrictions and more.
Q. Will it get me OTA's of the region i changed to?
A. No.
Q. Is there any easier method, one that does not require root, perhaps?
A. I don't know one.
Boring technical details:
Latest firmwares do not "belong" to region. Instead, they adapt to phone's own region. The check is done at each boot, settings are applied after build.prop.
The detection uses combination of operator code and country code (2 bytes, numbering convention unknown. In LG's documents it's referred to as "BUYER").
LG determines phone's region by looking into the "misc" partition, at addresses 0000A000-0000A020.
Information at them looks like this:
Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,12"
, where "12" is country code.
We can change it ourselves by using hex editor on a dumped image.
The regional parameters reside in /cust/ folder. The file "/cust/cust_path_mapping.cfg" maps "{operator_code},{country_code}" to a folder where it's parameters reside.
Note: some countries (FRA, for example) or some operators don't have their own folder in /cust/. They use 11 (OPEN_EU) as NT code, and identify themselves based on some other info I've yet to find.
Example of cust_path_mapping.cfg content:
Code:
20810,FF=/cust/VDF_COM/FR
20810,01=/cust/VDF_COM/LPM
Explanation: Vodafone in any country but 01 will use "/cust/VDF_COM/FR", while Vodafone in "01" country will use "/cust/VDF_COM/LPM". Notice theirs relative positions. This means that only the most exact match is used, and creating "FFFFFF,FF=/cust/XDA" key won't point the phone towards XDA folder.
By changing this file - or changing the contents of the folder your "operator,country" combo is pointing to - you can change your phone's region to anything you want.
There is also a "/cust/cust.prop" file. It contains fallback to defaults, if phone was unable to determine needed folder, or it didn't exist, it uses "/cust/SUPERSET/".
! In 5.0 firmwares, annoying message stating that "current version not avaliable for user" shows up if the above happens.
The folders in /cust/ hold operator/country settings. LG named them this way: "OPERATOR_COUNTRY". There are 2 special values - OPEN for operator - which means any operator, COM for country - which means any country.
OPEN_XXX hold parameters for specific country. These folders may contain subfolders with parameters for smaller operators which operate only inside this country.
Example: OPEN_ZA, which contains folders for MTN and VDC operators.
XXX_COM contain parameters for specific operator. These folders may contain subfolders with parameters for specific countries.
Example: /VDF_COM is intended for Vodafone. It contains folders FR and LPM, which are intended for France and LPM (?).
{OPERATOR_COUNTRY} folders are intended for 1 combination of operator and country, they should not contain subfolders with settings for other operators/countries.
Example: PCL_IL, contains settings for one of Israel operators.
The method itself:
1) Install Busybox.
1) Look at /cust/cust_path_mapping.cfg and choose some region's code. The folder names are usually self-explanatory, and you can always look into /cust/{folder}/cust.prop to see to what ro.build.target_operator, ro.build.target_country and ro.build.target_region variables are set.
2) Execute the below code, replacing "\x31\x32" in "echo -n '\x31\x32'" with your chosen code. Examples: "\x35\x36" is 56 region, "\x37\x33" is 73 region and so on.
First line backs up your "misc" partition to /sdcard/misc.bin, you should copy this file to safe storage.
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.bin
echo -n '\x31\x32' | /system/xbin/dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=40991 count=2 conv=notrunc
reboot
Why did i use busybox's dd? Because in LG's 5.0 default dd was compiled without conv option...
Enjoy your new region!
Other methods:
Method 1: substitution.
Step 1: Find out which country your phone was meant to use ("Settings->About Phone-> Software" ). Find your current operator code. Using these, find currently used folder in /cust/. You can get to know folder's region by looking on it's name, or opening the {folder}/cust.prop file and looking at these keys:
Code:
ro.build.target_operator
ro.build.target_country
ro.build.target_region
They are pretty self-explanatory.
Step 2: Replace the folder's content with content from the region you want to change to.
Step 3: Reboot and be happy!
Method 2: via editing "misc" partition.
Be extra careful with "misc". This partition is unique for every phone. If it's damaged or wiped, things may get ugly.
I do not know a way of regenerating "misc", since it contains your bluetooth/wifi mac's and IMEI. AFAIK, It is only used for displaying that info in Android and for LG's updates - so you won't lose bluetooth/wifi/mobile data, but still...
Since it's also used for updates, PC suite and "ota updater" won't be able to update your phone anymore if this partition is damaged.
It may also have uses which we don't know about. Make a backup, save it to several clouds and 2-3 offline storages.
Do not proceed if you don't know what "hex editor", "backup" and "partition dump" are.
1) Grab misc with "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.bin".
2) Open misc.bin in any hex editor, go to address "0000A000" and look for this:
Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,12"
Change "12" or whatever number you have there to the one that you need. You can look into cust_path_mapping.cfg to determine it. Save the result to a new file, name it "misc_edited.bin".
3) Replace your misc with edited one: "dd if=/sdcard/misc_edited.bin of=/dev/block/platform/msm_sdcc.1/by-name/misc".
4) Reboot.
I have no idea about how PC suite and others will react to IMEI and country code mismatch. They probably won't care, but we don't know it for sure.
Method 3:
Warning, in 5.0 this will cause the annoying "Current version not avaliable for user!" message to show up at each boot.
1) Backup your rom and /cust/ folder.
2) In /cust/cust_path_mapping.cfg delete all lines except
Code:
999999,99=/cust/SUPERSET
.
3) Copy everything from /cust/{Your_desired_region} to /cust/SUPERSET.
4) Reboot.
Big thanks to my Russian comrades rxu, KestL and Beerukoff for pointing out important details!
Reserved.
Hi, thanks very much for this write up. I'm still a bit confused as to how to actually do this - and I'm thinking others might be as well since there haven't been any responses. Would you mind walking me through how to change the region for a phone purchased in HK? I would like to change it to the EUR region.
Would I open the cust.prop file within the HK folder and change the values for the three variables above to match the ones found in the cust.prop file within the EU folder?
Thanks.
Japultra said:
Hi, thanks very much for this write up. I'm still a bit confused as to how to actually do this - and I'm thinking others might be as well since there haven't been any responses. Would you mind walking me through how to change the region for a phone purchased in HK? I would like to change it to the EUR region.
Would I open the cust.prop file within the HK folder and change the values for the three variables above to match the ones found in the cust.prop file within the EU folder?
Thanks.
Click to expand...
Click to collapse
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
I'm using a custom based off a version that doesn't have my cust (SEA) so mine reverts to the default. I'm in the uk.
Other than having to delete the ltesettings apk I haven't noticed any problems. Do you think I would notice anything if I change the mapping to point at EU it would improve anything?
Nice write-up, very detailed. This seems very specific, do you know why you would want to do this? A scenario maybe?
YaDr said:
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
Click to expand...
Click to collapse
Thanks! That worked.
oracleoftruth said:
I'm using a custom based off a version that doesn't have my cust (SEA) so mine reverts to the default. I'm in the uk.
Other than having to delete the ltesettings apk I haven't noticed any problems. Do you think I would notice anything if I change the mapping to point at EU it would improve anything?
Click to expand...
Click to collapse
No, i don't think that you'll notice anything. You'll get more manufacturers in qremote and other very minor features.
sprremix said:
Nice write-up, very detailed. This seems very specific, do you know why you would want to do this? A scenario maybe?
Click to expand...
Click to collapse
Thanks!
Why you may want to change region:
1) QRemote contains a lot more manufacturers if ro.build.target_region is set to ESA. Since /cust/ is applied after build.prop, you'll have to edit it.
For example, in CIS region Western Digital is absent. It is officially sold here in Russia, there is no embargo or whatever. LG just decided that Russians doesn't have the right to control "WD TV live" using QRemote. Nice.
2) Dialer - there are special dialer overlays with letters used in specific regions. For CIS it contains cyrillic letters, for Greece it contains Greek letters, and so on.
3) Featureset.xml also depends on region. It contains miscellaneous settings, like the ability to send empty sms.
4) There are a lot more overlays for other apps. Voicemate, etc. Nothing major, but this can change in future.
P.S. I updated first post with info about misc partition.
Thanks @YaDr
Just changed the V10M Hong kong to EUR-XX.
One question: do i need to manually change/fix all the new files permissions?
robalm said:
Thanks @YaDr
Just changed the V10M Hong kong to EUR-XX.
One question: do i need to manually change/fix all the new files permissions?
Click to expand...
Click to collapse
No, until files have been exposed to non-posix filesystem and lost their permissions, or you've changed them manually.
Default permissions for /cust/ are 755 with root/root as owner/group.
YaDr said:
No, until files have been exposed to non-posix filesystem and lost their permissions, or you've changed them manually.
Default permissions for /cust/ are 755 with root/root as owner/group.
Click to expand...
Click to collapse
Ok.
In /cust/SUPERSET There is already a "cust.prop" file should i replace that one with the cust.prop from my OPEN_XX folder?
Is there a risk to loose/get blocked IMEI in this way we change region?
robalm said:
Ok.
In /cust/SUPERSET There is already a "cust.prop" file should i replace that one with the cust.prop from my OPEN_XX folder?
Is there a risk to loose/get blocked IMEI in this way we change region?
Click to expand...
Click to collapse
Yes, you should replace it.
It is highly unlikely that you will lose IMEI. However, i ask everyone to make a full nandroid backup, efs included, before you do anything to your phone.
As for the blocking... Why would your service provider care enough to blacklist your IMEI? Unless it is forbidden by local laws or service contract, manipulating files on your phone is perfectly legal.
YaDr said:
Yes, you should replace it.
It is highly unlikely that you will lose IMEI. However, i ask everyone to make a full nandroid backup, efs included, before you do anything to your phone.
As for the blocking... Why would your service provider care enough to blacklist your IMEI? Unless it is forbidden by local laws or service contract, manipulating files on your phone is perfectly legal.
Click to expand...
Click to collapse
Thanks bud.
I have a efs backup, but no nandroid backup.
YaDr said:
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
Click to expand...
Click to collapse
Hi
Need to erase all the rest lines or only change those 2?
Thank you
alexa74 said:
Hi
Need to erase all the rest lines or only change those 2?
Thank you
Click to expand...
Click to collapse
You only need to change 1 line. Nothing has to be deleted.
Did anybody tried if this works on the Korean models (F400S/L/K)?
YaDr said:
You only need to change 1 line. Nothing has to be deleted.
Click to expand...
Click to collapse
Hi
Thanks, it was helpfully,but may be you can help me to change the region to Israel?
alexa74 said:
Hi
Thanks, it was helpfully,but may be you can help me to change the region to Israel?
Click to expand...
Click to collapse
What's your current region?
YaDr said:
What's your current region?
Click to expand...
Click to collapse
Was HKG and now is EU
alexa74 said:
Was HKG and now is EU
Click to expand...
Click to collapse
in /cust/cust_path_mapping.cfg find a line ending with "OPEN_EU", and change folder name from "OPEN_EU" to "PCL_IL" or "ORI_IL". If you don't have these folders, i can zip them and send them to you.

How to make others.xml work again after using CSC Feature Expert from Play Store

Hey! First time using the forum
Let me introduce my question.
Galaxy A5 2016 (Nougat) rooted, stock firmware
At first editing CSC settings via others.xml (used Root Browser) worked fine, until I tried CSC Feature Expert from Play Store.
Altough this app is nice I want to gain control again over others.xml. Now, only modifications via the app work and I cant get anything I type directly on the file to be applied after a reboot.
Tried uninstalling the app and using its restore button, but still others.xml does nothing.
How to edit others.xml again without the app?
Sorry for the noob question
Thanks in advance
brod56 said:
Hey! First time using the forum
Let me introduce my question.
Galaxy A5 2016 (Nougat) rooted, stock firmware
At first editing CSC settings via others.xml (used Root Browser) worked fine, until I tried CSC Feature Expert from Play Store.
Altough this app is nice I want to gain control again over others.xml. Now, only modifications via the app work and I cant get anything I type directly on the file to be applied after a reboot.
Tried uninstalling the app and using its restore button, but still others.xml does nothing.
How to edit others.xml again without the app?
Sorry for the noob question
Thanks in advance
Click to expand...
Click to collapse
I think there must be an another .xml file in system/csc which do the same job as others.xml. CSC Feature Expert maybe generated a feature.xml file in your csc folder. Delete it and try again.
xXPR0T0TYPEXx said:
I think there must be an another .xml file in system/csc which do the same job as others.xml. CSC Feature Expert maybe generated a feature.xml file in your csc folder. Delete it and try again.
Click to expand...
Click to collapse
Thanks! I didn't notice that file. I'm simply adding new lines to features.xml now and it works just fine.

Categories

Resources