Related
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
START ROOT EXPLORER
go to system
press r/o button you must see r/w
open the file build.prop with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone.. 2 times...
conect to pc companion
to obtain root access
go to: http://forum.xda-developers.com/showthread.php?t=824788
download adb and superoneclickv1.apk
replace the content of superoneclick folder with adb
in your phone go to config, aplications, development and select usb depuration mode
conect your phone with the pc and start superoneclick then see how its work, if stuck or the software dont work in one step select and deselect USB depuration mode repeteadly 2 times.
maybe you need to try many times
sudenly it will work, then go to:
http://forum.xda-developers.com/showpost.php?p=7827223&postcount=88
and folow steps to correct your keyboard
you can see what layout works for you
Check the folder Layouts inside the keyboard-config folder open each file and see how was the layout then replace like the example in the post
boilaa
work flawless, i can play angry birds, the icons see like compressed but the game works very good,
some minor changes like more colors and darker interfase, i see the photos a little better and the video has autofocus..
my android market dont want to work but after few configurations like enable non secure apk i can instal all good
few more widgets: market, on off conections and things, small views for webs, data traffic and youtube
and facebook update photos with contacts
when you select an user you can send email and do other things
pablo lara melcher said:
work flawless, i can play angry birds, the icons see like compressed but the game works very good,
some minor changes like more colors and darker interfase, i see the photos a little better and the video has autofocus..
my android market dont want to work but after few configurations like enable non secure apk i can instal all good
few more widgets: market, on off conections and things, small views for webs, data traffic and youtube
and facebook update photos with contacts
when you select an user you can send email and do other things
Click to expand...
Click to collapse
Really the video has autofocus ??? Fantastic ! And what about the menu of the camera options ? it's the same? Other improvements?
Thank you very much, it's really work!
Now we need to find out how to fix they keyboard ... as I ended up with scandinavian layout.
I have same problem .. well, not scadinavian, but german .. obviously. Everything else is working just perfect. Even localisation is fine.
Lweek said:
I have same problem .. well, not scadinavian, but german .. obviously. Everything else is working just perfect. Even localisation is fine.
Click to expand...
Click to collapse
Scandinavian for sure not german. My phone has German physical layout, I would have loved to have a german layout. But this update has letters as "a med ring" and is definitely a QWERTY and not german QWERTZ.
I have a problem with the keyboard too. I notice some changes in the keyboard. I hope this might help you.
1. Full stop ( . ) moves to the "?" key
2. Question mark ( ? ) moves to the full stop key ( . )
3. ' mark (Sorry I don't know what-its-called) move to the letter "e" (To type ', you need to activate the blue key first)
4. Semicolon ( ; ) moves to the letter "d" (To type ; , you need to activate the blue key first)
5. Comma ( , ) moves to the letter "c" (To type comma, you need to activate the blue key first)
6. Colon ( : ) moves to the "?" key (To type : , you need to activate the blue key first)
Here is how to fix they keyboard :
http://forum.xda-developers.com/showthread.php?t=824941
pablo lara melcher said:
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
open the file with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone..
conect to pc companion
boilaa
Click to expand...
Click to collapse
hi I live in uk .if I change the build prop would it effect any of my phone features example 3g connection, keyboard layout, I'm happy with the english layout.will I have english. also I use arabic language for txting does 2.1 have arabic language support.
Thanks.
i got error when rooting
Device Was Not Rooted
FAILED
hi there, i change the numbers and save the file but PC Comapanion and SEUS say "your phone is up to date", i am still with 1.6, my MINI PRO is from Claro Chile (Chilian build file)
heres is my original build.prop (for future use if anyone need the build number from Chile)
Code:
##### Final patch of properties #####
ro.build.product=SonyEricssonU20a
ro.build.description=U20a-user 1.6 1.2.A.1.181 413 test-keys
ro.build.display.id=1.2.A.1.181
ro.product.brand=SEMC
ro.product.name=U20a_1239-0006
ro.product.device=SonyEricssonU20a
ro.product.board=delta
ro.build.version.incremental=9
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/U20a_1239-0006/SonyEricssonU20a/delta:1.6/1.2.A.1.181/9:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1239-0006
ro.semc.version.cust_revision=R12A
ro.semc.ecclist.num=1
ro.semc.ecclist.type.0=Police
ro.semc.ecclist.number.0=133
ro.semc.ecclist.plmn.0=730 03F
ro.semc.max_digits_match=8
ro.voicemail.dialing-number=*20
ro.semc.disableSPN=false
ro.semc.enable.fast_dormancy=true
#########################################################################
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.semc.content.number=PA8
################# Updating of the SW Version #################
ro.semc.version.fs_revision=1.2.A.1.181
ro.build.id=1.2.A.1.181
##### Values from product package metadata #####
ro.product.model=U20a
ro.semc.ms_type_id=AAD-3880071-BV
ro.semc.version.fs=WORLD-1-2-5
ro.semc.product.name=X10 mini pro
# begin build properties
# autogenerated by buildinfo.sh
#ro.build.id=1.2.A.1.181
#ro.build.display.id=1.2.A.1.181
#ro.build.version.incremental=413
ro.build.version.sdk=4
ro.build.version.codename=REL
ro.build.version.release=1.6
ro.build.date=Fri Jul 2 13:25:20 2010
ro.build.date.utc=1278069920
ro.build.type=user
ro.build.user=SEMCUser
ro.build.host=SEMCHost
#ro.build.tags=test-keys
#ro.product.model=mimmi
#ro.product.brand=generic
#ro.product.name=mimmi
#ro.product.device=mimmi
#ro.product.board=mimmi
ro.product.cpu.abi=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
#ro.build.product=mimmi
# Do not try to parse ro.build.description or .fingerprint
#ro.build.description=mimmi-user 1.6 1.2.A.1.181 413 test-keys
#ro.build.fingerprint=generic/mimmi/mimmi/mimmi:1.6/1.2.A.1.181/413:user/test-keys
# end build properties
#
# system.prop for mimmi
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
wifi.interface = tiwlan0
ro.semc.fm_service=1
ro.semc.def_screen_orientation=sensor
ro.semc.timescape_keys=X10_mini_pro_key
ro.sf.lcd_density=120
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.cust.tel.eons=1
persist.ro.ril.sms_sync_sending=1
DEVICE_PROVISIONED=1
# Constant values for Battery test in Service menu.
ro.semc.batt.capacity=950
ro.semc.batt.test.consumption=150
ro.semc.batt.test.z_threshold=50
ro.semc.batt.test.min_level=60
ro.qualcomm.proprietary_obex=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
#ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.yt=android-sonyericsson
ro.com.google.clientidbase.am=android-sonyericsson
ro.com.google.clientidbase.vs=android-sonyericsson
ro.com.google.clientidbase.gmm=android-sonyericsson
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gms_preload_version=1.6_r16
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
ro.drm.whitelist.num=4
ro.drm.whitelist.domain.0=roap.drm.coremedia.com
ro.drm.whitelist.domain.1=.teslan.com
ro.drm.whitelist.domain.2=selddrmt02.teslan.com
ro.drm.whitelist.domain.3=.inovatel.com
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#ro.semc.version.fs_revision=1.2.A.1.181
pablo lara melcher said:
here is a mini guide:
what`s you need:
1. a root phone
2. root explorer installed
3. go to system/build.prop
open the file with a text editor (long pressover the file)
replace your buil.prop number with 1238-8536 what`s a german number (i think is in tree places)
shutdown and start you phone..
conect to pc companion
NEW:
to obtain root access
go to: http://forum.xda-developers.com/showthread.php?t=824788
download adb and superoneclickv1.apk
replace the content of superoneclick folder with adb
in your phone go to config, aplications, development and select usb depuration mode
conect your phone with the pc and start superoneclick then see how its work, if stuck in one step select and deselect USB depuration mode repeteadly
sudenly it will work, then go to:
http://forum.xda-developers.com/showpost.php?p=7827223&postcount=88
and folow steps to correct your keyboard
you can see what layout works for you
Check the folder Layouts inside the keyboard-config folder open each file and see how was the layout then replace like the example in the post
boilaa
Click to expand...
Click to collapse
Hi
Thanks for the guide....
I have problem to save build.prop file. it says the file is read only. I have rooted my phone and have done exactly like you decription. what to do???
rehan_i said:
Hi
Thanks for the guide....
I have problem to save build.prop file. it says the file is read only. I have rooted my phone and have done exactly like you decription. what to do???
Click to expand...
Click to collapse
Mount your file system as read/write in Root explorer.
Does this only work with pro?
Hello
I have a x10 mini (NOT A MINI PRO!), would this guide / fw work?
I've heard that this only works with mini PRO, is that correct?
Thanks
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
Model No. U20i
Firmware Version: 1.6
Kernel version: 2.6.29
Build No. 1.1.A.0.8
EDIT: I have a mini pro if it wasn't clear.
Exactly same situation here....
I cant seem to find NORDIC firmware for x10mini (not pro)
Skeldave said:
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Skeldave said:
Hi, mine says 'You already have the latest software' when i try and update with pc companion. I have a rooted phone, ive edited the build.prop, ive restarted the phone, ive connected it via usb and click on the 'support zone' and then on update. This is when it gives me the error.
As far as i know i have a UK phone.
Any help is appreciated, thanks.
EDIT: I have a mini pro if it wasn't clear.
Click to expand...
Click to collapse
Mine is an x10 mini
Exact same here. My phone was bought in Ireland, but I assume it's a UK handset.
btw u should state many people dont know...
when u in root explorer go to system and click mounted r/w
ok, enough is enough.
i can't wait any longer and i'm going to try this. it's no german number for sure, 'cause i got german-unbranded mini pro and no update is available.
Because sometime, somehow, the offical german update is coming out, i have following question:
when i want to flash the "right" 2.1 to my phone, do i only need to root it again (as i read its possible with 2.1) and change the number back to my default one, start Companion/SEUS and do a reset/repair? is it then going to download the german update, that war originally thought to be on this phone?
edit: oh well, doesnt work for me at all with the changed number. so, nevermind my question - like you allready did
edit: was about to give up, then it worked. changed all the numbers, not just the first appearing
I would like this thread dedicated to simply working through suggestions and trials to get this working. I went ahead and reverted to 4.2, rooted, and then upgraded to 4.4 again, so I'm rooted on KK now. I did some digging, compared to CM11 and some research from the android development site.
Here's what I've done and the results:
1)
Found the system\etc\nfc folder on the d800 ROM 4.4
Here's what's in the config:
<?xml version="1.0" encoding="EUC-KR" standalone="no" ?>
<Configure>
<Config operator="" country="" device="">
<!-- INITVALUE, three_toggleV1L, three_toggleV2L, three_toggleV2C, two_toggleN, two_toggleL -->
<!-- three_toggleV1L_tonedown, three_toggleV2L_tonedown, three_toggleV2C_tonedown, two_toggleN_tonedown, two_toggleL_tonedown -->
<IndicatorType> two_toggleN </IndicatorType>
<IndicatorType TargetModel="zee"> two_toggleN_tonedown </IndicatorType>
<!-- INITVALUE, usevibrate, onlyndefdiscovered -->
<RingSoundScenarioType> INITVALUE </RingSoundScenarioType>
<!-- INITVALUE, stay, update -->
<WCScenarioEnable> INITVALUE </WCScenarioEnable>
<!-- INITVALUE, icsjb -->
<OSComparabilityType> INITVALUE </OSComparabilityType>
<!-- INITVALUE, uicc, ese -->
<SecureElementType> uicc </SecureElementType>
<!--INITVALUE, googlenative, directbeam, directbeam_mtkbt, mtkbt, WPSHandover, autoapplaunch (overlap possible (divide "," sign)) -->
<HandoverSupportType> googlenative </HandoverSupportType>
<!-- INITVALUE, off, offp2p, oncardrwp2p, oncard, oncardrw, oncardp2p, onrwp2p, open -->
<DefaultOnOffType> oncardrwp2p </DefaultOnOffType>
<!-- INITVALUE, vzw, gsma -->
<PopupDialogType> gsma </PopupDialogType>
<!-- INITVALUE, all, rwp2p -->
<PowerSaveType> INITVALUE </PowerSaveType>
<!-- INITVALUE, egw, gw, st, egwst, gwst -->
<SupportWalletType> INITVALUE </SupportWalletType>
<!--apply Access Control routine, verifying access right to the apk through Access Control Manager-->
<AccessControlEnable> true </AccessControlEnable> <!-- default value is true -->
<TransactionAIDEnable> false </TransactionAIDEnable>
<!--apply Execution Environment routing according to screen state
in SCREEN_LOCK/SCREEN_OFF, card mode is disabled.
this feature has dependency with isis/sequent wallet.-->
<NfcEERoutingEnable> false </NfcEERoutingEnable>
<DisableInPowerOffEnable> false </DisableInPowerOffEnable>
<!--control feasibility of CE mode in Low power mode (after power-off)
if 'true', card emulation mode is still available even after the phone is powered-off.
if 'false', card emulation doesn't work anymore until the phone is powered-up again.-->
<CardEnableInPowerOff> true </CardEnableInPowerOff> <!-- default value is true -->
<!--extracts card mode activation process from initialization process during init/de-init process,
card mode is not controlled separately. card mode enabler looses card mode control.
so far, google wallet only needs this feature-->
<AsyncCardControlEnable> true </AsyncCardControlEnable>
<!--MUST BE APPLIED to all LGE NFC devices-->
<VendorStablePatch> true </VendorStablePatch> <!-- default value is true -->
<!--P2P receive function enabled/disabled together with RW enabled/disabled
google scenario is, NDEF push and get are controlled seperately.
so, "true" shoud be strongly recommended except for specific scenario-->
<RwP2pServerSyncEnable> true </RwP2pServerSyncEnable> <!-- default value is true -->
<!--this feature is for beam ui finish when alart UI(Calling, Alarm etc..)-->
<BeamUIFinishwhenAlertUIView> true </BeamUIFinishwhenAlertUIView> <!-- default value is true -->
<!--enable se-broadcasting only for NFC-permitted(NFC_PERM) applications
this feature came from ISIS requirement. so, the model requiring ISIS certi, should apply this feature-->
<PermittedSeBroadcastEnable> true </PermittedSeBroadcastEnable> <!-- default value is true -->
<!--NFC Empty Tag popup Dialog Scenario for ORG when Positve/Negative Detection,
PopupDialog will be display and offer link to play store-->
<EmptyPopupSupport> false </EmptyPopupSupport>
<!--Lock Screen Polling Enable Feature.-->
<LockScreenPollingEnable> false </LockScreenPollingEnable>
<NotifyonlyValidTag> true </NotifyonlyValidTag> <!-- default value is true -->
<SePatchEnabled> false </SePatchEnabled>
<TagLongTimePopupSupport> false </TagLongTimePopupSupport>
<!-- feature for nxp stack library -->
<!-- determine which HCI event type is supported INITVALUE, rffieldoff (EVT_FIELD_ON/OFF events not supported) -->
<HCIEventConfig> INITVALUE </HCIEventConfig>
<!-- apply volatile card configuration -->
<VolatileCardModeEnable> false </VolatileCardModeEnable>
<!-- B' type among UICC CE types is enable/disable -->
<UICCBPrimeEnable> false </UICCBPrimeEnable>
</Config>
</Configure>
I changed this from false to true
<AsyncCardControlEnable> true </AsyncCardControlEnable>
I rebooted, and nothing, Google wallet still said it wasn't supported.
2)
On the android dev site, I found that android.hardware.nfc.hce.xml is required for tap to pay to work, so I checked a CM11 ROM and found it, but it was missing from the LG ROM so I then copied it to the system\etc\permissions folder, set proper permissions and rebooted.
Checked Wallet and BOOM, Tap and Pay available, so I activated it. When I went to lunch, I stopped by a store and tried it and NOTHING. Very sad There's also no settings GUI to configure it like AOSP has, but Google Wallet shows it activated.
3) Found the config_US.xml in the system\etc\nfc folder on the LG ROM:
<?xml version="1.0" encoding="EUC-KR" standalone="no" ?>
<Configure>
<!-- AT&T / United States -->
<!-- T-Mobile / United States -->
<Config operator="" country="US" device="">
</Config>
<!-- Sprint / United States -->
<Config operator="SPR" country="US" device="">
<SecureElementType> ese </SecureElementType>
<AccessControlEnable> true </AccessControlEnable>
<PermittedSeBroadcastEnable> true </PermittedSeBroadcastEnable>
</Config>
<!-- Verizon / United States -->
<Config operator="VZW" country="US" device="">
<WCScenarioEnable> update </WCScenarioEnable>
<DefaultOnOffType> offp2p </DefaultOnOffType>
<RingSoundScenarioType> usevibrate </RingSoundScenarioType>
<PopupDialogType> vzw </PopupDialogType>
<NfcEERoutingEnable> true </NfcEERoutingEnable>
</Config>
</Configure>
Did not change anything here, but I'm thinking that Sprint has a config probably to enable tap to pay while ATT/TMO do not. Verizon obviously has something going on there too.
I'm going to change the config from SPR to ATT and see what happens.
Any other ideas?
Okay after the last change, here's what I got:
See Attached
But when I press it, I get a settings FC.
Here's the logcat from when the settings FC:
[ 02-28 15:27:26.055 953: 1554 I/ActivityManager ]
START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.nfc.aymentSettingsActivity} from pid 9568
[ 02-28 15:27:26.055 9568: 9568 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.lge.settings.easy, PID: 9568
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings/com.android.settings.nfc.aymentSettingsActivity}; have you declared this activity in your AndroidManifest.xml?
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1628)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1424)
at android.app.Activity.startActivityForResult(Activity.java:3468)
at android.app.Activity.startActivityForResult(Activity.java:3429)
at android.app.Activity.startActivity(Activity.java:3671)
at android.app.Activity.startActivity(Activity.java:3639)
at android.preference.Preference.performClick(Preference.java:970)
at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:215)
at android.widget.AdapterView.performItemClick(AdapterView.java:299)
at android.widget.AbsListView.performItemClick(AbsListView.java:1158)
at android.widget.AbsListView$PerformClick.run(AbsListView.java:2957)
at android.widget.AbsListView$3.run(AbsListView.java:3849)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5105)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
at dalvik.system.NativeStart.main(Native Method)
So the D800 wallet fix works on the D801 but 2 of the files are already in the T-Mobile D801 firmware, and actually one doesn't have the T-Mobile Isis entry, so I'm guessing Isis will stop working if the fix is applied. If someone doesn't want to reflash and is already rooted, in addition to changing the entry in the OP they have to:
Switch settings to list view so that it doesn't crash when opening the Tap & Pay option
Copy android.hardware.nfc.hce.xml from the D800 fix to /system/etc/permissions (I used ES file explorer)
I can't find the D800 wallet fix post to link to it. Not sure if it was removed. This is the thread.
Thanks to AndroidUser00110001 for his Wallet fix.
His fix got it to show up but actually mine above does the same and you can access from list view. But it won't accept a paypass tap ?. It does work on his international Rom for the d800.
Sent from my LG-D800 using Tapatalk
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings/com.android.settings.nfc.aymentSettingsActivity}; have you declared this activity in your AndroidManifest.xml?
have you checked the manifest for anything?
Manifest is part of the app itself before it's compiled. I don't think it's an app issue, but the app looking for the correct script to proceed.
Sent from my LG-D800 using Tapatalk
Appreciate ya'll looking into this very much!
Any news on this?
Sent from my LG-D801 using Tapatalk
I've looked everywhere I could think to get it working...no luck. Works great on international Rom though.
Sent from my LG-D800 using Tapatalk
Weird that it's on the vs980 update
Sent from my LG-VS980 using Tapatalk
aren't Google or LG coming up with an implementation this.?
Sent from my LG-D801 using Tapatalk
Just an update, this is now available via FOTA through ATT
Sent from my Nexus 7 using Tapatalk
Ghstudent said:
Just an update, this is now available via FOTA through ATT
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Wait so AT&T added this functionality back through an update or what? Did they buckle to pressure or did people figure out how to get it added back in?
ftblstr2319 said:
Wait so AT&T added this functionality back through an update or what? Did they buckle to Purdue out did people figure out how to get it added back in?
Click to expand...
Click to collapse
AT&T just released via OTA. Go to your system updates and it will be waiting on you, it's a 6 MB update.
Sent from my LG-D800 using Tapatalk
Ghstudent said:
AT&T just released via OTA. Go to your system updates and it will be waiting on you, it's a 6 MB update.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
I think they buckled from pressure from someone..el goog?
I'm on tmobile so I hope either someone can take the fix from att and apply it to tmo or tmobile buckles too
Can someone make it work for tmo?
Sent from my LG-D801 using Tapatalk
gegerva said:
Can someone make it work for tmo?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Anyone have a flashable zip version of the AT&T Google Wallet update? I'm sure we can extract those files to get TMO G2 work with Google Wallet.
paqmaster said:
Anyone have a flashable zip version of the AT&T Google Wallet update? I'm sure we can extract those files to get TMO G2 work with Google Wallet.
Click to expand...
Click to collapse
I swear I read in a post that if you flash the ATT one, it works. Don't take my word for it though. Can anyone chime in?
I still haven't flashed 4.4 yet. If this works, it would probably push me over the edge.
Is there an available zip?
Sent from my LG-D801 using Tapatalk
Hi,
First of all, I'm sorry if this isn't the section to post this question.
I backed up my SMS using Super Backup and I restored them after flashing a new rom.
All incomming text message shows as December 31st 1969 7PM (and all emoji are wierd).
I openned up the xml file to modify the phone number format a week ago and restored it, so maybe this is the issue.
Here is a sample:
Code:
<sms address="+1 555-555-1234" time="Jul 8, 2015 12:48:58 AM" date="1436330938572" type="1" body="incoming msg here" read="1" service_center="+14382762000" name="John Doe" />
<sms address="+1 555-555-1234" time="Jul 8, 2015 2:38:11 AM" date="1436337491359" type="2" body=Walala text here and there from me" read="1" service_center="" name="John Doe" />
What is the issue? I don't know if it's my sms app, cm12 bug, charset mistake...
Your help would be great!
Thanks !
Hey guys,
last week I disabled some Apps on my rooted OnePlus 5. Today in the morning, I needed to reboot the phone and then it happened. The phone hangs in a boot-loop. While booting, the red cycling OnePlus logo appears. After that I see very short the keys to type my code for the SIM card. Then, again the red cycling OnePlus logo.
Ok, ****... whats happens?
I think I disabled some wrong app. But which? I booted into the TWRP Recovery, start adb shell and have a look.
My thought was to enable all Apps with "pm" (PackageManager), but it isn't working in the TWRP Recovery Terminal:
Code:
CANNOT LINK EXECUTABLE "app_process": cannot locate symbol "_ZN7android14IPCThreadState11setBlockUidEib" referenced by "/system/lib64/libandroid_runtime.so"...
Aborted
I searched for some options to enable or disable an app. But I found only this from user arana1: https://forum.xda-developers.com/showpost.php?p=46287590&postcount=15
I also found a Java exception in /data/system/dropbox. There are many boot failure files:
Code:
/data/system/dropbox # ls -al
..
..
-rw------- 1 system system 1843 Dec 6 18:16 [email protected]_16_09_077.txt
-rw------- 1 system system 1843 Dec 6 18:16 [email protected]_16_19_819.txt
-rw------- 1 system system 1843 Dec 6 18:16 [email protected]_16_30_883.txt
-rw------- 1 system system 1843 Dec 6 18:16 [email protected]_16_41_800.txt
-rw------- 1 system system 1843 Dec 6 18:16 [email protected]_16_52_650.txt
-rw------- 1 system system 1843 Dec 6 18:17 [email protected]_17_03_520.txt
The content of the files are:
Code:
Process: system_server
Subject: SystemServer
Build: OnePlus/OnePlus5/OnePlus5:7.1.1/NMF26X/10171617:user/release-keys
android.util.Log$TerribleFailure: BOOT FAILURE Notifying Location Service running
at android.util.Log.wtf(Log.java:295)
at android.util.Slog.wtf(Slog.java:116)
at com.android.server.SystemServer.reportWtf(SystemServer.java:374)
at com.android.server.SystemServer.-wrap0(SystemServer.java)
at com.android.server.SystemServer$2.run(SystemServer.java:1524)
at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:14993)
at com.android.server.SystemServer.startOtherServices(SystemServer.java:1446)
at com.android.server.SystemServer.run(SystemServer.java:353)
at com.android.server.SystemServer.main(SystemServer.java:238)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
Caused by: java.lang.IllegalStateException: Unable to find a fused location provider that is in the system partition with version 0 and signed with the platform certificate. Such a package is
needed to provide a default fused location provider in the event that no other fused location provider has been installed or is currently available. For example, coreOnly boot mode when decry
pting the data partition. The fallback must also be marked coreApp="true" in the manifest
at com.android.server.LocationManagerService.ensureFallbackFusedProviderPresentLocked(LocationManagerService.java:572)
at com.android.server.LocationManagerService.loadProvidersLocked(LocationManagerService.java:620)
at com.android.server.LocationManagerService.systemRunning(LocationManagerService.java:358)
at com.android.server.SystemServer$2.run(SystemServer.java:1522)
... 7 more
There you can see that android? can't find a "fused location provider". I'm to 90% sure that I disabled this app.
I found this, but I don't know how to use this or where it writes something:
https://developer.android.com/refer...ionEnabledSetting(java.lang.String, int, int)
Do you guys know how to enable a app in the /data partition without the package manager "pm"? Maybe editing some files?
I found the solution.
I disabled some app at my old android device with "pm disable <app>" and searched for modified files in the last one minute:
Code:
# find /system -mmin -1
I found this file:
Code:
/data/system/users/0/package-restrictions.xml
Search for the app "com.android.location.fused" in the file and found this line:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" enabled="3" enabledCaller="shell:0" />
Deleted the enabled and enabledCaller attribute:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" />
Saved the file and successfully rebooted the phone! Yeah!
Thanks to user Marc.2377 at Stackoverflow for the hint to delete this both attributes.
That definitely what i call an autonoumous man
thanks, it also worked for j1m galaxy
Thanks so much!
I've been trying for hours to activate adb during boot before /data decryption and a bunch of other stuff.
You're a hero!
You definitely saved my life!
dickdickerson said:
I found the solution.
I disabled some app at my old android device with "pm disable <app>" and searched for modified files in the last one minute:
Code:
# find /system -mmin -1
I found this file:
Code:
/data/system/users/0/package-restrictions.xml
Search for the app "com.android.location.fused" in the file and found this line:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" enabled="3" enabledCaller="shell:0" />
Deleted the enabled and enabledCaller attribute:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" />
Saved the file and successfully rebooted the phone! Yeah!
Click to expand...
Click to collapse
Your solution worked like a charm! For my part, the package-restrictions.xml was a little bit different, I had to replace that piece of code:
Code:
<pkg name="com.android.location.fused" ceDataInode="1223">
<disabled-components>
<item name="com.android.location.fused.FusedLocationService" />
</disabled-components>
</pkg>
with this one:
Code:
<pkg name="com.android.location.fused" ceDataInode="1223">
<enabled-components>
<item name="com.android.location.fused.FusedLocationService" />
</enabled-components>
</pkg>
(replaced "disabled-component" node with "enabled-component").
Then that's it. Back to business with all my data kept!
Thanks again!
saved my ass! Xiaomi Redmi Note 7
I disabled the miaccount or micloud services and couldn't log into the phone because of it's inbuild security system.
I had the RPC error trying to reactivate the phone.
This solution worked out like a charm for me. Same steps. Thank you!
dickdickerson said:
I found the solution.
I disabled some app at my old android device with "pm disable <app>" and searched for modified files in the last one minute:
Code:
# find /system -mmin -1
I found this file:
Code:
/data/system/users/0/package-restrictions.xml
Search for the app "com.android.location.fused" in the file and found this line:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" enabled="3" enabledCaller="shell:0" />
Deleted the enabled and enabledCaller attribute:
Code:
<pkg name="com.android.location.fused" ceDataInode="2101300" />
Saved the file and successfully rebooted the phone! Yeah!
Thanks to user Marc.2377 at Stackoverflow for the hint to delete this both attributes.
Click to expand...
Click to collapse
Man you saved my ass.
I disabled MI Account (com.xiaomi.account) and got locked out of the device asking to unlock by entering xiaomi account password, but I could not enable by entering the password cause I had the ****ing application disabled.
Respect for you, bruh...
This needs to go in a "so you pwn3d yourself n00b" FAQ somewhere. (Even though I've been doing this for years... )
You saved me an EDL mode flash, thank you sir.
dickdickerson said:
I found the solution.
Click to expand...
Click to collapse
You're a fckn lifesaver. Thanks so much. I really hope someone turns this into a update.zip that can be flashed or a windows script that works on recovery adb
Hello,
I'm new member and new user of Samsung phone. Samsung Galaxy S9 Note is good but have one feature that I can't understand.
My operator: PLUS GSM (Poland), Phone with PLS Software installed.
MMS messages don't come in and come out if I manually turn on data transfer. On my last phone (Huaweii 5X) it worked without additional switching on and off data transfer. I don't want to have data transfer enabled all the time just for MMS. For me this doesn't have any reason to work like that. It's insecure, uses data transfer, many notifications comes to phone, battery is used without reason. That's the main reasons for what I want to change that behaviour of the phone.
Below is what I have found out. If You have another soultion or additional info please write
I made some research and found that one csc feature could be fixing this:
<CscFeature_RIL_ForceConnectMMS>TRUE</CscFeature_RIL_ForceConnectMMS>
But it needs to be changed That the tricky part.
As I know there are two solutions to achieve that:
1. Root phone and change that flag
2. Flash the software with that flag
I don't want to root phone to keep the varranty so for me the second solution is possible to do.
1. I downloaded firmware XEO-N960FXXS2ARL3-20181217161350
2. Unpacked ZIP:
AP_N960FXXS2ARL3_CL14366801_QB20913375_REV00_user_low_ship_meta.tar.md5
BL_N960FXXS2ARL3_CL14366801_QB20913375_REV00_user_low_ship.tar.md5
CP_N960FXXU2ARL2_CP11352558_CL14366801_QB20913375_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM2ARK2_CL14366801_QB20490073_REV00_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N960FOXM2ARK2_CL14366801_QB20490073_REV00_user_low_ship.tar.md5
3. Unpacked CSC_OMC_OXM_N960FOXM2ARK2_CL14366801_QB20490073_REV00_user_low_ship.tar.md5 with tool from that topic: https://forum.xda-developers.com/showpost.php?p=11164008&postcount=1
cache.img.lz4
CROWNLTE_EUR_OPEN.pit
hidden.img.lz4
odm.img.lz4
omr.img.lz4
3. Unpacked odm.img.lz4 with https://github.com/lz4/lz4/releases (lz4.exe -d inputfile outputfile) to file odm.img
4. Unpacked odm.img to odm.ext4.img with http://androidtutorials2014.blogspot.com/2015/06/windows-how-to-unpack-img-files-eg.html# (sgs2toext4)
5. Mount that img as read/write with https://www.osforensics.com/tools/mount-disk-images.html (OSFMount) with letter E
6. Went to E:\omc\XEO\conf
apps_NW00958.xml
cscfeature.xml
cscfeature_network.xml
customer.xml
default_application_order.xml
default_workspace.xml
omc.info
7. cscfeature.xml and cscfeature_network.xml are encrypted so.... need to decrypt with omc-decoder.jar or https://forum.xda-developers.com/android/software/decode-encode-omc-files-omc-decoder-t3791471
cscfeature.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<SamsungMobileFeature>
<Version>ED00005</Version>
<Country>POLAND</Country>
<CountryISO>PL</CountryISO>
<SalesCode>XEO</SalesCode>
<FeatureSet>
<CscFeature_Common_AutoConfigurationType>NO_DFLT_CSC, SIMBASED_OMC</CscFeature_Common_AutoConfigurationType>
<CscFeature_Common_ConfigAllowedPackagesDuringDataSaving>com.samsung.android.smartcallprovider</CscFeature_Common_ConfigAllowedPackagesDuringDataSaving>
<CscFeature_Common_ConfigEmergencyModePackages>com.ipsec.service,com.sec.android.providers.iwlansettings,com.sec.android.providers.mapcon</CscFeature_Common_ConfigEmergencyModePackages>
<CscFeature_Common_ConfigSvcProviderForUnknownNumber>whitepages,whitepages,whitepages</CscFeature_Common_ConfigSvcProviderForUnknownNumber>
<CscFeature_Common_EulaVersion>2</CscFeature_Common_EulaVersion>
<CscFeature_GMS_SetClientIDBaseMs>android-samsung-gn-rev1</CscFeature_GMS_SetClientIDBaseMs>
<CscFeature_LockScreen_ConfigClockDisplayPolicy>IgnoreNationalRoamingWithoutMNC</CscFeature_LockScreen_ConfigClockDisplayPolicy>
<CscFeature_Message_ConfigFreeMessage>off</CscFeature_Message_ConfigFreeMessage>
<CscFeature_Setting_EnableDataServicePopup>TRUE</CscFeature_Setting_EnableDataServicePopup>
<CscFeature_Setting_IncludeApn4SwUpdate>TRUE</CscFeature_Setting_IncludeApn4SwUpdate>
<CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>TRUE</CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>
<CscFeature_SmartPage_ConfigLocalization>*EU4,+Upday</CscFeature_SmartPage_ConfigLocalization>
<CscFeature_SystemUI_ConfigOverrideDataIcon>LTE</CscFeature_SystemUI_ConfigOverrideDataIcon>
<CscFeature_Vision_ConfigBeauty>NLLXX</CscFeature_Vision_ConfigBeauty>
<CscFeature_Vision_ConfigFood>NLLXX</CscFeature_Vision_ConfigFood>
<CscFeature_Vision_ConfigImageSearch>PTRXX</CscFeature_Vision_ConfigImageSearch>
<CscFeature_Vision_ConfigPlace>FSRXX</CscFeature_Vision_ConfigPlace>
<CscFeature_Vision_ConfigPlaceLandmark>SFSGO</CscFeature_Vision_ConfigPlaceLandmark>
<CscFeature_Vision_ConfigPlaceMap>GGLXX</CscFeature_Vision_ConfigPlaceMap>
<CscFeature_Vision_ConfigPlaceWeather>TWCXX</CscFeature_Vision_ConfigPlaceWeather>
<CscFeature_Vision_ConfigShopping>NLLXX</CscFeature_Vision_ConfigShopping>
<CscFeature_Vision_ConfigTextExchangerate>OANXX</CscFeature_Vision_ConfigTextExchangerate>
<CscFeature_Vision_ConfigTextTranslator>GGLXX</CscFeature_Vision_ConfigTextTranslator>
<CscFeature_Vision_ConfigWine>VVNXX</CscFeature_Vision_ConfigWine>
<CscFeature_VoiceCall_ConfigOpStyleForHdIcon>XEO_HD</CscFeature_VoiceCall_ConfigOpStyleForHdIcon>
<CscFeature_VoiceCall_SupportSettingVoWifiRegiDuringAirplaneMode>All</CscFeature_VoiceCall_SupportSettingVoWifiRegiDuringAirplaneMode>
<CscFeature_VoiceCall_SupportShowVowifiEndCall>TRUE</CscFeature_VoiceCall_SupportShowVowifiEndCall>
<CscFeature_Weather_ConfigCpType>TWC</CscFeature_Weather_ConfigCpType>
<CscFeature_Wifi_SupportSecureWifi>TRUE</CscFeature_Wifi_SupportSecureWifi>
</FeatureSet>
</SamsungMobileFeature>
cscfeature_network.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<SamsungMobileFeature>
<NetworkVersion>ED00005</NetworkVersion>
<NetworkCountry>POLAND</NetworkCountry>
<NetworkCountryISO>PL</NetworkCountryISO>
<NetworkCode>XEO</NetworkCode>
<FeatureSet>
<CscFeature_IMS_EnableEVS>TRUE</CscFeature_IMS_EnableEVS>
<CscFeature_IMS_EnableIMS>TRUE</CscFeature_IMS_EnableIMS>
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE>
<CscFeature_IMS_FrameworkVersion>6.0</CscFeature_IMS_FrameworkVersion>
<CscFeature_RIL_BlockUssdDuringVolteCall>TRUE</CscFeature_RIL_BlockUssdDuringVolteCall>
<CscFeature_RIL_CallCsVtSupport>TRUE</CscFeature_RIL_CallCsVtSupport>
<CscFeature_RIL_ConfigAlwaysOnApn>mms_26003,mms_26006,ims,xcap</CscFeature_RIL_ConfigAlwaysOnApn>
<CscFeature_RIL_ConfigDataStatus>TRUE</CscFeature_RIL_ConfigDataStatus>
<CscFeature_RIL_ConfigEpdgE911RoutingPolicy>NoService</CscFeature_RIL_ConfigEpdgE911RoutingPolicy>
<CscFeature_RIL_ConfigEpdgExtraFunction>SUPPORTWEAKSIGNALHO,ENHANCEDVOWIFI20,WFCCALLMENU</CscFeature_RIL_ConfigEpdgExtraFunction>
<CscFeature_RIL_ConfigGlobalModuleType>LTE</CscFeature_RIL_ConfigGlobalModuleType>
<CscFeature_RIL_ConfigNetworkTypeCapability>EUR-EUR-GSM-EUR</CscFeature_RIL_ConfigNetworkTypeCapability>
<CscFeature_RIL_ConfigPresetMtuSize>modem</CscFeature_RIL_ConfigPresetMtuSize>
<CscFeature_RIL_ConfigSpecialPdpFlag>im_cn</CscFeature_RIL_ConfigSpecialPdpFlag>
<CscFeature_RIL_ConfigWbamr>2G</CscFeature_RIL_ConfigWbamr>
<CscFeature_RIL_DataPrefDataTechSnapShot>TRUE</CscFeature_RIL_DataPrefDataTechSnapShot>
<CscFeature_RIL_DisplayAntennaLimited>TRUE</CscFeature_RIL_DisplayAntennaLimited>
<CscFeature_RIL_DisplayPlmnnameSimload>TRUE</CscFeature_RIL_DisplayPlmnnameSimload>
<CscFeature_RIL_E911RoutingPolicy>auto</CscFeature_RIL_E911RoutingPolicy>
<CscFeature_RIL_EnableLaunchBrowser>TRUE</CscFeature_RIL_EnableLaunchBrowser>
<CscFeature_RIL_GcfSor>TRUE</CscFeature_RIL_GcfSor>
<CscFeature_RIL_ImsPdnRetryTimeChange>FALSE</CscFeature_RIL_ImsPdnRetryTimeChange>
<CscFeature_RIL_ReferEonsWithoutLac>TRUE</CscFeature_RIL_ReferEonsWithoutLac>
<CscFeature_RIL_SetNetworkTypeWhenRadioOff>TRUE</CscFeature_RIL_SetNetworkTypeWhenRadioOff>
<CscFeature_RIL_SignalstrengthPolicy>0</CscFeature_RIL_SignalstrengthPolicy>
<CscFeature_RIL_SmsLoadShortcodeFromResourceOnly>TRUE</CscFeature_RIL_SmsLoadShortcodeFromResourceOnly>
<CscFeature_RIL_SrvccRel>10</CscFeature_RIL_SrvccRel>
<CscFeature_RIL_SsacInfoToIms>TRUE</CscFeature_RIL_SsacInfoToIms>
<CscFeature_RIL_SupportEpdg>TRUE</CscFeature_RIL_SupportEpdg>
<CscFeature_RIL_SupportEpdgOnAirplaneMode>TRUE</CscFeature_RIL_SupportEpdgOnAirplaneMode>
<CscFeature_RIL_SupportImsClirOverriding>TRUE</CscFeature_RIL_SupportImsClirOverriding>
<CscFeature_RIL_SupportImsService>TRUE</CscFeature_RIL_SupportImsService>
<CscFeature_RIL_SupportRegistrationLocationInfo>TRUE</CscFeature_RIL_SupportRegistrationLocationInfo>
<CscFeature_RIL_SupportSmsFallbackForIms>TRUE</CscFeature_RIL_SupportSmsFallbackForIms>
<CscFeature_RIL_SupportSrvcc>TRUE</CscFeature_RIL_SupportSrvcc>
<CscFeature_RIL_SupportVolte>TRUE</CscFeature_RIL_SupportVolte>
<CscFeature_RIL_UpdateCscApnAfterSwitchingImsi>TRUE</CscFeature_RIL_UpdateCscApnAfterSwitchingImsi>
<CscFeature_RIL_UseMpsForImsSetting>TRUE</CscFeature_RIL_UseMpsForImsSetting>
<CscFeature_RIL_WbamrDefaultOn>TRUE</CscFeature_RIL_WbamrDefaultOn>
<CscFeature_Setting_DataRoamingOption>national</CscFeature_Setting_DataRoamingOption>
<CscFeature_Setting_HideApnList>hos,HOS,Orange SERVICES,T-Mobile IMS,T-Mobile.pl IMS,T-Mobile.pl MMS,T-Mobile.pl HOS,Orange IMS</CscFeature_Setting_HideApnList>
<CscFeature_Setting_SupportWifiCall>TRUE</CscFeature_Setting_SupportWifiCall>
<CscFeature_VoiceCall_ConfigOpStyleForEmergencyDialCall>EndPreviousCall</CscFeature_VoiceCall_ConfigOpStyleForEmergencyDialCall>
<CscFeature_VoiceCall_ConfigOpStyleForMobileNetSetting>voltesettingscommon,voltesettingEUR</CscFeature_VoiceCall_ConfigOpStyleForMobileNetSetting>
<CscFeature_VoiceCall_ConfigOpStyleForNetworkSetting>StopNetworkSearchingOnPause</CscFeature_VoiceCall_ConfigOpStyleForNetworkSetting>
<CscFeature_VoiceCall_ConfigOpStyleForRoaming>nationalroamingmodemenuplay</CscFeature_VoiceCall_ConfigOpStyleForRoaming>
</FeatureSet>
</SamsungMobileFeature>
8. So now I think that the best place to put that <CscFeature_RIL_ForceConnectMMS>TRUE</CscFeature_RIL_ForceConnectMMS> is cscfeature_network.xml
9. Add <CscFeature_RIL_ForceConnectMMS>TRUE</CscFeature_RIL_ForceConnectMMS> to cscfeature_network.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<SamsungMobileFeature>
<NetworkVersion>ED00005</NetworkVersion>
<NetworkCountry>POLAND</NetworkCountry>
<NetworkCountryISO>PL</NetworkCountryISO>
<NetworkCode>XEO</NetworkCode>
<FeatureSet>
<CscFeature_IMS_EnableEVS>TRUE</CscFeature_IMS_EnableEVS>
<CscFeature_IMS_EnableIMS>TRUE</CscFeature_IMS_EnableIMS>
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE>
<CscFeature_IMS_FrameworkVersion>6.0</CscFeature_IMS_FrameworkVersion>
<CscFeature_RIL_BlockUssdDuringVolteCall>TRUE</CscFeature_RIL_BlockUssdDuringVolteCall>
<CscFeature_RIL_CallCsVtSupport>TRUE</CscFeature_RIL_CallCsVtSupport>
<CscFeature_RIL_ConfigAlwaysOnApn>mms_26003,mms_26006,ims,xcap</CscFeature_RIL_ConfigAlwaysOnApn>
<CscFeature_RIL_ConfigDataStatus>TRUE</CscFeature_RIL_ConfigDataStatus>
<CscFeature_RIL_ConfigEpdgE911RoutingPolicy>NoService</CscFeature_RIL_ConfigEpdgE911RoutingPolicy>
<CscFeature_RIL_ConfigEpdgExtraFunction>SUPPORTWEAKSIGNALHO,ENHANCEDVOWIFI20,WFCCALLMENU</CscFeature_RIL_ConfigEpdgExtraFunction>
<CscFeature_RIL_ConfigGlobalModuleType>LTE</CscFeature_RIL_ConfigGlobalModuleType>
<CscFeature_RIL_ConfigNetworkTypeCapability>EUR-EUR-GSM-EUR</CscFeature_RIL_ConfigNetworkTypeCapability>
<CscFeature_RIL_ConfigPresetMtuSize>modem</CscFeature_RIL_ConfigPresetMtuSize>
<CscFeature_RIL_ConfigSpecialPdpFlag>im_cn</CscFeature_RIL_ConfigSpecialPdpFlag>
<CscFeature_RIL_ConfigWbamr>2G</CscFeature_RIL_ConfigWbamr>
<CscFeature_RIL_DataPrefDataTechSnapShot>TRUE</CscFeature_RIL_DataPrefDataTechSnapShot>
<CscFeature_RIL_DisplayAntennaLimited>TRUE</CscFeature_RIL_DisplayAntennaLimited>
<CscFeature_RIL_DisplayPlmnnameSimload>TRUE</CscFeature_RIL_DisplayPlmnnameSimload>
<CscFeature_RIL_E911RoutingPolicy>auto</CscFeature_RIL_E911RoutingPolicy>
<CscFeature_RIL_EnableLaunchBrowser>TRUE</CscFeature_RIL_EnableLaunchBrowser>
<CscFeature_RIL_ForceConnectMMS>TRUE</CscFeature_RIL_ForceConnectMMS>
<CscFeature_RIL_GcfSor>TRUE</CscFeature_RIL_GcfSor>
<CscFeature_RIL_ImsPdnRetryTimeChange>FALSE</CscFeature_RIL_ImsPdnRetryTimeChange>
<CscFeature_RIL_ReferEonsWithoutLac>TRUE</CscFeature_RIL_ReferEonsWithoutLac>
<CscFeature_RIL_SetNetworkTypeWhenRadioOff>TRUE</CscFeature_RIL_SetNetworkTypeWhenRadioOff>
<CscFeature_RIL_SignalstrengthPolicy>0</CscFeature_RIL_SignalstrengthPolicy>
<CscFeature_RIL_SmsLoadShortcodeFromResourceOnly>TRUE</CscFeature_RIL_SmsLoadShortcodeFromResourceOnly>
<CscFeature_RIL_SrvccRel>10</CscFeature_RIL_SrvccRel>
<CscFeature_RIL_SsacInfoToIms>TRUE</CscFeature_RIL_SsacInfoToIms>
<CscFeature_RIL_SupportEpdg>TRUE</CscFeature_RIL_SupportEpdg>
<CscFeature_RIL_SupportEpdgOnAirplaneMode>TRUE</CscFeature_RIL_SupportEpdgOnAirplaneMode>
<CscFeature_RIL_SupportImsClirOverriding>TRUE</CscFeature_RIL_SupportImsClirOverriding>
<CscFeature_RIL_SupportImsService>TRUE</CscFeature_RIL_SupportImsService>
<CscFeature_RIL_SupportRegistrationLocationInfo>TRUE</CscFeature_RIL_SupportRegistrationLocationInfo>
<CscFeature_RIL_SupportSmsFallbackForIms>TRUE</CscFeature_RIL_SupportSmsFallbackForIms>
<CscFeature_RIL_SupportSrvcc>TRUE</CscFeature_RIL_SupportSrvcc>
<CscFeature_RIL_SupportVolte>TRUE</CscFeature_RIL_SupportVolte>
<CscFeature_RIL_UpdateCscApnAfterSwitchingImsi>TRUE</CscFeature_RIL_UpdateCscApnAfterSwitchingImsi>
<CscFeature_RIL_UseMpsForImsSetting>TRUE</CscFeature_RIL_UseMpsForImsSetting>
<CscFeature_RIL_WbamrDefaultOn>TRUE</CscFeature_RIL_WbamrDefaultOn>
<CscFeature_Setting_DataRoamingOption>national</CscFeature_Setting_DataRoamingOption>
<CscFeature_Setting_HideApnList>hos,HOS,Orange SERVICES,T-Mobile IMS,T-Mobile.pl IMS,T-Mobile.pl MMS,T-Mobile.pl HOS,Orange IMS</CscFeature_Setting_HideApnList>
<CscFeature_Setting_SupportWifiCall>TRUE</CscFeature_Setting_SupportWifiCall>
<CscFeature_VoiceCall_ConfigOpStyleForEmergencyDialCall>EndPreviousCall</CscFeature_VoiceCall_ConfigOpStyleForEmergencyDialCall>
<CscFeature_VoiceCall_ConfigOpStyleForMobileNetSetting>voltesettingscommon,voltesettingEUR</CscFeature_VoiceCall_ConfigOpStyleForMobileNetSetting>
<CscFeature_VoiceCall_ConfigOpStyleForNetworkSetting>StopNetworkSearchingOnPause</CscFeature_VoiceCall_ConfigOpStyleForNetworkSetting>
<CscFeature_VoiceCall_ConfigOpStyleForRoaming>nationalroamingmodemenuplay</CscFeature_VoiceCall_ConfigOpStyleForRoaming>
</FeatureSet>
</SamsungMobileFeature>
10. Encrypt cscfeature_network.xml with omc-decoder.jar or https://forum.xda-developers.com/android/software/decode-encode-omc-files-omc-decoder-t3791471
11. Unmount E drive (OSFMount)
12. Make img from ext4.img -> Here I'm stucked and need help in correct creation of odm.img from ext4 format.
Please help
The patient s10 lite z plus. A clean xeo plus card uploaded. MMS sending does not work. Root is off adb not working. Found an app called android hidden settings. Nothing special, but burying the settings of this application with the data transmission disabled, the function of sending and receiving MMS appeared. Thank you greetings
Pacjent s10 lite z plusa. Wgrane czyste xeo karta plusa. Nie działa wysyłanie MMS. Root odpada adb nie działało. Znalazłem aplikacje o nazwie android hidden settings. Niby nic szczególnego ale grzebiąc w ustawieniach tej aplikacji przy wyłączonej transmisji danych ukazała się funkcja wysyłania i odbierania MMS. Dziękuję pozdrawiam
Dorzucam link do postu members ze screenem https://eu.community.samsung.com/t5...nsmisji-danych-przy-wysyłaniu-mms/td-p/914776