Database Info

Ideas for rooting our phones - Verizon Galaxy S 5 General

This thread is for both AT&T and Verizon models. I am on Verizon, so that is why it is in this thread.​
I am making this thread for those who have ideas on rooting the SM-G900V and SM-G900A varieties of the Samsung Galaxy S5. You can post your ideas here, and devs who look at this forum are free to try the ideas, as long as, if it works in the long run, the original poster of the idea gets credit. Feel free to post whatever ideas you may have, as all will be looked into at some point.

eragon5779 said:
This thread is for both AT&T and Verizon models. I am on Verizon, so that is why it is in this thread.​
I am making this thread for those who have ideas on rooting the SM-G900V and SM-G900A varieties of the Samsung Galaxy S5. You can post your ideas here, and devs who look at this forum are free to try the ideas, as long as, if it works in the long run, the original poster of the idea gets credit. Feel free to post whatever ideas you may have, as all will be looked into at some point.
Click to expand...
Click to collapse
Do you know ? The Verizon and AT&T versions have locked bootloaders and are not able to be rooted at the moment.

Guadalupeohara said:
Do you know ? The Verizon and AT&T versions have locked bootloaders and are not able to be rooted at the moment.
Click to expand...
Click to collapse
I know they have locked bootloaders. That is the whole reason I created this thread: to share ideas for an exploit or a bootloader unlock so that we can get root. I own the phone and have done a lot of research. I have also been following the root status thread (here) since almost the creation. I am hoping that devs will see this thread and read ideas and/or post ideas. Something is better than nothing. I don't want to just sit here and wait when I can try it myself.

eragon5779 said:
I know they have locked bootloaders. That is the whole reason I created this thread: to share ideas for an exploit or a bootloader unlock so that we can get root. I own the phone and have done a lot of research. I have also been following the root status thread (here) since almost the creation. I am hoping that devs will see this thread and read ideas and/or post ideas. Something is better than nothing. I don't want to just sit here and wait when I can try it myself.
Click to expand...
Click to collapse
Fine.. Did you try kingo rooting method ?

The saferoot method? Yes. No luck.
EDIT:
Never mind. They are to different things. No, I didn't, but I saw a post that someone had unsuccessfully tried it. I tried safe root though.
Sent from my white SM G900V on XDA Premium 4

Okay. I will try to find next method for this..

eragon5779 said:
The saferoot method? Yes. No luck.
EDIT:
Never mind. They are to different things. No, I didn't, but I saw a post that someone had unsuccessfully tried it. I tried safe root though.
Sent from my white SM G900V on XDA Premium 4
Click to expand...
Click to collapse
Saferoot is based on the get/put exploit from 4.3, it should be patched in all 4.4+ builds. Are Verizon and AT&T both SELinux Enforcing?

ryanbg said:
Saferoot is based on the get/put exploit from 4.3, it should be patched in all 4.4+ builds. Are Verizon and AT&T both SELinux Enforcing?
Click to expand...
Click to collapse
AT&T is I assume VZW is the same.

cciechad said:
AT&T is I assume VZW is the same.
Click to expand...
Click to collapse
In terminal emulator/adb shell, can you give me the output of the following commands:
Code:
getsebool -a
Code:
getprop

ryanbg said:
In terminal emulator/adb shell, can you give me the output of the following commands:
Code:
getsebool -a
Code:
getprop
Click to expand...
Click to collapse
Code:
[email protected]:/ $ getsebool -a
android_cts --> off
disableAudio --> off
disableAudioCapture --> off
disableBluetooth --> off
disableCamera --> off
manage_ams --> on
manage_mac --> on
manage_selinux --> on
support_runas --> on
[email protected]:/ $ getprop
[DEVICE_PROVISIONED]: [1]
[af.resampler.quality]: [4]
[android.telephony.apn-restore]: [1800000]
[boot.sfbootcomplete]: [1]
[dalvik.vm.heapgrowthlimit]: [128m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [2m]
[dalvik.vm.heapsize]: [512m]
[dalvik.vm.heapstartsize]: [8m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.composition.type]: [c2d]
[debug.disable.bwc]: [1]
[debug.egl.hw]: [1]
[debug.force_rtl]: [0]
[debug.mdpcomp.logs]: [0]
[debug.sf.hw]: [1]
[debug.sf.layerdump]: [0]
[dev.MDPLimitCondition]: [0]
[dev.bootcomplete]: [1]
[dev.kies.sommode]: [TRUE]
[dev.kiessupport]: [TRUE]
[dev.knoxapp.running]: [false]
[dev.pm.dyn_samplingrate]: [1]
[dev.ssrm.emergencymode]: [false]
[dev.ssrm.init]: [1]
[dev.ssrm.mode]: [dm;]
[dev.ssrm.pst]: [307]
[dhcp.wlan0.dns1]: [192.168.1.1]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: []
[dhcp.wlan0.gateway]: [192.168.1.1]
[dhcp.wlan0.ipaddress]: [192.168.1.236]
[dhcp.wlan0.leasetime]: [86400]
[dhcp.wlan0.mask]: [255.255.255.0]
[dhcp.wlan0.mtu]: []
[dhcp.wlan0.pid]: [3881]
[dhcp.wlan0.reason]: [REBOOT]
[dhcp.wlan0.result]: [failed]
[dhcp.wlan0.roaming]: [0]
[dhcp.wlan0.server]: [192.168.1.1]
[dhcp.wlan0.vendorInfo]: []
[gsm.current.phone-type]: [2]
[gsm.default.channel]: [0]
[gsm.defaultpdpcontext.active]: [true]
[gsm.network.type]: [LTE:14]
[gsm.nitz.time]: [1398297495673]
[gsm.operator.alpha]: [Verizon Wireless]
[gsm.operator.iso-country]: [us]
[gsm.operator.ispsroaming]: [false]
[gsm.operator.isroaming]: [false]
[gsm.operator.numeric]: [311480]
[gsm.sim.operator.alpha]: [Verizon Wireless]
[gsm.sim.operator.iso-country]: [us]
[gsm.sim.operator.numeric]: [311480]
[gsm.sim.state]: [READY]
[gsm.version.baseband]: [G900VVRU1ANCG]
[gsm.version.ril-impl]: [Samsung RIL v3.0]
[init.svc.BCS-daemon]: [running]
[init.svc.DR-daemon]: [running]
[init.svc.SIDESYNC_service]: [running]
[init.svc.SMD-daemon]: [running]
[init.svc.TvoutService_C]: [running]
[init.svc.adbd]: [running]
[init.svc.adsprpcd]: [running]
[init.svc.apaservice]: [running]
[init.svc.at_distributor]: [stopped]
[init.svc.atfwd]: [running]
[init.svc.auditd]: [running]
[init.svc.bootanim]: [stopped]
[init.svc.bootchecker]: [stopped]
[init.svc.cnd]: [running]
[init.svc.config_bluetooth]: [stopped]
[init.svc.cs_service]: [running]
[init.svc.debuggerd]: [running]
[init.svc.dhcpcd_wlan0]: [stopped]
[init.svc.diag_uart_log]: [running]
[init.svc.drm]: [running]
[init.svc.drsd]: [running]
[init.svc.edmaudit]: [running]
[init.svc.freshsebool]: [stopped]
[init.svc.fuse_extSdCard]: [stopped]
[init.svc.gsiff_daemon]: [running]
[init.svc.healthd]: [running]
[init.svc.icd]: [stopped]
[init.svc.immvibed]: [stopped]
[init.svc.imsdatadaemon]: [restarting]
[init.svc.imsqmidaemon]: [running]
[init.svc.installd]: [running]
[init.svc.insthk]: [stopped]
[init.svc.irsc_util]: [stopped]
[init.svc.jackservice]: [running]
[init.svc.keystore]: [running]
[init.svc.knox]: [stopped]
[init.svc.macloader]: [stopped]
[init.svc.media]: [running]
[init.svc.ml_service]: [running]
[init.svc.mobex-daemon]: [running]
[init.svc.mpdecision]: [running]
[init.svc.netd]: [running]
[init.svc.netmgrd]: [stopped]
[init.svc.olsrd]: [stopped]
[init.svc.p2p_supplicant]: [running]
[init.svc.powersnd]: [stopped]
[init.svc.prepare-mobicore]: [stopped]
[init.svc.prepare_param]: [stopped]
[init.svc.privatemode]: [stopped]
[init.svc.qcamerasvr]: [running]
[init.svc.qcom-c_core-sh]: [stopped]
[init.svc.qcom-post-boot]: [stopped]
[init.svc.qcom-sh]: [stopped]
[init.svc.qcom-usb-sh]: [stopped]
[init.svc.qmuxd]: [running]
[init.svc.qrngd]: [running]
[init.svc.qrngp]: [stopped]
[init.svc.qseecomd]: [running]
[init.svc.rfs_access]: [running]
[init.svc.ril-daemon]: [running]
[init.svc.ril-qmi]: [stopped]
[init.svc.rmt_storage]: [running]
[init.svc.run-mobicore]: [running]
[init.svc.scranton_RD]: [stopped]
[init.svc.sdcard]: [stopped]
[init.svc.sdumpstate]: [stopped]
[init.svc.sec-sh]: [stopped]
[init.svc.secure_storage]: [running]
[init.svc.security-check1]: [stopped]
[init.svc.security-check2]: [stopped]
[init.svc.sensorhubservice]: [running]
[init.svc.servicemanager]: [running]
[init.svc.ssr_diag]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.swapon]: [stopped]
[init.svc.thermal-engine]: [running]
[init.svc.time_daemon]: [running]
[init.svc.ueventd]: [running]
[init.svc.usf-post-boot]: [stopped]
[init.svc.vcsFPService]: [running]
[init.svc.vold]: [running]
[init.svc.wcnss-service]: [stopped]
[init.svc.zygote]: [running]
[installd.sdcard_manipulate_done]: [1]
[keyguard.no_require_sim]: [true]
[lpa.decode]: [false]
[lpa.use-stagefright]: [true]
[media.aac_51_output_enabled]: [true]
[media.enable-commonsource]: [true]
[media.stagefright.enable-aac]: [true]
[media.stagefright.enable-fma2dp]: [true]
[media.stagefright.enable-http]: [true]
[media.stagefright.enable-player]: [true]
[media.stagefright.enable-qcp]: [true]
[media.stagefright.enable-scan]: [true]
[mm.enable.qcom_parser]: [37491]
[mm.enable.smoothstreaming]: [true]
[mmp.enable.3g2]: [true]
[net.bt.name]: [Android]
[net.change]: [net.dns2]
[net.dns1]: [198.224.186.135]
[net.dns2]: [198.224.187.135]
[net.dns3]: []
[net.dns4]: []
[net.hostname]: [android-cb61d33155744fb5]
[net.qtaguid_enabled]: [1]
[net.rmnet0.dns1]: []
[net.rmnet0.dns2]: []
[net.rmnet0.dns3]: [2001:4888:12:ff00:106:d::]
[net.rmnet0.dns4]: [2001:4888:13:ff00:123:d::]
[net.rmnet1.dns1]: [198.224.186.135]
[net.rmnet1.dns2]: [198.224.187.135]
[net.rmnet1.dns3]: [::]
[net.rmnet1.dns4]: [::]
[net.tcp.buffersize.default]: [4096,87380,704512,4096,16384,110208]
[net.tcp.buffersize.edge]: [4093,26280,35040,4096,16384,35040]
[net.tcp.buffersize.evdo]: [4094,87380,262144,4096,16384,262144]
[net.tcp.buffersize.gprs]: [4092,30000,30000,4096,8760,11680]
[net.tcp.buffersize.hsdpa]: [4094,87380,704512,4096,16384,262144]
[net.tcp.buffersize.hspa]: [4094,87380,704512,4096,16384,262144]
[net.tcp.buffersize.hspap]: [4094,87380,1220608,4096,16384,1220608]
[net.tcp.buffersize.hsupa]: [4094,87380,704512,4096,16384,262144]
[net.tcp.buffersize.lte]: [524288,1048576,2560000,524288,1048576,2560000]
[net.tcp.buffersize.umts]: [4094,87380,704512,4096,16384,110208]
[net.tcp.buffersize.wifi]: [524288,1048576,4525824,524288,1048576,4525824]
[persist.audio.allsoundmute]: [0]
[persist.audio.fluence.speaker]: [true]
[persist.audio.fluence.voicecall]: [true]
[persist.audio.fluence.voicerec]: [false]
[persist.audio.headsetsysvolume]: [9]
[persist.audio.hphonesysvolume]: [9]
[persist.audio.ringermode]: [0]
[persist.audio.sysvolume]: [9]
[persist.cne.feature]: [0]
[persist.data.netmgrd.qos.enable]: [false]
[persist.debug.wfd.enable]: [1]
[persist.demo.hdmirotationlock]: [false]
[persist.env.phone.global]: [false]
[persist.env.plmn.update]: [false]
[persist.eons.enabled]: [false]
[persist.fuse_sdcard]: [true]
[persist.gps.qc_nlp_in_use]: [1]
[persist.hwc.mdpcomp.enable]: [true]
[persist.radio.add_power_save]: [1]
[persist.radio.apm_sim_not_pwdn]: [1]
[persist.radio.cdma.msgid]: [186]
[persist.radio.icc.cb.count]: [0]
[persist.radio.icc.cb.list]: []
[persist.radio.initphone-type]: [2]
[persist.radio.no_wait_for_card]: [1]
[persist.radio.snapshot_enabled]: [1]
[persist.radio.snapshot_timer]: [22]
[persist.radio.use_se_table_only]: [1]
[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_plmn]: []
[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.security.ams.enforcing]: [1]
[persist.speaker.prot.enable]: [false]
[persist.sys.clssprld1]: [702]
[persist.sys.clssprld2]: [722]
[persist.sys.country]: [US]
[persist.sys.dalvik.vm.lib]: [libdvm.so]
[persist.sys.drs.date]: [Mon Mar 31 13:28:02 KST 2014]
[persist.sys.enablehomekey]: [false]
[persist.sys.flipfontpath]: [default]
[persist.sys.ims.pco_enabled]: [1]
[persist.sys.language]: [en]
[persist.sys.localevar]: []
[persist.sys.logkit.ctrlcode]: [0]
[persist.sys.profiler_ms]: [0]
[persist.sys.setupwizard]: [FINISH]
[persist.sys.silent]: [1]
[persist.sys.storage_preload]: [2]
[persist.sys.strict_op_enable]: [false]
[persist.sys.timezone]: [America/Detroit]
[persist.sys.usb.config]: [diag,acm,adb]
[persist.sys.vzw_setup_running]: [false]
[persist.sys.vzw_wifi_running]: [false]
[persist.sys.wfd.virtual]: [0]
[persist.sys.whitelist]: [/system/etc/whitelist_appops.xml]
[persist.sys.xtra_time]: [1398331933265]
[persist.timed.enable]: [true]
[qcom.hw.aac.encoder]: [true]
[ril.CompleteMsg]: [01]
[ril.ICC_TYPE]: [2]
[ril.LoopbackCallFlag]: [false]
[ril.RildInit]: [1]
[ril.approved_codever]: [none]
[ril.approved_cscver]: [none]
[ril.approved_modemver]: [none]
[ril.atd_status]: [1_0_0]
[ril.cs_svc]: [1]
[ril.def_ipv6_on_ehrpd]: [0]
[ril.deviceOffRes]: [0]
[ril.ecclist0]: [112,911]
[ril.ecclist]: [911,112,*911,#911]
[ril.eri_num]: [1]
[ril.eri_ver_1]: [E:5]
[ril.euimid]: [a000004cdef97e]
[ril.hw_ver]: [G900V.05]
[ril.ims.ltevoicesupport]: [1]
[ril.initPB]: [1]
[ril.isIccChanged]: [0]
[ril.modem.board]: [MSM8974PRO]
[ril.modem.lte.powercontrol]: [on]
[ril.official_cscver]: [G900VVZW1ANCG]
[ril.otasp_state]: [3]
[ril.pcscfv4.gsm0.0]: [0.0.0.0]
[ril.pcscfv4.gsm0.1]: [0.0.0.0]
[ril.pcscfv4.gsm0.2]: [0.0.0.0]
[ril.pcscfv6.gsm0.0]: [2001:4888:5:fe00:e0:104:0:68]
[ril.pcscfv6.gsm0.1]: [2001:4888:2:fe04:a0:105:0:17]
[ril.pcscfv6.gsm0.2]: [2001:4888:5:fe00:e0:104:0:65]
[ril.product_code]: [Not Active]
[ril.rfcal_date]: [2014.04.03]
[ril.sales_code]: [VZW]
[ril.serialnumber]: [00000000000]
[ril.servicestate]: [0]
[ril.subscription.types]: [NV,RUIM]
[ril.sw_ver]: [G900VVRU1ANCG]
[ril.volte.911callCount]: [0]
[ril.wbamrstatus]: [0]
[rild.libargs]: [-d /dev/smd0]
[rild.libpath]: [/system/lib/libsec-ril.so]
[ro.HorizontalVVM]: [true]
[ro.adb.secure]: [1]
[ro.allow.mock.location]: [0]
[ro.baseband]: [msm]
[ro.bluetooth.dun]: [true]
[ro.bluetooth.hfp.ver]: [1.6]
[ro.bluetooth.sap]: [true]
[ro.board.platform]: [msm8974]
[ro.boot.baseband]: [msm]
[ro.boot.boot_recovery]: [0]
[ro.boot.bootloader]: [G900VVRU1ANCG]
[ro.boot.cp_debug_level]: [0x55FF]
[ro.boot.debug_level]: [0x4f4c]
[ro.boot.emmc]: [true]
[ro.boot.emmc_checksum]: [3]
[ro.boot.hardware]: [qcom]
[ro.boot.nvdata_backup]: [0]
[ro.boot.sec_atd.tty]: [/dev/ttyHSL0]
[ro.boot.serialno]: [a0339734]
[ro.boot.warranty_bit]: [0]
[ro.boot_recovery]: [0]
[ro.bootloader]: [G900VVRU1ANCG]
[ro.bootmode]: [unknown]
[ro.bt.bdaddr_path]: [/efs/bluetooth/bt_addr]
[ro.build.PDA]: [G900VVRU1ANCG]
[ro.build.changelist]: [964333]
[ro.build.characteristics]: [verizon]
[ro.build.date.utc]: [1396240082]
[ro.build.date]: [Mon Mar 31 13:28:02 KST 2014]
[ro.build.description]: [kltevzw-user 4.4.2 KOT49H G900VVRU1ANCG release-keys]
[ro.build.display.id]: [KOT49H.G900VVRU1ANCG]
[ro.build.fingerprint]: [Verizon/kltevzw/kltevzw:4.4.2/KOT49H/G900VVRU1ANCG:user/release-keys]
[ro.build.hidden_ver]: [G900VVRU1ANCG_NCI]
[ro.build.host]: [SWDD5814]
[ro.build.id]: [KOT49H]
[ro.build.knox.container]: []
[ro.build.product]: [kltevzw]
[ro.build.scafe.shot]: [single]
[ro.build.scafe.size]: [short]
[ro.build.scafe]: [capuccino]
[ro.build.selinux.enforce]: [1]
[ro.build.selinux]: [1]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [dpi]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [G900VVRU1ANCG]
[ro.build.version.release]: [4.4.2]
[ro.build.version.sdk]: [19]
[ro.carrier]: [unknown]
[ro.chipname]: [MSM8974PRO]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.google.clientidbase.am]: [android-verizon]
[ro.com.google.clientidbase.gmm]: [android-samsung]
[ro.com.google.clientidbase.ms]: [android-verizon]
[ro.com.google.clientidbase.yt]: [android-verizon]
[ro.com.google.clientidbase]: [android-samsung]
[ro.com.google.gmsversion]: [4.4.2_r1]
[ro.config.alarm_alert]: [Morning_flower.ogg]
[ro.config.combined_signal]: [true]
[ro.config.knox]: [v30]
[ro.config.multimode_cdma]: [1]
[ro.config.notification_sound]: [Verizon_Alert.ogg]
[ro.config.ringtone]: [Verizon_Airwaves_1.ogg]
[ro.config.rm_preload_enabled]: [0]
[ro.config.tima]: [1]
[ro.config.timaversion]: [3.0]
[ro.config.vc_call_vol_steps]: [7]
[ro.cp_debug_level]: [0x55FF]
[ro.crypto.state]: [unencrypted]
[ro.csc.country_code]: [USA]
[ro.csc.countryiso_code]: [US]
[ro.csc.sales_code]: [VZW]
[ro.data.large_tcp_window_size]: [true]
[ro.debug_level]: [0x4f4c]
[ro.debuggable]: [0]
[ro.emmc]: [true]
[ro.emmc_checksum]: [3]
[ro.error.receiver.default]: [com.samsung.receiver.error]
[ro.factorytest]: [0]
[ro.gps.agps_provider]: [1]
[ro.gsm.data_retry_config]: [max_retries=infinite,5000,5000,60000,120000,480000,900000]
[ro.hardware]: [qcom]
[ro.hdcp2.rx]: [tz]
[ro.hdmi.enable]: [true]
[ro.hwui.drop_shadow_cache_size]: [4]
[ro.hwui.gradient_cache_size]: [1]
[ro.hwui.layer_cache_size]: [32]
[ro.hwui.path_cache_size]: [8]
[ro.hwui.shape_cache_size]: [2]
[ro.hwui.text_large_cache_height]: [1024]
[ro.hwui.text_large_cache_width]: [2048]
[ro.hwui.text_small_cache_height]: [512]
[ro.hwui.text_small_cache_width]: [1024]
[ro.hwui.texture_cache_size]: [48]
[ro.kernel.qemu]: [0]
[ro.mvp.features]: [srvc,mvpdsec,grbks2,vpn,vpncrt,mvpdaff]
[ro.nfc.port]: [I2C]
[ro.nvdata_backup]: [0]
[ro.opengles.version]: [196608]
[ro.product.board]: [MSM8974]
[ro.product.brand]: [Verizon]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [kltevzw]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [samsung]
[ro.product.model]: [SM-G900V]
[ro.product.name]: [kltevzw]
[ro.product_ship]: [true]
[ro.qc.sdk.audio.fluencetype]: [none]
[ro.qc.sdk.audio.ssr]: [false]
[ro.qc.sdk.camera.facialproc]: [false]
[ro.qc.sdk.gestures.camera]: [false]
[ro.qc.sdk.izat.premium_enabled]: [0]
[ro.qc.sdk.izat.service_mask]: [0x0]
[ro.qc.sdk.sensors.gestures]: [true]
[ro.qualcomm.bluetooth.ftp]: [true]
[ro.qualcomm.bluetooth.hfp]: [true]
[ro.qualcomm.bluetooth.hsp]: [true]
[ro.qualcomm.bluetooth.map]: [true]
[ro.qualcomm.bluetooth.nap]: [true]
[ro.qualcomm.bluetooth.opp]: [true]
[ro.qualcomm.bluetooth.pbap]: [true]
[ro.qualcomm.bt.hci_transport]: [smd]
[ro.qualcomm.cabl]: [1]
[ro.revision]: [14]
[ro.ril.ecclist]: [911,#911,*911]
[ro.ril.svdo]: [false]
[ro.ril.svlte1x]: [true]
[ro.runtime.firstboot]: [1398259918652]
[ro.sec.fle.encryption]: [true]
[ro.secure]: [1]
[ro.securestorage.support]: [true]
[ro.security.mdpp.release]: [2]
[ro.security.mdpp.ux]: [Enabled]
[ro.security.mdpp.ver]: [1.0]
[ro.security.vpnpp.release]: [1]
[ro.security.vpnpp.ver]: [1.4]
[ro.secwvk]: [144]
[ro.serialno]: [a0339734]
[ro.setupwizard.mode]: [OPTIONAL]
[ro.sf.lcd_density]: [480]
[ro.slook.ver]: [1]
[ro.telephony.call_ring.multiple]: [false]
[ro.telephony.default_network]: [10]
[ro.use_data_netmgrd]: [false]
[ro.vendor.extension_library]: [/vendor/lib/libqc-opt.so]
[ro.warranty_bit]: [0]
[ro.wifi.channels]: []
[sec.fle.encryption.status]: [Dec NewFile IncludeMedia]
[secmm.player.disabledivx]: [True]
[secmm.player.gp.url]: [true]
[secmm.player.uhqamode]: [True]
[security.mdpp.result]: [None]
[security.mdpp]: [Ready]
[selinux.policy_version]: [SEPF_SM-G900V_4.4.2_0011]
[selinux.reload_policy]: [1]
[service.bootanim.exit]: [0]
[service.camera.hdmi_preview]: [0]
[service.camera.running]: [0]
[service.media.powersnd]: [1]
[storage.mmc.size]: [15758000128]
[sys.boot_completed]: [1]
[sys.cameramode.blackbox]: [0]
[sys.cameramode.vtcall]: [0]
[sys.dumpstate.opt]: [-k -t -z -d -o /data/log/dumpstate_app_error]
[sys.factory.mediaScanningCount]: [2]
[sys.hangouts.fps]: [-1]
[sys.ims.QMI_DAEMON_STATUS]: [1]
[sys.knox.store]: [0]
[sys.mobicoredaemon.enable]: [true]
[sys.qseecomd.enable]: [true]
[sys.settings_global_version]: [2]
[sys.settings_system_version]: [37]
[sys.shutdown.fastboot]: [false]
[sys.siop.longlife]: [0]
[sys.sysctl.extra_free_kbytes]: [24300]
[sys.usb.config]: [diag,acm,adb]
[sys.usb.state]: [diag,acm,adb]
[telephony.lteOnCdmaDevice]: [1]
[tunnel.audio.encode]: [true]
[tunnel.audiovideo.decode]: [true]
[tunnel.decode]: [true]
[vidc.debug.level]: [1]
[vmware.hypervisor.running]: [0]
[vold.post_fs_data_done]: [1]
[vzw.telephony.appsapn-restore]: [60000]
[wifi.interface]: [wlan0]
[wlan.driver.status]: [ok]
[wlan.wfd.status]: [disconnected]

So what I've gathered from download mode, that log, and my logcat, is that Knox isn't actually present.

Dude we've already got a thread for all things root/recovery/bootloader
http://forum.xda-developers.com/showthread.php?t=2714140

Syn Ack said:
Dude we've already got a thread for all things root/recovery/bootloader
http://forum.xda-developers.com/showthread.php?t=2714140
Click to expand...
Click to collapse
I know. I'm following that thread too. However, I want this one to be just for ideas so they get seen
Sent from my white SM G900V on XDA Premium 4

eragon5779 said:
I know. I'm following that thread too. However, I want this one to be just for ideas so they get seen
Sent from my white SM G900V on XDA Premium 4
Click to expand...
Click to collapse
The other one can be seen too. So what's gonna be different here?

Please excuse my ignorance. I am new to the forums and have never personally rooted a phone. My last phone (Motorola Razer XT912), I had a friend root for me because I still have unlimited data and needed access to the hotspot (I'm dutch and don't want to pay for it). Anyways, if you are looking for ideas or things we'd like to see, I personally would like to see the friends widget that Motorola did for your Favorite contacts. You could see four or five contacts lined up, and if you dragged them down, it would show all your favorite contacts. Is their a way to get that widget onto the Samsung S5?
Also too, if someone doesn't mind answering a noob question; does all rooting unlock the mobile hotspot feature so you don't have to pay for it?Or is it only certain ROM's/Root files that unlock the MHS?
Thanks for any help with these two questions!

ErosAoA said:
Please excuse my ignorance. I am new to the forums and have never personally rooted a phone. My last phone (Motorola Razer XT912), I had a friend root for me because I still have unlimited data and needed access to the hotspot (I'm dutch and don't want to pay for it). Anyways, if you are looking for ideas or things we'd like to see, I personally would like to see the friends widget that Motorola did for your Favorite contacts. You could see four or five contacts lined up, and if you dragged them down, it would show all your favorite contacts. Is their a way to get that widget onto the Samsung S5?
Also too, if someone doesn't mind answering a noob question; does all rooting unlock the mobile hotspot feature so you don't have to pay for it?Or is it only certain ROM's/Root files that unlock the MHS?
Thanks for any help with these two questions!
Click to expand...
Click to collapse
You might wanna try this: https://play.google.com/store/apps/details?id=com.gau.go.launcherex.gowidget.contactwidget or this: https://play.google.com/store/apps/details?id=com.gmail.yuyang226.contactswidget.pro
As for rooting for mobile hotspot, that has yet to be discovered as there's no rooting process (yet) for our S5s. Just keep an eye on this thread for updates: http://forum.xda-developers.com/showthread.php?t=2714140

Droid_Evo_8 said:
The other one can be seen too. So what's gonna be different here?
Click to expand...
Click to collapse
That thread got partially derailed for a few pages. I am hoping this one won't.
Sent from my white SM G900V on XDA Premium 4

ErosAoA said:
Please excuse my ignorance.....
Click to expand...
Click to collapse
Lol, Already derailed. We've got a "Verizon Galaxy S 5 Q&A, Help & Troubleshooting" forum, and the whole other thread that has mostly questions. And less than two pages into yet another "rooting ideas/sharing" someone asks a question about rooting. Too funny.

It's funny how the M8 guys are creeping the s5 forums all the time, seems like they are already bored with their sub par phones...lol
Sent from my SM-G900V using xda app-developers app

Broadley1 said:
It's funny how the M8 guys are creeping the s5 forums all the time, seems like they are already bored with their sub par phones...lol
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
One thing I can say I've never done in all my time rooting; trolling another phones threads. That's just crazy town.
Sent from my SM-G900V using Tapatalk

Related

Do rogers and telus carry the SM-G930F ? and if so, what region are they using?
cant find their sctock firmware on sammobile.
thanks
answer: "XAC" Canada Multi-CSC (W8) contains: BMC, BWA, ESK, FMC, GLW, KDO, MTA, RWC, TLS, VMC

BMC bell, fmc fido, rwc rogers, tls telus, xac all unlocked network
all w8 s7 s8 s9
For noob
https://forum.xda-developers.com/showthread.php?t=2546689
https://www.androidsage.com/2017/07...specific-product-code-csc-and-country-region/

I'm playing around with the nve modem files to enable all bands same as mate 10 as its same internals and modem. Anyone have any success on this yet ?

Aws 1700 I have unlocked.

unlock LTE band 3 (1800) on Honor View 10
is there a way to unlock the LTE band 3 (1800) doing a Debranding / Rebranding and/or using oeminfo from europe or china version?
I have an Honor View 10, the USA Version which only have the following bands: LTE band 1(2100), 3(1800), 5(850), 7(2600), 8(900), 20(800), 38(2600), 40(2300), 41(2500).
thanks in advance.:good:
Pedro

mr_lalsin said:
Aws 1700 I have unlocked.
Click to expand...
Click to collapse
Can you tell more about the procedure? I did not find any hints in this forum.

mr_lalsin said:
Aws 1700 I have unlocked.
Click to expand...
Click to collapse
Can you tell me more about the procedure? Did you work with modem (AT) commands or did you change files on system partitions (oeminfo, mnvm ...)?

Whats the difference between the two?

I don't know, if it can help my 128g midnight is 6003

My mirror black 128 GB is A6000.

whats the difference though?
why are there two different models?

virtyx said:
whats the difference though?
why are there two different models?
Click to expand...
Click to collapse
Just the difference of LTE bands
AFAIK 6003 should be EU/US model and 6000 would be IN/CN model :fingers-crossed:

Funk Wizard said:
Just the difference of LTE bands
AFAIK 6003 should be EU/US model and 6000 would be IN/CN model :fingers-crossed:
Click to expand...
Click to collapse
Can you be more specific ?
Which bands?
Does one have more than the other?

You can contact the OnePlus support for more information but EU/US have different bands from IN/CN so the 4g can be unusable or instable if you are using a model that doesn't match your region

supertx2 said:
You can contact the OnePlus support for more information but EU/US have different bands from IN/CN so the 4g can be unusable or instable if you are using a model that doesn't match your region
Click to expand...
Click to collapse
Can't get through to them...

gulshanstrider said:
My mirror black 128 GB is A6000.
Click to expand...
Click to collapse
I was informed by oneplus
A6000 = hydrogen OS and bands for China, no Google play service
A6003 = oxygen everywhere else
Bands on Chinese version is different too

virtyx said:
I was informed by oneplus
A6000 = hydrogen OS and bands for China, no Google play service
A6003 = oxygen everywhere else
Bands on Chinese version is different too
Click to expand...
Click to collapse
I have a6000 here in India, apologies but i do not have exact info on the bands. Please write to support :fingers-crossed:

Funk Wizard said:
I have a6000 here in India, apologies but i do not have exact info on the bands. Please write to support :fingers-crossed:
Click to expand...
Click to collapse
India and China have A6000 I believe apparently it runs hydrogen OS, oneplus told me hardware is the same just os is different

Originally Posted by Funk Wizard
I have a6000 here in India, apologies but i do not have exact info on the bands. Please write to support
India and China have A6000 I believe apparently it runs hydrogen OS, oneplus told me hardware is the same just os is different
Click to expand...
Click to collapse
That is my understanding too:
i am in France and have a A6000 (Avenger edition) BUT TOMTOP sent it with Oxygen OS (i guess that they flashed it):
No issue at all :
i have all the french 4G bands (B20 and B28 ok) and everything is doing ok

virtyx said:
India and China have A6000 I believe apparently it runs hydrogen OS, oneplus told me hardware is the same just os is different
Click to expand...
Click to collapse
I have the A6000 and it runs on oxygenOS, I'm from India

My 8/256 Midnight Black is an A6003 and runs OxygenOS. I live in Italy and I have ordered it directly on OP online store at Day One.

My OP6 midnight black 128gb is an A6003 and I live in Austria

A6003 midnight black 128 greece

A6003 256GB from France [emoji632]
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

So can I unlock Bootloader, flash firmwares and custom ROMS without any problems on both versions?
I waiting now for my OP6 from chinese distribution (probably A6000).

Plutplut said:
That is my understanding too:
i am in France and have a A6000 (Avenger edition) BUT TOMTOP sent it with Oxygen OS (i guess that they flashed it):
No issue at all :
i have all the french 4G bands (B20 and B28 ok) and everything is doing ok
Click to expand...
Click to collapse
Dude .. You are right I have the same like you. I got it from China with H2OS, so I just flashed the Global one OOS, and as you said everything is fine
Thanks.

here are the bands according to gsmarena
4G bandsLTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 29(700), 30(2300), 32(1500), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 66(1700/2100), 71(600) - Europe, North America
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 29(700), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 66(1700/2100) - India, Asia, China

TLDR: I've read Samsung is rolling out the Tizen 4 update for Gear wearables, but I can't get that to even show up in the Wearable app. My device is "already up to date" with 3.0.0.2.
Let me explain a little further: I have a Samsung Gear S3 Frontier, paired to my Moto Z2 Play, and here comes the first "issue". Samsung is not supporting my phone to be used with the Galaxy Wearable app, not even letting the user download it from the Play Store (even though they support older device that I owned, like the Moto G3 and the LG G3). Anyway, I've downloaded the APK from ApkMirror, installed and successfully set up my watch. No major issues since then.
Now, I'm pretty sure the updates system is working, because I've already downloaded and installed an update previously with the same device combination and Tizen 4 is rolling out where I live (BTW, Italy): a friend of mine, who has a Gear Sport, already got the new firmware.
And all I'm getting is a "Your system is already up to date" message box, when it obviously is not, still rocking 3.0.0.2.
What do I need to do in order to (safely) update my watch?
Thanks, and sorry for the long post
Zago

What CSC do you have? Only north america receive update at this moment. If you want update you must change CSC to XAR. Maybe your friend with gear sport bought his watch from internet with xar csc.

I'm in Canada.
My Gear Sport updated several days ago, but no update is available for my S3 Frontier.
Confused..

Code:
ACR: R760XXU2CRH1
AFR: R760XXU2CRH1
ARO: R760XXU2CRH1
ATO: R760XXU2CRH1
AUT: R760XXU2CRH1
BGL: R760XXU2CRH1
BRI: R760XXU2CRH1
BTU: R760XXU2CRK2
BVO: R760XXU2CRH1
CAC: R760XXU2CRH1
CAM: R760XXU2CRH1
CHC: R760XXU2CRK2
CHO: R760XXU2CRH1
COO: R760XXU2CRH1
DBT: R760XXU2CRK2
ECT: R760XXU2CRH1
EUR: R760XXU2CRH1
ILO: R760XXU2CRH1
INU: R760XXU2CRH1
ITV: R760XXU2CRH1
[B]KOO: R760XXU2DSA1[/B] Korea
KSA: R760XXU2CRH1
LUX: R760XXU2CRH1
LYS: R760XXU2CRH1
MID: R760XXU2CRH1
MWD: R760XXU2CRH1
MXO: R760XXU2CRH1
MYM: R760XXU2CRH1
NEE: R760XXU2CRH1
NPL: R760XXU2CRH1
PAK: R760XXU2CRH1
PEO: R760XXU2CRH1
[B]PHE: R760XXU2DSA1[/B] Spain???
PHN: R760XXU2CRH1
ROM: R760XXU2CRH1
SEB: R760XXU2CRH1
SEE: R760XXU2CRH1
SEK: R760XXU2CRH1
SER: R760XXU2CRK2
SKZ: R760XXU2CRH1
TGY: R760XXU2CRH1
THO: R760XXU2CRH1
THR: R760XXU2CRK2
TMC: R760XXU2CRH1
TPA: R760XXU2CRH1
TPH: R760XXU2CRH1
TTT: R760XXU2CRH1
TUN: R760XXU2CRH1
TUR: R760XXU2CRH1
UPO: R760XXU2CRH1
WTL: R760XXU2CRH1
[B]XAC: R760XXU2DSA1[/B] Cannada
[B]XAR: R760XXU2DSA1[/B] USA
XEF: R760XXU2CRK2
XEH: R760XXU2CRH1
XEO: R760XXU2CRH1
XEZ: R760XXU2CRH1
XFA: R760XXU2CRH1
XJP: R760XXU2CRH1
XME: R760XXU2CRH1
XNZ: R760XXU2CRH1
XSA: R760XXU2CRH1
XSE: R760XXU2CRH1
XSG: R760XXU2CRH1
XSK: R760XXU2CRH1
XSP: R760XXU2CRH1
XTC: R760XXU2CRH1
XXV: R760XXU2CRH2
ZTO: R760XXU2CRK2
Ask Samsung...
If somebody can not wait... Firmware for netOdin is available.
Best Regards

adfree where can you find this kind of firmware lists? Can you check what firmware have XEO now?

http://fota-cloud-dn.ospserver.net/firmware/XEO/SM-R760/version.xml
XEO have Tizen 4... DSA1
Best Regards

I checked my csc and i have xeo, but i didn't receive any update... Galaxy wear and gear s plugin up to date, never root or anything...

@agawron91
I checked my csc and i have xeo...
Click to expand...
Click to collapse
1.
How you know you have XEO?
Please exact what you did to "see" XEO
1.1
Me myself and I use SDB Tool...
or...
1.2
Rooted Phone... or rooted Watch...
2.
If you can not wait... Full Firmware for use with netOdin is available...
If I am back at home... I can check which countries not got DSA1...
Last time I saw...
INU
SER
and few more NOT received DSA1...
Best Regards

i use sdb tool to check my csc. I use this method to change CSC (i didn' change)
https://forum.xda-developers.com/smartwatch/gear-s3/guide-how-to-change-gear-s3-r760-csc-t3784226
first dilsplayed is XEO. I bought watch in Poland, live in Poland and CSC match to this.
I never change this, only use to check. Phone is 0x0 knox, never rooted, as watch.
Last time i send my watch to service because my battery was horrible live. I hope they didn't screw anything

@agawron91
If you want we can try together...
1.
Usefull info is to know FULL output from:
Code:
*#1234#
2.
Later more if I know result from 1...
3.
After Service... you ever updated at home this device?
Or since Service no change of Firmware?
Best Regards

1. AP: R760XXU2CRK2
CP: NO PHONE
CSC: R760OXA2CRK2
2. I wait for result
3. Before my warranty repair of course. I bought this watch when it is released. Some small updates, bigger is to tizen 3.0. I have not received anything for about half a year

@agawron91
Look into XEO Link:
http://fota-cloud-dn.ospserver.net/firmware/XEO/SM-R760/version.xml
No CRK2 is inside...
As example from XAR....
http://fota-cloud-dn.ospserver.net/firmware/XAR/SM-R760/version.xml
Sometimes not all avaliable Firmware visible because this is database request crap...
Maybe this is 1 reason why no update for you...
Ideas... :cyclops:
A
Maybe I am wrong... maybe soon "fixed"...
B
Depend how much you wish to have Tizen 4....
You could do the Factory blabla crap reset all you have blabla check Phone blabla... Gear App blabla...
Maybe Phone app "sleep"...
B.1
If you like Factory Reset...
You could eliminate problems from Phone + Gear App by starting as Standalone... WITHOUT pairing with Phone...
Then Option possible on SM-R760 to update Firmware with SM-R760 itself...
I have no other example... look here in Galaxy Watch Thread:
https://www.android-hilfe.de/forum/...lauderthread.891891-page-7.html#post-11363284
But this NOT helps if really CRK2 is not in FOTA database of XEO...
C
Use netOdin and flash manually...
DSA1 is as Full Firmware here in XDA...
D.
You could alternate change to XAR as example... then CRK2 is for sure valid to update to DSA1...
Summary...
OWN RISK! :angel:
Best Regards

ok now I know at least why I don't have an update. Why I have this version of XEO firmware will remain a mystery. Either way, thanks a lot for your help. You are great. I wait some days and if i didn't receive any update i change to XAR and back to XEO after update

fawazjet123 said:
Click to expand...
Click to collapse
Great! This is very helpful for me at the moment!