i have setup a sipdroid, ipkall, pbexes, and sipsorcery account. however when i try and make a call it keeps asking for a password...?
i am not sure what i have done wrong and have followed the guide on this site and was wondering if someone could help?
also not sure how i need to configure gv or if that may have anything to do with it?? cause when you call my gv number it goes directly to gv and does not ring my mobile
Ok I have just told gv to use every time I make a call. Wasn't sure if that was something I should do or not? Also the password I entered for all my accounts this time worked, yet it said the call could not be completed?
***Edit***
Ok I think I have gotten alot further... It is no longer asking me for a password and is just now saying the call cant be completed as dialed. I have checked my sipsorcery account and it appears that im having an error loading my dial plan??? here is a copy of the plan i have below. also how can i get google to verify my sip number to forward my gv calls to the correct number?
appreciate all the help as i was just transferred to amsterdam and was looking for a low cost way to keep in touch with family and friends.
PHP:
# Copyright(c) 2010 Mike Telis
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations under
# the License.
# Click "View raw file" in the lower right for the best copy/paste view
AREA_CODE = '843' # my area code
GV_USER = '*********' # my GV e-mail address ([email protected])
GV_PASS = '*********' # my GV password
CB_NUMBER = '12064247339' # my 11-digit SIP number (only one)
SPEED_DIAL = { # my speed dial numbers
'1' => '19879879876', # Mom
'123' => '12345678901', # Work
'45' => '17479876543', # Gizmo BFF
'411' => '8004664411', # Google 411
'266' => '[email protected]', # CNN Headlines
}
begin
sys.Log "** Call from #{req.Header.From} to #{req.URI.User} **"
if sys.Out # if outbound call
num = req.URI.User.to_s # Get a string copy of the number to dial
num = SPEED_DIAL[num] || num # Substitute with speed dial entry, if any
case num
when /@/ then sys.Dial num # URI dialing
when /^[2-9]\d{6}$/ # Local call, 7-digit number
num = '1'+ AREA_CODE + num # prefix it with country and area code
when /^[01]?([2-9]\d{9})/ # US number with or without country code
num = '1' + $1 # add country code and truncate number to 10-digit
when /^(011|00|\+)(\d{9,})/ # international number
num = '+' + $2 # GoogleVoiceCall works with '+' prefix only
else sys.Respond 603, 'Wrong number, check & dial again'
end
sys.Log "Calling #{num} via Google Voice"
sys.GoogleVoiceCall GV_USER, GV_PASS, CB_NUMBER, num, '.*', CB_NUMBER =~ /^1747/ ? 7 : 1, 30
else # sys.Out
sys.Dial "#{sys.Username}@local"
end
rescue
sys.Log("** Error: " + $!) unless $!.to_s =~ /Thread was being aborted./
end
Hello everyone,
I come to ask for help because I can not root my smartphone.
This is a 4G wiko ridge.
Qualcomm quad core 1.2Ghz processor
2Gb RAM and 16GB ROM
Rear Camera 13 Mp and before 5 Mp.
Android 4.4.4
Thank you for your help
chuppito said:
Hello everyone,
I come to ask for help because I can not root my smartphone.
This is a 4G wiko ridge.
Qualcomm quad core 1.2Ghz processor
2Gb RAM and 16GB ROM
Rear Camera 13 Mp and before 5 Mp.
Android 4.4.4
Thank you for your help
Click to expand...
Click to collapse
Up please
chuppito said:
Up please
Click to expand...
Click to collapse
Hi,
Now I have one Ridge FAB 4G... Kingroot and KingrootPC don't work for rooting.
Note: To install ADB drivers you can use Universal Android USB Driver (http://adbdriver.com/) or 15 seconds ADB Installer (http://forum.xda-developers.com/showthread.php?t=2588979)
I'm searching for rooting with similar devices, like ZTE Nubia V5 MAX
Hi,
Searching for a Custom Recovery, I try several from other similar devices... The only one with minimal success (but not working) is this from Cubot Zorro: http://www.needrom.com/download/english-cwm-for-cubot-zorro-001/
If you extract the cwm.img and execute it from FASTBOOT mode with command:
Code:
$ fastboot boot cwm.img
Then you boot to this recovery... but the screen is odd, also no USB support.
WARNING: Not flash any recovery.img from other devices!
manos78 said:
Hi,
Searching for a Custom Recovery, I try several from other similar devices... The only one with minimal success (but not working) is this from Cubot Zorro: http://www.needrom.com/download/english-cwm-for-cubot-zorro-001/
If you extract the cwm.img and execute it from FASTBOOT mode with command:
Code:
$ fastboot boot cwm.img
Then you boot to this recovery... but the screen is odd, also no USB support.
WARNING: Not flash any recovery.img from other devices!
Click to expand...
Click to collapse
Hi, thank you for recovery is a good start. I mainly need to give him the superuser (root) privileges.
thank you again
chuppito said:
Hi, thank you for recovery is a good start. I mainly need to give him the superuser (root) privileges.
thank you again
Click to expand...
Click to collapse
Hi Chuppito!
This recovery DON'T works! Painting in screen is odd, and the USB port for access using ADB is disabled (or don't work). But, it really boots and executes. My objective is found one custom recovery (from other device) with sufficient functionality to mount rw the /system partition and copy SuperSU.apk to it. At time this is not done!
However this is a good start, because sources and tools from a similar devices can be useful for stating.
I hope soon an experienced developer gets this device and provides some custom recovery... wihtout root any Android device is... useless!
Hi,
Wikomobile has already released the KERNEL source code. Go to: http://www.wikogeek.com/ and select "Ridge 4G".
I hope someone can compile a custom kernel based on this! :fingers-crossed:
And waiting for stock firmware published in: http://androidxda.com/download-wiko-stock-rom-models
Hi,
The "sources" are only for "Ridge 4G". Hovewer, the config file identifies also the "Ridge Fab 4G". Internal names are:
- Ridge 4G: l5510
- Ridge Fab 4G: l5320
After some tries for compile, I can't do it! The problem is that scripts likes to compile anything in the firmware... but I need only kernel/recovery. I appreciate if someone with experience can check this sources.
I hope soon someone can found a method for rooting these devices. Without root, the device is competly useless!!! :crying:
Hi,
More info about using the recovery from another device: the fstab file from sources of Ridge 4G, and the fstab from the recovery of the Cubot Zorro are different. So perhaps the only solution is compile from scratch a custom recovery using the sources provided by Wiko. I hope soon they publish also the sources for Ridge FAB.
**
Hi,
I hope someone with sufficient experience can compile TWRP for this device.
General guide at: http://forum.xda-developers.com/showthread.php?t=1943625
Files "/android/device/qcom/l5510/BoardConfig.mk" and "/android/device/qcom/l5510/recovery.fstab" are found in the source code
http://geek.wikoplus.com/index.php?tel=14bfa6bb14875e45bba028a21ed38046
BoardConfig.mk:
Code:
# Copyright (C) 2011 The Android Open-Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# config.mk
#
# Product-specific compile-time definitions.
#
ifeq ($(TARGET_ARCH),)
TARGET_ARCH := arm
endif
BOARD_USES_GENERIC_AUDIO := true
USE_CAMERA_STUB := true
-include $(QCPATH)/common/msm8916_32/BoardConfigVendor.mk
TARGET_COMPILE_WITH_MSM_KERNEL := true
#TODO: Fix-me: Setting TARGET_HAVE_HDMI_OUT to false
# to get rid of compilation error.
TARGET_HAVE_HDMI_OUT := false
TARGET_USES_OVERLAY := true
NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3
TARGET_NO_BOOTLOADER := false
TARGET_NO_KERNEL := false
TARGET_NO_RADIOIMAGE := true
TARGET_NO_RPC := true
TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := cortex-a53
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HARDWARE_3D := false
TARGET_BOARD_PLATFORM := msm8916
TARGET_BOARD_PLATFORM_VENDOR_COMMON := msm8916_32
TARGET_BOOTLOADER_BOARD_NAME := msm8916
BOARD_KERNEL_BASE := 0x80000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_KERNEL_TAGS_OFFSET := 0x01E00000
BOARD_RAMDISK_OFFSET := 0x02000000
# Enables Adreno RS driver
OVERRIDE_RS_DRIVER := libRSDriver_adreno.so
# Shader cache config options
# Maximum size of the GLES Shaders that can be cached for reuse.
# Increase the size if shaders of size greater than 12KB are used.
MAX_EGL_CACHE_KEY_SIZE := 12*1024
# Maximum GLES shader cache size for each app to store the compiled shader
# binaries. Decrease the size if RAM or Flash Storage size is a limitation
# of the device.
MAX_EGL_CACHE_SIZE := 2048*1024
# Use signed boot and recovery image
#TARGET_BOOTIMG_SIGNED := true
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE := ext4
BOARD_PERSISTIMAGE_FILE_SYSTEM_TYPE := ext4
# zgm remove - console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0
#BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900
.sdhci
BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci
BOARD_KERNEL_SEPARATED_DT := true
BOARD_EGL_CFG := device/qcom/l5510/egl.cfg
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x02000000 #32M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x02000000 #32M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1702887424 #1G+600M
#BOARD_USERDATAIMAGE_PARTITION_SIZE := 5122795872 #8GB
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12936655872 #16GB
BOARD_CACHEIMAGE_PARTITION_SIZE := 274726912 #134217728
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
# Enable suspend during charger mode
BOARD_CHARGER_ENABLE_SUSPEND := true
# Add NON-HLOS files for ota upgrade
ADD_RADIO_FILES ?= true
# Added to indicate that protobuf-c is supported in this build
PROTOBUF_SUPPORTED := true
TARGET_USE_QCOM_BIONIC_OPTIMIZATION := true
TARGET_USES_ION := true
TARGET_USES_NEW_ION_API :=true
TARGET_USES_QCOM_BSP := true
TARGET_RECOVERY_UPDATER_LIBS := librecovery_updater_msm
TARGET_INIT_VENDOR_LIB := libinit_msm
TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/
#Add support for firmare upgrade on 8916
HAVE_SYNAPTICS_I2C_RMI4_FW_UPGRADE := true
#Add By YangRujin <2014.10.10> : support for enabling diag/adb port during pwroff chg
ENABLE_ADB_DIAG_IN_PWROFF_CHARGE := true
#Add By MickyHe <2014.11.11> : support for GTS widevine DRM
BOARD_WIDEVINE_OEMCRYPTO_LEVEL := 3
PRODUCT_BOOT_JARS := $(subst $(space),:,$(PRODUCT_BOOT_JARS))
recovery.fstab:
Code:
# Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#<FFBAKK-335><20141210><encryption>xusong
#device mount point fstype [device2] [length=]
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,length=-16384
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
Please, help us to compile a Custom Recovery! :crying:
Hi,
No experienced developer likes to help us? :crying:
Hello,
I return to the subject, I still looking but I can not find.
Is someone about to try to find a solution?
thank you
chuppito said:
Hello,
I return to the subject, I still looking but I can not find.
Is someone about to try to find a solution?
thank you
Click to expand...
Click to collapse
What is the date your kernel was made?
Sent from my A0001 using XDA Free mobile app
Kernel Version
3.10.28
[email protected]#1
Fri Mar 13 13:30:47 CST 2015
chuppito said:
Kernel Version
3.10.28
[email protected]#1
Fri Mar 13 13:30:47 CST 2015
Click to expand...
Click to collapse
Wow, that's an extremely new kernel! Lol. Anyways I was going to suggest trying Towelroot but most kernels made after June 3rd, 2013 have been patched to the futex exploit but I've had limited success on a few phones with kernels made after that date.
Good luck!
Sent from my A0001 using XDA Free mobile app
towelroot v1 and 3 do not work
Hi,
The "exploit" way ins't a solution at the moment because no new exploits have found for the last Android kernel versions.
The only valid way is a Custom Recovery. At time, we're waiting for the flashing version of the stock ROM (Wiko don't published it yet!). However, we have some source code and we need to obtain a minimal custom recovery for mount system r/w and copy to it SuperSU. This is the only way at time for rooting this device!
manos78 said:
Hi,
The "exploit" way ins't a solution at the moment because no new exploits have found for the last Android kernel versions.
The only valid way is a Custom Recovery. At time, we're waiting for the flashing version of the stock ROM (Wiko don't published it yet!). However, we have some source code and we need to obtain a minimal custom recovery for mount system r/w and copy to it SuperSU. This is the only way at time for rooting this device!
Click to expand...
Click to collapse
Thank you, i think the flashing rom of the stock wiko will be in line with the android version of L
Thank you
chuppito said:
Thank you, i think the flashing rom of the stock wiko will be in line with the android version of L
Click to expand...
Click to collapse
:crying: For this, we need to wait until the end of the summer!
I hope Wiko will publish the current ROM in his site soon. With the current stock "recovery.img" we can try to port the custom recovery from other device to the Ridge, because the sources are incomplete and don't compile. We need the help of the OEM! :angel:
Hope they will be useful to get Xiaomi remote working with Nexus player
Vendor_2717_Product_32b0.kl and Vendor_2717_Product_3200.kl
# Copyright (C) 2013 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# BLE Remote layout file for xiaomi Remote keyboards.
# This file is intentionally very generic and is intended to support a broad rang of keyboards.
# Do not edit the generic key layout to support a specific keyboard; instead, create
# a new key layout file with the required keyboard configuration.
#
key 158 BACK
key 127 MENU
key 108 DPAD_DOWN
key 103 DPAD_UP
key 102 HOME
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 235 SWITCHRESOLUTION
key 28 ENTER
key 116 POWER WAKE
key 97 DPAD_CENTER
key 232 DPAD_CENTER
does this works for you? I add this keylayout to my NP but it doesn´t works. For Nvidia works, with the issue that you have to pair every time when the Nvidia shut off.
thanks for great information..
mposadzy said:
Hope they will be useful to get Xiaomi remote working with Nexus player
Vendor_2717_Product_32b0.kl and Vendor_2717_Product_3200.kl
# Copyright (C) 2013 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# BLE Remote layout file for xiaomi Remote keyboards.
# This file is intentionally very generic and is intended to support a broad rang of keyboards.
# Do not edit the generic key layout to support a specific keyboard; instead, create
# a new key layout file with the required keyboard configuration.
#
key 158 BACK
key 127 MENU
key 108 DPAD_DOWN
key 103 DPAD_UP
key 102 HOME
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 235 SWITCHRESOLUTION
key 28 ENTER
key 116 POWER WAKE
key 97 DPAD_CENTER
key 232 DPAD_CENTER
Click to expand...
Click to collapse
Hey, do you know hot to out the Xiaomi Bluetooth remote in pairing mode?
Can anyone confirm that this is working? @mposadzy, @icthamza3
HTML:
Hi my names joe and im very new to this forum and editing in gerneral im on 4.4 and am trying to swap external to internal memory cause my phone only has a little over a gig and i want to play some games that are 2 gigs, i bought a 32 gig card and want to swap them i went to edit my void.fstab bt when i opened it looked nothing like i saw in other posts also i tryed the programs external 2 ibternal and a couple other with no avail. Please help this is what i get when opening it in es explorer with rriotoot access
# Copyright (c) 2012, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
/devices/msm_sdcc.2/mmc_host auto vfat defaults voldmanaged=external_SD:auto
Thanks for the help in advance guys
Service codes:
* # 0 * # Basic tests of devices in the device.*(Mandatory when buying!)*
* 7353 # Another menu with tests.*(Mandatory when buying!)*
* # 06 # IMEI.*
* # 0228 # Network information, full battery information.*
* # 0283 # Data connection test (Loopback Test).*
* # 1111 # FTA SW Version.*
* # 1234 # Firmware version (AP, CP, CSC).*
* # 2222 # Information on the revision of iron.*
* # 2663 # Information about the firmware of touch input devices.*
* # 22558463 # Reset talk time.*
* # 34971539 # Information about camera modules and updating their firmware.*
* # 7284 # UART and USB modes of operation (in modem or multimedia mode).*
* # 9090 # Service Mode.*
* # 9900 # Dump of system data (kernel logs, etc.).
* # 0011 # NET Monitor.*
* 0283 # Convenient microphone test, and headset microphone test.*
* # 34971539 # Information about camera modules and updating their firmware.*
* # 2767 * 2878 # SoftReset.*The settings will be reset to the factory settings, but the data will be saved.*
* # 2767 * 3855 # HardReset.*Restoring the system factory settings, clears all system information, installed programs, contacts, SMS.*Data on memory cards and SIM is not deleted.*
* # 87976633 # FactoryReset.*The same HardReset without any questions.*
* # 12580 * 369 # Production date.*
Thanks for the info.
Though code *7353# does not work on my device.
i just got a factory unlocked s10 plus and none of the hidden codes work?im on Pie 9, verizon sim.i have walked into best buy and tried some codes hidden secret menu and it did work on there s10 plus.
SpanKyM3 said:
i just got a factory unlocked s10 plus and none of the hidden codes work?im on Pie 9, verizon sim.i have walked into best buy and tried some codes hidden secret menu and it did work on there s10 plus.
Click to expand...
Click to collapse
cuz vzw blocks hiddenmenu/keystr to an extent.. u need system privs to enable them which will allow more but even then its only capable of whats allowed and ot varies by carrier and is dependent on whats allowed.. theres a keystrings.dat file in each carriers csc directory but its encryoted so u cant see exactly what keystrings are available.