Where is the setting "Allow OEM unlock" being stored?
I mean physically in that partition at what offset or in which file the setting value is stored.
It will be on developer . option in setting.
I mean physically in that partition at what offset or in which file the setting value is stored.
Not where the check box for it is.
Related
http://forum.xda-developers.com/showthread.php?t=1409304
trying to follow those instructions to change from swipe to password lock, but I can't find lockscreen.password_type in the database. In short, here's my problem:
http://android.stackexchange.com/questions/51180/using-adb-to-change-the-screen-lock
I'm trying to change swipe lock to password lock without using the UI. The database is supposed to contain the salt value which I can somehow (how?) use to hash up a default password, and (in theory) overwrite or create the password.key file, thereby changing the password. On my password-protected device, I can neither see lockscreen.password_type nor lockscreen.password_salt in the settings.db:secure table (or in the entire db for that matter). I'm wondering if it's been moved, or if something is wrong with my system.
bump for fast moving board?
Hi!
From the changelog thread:
Anu6is said:
Keyguard quick unlock
Device Type : ALL
Default : ALWAYS ON
Location : ---
Description : Automatically unlock the device once the correct PIN is entered.
Removes the requirement to select submit.
Click to expand...
Click to collapse
Always on, and no setting available in the Settings to disable.
Still, is there a way to disable quick unlock? A param in a config file or a settings database or elsewhere...? I took a quick look at the filenames un /system folder, but nothing really inspiring; I'm no expert on Android system files, I might not even been looking in the right folder...
Thanks!
Is there a way of removing the default APN on a Galaxy Note3 (running Android 4.3)? I have the phone rooted.
Thanks!
m4f1050 said:
Is there a way of removing the default APN on a Galaxy Note3 (running Android 4.3)? I have the phone rooted.
Thanks!
Click to expand...
Click to collapse
create a new one, if u cant delete it...
and add this to APN type...
APN type= default,supl,mms (this will make it default APN)
mdiaz33685 said:
create a new one, if u cant delete it...
and add this to APN type...
APN type= default,supl,mms (this will make it default APN)
Click to expand...
Click to collapse
Thanks but I already did that. I am looking to delete the default T-Mobile US LTE one
You can't and there is no real reason to bother to remove it anyway. Just use the new entry.
You can remove it, but it requires a SQL editor.
Go to data/data/com.android.providers.telephony/databases and edit nwk_info.db
Select the "carriers" table and locate the T-Mobile US LTE / 310260 entry (should be line 26)
Scroll all the way to the far right and change the editable value from 0 to 1.
Restart your phone and you should be able to edit the entry.
The other option is to edit /system/etc/apns-conf.xml directly.
Remember the first rule in tweaking your system... make a backup copy first.
rjohnstone said:
You can remove it, but it requires a SQL editor.
Go to data/data/com.android.providers.telephony/databases and edit nwk_info.db
Select the "carriers" table and locate the T-Mobile US LTE / 310260 entry (should be line 26)
Scroll all the way to the far right and change the editable value from 0 to 1.
Restart your phone and you should be able to edit the entry.
The other option is to edit /system/etc/apns-conf.xml directly.
Remember the first rule in tweaking your system... make a backup copy first.
Click to expand...
Click to collapse
See, this is the type of answer I like to get... not "create a new one" or "you don't need to remove it".. If I want to remove it, LET ME REMOVE IT, it's my phone!
Thanks rjohnstone (for telling me how to edit the entry) and mdiaz (for the APN types)! BTW used SqlLite, great app, only $2.99 on Play store and works VERY well!
The twrp on my mix 2 does not show any files or folders in sdcard, instead it shows some unknown folders that should not exist ??
That's because you haven't entered the right phone security password (the password you use to unlock lockscreen), or maybe you haven't even entered none.
Hello dears.
I have been working for 5g volte vowifi since i bought the phone.
Also You know we have carrier settings files in /product/etc/carriersettings I edited one of them and now I need to replace with original one to try.
but this /product fs cannot be touched cannot be mounted R/W. But We have a option from Magisk. it is overlayfs for all R/O filesystem acting like real one.
Question is How we do this /product fs as overlayfs?
Here one guide we have but I did not excaly get it because I didnot work about building magisk models before.
https://topjohnwu.github.io/Magisk/guides.html
Also I find a module but When I try this I am getting Unzip error. (I already tried to zip again without upper folder )
GitHub - Magisk-Modules-Alt-Repo/magisk_overlayfs: Emulate read-write partition for read-only system partitions
Emulate read-write partition for read-only system partitions - GitHub - Magisk-Modules-Alt-Repo/magisk_overlayfs: Emulate read-write partition for read-only system partitions
github.com
I worked with for ex vodafone_tr.pb file I get parameters from att5g_us.pb( It has lots of parameters for 5g volte vowifi) And I add these information to my carrier file. But I have to push this file to product.
Thank you
You need to create a Magisk module. Best is to download an existing module, unzip it, then modify it, the re-zip it.
Under the directory of the Magisk module, create a subdir called 'system', create a subdir 'product' underneath and 'etc/carriersettings´ subdirs as well. Put your file in there. Re-zip the module. Use adb to push to phone and install the module with the Magisk app. Reboot phone.
Magisk will mount your (modified) file in /product/etc/carriersettings/...
Check if the file is there:
Code:
> adb shell
$ su
# cd /product/etc/carriersettings/...
# ls
Did you edit the confseq files? What exactly did you edit, they are binary blobs. I also believe they are signed in one way or another - however I do not know what happens if the phone fails to accept one. Does it fall back to a hardware level carrier policy? Does it only leave out the specific confseq that was tampered with? Does it stop the modem from booting up at all?
Theres the cfg.db file along with its cfg.sha2 signature file - that would be my first point of try for remapping and editing via magisk... no idea wether the sha2 signature matters and what happens if it doesnt match.
It is a simple sqlite database:
1) you can look at the confnames table to identify the sequences per carrier
2) refer to the confmap table to see which carrier_id from the previous table responds to the confman hash
3) there are a load of confman_* tables, each of which includes the list of confseq files from the confseq folder - these confseq files have their corresponding names in their file headers - LTE CA carrier policies, NRDC carrier policies, mobile network based carrier policies, they all get added together in a sequence and all of them share most of the confseq files (the carrier specific ones are the ones that differ)
so what you can try, is, assuming you're on a "unsupported network", refer to the wildcard profile - this has the carrier_id of 0, which uses confman_43f507494f63c42cbf1aba626685b29710cd90eb as its table - the 10th one in order corresponds to the wildcard.sim1 confseq file which you can try an replace with one from another carrier (I've made a list of them https://paste.ee/p/NVju0)
the hashes also change by every modem release
Here is the sequence for wildcard and Orange Spain as an example:
default.common
suclr_big_data_cc_num.common
lte_ca_common
lte_ca_0.common
lte_ca_1.common
endc_nr_ca_common.common
default.sim1
endc_nr_ca_common_manual.sim1
endc_nr_ca_common.sim1
wildcard.sim1
default.sim2
endc_nr_ca_common_manual.sim2
endc_nr_ca_common.sim2
wildcard.sim2
default.multislotdefault.common
suclr_big_data_cc_num.common
lte_ca_common
lte_ca_0.common
lte_ca_1.common
endc_nr_ca_common.common
eu_common.common
default.sim1
endc_nr_ca_common_manual.sim1
endc_nr_ca_common.sim1
eu_common.sim1
eu_nr_common.sim1
es_orange.sim1
default.sim2
endc_nr_ca_common_manual.sim2
endc_nr_ca_common.sim2
eu_common.sim2
eu_nr_common.sim2
es_orange.sim2
default.multislot
eu_common.multislot
es_orange.multislot
Edit: nvm, didnt read the footer of your post
tauio111 said:
Did you edit the confseq files? What exactly did you edit, they are binary blobs. I also believe they are signed in one way or another - however I do not know what happens if the phone fails to accept one. Does it fall back to a hardware level carrier policy? Does it only leave out the specific confseq that was tampered with? Does it stop the modem from booting up at all?
Theres the cfg.db file along with its cfg.sha2 signature file - that would be my first point of try for remapping and editing via magisk... no idea wether the sha2 signature matters and what happens if it doesnt match.
It is a simple sqlite database:
1) you can look at the confnames table to identify the sequences per carrier
2) refer to the confmap table to see which carrier_id from the previous table responds to the confman hash
3) there are a load of confman_* tables, each of which includes the list of confseq files from the confseq folder - these confseq files have their corresponding names in their file headers - LTE CA carrier policies, NRDC carrier policies, mobile network based carrier policies, they all get added together in a sequence and all of them share most of the confseq files (the carrier specific ones are the ones that differ)
so what you can try, is, assuming you're on a "unsupported network", refer to the wildcard profile - this has the carrier_id of 0, which uses confman_43f507494f63c42cbf1aba626685b29710cd90eb as its table - the 10th one in order corresponds to the wildcard.sim1 confseq file which you can try an replace with one from another carrier (I've made a list of them https://paste.ee/p/NVju0)
the hashes also change by every modem release
Here is the sequence for wildcard and Orange Spain as an example:
default.common
suclr_big_data_cc_num.common
lte_ca_common
lte_ca_0.common
lte_ca_1.common
endc_nr_ca_common.common
default.sim1
endc_nr_ca_common_manual.sim1
endc_nr_ca_common.sim1
wildcard.sim1
default.sim2
endc_nr_ca_common_manual.sim2
endc_nr_ca_common.sim2
wildcard.sim2
default.multislotdefault.common
suclr_big_data_cc_num.common
lte_ca_common
lte_ca_0.common
lte_ca_1.common
endc_nr_ca_common.common
eu_common.common
default.sim1
endc_nr_ca_common_manual.sim1
endc_nr_ca_common.sim1
eu_common.sim1
eu_nr_common.sim1
es_orange.sim1
default.sim2
endc_nr_ca_common_manual.sim2
endc_nr_ca_common.sim2
eu_common.sim2
eu_nr_common.sim2
es_orange.sim2
default.multislot
eu_common.multislot
es_orange.multislot
Edit: nvm, didnt read the footer of your post
Click to expand...
Click to collapse
Woow you started middle of the book.
These carrierconfig part another story in the /vendor.
I didn't touch this confseq files because as you say these look like certificated. Also yes they are binary.
First /product/carriersettings section seems easy to touch for me.
Why I started this part you know some files coming in /data/user_de/0/com.android.phone/files when insert a sim card it's name like carrierconfig-com.google.android.carrier-899002....xml this is simple xml file that contains carrier parameters.
I started to try edit this file for a while. And Really ıf I change some thing wrong It directly affects the modem operation.
Seeing the same parameters in pb files in carriersettings, I thought I could edit them.
This is the story.
The next first I will try build a magisk module I will try to mount in hex base edited pb file
After that I will start to dig into these confseq binaries. Thank you for respond.
furkanosman said:
Why I started this part you know some files coming in /data/user_de/0/com.android.phone/files when insert a sim card it's name like carrierconfig-com.google.android.carrier-899002....xml this is simple xml file that contains carrier parameters.
I started to try edit this file for a while. And Really ıf I change some thing wrong It directly affects the modem operation.
Click to expand...
Click to collapse
I just copy and paste the xml values every time, its persistent until you enter a different sim or update android.
I think it would be more viable to make a magisk script that adds the part you want to the front of the xml instead of replacing the bp files.
furkanosman said:
Woow you started middle of the book.
These carrierconfig part another story in the /vendor.
I didn't touch this confseq files because as you say these look like certificated. Also yes they are binary.
First /product/carriersettings section seems easy to touch for me.
Why I started this part you know some files coming in /data/user_de/0/com.android.phone/files when insert a sim card it's name like carrierconfig-com.google.android.carrier-899002....xml this is simple xml file that contains carrier parameters.
I started to try edit this file for a while. And Really ıf I change some thing wrong It directly affects the modem operation.
Seeing the same parameters in pb files in carriersettings, I thought I could edit them.
This is the story.
The next first I will try build a magisk module I will try to mount in hex base edited pb file
After that I will start to dig into these confseq binaries. Thank you for respond.
Click to expand...
Click to collapse
Hi
Did u manage to work on the pb files in /product
I tried the cfg method but my ims registration isn't changing