Related
I had a Galaxy i5700 a few years ago but it has been sitting gathering dust. I changed to an iPhone 3GS and now onto a Galaxy S3 which I love.
I want to get my old i5700 back in use as a prepaid phone on a different network but I have a few issues.
1 - it needs to be unlocked. I flashed the firmware along time ago to get rid of network branding but I'm now trying to use it on the 3 Ireland network and I think it is still locked on 3 UK. When I turn on with the sim in it says "sim network unlock code".
2 - I don't have the Play Store, only the old Market app and I can't seem to update to the play store. I tried to download what I think is the APK for it but when I try to install is says "there was an error parsing the package".
I kow this is an old phone but can someone point me in the right direction? Thanks!
How To
Hello! With regard to Play Store, you must update the device to version 2.2 or higher! If you can not install it because you, Presumably, the 2.1 is the latest version available officially for the Galaxy Spica.
As regards the release to use other sim driving is this:
UPDATED# 24/4/2011
Hello another time.
I dicovered a new method to unlock the Spica for all carriers.
This method can be public, is no related with imei generation, I do it public for all Spica users.
You need be root, root explorer and one hex editor, I use UltraEdit, you can use the trial version.
First step, backup efs folder.
With root explorer, copy the efs folder from your Spica to your sd memory, save two copies in your pc, one is a backup, no modify it, and the other copy is for modify nv_data.bin to unlock the Spica.
Second step, edit nv_data bin and paste in efs folder.
Open nv_data.bin with your hex-editor, I use Ultraedit.
Go to line 433a0h, you only need do changes in this line.
Look at this first image, is your locked sim nv_data.bin:
You need do this changes, is a unlocked sim nv_data.bin:
Edit line 433a0h, do changes in hexadecimal area, not the encrypted area, only two values, change 01 to 00, see the pictures, and save the nv_data.bin modify.
Now the nv_data.bin is sim unlocked.
Put the new nv_data.bin in your sd card.
Copy with root explorer from your sd card, and paste in to efs folder, overwrite the original nv_data.bin.
Reboot and enjoy
PD: Other values, and changes in near lines too are valid, this disable the check sim.
If you like my work, buy me a english dictionary, is very bad Donate
Click to expand...
Click to collapse
Via Samdr*id
Seraser thanks for the guide, Samdr*id*com Forum user. I would put the link but I have 10 posts and then the forum does not allow that to prevent spam.
Hey guys,
I am trying to get my photos from my s3 onto my Nexus 4, while keeping the modify time correct, so the Gallery displays them in the correct order. All methods I've tried so far result in the modify time being set to the create time.
I pulled them from the s3 with adb, corrected the MTIME using jhead (linux), and tar'd them up with the MTIME preserved.
I've yet to find a way I can extract this tar onto the phone without it losing the MTIME. I've tried many different apps that can deal with archives, none have the option to keep it. Trying to extract the tar on the command line results in an archive magic error, or similar (not at my phone now).
With the s3 this was easy due to the external SD card, but I can't for the life of me find a way to do this here. I tried QuickPic's fix dates feature but it doesn't correct the dates
Anyone have any ideas?
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.
I know this is a Samsung S7 forum. But I think the files will be very fimilar and thus the reason I am asking here as well.
I need your guys help. I am trying to create a data fix file for Note 4 for a note 7 rom. I need some files off of a note7. I need all of the following:
all files, folders and sub files under System/CSC. all files, folders and sub files under System/Etc, all just files under System. lastly I need the file under Data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml this file
you most likely don't even need root to get these as you won't be modifying anything just copying them.
the size of the combined files should be under 10 megs zipped.
Or if anyone knows of a way I can use a stock firmware to extract files from it that would be awesome. However I have yet to find a way.
In the note 4 sprint forums we are having a hell of a time trying to get the note 7 roms to work on the note 4 for SMS, MMS, DATA, Phone calls. this would help out a ton if someone can do this for me.
Thank you guys.
I REALLY REALLY need Customer.xml and Others.xml ASAP however I really need the rest as well
●BRIEF INTRODUCTION :-
•Here Is Guide For Those Samsung Galaxy Devices Users Who Are Missing Some OMC-CSC Features On Their Devices
•Since Only Few Country's Cscfeatures.xml OR Others.xml Are Fully Modified By Devs Due To Time Lackness Or Any Other Reasons While Other Country's Need To Be Modified
●REQUIREMENTS :-
•Any Custom S8+ Based/Note 5 Based/Note FE Based Nougat 7.0/Marshmallow 6.0.1 TouchWiz Custom/TouchWiz Stock Rooted Rom
•Rooted With Properly Working SuperSU Root OR Magisk Root
•Root Explorer Like Es File Explorer OR Root Explorer by SpeedSoftware
•Some Typing Experience As Small Typo Is Unacceptable
●INSTRUCTIONS :-
•Use Any Root Explorer Above Mentioned With
Proper Root Access Granted
Mount R/W Permitted
•Follow The Path Local/System/Csc/Others.xml
Note :-
*For N5 Based Custom TouchWiz Roms/Any Custom TouchWiz Roms That Uses Others.xml Features Format
•Follow The Path Local/System/Omc/Your Selected One While Installing Rom/Cscfeatures.xml
Note :-
*For S8+ Based Custom TouchWiz Roms/Any Custom TouchWiz Rom With Cscfeatures.xml Features Format
•Take Cscfeatures.xml OR Others.xml For Editing Purpose As Per Your Rom's Format To add Some Useful OMC-CSC Tweaks
•After Editing Completes Kindly Save Changes And Reboot Your Device Right After Editing/Saving To Make Mentioned OMC-CSC Tweaks Works Actually
●SOME USEFUL OMC-CSC TWEAKS :-
▪Places Tab In Samsung Stock Phone App :-
Note :-
*Line To Be Added In Cscfeatures.xml OR Others.xml Is As Below
<CscFeature_Common_ConfigSvcProviderForUnknownNumber>whitepages,whitepages,on</CscFeature_Common_ConfigSvcProviderForUnknownNumber>
▪Samsung Stock Real Time Network Speed In StatusBar :-
Note :-
*Place It Below <Cscfeature_Setting_> Tweaks
<CscFeature_Setting_SupportRealTimeNetworkSpeed>TRUE</CscFeature_Setting_SupportRealTimeNetworkSpeed>
▪Data Usage View On Quick Settings Panel :-
Note :-
*Place It Below <Cscfeature_SystemUI_> Tweaks
<CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>TRUE</CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>
▪Adding Some Essential Missing Toggles In Quick Setting Panel
Note :-
*For Eg.
Some Useful Quick Toggles Like Following "ScreenCapture,VoLte,Ebook,UHQ,TouchSensitivity,DeviceVisibility" etc.
Sticky :-
*Find The Below Line in <Cscfeature_SystemUI_> Tweaks
*See Which Toggles Missing In Your Quick Setting Panel
*Add Them Manually As Per Requirements
*While Adding Quick Toggles Manually Kindly Be Careful To Put Comma Symbol [ , ] To Make Them Work Effectively
<CscFeature_SystemUI_ConfigDefQuickSettingItem>Wifi,SilentMode,MobileData,Bluetooth,RotationLock,Flashlight,AirplaneMode,ScreenCapture,Performance,EdgeLighting,Nfc,WifiHotspot,BlueLightFilter,UDS,PowerSaving,Aod,AllShareCast,SFinder,DeviceVisibility,Ebook,Dnd,SideKey,Location,Sync,SecureFolder,VoLte,UHQ,TouchSensitivity,RedPacket,SmartStay,Toolbox,MultiWindow,SecureFolder,UltraPowerSaving</CscFeature_SystemUI_ConfigDefQuickSettingItem>
▪AppLock OR Any SmartManager Related Missing Features
Note :-
*Place It Below <Cscfeature_SmartManager_> Tweaks
*Add AppLock OR Any Missing SmartManager Realted Features
Sticky :-
*You Will Need AppLock.Apk From Another Custom Rom/Downloaded From External Sources To Place In Local/System/Priv-app/Applock Folder
*Give Proper Permissions To Both Folder And App Inside The Folder Correctly
<CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autolaunch|autorestart|storageclean|backgroundapp|applock|trafficmanager|trafficmanager_auto|notificationmanager|data_compression|cstyle|fake_base_station|appclean|devicesecurity</CscFeature_SmartManager_ConfigSubFeatures>
▪Auto Call Recording Option While Calling From Native Samsung Phone App :-
Note :-
*Place It Below <CscFeature_VoiceCall_> Tweaks
Sticky :-
*Above Mentioned Feature May Not Work On Every Device Due To County's OMC-CSC Limitations
*Base Is Complete Different For Every Roms
*Some Belongs Note5 Base/Some Belongs S8+ Base/Some Belongs To Note FE Base Etc.
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
▪Call Recording Button Replaced With Add Call Button In Native Samsung Phone App :-
Note :-
*Place It Below <Cscfeature_VoiceCall_> Tweaks
<CscFeature_VoiceCall_EnableCallButtonInFdnList>TRUE</CscFeature_VoiceCall_EnableCallButtonInFdnList>
▪For LTE Icon Instead Of 4G Icon Have To Place/Add Following Line OR For 4G Icon Instead Of LTE Icon Have To Remove The Following Line :-
Note :-
*Place It Below <CscFeature_SystemUI_> Tweaks
<CscFeature_SystemUI_ConfigOverrideDataIcon>LTE</CscFeature_SystemUI_ConfigOverrideDataIcon>
●IMPORTANT NOTE :-
Not All Features Will Work On Every Device Or Every Country's OMC-CSC Due To Country/Regional Restrictions But Most Should Work Well
More Tweaks Will Be Added As Per Availability And Working Status After Being Tested.
I'm attaching my App Lock .zip if someone wants to use it, I was missing the line that enables it :silly:
cachanilla86 said:
I'm attaching my App Lock .zip if someone wants to use it, I was missing the line that enables it :silly:
Click to expand...
Click to collapse
Thanks For Your Contribution Mate
Hi Some questions
1. Are these features dependent on the type of processor Snapdragon / Exynos. For eg some feature set require parameters to be provided, would they change depending on the processor especially network related features (eg: enabling VOLTE)
2. Lets say i root the phone and make changes to the CSCFeatures file. Now if i unroot the phone by flashing the stock AP file back using ODIN, then technically i have unrooted the phone and since i did not flash the CSC file, the changes made should continue to be there. Would the changes and files written to the system/csc areas continue to be there after i flash it with the stock AP file ?
deltacharlie said:
Hi Some questions
1. Are these features dependent on the type of processor Snapdragon / Exynos. For eg some feature set require parameters to be provided, would they change depending on the processor especially network related features (eg: enabling VOLTE)
2. Lets say i root the phone and make changes to the CSCFeatures file. Now if i unroot the phone by flashing the stock AP file back using ODIN, then technically i have unrooted the phone and since i did not flash the CSC file, the changes made should continue to be there. Would the changes and files written to the system/csc areas continue to be there after i flash it with the stock AP file ?
Click to expand...
Click to collapse
1)Though Some Features are related with CPU but almost all are hardware
Since these tweaks are Software related should work without any conflict between CPU's
VoLte is totally CSC related thing n ofcourse needs to be supported by network carrier provider within country
(For unlocked devices it might would be used as many other guides would be there to enable native VoLte feature on Network unlocked devices Since CPU versions varies accordingly markets and many people prefer to use snapdragon or exynos as per own choices hence needs sometimes unlocking of network)
2)For making changes in omc-csc obviously you needs to be rooted point granted. But if you unroot to stock by flashing Stock Firmware using odin saved changes will lost as Odin flashing does complete wipe including Internal storage (Not confirmed as sometimes it doesn't wipes internal storage dramatically but in every case it does. I guess especially in case of flashing Stock over Stock it doesn't wipe internal storage but In case of complete unroot from Custom to Stock it wipes as well as you yourself need to wipe internal storage to avoid odin flashing errors)
3)Also AP (One File Firmware Contains Home_CSC Pre Included In Cache.img if you extract it you can even get flashable zip for your Home_csc in Case if you want to use native features like eg.VoLte on Other CSC Based Custom Roms), So ofcourse changes you previously done will be lost after flashing omc-csc alone OR whole AP/Four Files Full Firmware through Odin
Thanks for the detailed explanation. But one clarification required again. In the option where i am trying to unroot the deivce i only flash the AP file (not the one file that contains all files) but one of the 4 firmware files. I uncompressed it and found it to contain - boot.img, recovery.imk and system.img.ext4. So will that still overwrite the CSC files that were modified when root was in place. ?
deltacharlie said:
Thanks for the detailed explanation. But one clarification required again. In the option where i am trying to unroot the deivce i only flash the AP file (not the one file that contains all files) but one of the 4 firmware files. I uncompressed it and found it to contain - boot.img, recovery.imk and system.img.ext4. So will that still overwrite the CSC files that were modified when root was in place. ?
Click to expand...
Click to collapse
1)Odin Is Designed To Flash Specifically .tar/.tar.md5 files afaik So even if you decompress Stock One File Firmware AP Into 4 Files Likes .img, Odin Will Not Flash It So No Further Discussion Here
(As You Can only Flash Single AP.tar.md5 file in case of One File Firmware So Obviously your whole data will be reset including previous changes you done while on Root using custom Rom)
2)In case of 4 files Full firmware which includes .tar.md5 files for AP/CP/BL/CSC Etc to be added in Odin's respective Tabs
You will also loose your previous changes made while on Root As flashing Odin will completely unroot your device so no access to system/root directory
(In simple way, Odin flash will lead your device to complete stock experience without root only Knox flag tripped exception OR else your device gets in Factory manner after flashing Stock firmware through odin)
Apologies, I just dont seem to able to articulate my point/query. So further questions.
In the second case you mentioned (of 4 files Full firmware which includes .tar.md5 files for AP/CP/BL/CSC Etc to be added in Odin's respective Tabs) what if i only flash the AP file and leave the other tabs blank. Will it still wipe out the CSC area ?
deltacharlie said:
Apologies, I just dont seem to able to articulate my point/query. So further questions.
In the second case you mentioned (of 4 files Full firmware which includes .tar.md5 files for AP/CP/BL/CSC Etc to be added in Odin's respective Tabs) what if i only flash the AP file and leave the other tabs blank. Will it still wipe out the CSC area ?
Click to expand...
Click to collapse
1)Yes It Will erase your previous CSC contains specially if you were on different CSC And Modified It Per Your Requirements While on Root
2)As I Already Mentioned In my earlier post that CSC features are packed within one file firmware too in cache.img format That's why stock Firmwares are specifically categorised according to country for eg. like INS/XSG/XXV/BTU/XME Etc.Which suggests Home_CSC Codes
3)So the conclusion is that either flash 1 file i.e. AP through Odin Or Flash Separate 4 Files Firmware You Will Loose Modified CSC Contains while On Root/On Different CSC Because Odin totally resets your device to factory state/Unroot it So Obviously Modifications Done While On Root Would Be Erased
Hmm this seems like a good post to follow for the Note FE. Thanks !
DarkManX4lf said:
Hmm this seems like a good post to follow for the Note FE. Thanks !
Click to expand...
Click to collapse
Real Note FE or modded ROM? There are a few Note FE ports, but they all have all of this enabled, no need for aditional mods.
cachanilla86 said:
Real Note FE or modded ROM? There are a few Note FE ports, but they all have all of this enabled, no need for aditional mods.
Click to expand...
Click to collapse
I'm on a real Note FE from South Korea N935K.
Hello guys... I'm trying to put up a few things(data speed and count) in my stock nougat ROM for galaxy s6 . There's something that's bothering me... that I don't have the omc folder in my root and in csc/others.xml I can't locate as to where should I type the code.
I know it's CscFeature_ like something mentioned in the OP but I can't find the headings under which the OP states the code is to be put.
I'll appreciate this help.
Please tell if you need screenshot.
Edit: Thanks for consideration (if anyone did ! ) but I figured out my way. Now I have what I wanted.
Thanks for the codes.
Regards
Here is some working csc codes.
<CscFeature_Message_DisableSmsToMmsConversionByTextInput>TRUE</CscFeature_Message_DisableSmsToMmsConversionByTextInput>
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Message_EnableBlackList>TRUE</CscFeature_Message_EnableBlackList>
<CscFeature_Setting_EnableMenuBlockCallMsg>TRUE</CscFeature_Setting_EnableMenuBlockCallMsg>
<CscFeature_Message_EnableSaveRestoreSDCard>TRUE</CscFeature_Message_EnableSaveRestoreSDCard>
<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_SystemUI_SupportRecentAppProtection>TRUE</CscFeature_SystemUI_SupportRecentAppProtection>
<CscFeature_SmartManager_ConfigDashboard>dual_dashboard</CscFeature_SmartManager_ConfigDashboard>
<CscFeature_SystemUI_SupportAssistanceAppChooser>TRUE</CscFeature_SystemUI_SupportAssistanceAppChooser>
<CscFeature_Setting_DisableMenuSoftwareUpdate>TRUE</CscFeature_Setting_DisableMenuSoftwareUpdate>
<CscFeature_Wifi_SupportAdvancedMenu>TRUE</CscFeature_Wifi_SupportAdvancedMenu>
<CscFeature_NFC_StatusBarIconType>DEFAULT</CscFeature_NFC_StatusBarIconType>
<CscFeature_RIL_ForceConnectMMS>TRUE</CscFeature_RIL_ForceConnectMMS>
<CscFeature_Setting_CustNetworkSelMenu4>LTEONLY</CscFeature_Setting_CustNetworkSelMenu4>
<CscFeature_Message_EnableMsgTypeIndicationDuringComposing>TRUE</CscFeature_Message_EnableMsgTypeIndicationDuringComposing>
<CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autorestart|networkpowersaving|storageclean|applock|trafficmanager|notificationmanager|applicationpermission|devicesecurity|data_compression|rootbadgefeature|UDS|cstyle</CscFeature_SmartManager_ConfigSubFeatures>
<CscFeature_Common_EnableAirMessage>TRUE</CscFeature_Common_EnableAirMessage>
<CscFeature_Common_ConfigSvcProviderForUnknownNumber>whitepages,whitepages,on</CscFeature_Common_ConfigSvcProviderForUnknownNumber>