Related
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
I have been searching for a way to root my Blu Studio 5.0 LTE - which doesn't seem Vulnerable to framaroot.
after 3 days of non stop searching and trying the basic one-clicks as well as trying a number of commands through terminal I have finally found one to root my device. Here is a bit of information on my device.
Model #: Studio 5.0LTE
Android Version: 4.3
Baseband Version: TBW599010_9520_LTE_V0104
ROM: Original Factory Shipped 4.3 - Will backup then unroot - update and see if it still works then post back
I am fairly new to posting to xda, but I have been using XDA since htc google G1 came out... and haven't used anything but androids for myself since... so thank you all and hopefully someone will be able to use this method that i found...
Note: I am not developer of the software that is used in this posting - and I am not responsible for any damage or warranty status that my be negated as a result of the use of this tutorial! This tutorial has possibility to brick your phone, which neither myself nor providers of the root software are responsible .
Note2: I have contacted Shuame about posting their software on alternate site and they have not responded - if they request me to though, I will remove file and post link.
First of all let me just inform you that this will remove the Messaging app from your phone - I haven't hacked the file to see what commands it's running but from what I can tell is they have exploited the sms app and in process of root the app is removed.
You will need - Blue drivers which you can download here - attached
{You can install the sdk and drivers with installer or unpack the exe and using computer management install the drivers within the folder.View attachment ADB-Driver-v1.4.2.zip
Then you can download the installation file for the one click type root method - virus free - attached below cause im not allowed to post links yet - but install the program - chinese mostly translated but follow few steps to install then after its rooted you will see it say on screen rooted and give you options.
Then you can either download from play store or from attached APK for messaging.View attachment 3156953
There you go - root can be checked with any software - I am still working on what cwm will work and will update - hope this helps!
Thanks a lot Great Work :good::good::good:
That saved me a lot of time. It worked perfectly. although I would like to add a few points
1. For me it didn't delete the messaging app so it was great
2. after rooting, I installed supersu from play store, restarted and then deleted the kinguser app
3. installed adfree to remove ads
4. In my case, the genius root didn't seem to work the first time since the phone was in MTP setting. As soon as I changed USB setting to storage the program worked
I have link to some custom roms for this phone from a different forum, let me find the links again and I will update.
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Ok found the links
well seems like I cant post any links until , I have 10 posts ..
but it is there on google plus
It would be great if you can make something out of these links .
---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------
FYI: This phone is a clone of k-touvh touch3 and there is a custom rom for the other phone. Not sure about the recovery or CWm
memory swap
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
vsmartguy said:
Thanks a lot Great Work :good::good::good:
That saved me a lot of time. It worked perfectly. although I would like to add a few points
1. For me it didn't delete the messaging app so it was great
2. after rooting, I installed supersu from play store, restarted and then deleted the kinguser app
3. installed adfree to remove ads
4. In my case, the genius root didn't seem to work the first time since the phone was in MTP setting. As soon as I changed USB setting to storage the program worked
I have link to some custom roms for this phone from a different forum, let me find the links again and I will update.
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Ok found the links
well seems like I cant post any links until , I have 10 posts ..
but it is there on google plus
It would be great if you can make something out of these links .
---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------
FYI: This phone is a clone of k-touvh touch3 and there is a custom rom for the other phone. Not sure about the recovery or CWm
Click to expand...
Click to collapse
You know, I heard that on the blu lte google+ page but I also heard that the roms were not completely working right. Something about the GPS doesn't quite work right when doing that, but I'm still looking as well
compary said:
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
Click to expand...
Click to collapse
I didn't have to do anything with the swapping of memory... i'm not sure what you mean, but I was able to install xposed and at least fix some of the lame inabilities of this ROM - including apps to sd
I think user "company" is talking about the fact that on other devices with 4GB or lower ROM space, developers have figured out a way swap sd card with internal sd card so now you have a lot more space to install apps. For example Lg f6 forum has large thread about this. Obviously it needs a rooted phone to get the swap to work.
---------- Post added at 11:33 PM ---------- Previous post was at 11:07 PM ----------
compary said:
Just curious have you figured out how to swap the memory with the SD card? Link 2 SD doesn't seem to work neither does editing the vol.fs file
Click to expand...
Click to collapse
I tried using the script on LG F6 forum but it didn't work. spent quite sometime to do debugging and this is what I have figured out
1. Internal naming of disk space is different between the phones
2. Also the block space assigned in my case was different
This is the 11extsd2internals script for LG F6 ( you need to follow all the previous steps like installing unitinit.apk , smanager etc)
sleep 2
mount -o remount,rw /
mkdir -p /data/internal_sd
mount -o bind /storage/sdcard0 /data/internal_sd
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /storage/sdcard0
mount -o bind /data/internal_sd /storage/external_SD
I think if we change it to this, it might work. Although I am not going to try this out untill I have CWM recovery for this device ( added comments).
#######################
# Warning this is untested , try at your own risk
sleep 2
# this will remount all the partitions again with read write permission
mount -o remount,rw /
# create an empty temp directory to link the internal sd card to it
mkdir -p /data/internal_sd
#mount old-dir new-dir. Bind the original space to the temp directory
mount -o bind /storage/emulated/legacy /data/internal_sd
# Now read the SD card ( I got 179:66 when I put a 64GB sd card). Read both vfat and exfat
mount -t vfat -o umask=0000 /dev/block/vold/179:66 /storage/emulated/legacy
mount -t exfat -o umask=0000 /dev/block/vold/179:66 /storage/emulated/legacy
# Once we have mounted the sd card , swap the internal memory to external memory
if mount | grep vold/179:66; then
mount -o bind /data/internal_sd /storage/external_SD
fi
chown system /data/media/0
#############################
As I said, This is untested and I am not going to try it out for the time being but if someone want to use this and update if this works
vold fs
# 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. dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
This is all it shows
I don't think we can make changes to vold.fs to fix the low memory issue.
It has to be done through either ROM support or making fixes to the init script as I posted.
Anyways if someone can figure out a way to put recovery CWM or TWRP on this phone , I can start playing around with the storage fixes.
I've tried all kinds of root and nothing is working. I'm on V10_generic for the build number. Any other root options? also please an os x or linux root option as i don't have a windows machine. I hope we can find something soon. thanks y'all
blu studio 5.0 lte y530q
I can not flash the mobile blu studio 5.0 lte y530q, Help me find firmware for it and for firmware custom recovery, turns off radio module and the extremely hot processor.
Thank you in advance for your help.
droidkeyboardfan12 said:
I've tried all kinds of root and nothing is working. I'm on V10_generic for the build number. Any other root options? also please an os x or linux root option as i don't have a windows machine. I hope we can find something soon. thanks y'all
Click to expand...
Click to collapse
Yep. King Root Dot net, v.4.6.2....
can you help me with the QCN file for BLU Y530Q please
tomelich said:
can you help me with the QCN file for BLU Y530Q please
Click to expand...
Click to collapse
I did not fix this phone model and threw it away, sorry, I can't help you at all.
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:
My phone fell down before 2 days and from that time onwards the hadware navigation keys are not working. Everything else is working fine in the display. I tried flashing official MIUI global or developer rom, still it is not working. Currently I am using on-screen navigation keys. Any solution guys?
1）add build prop
qemu.hw.mainkeys=0
2）delete all keys Atmel_maXTouch_Touchscreen.kl
# 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
Click to expand...
Click to collapse
3）reboot
@Ost268 I think this disables the hardware keys. But my hardware keys are already disabled , I need to enable them.They are not working.
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.