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:
Related
..........
Well, I found this thread, might as well reply... I'm no ARM expert, but I think the problem is that ARMv6j supports these instructions only while compiling in 'arm' mode, not while compiling in 'thumb' mode. At least, that's my reading of the ARM developer manual thingy:
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204f/Cihbghef.html
What's worked for me is force-compile any offending files in arm mode like this:
Code:
LOCAL_SRC_FILES := AudioFlinger.cpp.arm
i.e. adding '.arm' after the file name in the Makefile (don't rename the files though). Alternatively, there's
Code:
LOCAL_ARM_MODE := arm
which disables thumb for the entire module.
Hi guys,
I've got another one for you. I've compiled the LiME (Linux Memory Extractor) module for fun. You can use this to make a full raw RAM dump. Unlike viewmem and other utilities which are limited to /dev/mem and /dev/kmem, this will give you an unrestricted RAM dump for examination and research. You can find more information at LiME's Google Code page.
THIS MODULE WILL ONLY WORK ON THE NC2 KERNEL!
To use:
Copy lime.ko to /sdcard
Code:
insmod /sdcard/lime.ko "path=/sdcard/ram.lime format=lime"
From there you can copy via USB the dump to your computer. You can also do a TCP dump over network, but I won't explain that here. Raw format is also available, but I prefer lime for a number of reasons.
Download here
Thanks to @Surge1223 and @BeansTown106
Shout out to @darkspr1te and @E:V:A also.
And a resentful thanks to Samsung Open Source center for releasing NC4 source months later...
Enjoy!
(Sorry moderators in advance, I wasn't quite sure where to post this.)
Great! But, since you've already jumped through all the compilation hoops, perhaps you can also give a brief description how to compile this for other kernels? (or what you did on your own.)
E:V:A said:
Great! But, since you've already jumped through all the compilation hoops, perhaps you can also give a brief description how to compile this for other kernels? (or what you did on your own.)
Click to expand...
Click to collapse
That will be a rather extensive write-up, perhaps when I get some more time. That would require a tutorial on setting up an entire build environment, which as we know, doesn't always play nicely
E:V:A said:
Great! But, since you've already jumped through all the compilation hoops, perhaps you can also give a brief description how to compile this for other kernels? (or what you did on your own.)
Click to expand...
Click to collapse
cd to directory with lime source the type make after editing the makefile to reflect something similar to the one I use below. This assumes one has kernel compiled already.
Edit to reflect your build environment and make sure your paths are set up beforehand (i.e., sudo gedit ~/.bashrc , ~/.bash_profile or ~/.profile etc)
Makefile used:
obj-m := lime.o
lime-objs := tcp.o disk.o main.o
KDIR := /home/surge/android
KVER := $(shell uname -r)
PWD := $(shell pwd)
CCPATH := /home/surge/android/arm-eabi-4.7/bin
default:
$(MAKE) ARCH=arm CROSS_COMPILE=$(CCPATH)/arm-eabi- EXTRA_CFLAGS=-fno-pic -C $(KDIR) M=$(PWD) modules
$(MAKE) tidy
tidy:
rm -f *.o *.mod.c Module.symvers Module.markers modules.order \.*.o.cmd \.*.ko.cmd \.*.o.drm -rf \.tmp_versions
clean:
Click to expand...
Click to collapse
Environmental variables used:
export JAVA_HOME=/usr/lib/jvm/java-7-oracle
export PATH=$PATH:$JAVA_HOME/bin
export PATH=$PATH:~/android/arm-eabi-4.7/bin
export CROSS_COMPILE=arm-eabi-
Click to expand...
Click to collapse
Sent from my SCH-I545 using XDA Premium 4 mobile app
Wait what does this do?
It makes dumps all your RAM into an image file.
Hi,
by any chance does anyone have module for Nexus 4 or 5?
Hello,
I'm a newbie dev, trying my hands on deving a tablet called the Galaz A1. Its a Tegra 4 tablet. Anyway, I'm down to making a custom recovery but the only thing that stops me is that I keep getting an error saying the recovery is too big and it deletes the file. Here is what my BoardConfig shows
Hello, I seem to be having the same issue.
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
When i pull the files via dd both recovery and boot are 8 to 8.4 mb. I need to raise the size level for the B_RECOVERYIMG_PARTITION_SIZE to 9. I believe this would completely clear up my issue. However, I'm absolutely no good with hex. And also, if I increase the size of the recovery partition should I be increasing the size of the FLASH_BLOCK_SiZE as well? Thanks. for any help or feedback.
Hi! I am in need of 4 partition sizaes in decimal:
BOARD_BOOTIMAGE_PARTITION_SIZE :=
BOARD_RECOVERYIMAGE_PARTITION_SIZE :=
BOARD_SYSTEMIMAGE_PARTITION_SIZE :=
BOARD_USERDATAIMAGE_PARTITION_SIZE :=
I assume I need to use ADB somehow to get these sizes, so what command do I use to get these partition sizes?
Thanks
NateDev473 said:
Hi! I am in need of 4 partition sizaes in decimal:
BOARD_BOOTIMAGE_PARTITION_SIZE :=
BOARD_RECOVERYIMAGE_PARTITION_SIZE :=
BOARD_SYSTEMIMAGE_PARTITION_SIZE :=
BOARD_USERDATAIMAGE_PARTITION_SIZE :=
I assume I need to use ADB somehow to get these sizes, so what command do I use to get these partition sizes?
Thanks
Click to expand...
Click to collapse
Download Diskinfo app from play store. Go to Diskinfo app setting and check all options in the settings.
You get partitions name with their sizes.
If it helped. Please thank me.
Ashwinrg said:
Download Diskinfo app from play store. Go to Diskinfo app setting and check all options in the settings.
You get partitions name with their sizes.
If it helped. Please thank me.
Click to expand...
Click to collapse
Awesome, thanks!
Hey guys, I am trying to get the retrofit dynamic partition for my phone which with A/B By Default But Not With Dynamic Partition.
In That I Don't know the values of
BOARD_ODMIMAGE_PARTITION_RESERVED_SIZE :=
BOARD_PRODUCTIMAGE_PARTITION_RESERVED_SIZE :=
BOARD_SYSTEMIMAGE_PARTITION_RESERVED_SIZE :=
BOARD_SYSTEM_EXTIMAGE_PARTITION_RESERVED_SIZE :=
BOARD_VENDORIMAGE_PARTITION_RESERVED_SIZE :=
How Can I Know This Values and Also Tell Me More About Dynamic Partition Implementation.
Thank You