FORUMS

Google No Longer Sending Calendar SMS Notifications

In a not entirely surprising move, Google announced that it’s putting an … more

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

Android M Preview Images – XDA TV

Android M preview images are available. That and much more news is covered by Jordan when he … more

Alacatel C1 4015

Thanks Meter: 7
 
By silver_619, Junior Member on 11th July 2014, 01:06 AM
Post Reply Subscribe to Thread Email Thread
22nd May 2015, 05:19 PM |#111  
Junior Member
Thanks Meter: 0
 
More
Please help
Quote:
Originally Posted by darren1

Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.


Very simple to use, just install and follow instructions.

Please help, I have an alcatel pop c1 from uk ee and I tried to install kitkat 4.4.2 rom on but it got stuck on the alcatel loading screen and I messed on a bit in the cwm settings and I even tried wiping everything that was wipeable and then I installed the stock ee rom and it is still stuck on the boot screen. What can I do now? PLEASE HELP!
 
 
23rd May 2015, 07:55 PM |#112  
Senior Member
Thanks Meter: 57
 
More
Quote:
Originally Posted by Chung2015

Please help, I have an alcatel pop c1 from uk ee and I tried to install kitkat 4.4.2 rom on but it got stuck on the alcatel loading screen and I messed on a bit in the cwm settings and I even tried wiping everything that was wipeable and then I installed the stock ee rom and it is still stuck on the boot screen. What can I do now? PLEASE HELP!

Download Mobile Upgrade S from here

http://www.alcatelonetouch.com/globa...uch_idolx.html

and install on your PC. Very straightforward to use.
24th May 2015, 03:25 PM |#113  
Senior Member
Thanks Meter: 5
 
More
whats the latest rom working on alcatel 4015d?
28th May 2015, 01:10 AM |#114  
xdarthanonx's Avatar
Junior Member
Thanks Meter: 5
 
More
Exclamation Carliv Touch Recovery v2.7 for Alcatel POP C1 4015

SCREENSHOTS


KEY FILES


recovery.fstab
Code:
# mount point   fstype      device                  [device2]
# Modified by xdarthanonx 27/05/2015
/boot           emmc        /dev/bootimg
/misc           emmc        /dev/misc
/recovery       emmc        /dev/recovery
/nvram          emmc        /dev/nvram
/uboot          emmc        /dev/uboot
/system         ext4        /dev/block/mmcblk0p7
/data           ext4        /dev/block/mmcblk0p9
/cache          ext4        /dev/block/mmcblk0p8
/custpack       ext4        /dev/block/mmcblk0p5
#/mobile_info    ext4        /dev/block/mmcblk0p6
#/protect_f      ext4        /dev/block/mmcblk0p2
#/protect_s      ext4        /dev/block/mmcblk0p3
/sdcard         vfat        /dev/block/mmcblk1p1    /dev/block/mmcblk1
/sd-ext         auto        /dev/block/mmcblk1p2
default.prop
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
# Modified by xdarthanonx 28/05/2015

# Run adbd as root
ro.secure=0
ro.debuggable=1

ro.allow.mock.location=1
persist.mtk.aee.aed=on
persist.sys.usb.config=mass_storage,adb
persist.sys.root_access=1
persist.service.acm.enable=0
ro.bootloader.mode=download
ro.mount.fs=EXT4

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=Jelly Bean
ro.build.version.incremental=v6CGJ-0
ro.custom.build.version=v6CGJ-0
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Tue Jul 15 09:09:57 CST 2014
ro.build.date.utc=1405386597
ro.build.type=user
ro.build.user=int
ro.build.host=int-185
ro.build.tags=release-keys
ro.product.model=ONE TOUCH 4015D
ro.product.display.model=ONE TOUCH 4015D
ro.product.usb.model=ALCATEL ONE TOUCH POP C1
ro.product.brand=TCT
ro.product.name=Yaris35
ro.product.device=Yaris35_GSM
ro.product.board=Yaris35
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=TCT
ro.wifi.channels=
ro.board.platform=mt6572
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Yaris35_GSM
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Yaris35-user 4.2.2 JDQ39 v6CGJ-0 release-keys
ro.build.fingerprint=TCT/Yaris35/Yaris35_GSM:4.2.2/JDQ39/v6CGJ-0:user/release-keys
ro.build.characteristics=default
# end build properties

#
#jrd sys properties
#
qemu.hw.mainkeys=1
ro.product.locale.language=en
ro.product.locale.region=US
ro.power.key.default.behavior=1
ro.com.google.clientidbase=android-alcatel
ro.def.screen.brightness=75
persist.sys.timezone=UTC
keyguard_no_require_sim=true
usb.manufacturer=TCT
sys.usb.product=ALCATEL ONE TOUCH POP C1
ro.product.resolution=320*480
ro.product.distinguish=yaris35

# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB3.MP.V1
ro.mediatek.platform=MT6572
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB3.MP
ro.mediatek.version.sdk=1
# end mediatek build properties

#
# system.prop for generic sdk
#
ro.opengles.version=131072
ro.kernel.zio=38,108,105,16

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.alsps_ctp=true
ro.yaris_s_project=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.rc
Code:
# Modified by xdarthanonx 28/05/2015

on early-init
    start ueventd

on init
    export PATH /sbin
    export ANDROID_ROOT /system
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard

    symlink /system/etc /etc

    mkdir /boot
    mkdir /misc
    mkdir /storage
    mkdir /sdcard
    mkdir /internal_sd
    mkdir /external_sd
    mkdir /sd-ext
    mkdir /custpack
    mkdir /datadata
    mkdir /emmc
    mkdir /system
    mkdir /data
    mkdir /cache
    mount /tmp /tmp tmpfs

    chown root shell /tmp
    chmod 0775 /tmp

    write /sys/class/android_usb/android0/enable 0
    write /sys/class/android_usb/android0/idVendor 1BBB
    write /sys/class/android_usb/android0/idProduct 0165
    write /sys/class/android_usb/android0/functions mass_storage,adb
    write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
    write /sys/class/android_usb/android0/iProduct ${ro.product.model}
    write /sys/class/android_usb/android0/iSerial "0123456789ABCDEF"
    write /sys/class/android_usb/android0/enable 1

    #Mount mobile_info
    mkdir /mobile_info
    mount ext4 emmc@mobile_info /mobile_info wait commit=1,noauto_da_alloc

    #Mount protect_f
    mkdir /protect_f
    mount ext4 emmc@protect_f /protect_f wait commit=1,noauto_da_alloc

    #Mount protect_s
    mkdir /protect_s
    mount ext4 emmc@protect_s /protect_s wait commit=1,noauto_da_alloc

    #mount ext4 emmc@custpack /custpack wait commit=1,noauto_da_alloc

on boot

    ifup lo
    hostname localhost
    domainname localdomain

    class_start default

on property:sys.powerctl=*
    powerctl ${sys.powerctl}

service ueventd /sbin/ueventd
    critical

service recovery /sbin/recovery

service setup_adbd /sbin/setup_adbd
    oneshot

service adbd /sbin/adbd recovery
    disabled

# Recovery will start adb once it has checked the keys

on property:ro.debuggable=1
    #write /sys/class/android_usb/android0/enable 1
    #start adbd
    setprop service.adb.root 1

# Restart adbd so it can run as root
on property:service.adb.root=1
    write /sys/class/android_usb/android0/enable 0
    restart adbd
    write /sys/class/android_usb/android0/enable 1


Thanks:
Attached Files
File Type: img CTRecovery27.img - [Click for QR Code] (5.40 MB, 8 views)
Last edited by xdarthanonx; 28th May 2015 at 01:16 AM. Reason: fix mention
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes