FORUMS

Wink-Relay touchscreen runs android 4.3

5 posts
Thanks Meter: 5
 
By fintina, Junior Member on 5th January 2016, 04:53 AM
Post Reply Email Thread
24th October 2018, 09:11 PM |#51  
coder12's Avatar
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by JKSurf

Anybody have edison.zip? I need it.

Likewise. Anyone with a copy of edison.zip out there? I received a device that won't boot and I'd rather fix it than return it.
10th February 2019, 05:58 AM |#52  
Member
Thanks Meter: 6
 
More
It's been awhile - and I see there are some updates to unbricking this device. I'm coming back to fix my bootlooped device after seeing this youtube vid :
That said, I had extracted the edison.zip file and posted in a smart things thread : https://community.smartthings.com/t/...elay/40946/400

The edison file is here : https://mega.nz/#!UphkTLAb!t5KvopVZb...QHf9-USlr0_dFc

Good luck! If anyone knows how to get out of UBOOT and back to the ADB let me know please
10th February 2019, 07:02 AM |#53  
Member
Thanks Meter: 6
 
More
The information in this thread is very very helpful. The YouTube video I cite in my previous response is a MUST view - as that will provide ample guidance to unbrick your Wink Relay.

That said, I was stuck in an infinite boot loop - and it would load UBOOT over and over again. Through trial and error - this is what I did.
1. While your relay is LOOPING, cover up the Proximity Sensor and press the Top Switch Button.
2. Doing so should bring you to Recovery Mode
3. Wipe the Cache 3 Times
4. Delete and Reset Device 3 Times
5. Reboot device
6. Your Putty screen will start printing a bunch of gibberish.
7. Have the following copied to your clipboard : am start -n com.android.launcher/com.android.launcher2.Launcher
8. While your Putty is updating - keep pasting what is in line 7, and keep pressing Enter on your keyboard.
9. Hopefully, you will get lucky - and the Launch Screen will appear.
10. From there you can follow the rest of the guide in the aforementioned video.

Good luck!
9th May 2020, 07:30 AM |#54  
Junior Member
Thanks Meter: 0
 
More
Wink Subscription Service and their Imminent Demise
So.... Wink just recently announced they are going to start charging a subscription fee for the privilege of using their app, hub devices, and voice control in a few days. I'm certainly not going to start paying them $5 a month for what SmartThings and any number of other smart home ecosystems still do for free. If I was using the Wink Hub or Hub 2, I'd just trash it and get switch to something else, but I've got four of these Wink Relays in my home and they each act as 2 relay switches, a temperature sensor, a humidity sensor, a proximity sensor, an intercom, a touchscreen display running a locked down version of Android 4.3, and finally a Zigbee/Bluetooth/WiFi hub.

It sure would be nice if there was a custom ROM available that could free up all of that nice hardware from their stranglehold. I'm pretty sure nobody capable of making one cares at this point, but I figured I'd ask just in case. I'll be sad to have to replace them all. What a bunch of wasted money and hardware

Update:
It looks like there is already a Wink Relay Manager available on GitHub that "sends events to MQTT" and can be installed on a rooted Wink Relay via ADB, though the installation process looks complicated. Can you still root and access ADB for a fully upgraded Wink Relay?

Anyway, here is the GitHub link for the project:
***oops, I can't post links yet***

It might be nice to get an up to date tutorial or walkthrough in place for rooting and installing this Wink Relay Manager to help all the rats like me who are scurrying away from the sinking Wink ship.

It looks like there is also an integration available for SmartThings here:
***oops, I can't post links yet***
16th May 2020, 06:20 PM |#55  
Member
Thanks Meter: 6
 
More
Here's A Guide I Wrote To Help Migrate :)
Quote:
Originally Posted by Xenrid

So.... Wink just recently announced they are going to start charging a subscription fee for the privilege of using their app, hub devices, and voice control in a few days. I'm certainly not going to start paying them $5 a month for what SmartThings and any number of other smart home ecosystems still do for free. If I was using the Wink Hub or Hub 2, I'd just trash it and get switch to something else, but I've got four of these Wink Relays in my home and they each act as 2 relay switches, a temperature sensor, a humidity sensor, a proximity sensor, an intercom, a touchscreen display running a locked down version of Android 4.3, and finally a Zigbee/Bluetooth/WiFi hub.

It sure would be nice if there was a custom ROM available that could free up all of that nice hardware from their stranglehold. I'm pretty sure nobody capable of making one cares at this point, but I figured I'd ask just in case. I'll be sad to have to replace them all. What a bunch of wasted money and hardware

Update:
It looks like there is already a Wink Relay Manager available on GitHub that "sends events to MQTT" and can be installed on a rooted Wink Relay via ADB, though the installation process looks complicated. Can you still root and access ADB for a fully upgraded Wink Relay?

Anyway, here is the GitHub link for the project:
***oops, I can't post links yet***

It might be nice to get an up to date tutorial or walkthrough in place for rooting and installing this Wink Relay Manager to help all the rats like me who are scurrying away from the sinking Wink ship.

It looks like there is also an integration available for SmartThings here:
***oops, I can't post links yet***

Hi here's a guide I wrote to help ease the transition
https://community.home-assistant.io/...hubitat/196464
23rd May 2020, 07:17 PM |#56  
Junior Member
Thanks Meter: 0
 
More
Can anyone help me get my wink relay out of boot loop? I have tried the youtube method and can't get android to boot. I have downloaded the edison file but I don't know how to flash it. I am new to this so if there is a guide to follow to flash it through putty or adb please send it along. I have tried to connect to it through adb without success. I don't know if I am using the right commands.

This is what i see through putty terminal. Then it reboots and goes through all this again.

U-Boot 2009.08-00171-gb9851cb-dirty (Oct 17 2014 - 14:39:59)

CPU: Freescale i.MX6 family TO1.2 at 792 MHz
Thermal sensor with ratio = 186
Temperature: 51 C, calibration data 0x5975155f
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock : 66000000Hz
ipg per clock : 66000000Hz
uart clock : 80000000Hz
cspi clock : 60000000Hz
ahb clock : 132000000Hz
axi clock : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock : 396000000Hz
usdhc1 clock : 198000000Hz
usdhc2 clock : 198000000Hz
usdhc3 clock : 198000000Hz
usdhc4 clock : 198000000Hz
nfc clock : 24000000Hz
Board: i.MX6DL/Solo-SABRESD: unknown-board Board: 0x61012 [WDOG ]
Boot Device: MMC
I2C: ready
DRAM: 1 GB
MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
*** Warning - bad CRC or MMC, using default environment

In: serial
Out: serial
Err: serial
Net: got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc2(part 0) is current device

MMC read: dev # 2, block # 2048, count 9728 ... Card did not respond to voltage select!
MMC: block number 0x2e00 exceeds max(0x0)
0 blocks read: ERROR
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Card did not respond to voltage select!
mmc2 init failed
kernel @ 10808000 (4825656)
ramdisk @ 11800000 (238581)
kernel cmdline:
use boot.img command line:
console=ttymxc0,115200 init=/init video=mxcfb0:dev=lcd,mxcfb_dataimage_lcd,if=RGB666 video=mxcfb1ff video=mxcfb2ff fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale no_console_suspend=1

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 3.0.35 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #97 SMP PREEMPT Thu May 11 15:35:31 UTC 2017
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6DL/SOLO, silicon rev 1.2
PERCPU: Embedded 7 pages/cpu @c131e000 s6592 r8192 d13888 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 208128
Kernel command line: console=ttymxc0,115200 init=/init video=mxcfb0:dev=lcd,mxcfb_dataimage_lcd,if=RGB666 video=mxcfb1ff video=mxcfb2ff fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale no_console_suspend=1
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 379MB 378MB 64MB = 821MB total
Memory: 820432k/820432k available, 228144k reserved, 441344K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xfbe00000 - 0xffe00000 ( 64 MB)
vmalloc : 0xd9800000 - 0xf2000000 ( 392 MB)
lowmem : 0xc0000000 - 0xd9000000 ( 400 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc0044000 ( 240 kB)
.text : 0xc0044000 - 0xc08f6d0c (8908 kB)
.data : 0xc08f8000 - 0xc0984190 ( 561 kB)
.bss : 0xc09841b4 - 0xc0b14848 (1602 kB)
Preemptible hierarchical RCU implementation.
NR_IRQS:624
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
Set periph_clk's parent to pll2_pfd_400M!
arm_max_freq=1GHz
MXC_Early serial console at MMIO 0x2020000 (options '115200')
bootconsole [ttymxc0] enabled
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
CPU1: Booted secondary processor
Brought up 2 CPUs
SMP: Total of 2 processors activated (3162.11 BogoMIPS).
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
ram_console: got buffer at 3ff00000, size 100000
ram_console: found existing buffer, size 21174, start 21174
console [ram-1] enabled
brcm_wlan_init: start
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32050000, Cache size: 524288 B
bio: create slab <bio-0> at 0
mxs-dma mxs-dma-apbh: initialized
print_constraints: SPKVDD: 4200 mV
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
mc_pfuze 1-0008: ID: 0,Full lay: 2 ,Metal lay: 1
mc_pfuze 1-0008: FAB: 0 ,FIN: 0
print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1300 mV
print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV
print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1300 mV
print_constraints: PFUZE100_SW2: 800 <--> 3950 mV at 3300 mV
print_constraints: PFUZE100_SW3A: 400 <--> 1975 mV at 1500 mV
print_constraints: PFUZE100_SW3B: 400 <--> 1975 mV at 1500 mV
print_constraints: PFUZE100_SW4: 800 <--> 3950 mV at 3150 mV
print_constraints: PFUZE100_SWBST: 5000 <--> 5150 mV at 5000 mV
print_constraints: PFUZE100_VSNVS: 1200 <--> 3000 mV at 1800 mV
print_constraints: PFUZE100_VREFDDR: at 750 mV
print_constraints: PFUZE100_VGEN1: 800 <--> 1550 mV at 1500 mV
print_constraints: PFUZE100_VGEN2: 800 <--> 1550 mV at 1500 mV
print_constraints: PFUZE100_VGEN3: 1800 <--> 3300 mV at 2500 mV
print_constraints: PFUZE100_VGEN4: 1800 <--> 3300 mV at 1800 mV
print_constraints: PFUZE100_VGEN5: 1800 <--> 3300 mV at 2800 mV
print_constraints: PFUZE100_VGEN6: 1800 <--> 3300 mV at 3300 mV
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
i2c-core: driver [max17135] using legacy suspend method
i2c-core: driver [max17135] using legacy resume method
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 232K
PMU: registered new PMU device of type 0
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = d9820000 suspend_iram_base=d989c000
PM driver module loaded
IMX usb wakeup probe
the wakeup pdata is 0xd45f2ee0
add wake up source irq 75
IMX usb wakeup probe
the wakeup pdata is 0xd45f2ca0
mxc_bt_rfkill driver success loaded
rfkill: BT RF going to : on
mx6q_sd_bt_reset
cpu regulator mode:ldo_bypass
_regulator_get: get() with no identifier
mx6_cpu_regulator_init: failed to get pu regulator
i.MXC CPU frequency driver
highmem bounce pool size: 64 pages
ashmem: initialized
NTFS driver 2.1.30 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 740
NET: Registered protocol family 38
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver lcd
mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!
LCD SPI Request GPIO 58 OK!!
LCD SPI Request GPIO 55 OK!!
LCD SPI Request GPIO 56 OK!!
------------[ cut here ]------------
WARNING: at arch/arm/plat-mxc/clock.c:63 clk_disable+0x44/0x8c()
clock enable/disable mismatch! clk ipu1_clk
Modules linked in:
[<c0051fc4>] (unwind_backtrace+0x0/0x138) from [<c008af90>] (warn_slowpath_common+0x4c/0x64)
[<c008af90>] (warn_slowpath_common+0x4c/0x64) from [<c008b03c>] (warn_slowpath_fmt+0x30/0x40)
[<c008b03c>] (warn_slowpath_fmt+0x30/0x40) from [<c006c738>] (clk_disable+0x44/0x8c)
[<c006c738>] (clk_disable+0x44/0x8c) from [<c02de938>] (mxcfb_set_par+0x69c/0x834)
[<c02de938>] (mxcfb_set_par+0x69c/0x834) from [<c02d0888>] (fb_set_var+0x124/0x290)
[<c02d0888>] (fb_set_var+0x124/0x290) from [<c02e187c>] (lcd_init_fb+0x54/0x70)
[<c02e187c>] (lcd_init_fb+0x54/0x70) from [<c0682050>] (lcd_plat_probe+0x304/0x364)
[<c0682050>] (lcd_plat_probe+0x304/0x364) from [<c0309410>] (platform_drv_probe+0x18/0x1c)
[<c0309410>] (platform_drv_probe+0x18/0x1c) from [<c0308058>] (driver_probe_device+0xb0/0x290)
[<c0308058>] (driver_probe_device+0xb0/0x290) from [<c03082c4>] (__driver_attach+0x8c/0x90)
[<c03082c4>] (__driver_attach+0x8c/0x90) from [<c03070ac>] (bus_for_each_dev+0x5c/0x88)
[<c03070ac>] (bus_for_each_dev+0x5c/0x88) from [<c0307944>] (bus_add_driver+0x188/0x268)
[<c0307944>] (bus_add_driver+0x188/0x268) from [<c0308794>] (driver_register+0x78/0x13c)
[<c0308794>] (driver_register+0x78/0x13c) from [<c0044640>] (do_one_initcall+0xfc/0x164)
[<c0044640>] (do_one_initcall+0xfc/0x164) from [<c00089a8>] (kernel_init+0x9c/0x140)
[<c00089a8>] (kernel_init+0x9c/0x140) from [<c004b408>] (kernel_thread_exit+0x0/0x8)
---[ end trace 199f8b1c5287134b ]---
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
console [ttymxc0] enabled, bootconsole disabled
console [ttymxc0] enabled, bootconsole disabled
brd: module loaded
loop: module loaded
m25p80 spi0.0: unrecognized JEDEC id ffffff
GPMI NAND driver registered. (IMX)
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPTP driver version 0.8.5
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for Qualcomm USB modem
usbcore: registered new interface driver qcserial
ARC USBOTG Device Controller driver (1 August 2005)
android_usb gadget: Mass Storage Function, version: 2009/09/11
android_usb gadget: Number of LUNs=1
lun0: LUN: removable file: (no medium)
Gadget Android: controller 'fsl-usb2-udc' not recognized
android_usb gadget: android_usb ready
Suspend udc for OTG auto detect
USB Host suspend begins
will suspend roothub and its children
ehci_fsl_bus_suspend begins, DR -- bypassed
host suspend ends
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
dr_controller_run: udc enter low power mode
USB Gadget resume ends
fsl-usb2-udc: bind to driver android_usb
mousedev: PS/2 mouse device common for all mice
[himax] himax_ts_init
himax_add_i2c_device : i2c_bus=1; slave_address=0x4a; i2c_name=himax-tsHimax IC package 8528 D
Himax himax_read_flash addr_start = 622 , local_start_addr = 155 , local_length = 3 , local_end_addr = 157 , local_addr = 2
Himax cmd[0]=30,cmd[1]=0,cmd[2]=11,cmd[3]=17
Himax cmd[0]=32,cmd[1]=19,cmd[2]=2,cmd[3]=0
Himax himax_read_flash addr_start = 626 , local_start_addr = 156 , local_length = 6 , local_end_addr = 159 , local_addr = 2
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
Himax cmd[0]=32,cmd[1]=19,cmd[2]=2,cmd[3]=0
Himax cmd[0]=1,cmd[1]=224,cmd[2]=3,cmd[3]=32
Himax cmd[0]=0,cmd[1]=0,cmd[2]=0,cmd[3]=0
Himax himax_read_flash addr_start = 512 , local_start_addr = 128 , local_length = 6 , local_end_addr = 130 , local_addr = 0
Himax cmd[0]=95,cmd[1]=0,cmd[2]=0,cmd[3]=16
Himax cmd[0]=0,cmd[1]=0,cmd[2]=100,cmd[3]=14
input: himax-touchscreen as /devices/virtual/input/input0
[himax]himax_ts_register_interrupt request_irq ok
[HIMAX TP ERROR]himax_ts_probe: handle missed interrupt
[HIMAX PORTING ERROR] interrupt gpio 107 request fail.
i2c-core: driver [himax-ts] using legacy suspend method
i2c-core: driver [himax-ts] using legacy resume method
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
si114x 2-005a: si114x_probe: Probing si114x..
si114x 2-005a: _check_part_id: Detected SI1143 part_id:43
[HIMAX TP MSG] checksum fail : check_sum_cal: 0x00
si114x 2-005a: _i2c_read_mult Retried read count:0
ehci_fsl_bus_suspend begins, Host 1 -- bypassed
si114x 2-005a: _i2c_read_mult Retried read count:1
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
input: si114x_als_ir as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input1
input: si114x_als_vis as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input2
input: si114x_ps as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input3
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
si114x 2-005a: _i2c_write_mult Retried read count:0
si114x 2-005a: _i2c_write_mult Retried read count:1
si114x 2-005a: _i2c_write_mult Retried read count:2
si114x 2-005a: _i2c_write_mult i2c write retry exceeded
using rtc device, snvs_rtc, for alarms
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.1.0)
si70xx: probe of 2-0040 failed with error -110
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using ADMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Galcore version 4.6.9.9754
revserved_memory_account:viv_gpu registerd
Thermal calibration data is 0x5975155f
Thermal sensor with ratio = 186
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
mmc0: new high speed DDR MMC card at address 0001
mmcblk0: mmc0:0001 SEM04G 3.68 GiB
mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4
mmcblk0boot1: unknown partition table
mmcblk0boot0: unknown partition table
wm8962 0-001a: customer id 0 revision D
input: WM8962 Beep Generator as /devices/platform/imx-i2c.0/i2c-0/0-001a/input/input4
asoc: wm8962 <-> imx-ssi.1 mapping ok
input: wm8962-audio DMIC as /devices/platform/soc-audio.5/sound/card0/input5
input: wm8962-audio Headphone Jack as /devices/platform/soc-audio.5/sound/card0/input6
ALSA device list:
#0: wm8962-audio
oprofile: using arm/armv7-ca9
GACT probability NOT on
Mirror/redirect action on
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (12822 buckets, 51288 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 10
Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
L2TP core driver, V2.0
PPPoL2TP kernel driver, V2.0
L2TP IP encapsulation support (L2TPv3)
L2TP netlink interface
L2TP ethernet pseudowire support (L2TPv3)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
lib80211_crypt: registered algorithm 'TKIP'
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-02 00:36:00 UTC (88560)
Freeing init memory: 240K
init: cannot find '/system/bin/ingsvcd', disabling 'ing'
android_usb: already disabled
mtp_bind_config
EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
[email protected]_dvt:/ # EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
si114x 2-005a: _i2c_read_mult Retried read count:0
si114x 2-005a: _i2c_read_mult Retried read count:1
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
si114x 2-005a: si114x_input_poll_ps_cb: Unable to read ps data
EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)
si114x 2-005a: _i2c_read_mult Retried read count:0
si114x 2-005a: _i2c_read_mult Retried read count:1
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
si114x 2-005a: si114x_input_poll_als_vis_cb: Unable to read als data
si114x 2-005a: _i2c_read_mult Retried read count:0
PM: Syncing filesystems ...
si114x 2-005a: _i2c_read_mult Retried read count:1
done.
PM: Preparing system for standby sleep
suspend: start 1 suspend...
suspend: finish 1 suspend after:0.2606666 seconds...
Freezing user space processes ...
active wake lock main

Freezing of user space aborted

Restarting tasks ... done.
suspend: finish 1 suspend after:0.37591001 seconds...
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
si114x 2-005a: si114x_input_poll_als_ir_cb: Unable to read als data
warning: `zygote' uses 32-bit capabilities (legacy support in use)
cpufreq_interactive_input_connect: connect to himax-touchscreen
si114x 2-005a: _i2c_read_mult Retried read count:0
acc_open
acc_release
si114x 2-005a: _i2c_read_mult Retried read count:1
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
si114x 2-005a: si114x_input_poll_ps_cb: Unable to read ps data
si114x 2-005a: _i2c_read_mult Retried read count:0
si114x 2-005a: _i2c_read_mult Retried read count:1
ehci_fsl_bus_resume begins, Host 1
ehci_fsl_bus_resume ends, Host 1
ehci_fsl_bus_resume begins, DR
si114x 2-005a: _i2c_read_mult Retried read count:2
si114x 2-005a: _i2c_read_mult i2c read retry exceeded
si114x 2-005a: si114x_input_poll_als_vis_cb: Unable to read als data
EXT4-fs error (device mmcblk0p4): ext4_lookup:1044: inode #114806: comm er.ServerThread: deleted inode referenced: 115076
Aborting journal on device mmcblk0p4-8.
Kernel panic - not syncing: EXT4-fs (device mmcblk0p4): panic forced after error

[<c0051fc4>] (unwind_backtrace+0x0/0x138) from [<c068cbb0>] (panic+0x74/0x194)
[<c068cbb0>] (panic+0x74/0x194) from [<c01bce38>] (ext4_handle_error+0x68/0xa4)
[<c01bce38>] (ext4_handle_error+0x68/0xa4) from [<c01bd134>] (ext4_error_inode+0xa4/0xcc)
[<c01bd134>] (ext4_error_inode+0xa4/0xcc) from [<c01aede0>] (ext4_lookup+0x104/0x118)
[<c01aede0>] (ext4_lookup+0x104/0x118) from [<c013647c>] (d_alloc_and_lookup+0x44/0x64)SA
[<c013647c>] (d_alloc_and_lookup+0x44/0x64) from [<c0136b58>] (do_lookup+0x284/0x2f8)
[<c0136b58>] (do_lookup+0x284/0x2f8) from [<c0138458>] (path_lookupat+0x124/0x698)
[<c0138458>] (path_lookupat+0x124/0x698) from [<c0138f38>] (do_path_lookup+0x1c/0x5c)
[<c0138f38>] (do_path_lookup+0x1c/0x5c) from [<c013a038>] (user_path_at_empty+0x50/0x94)
[<c013a038>] (user_path_at_empty+0x50/0x94) from [<c013a090>] (user_path_at+0x14/0x1c)
[<c013a090>] (user_path_at+0x14/0x1c) from [<c0130e8c>] (vfs_fstatat+0x3c/0x6c)
[<c0130e8c>] (vfs_fstatat+0x3c/0x6c) from [<c013108c>] (sys_stat64+0x14/0x30)
[<c013108c>] (sys_stat64+0x14/0x30) from [<c004a900>] (ret_fast_syscall+0x0/0x30)
CPU1: stopping
[<c0051fc4>] (unwind_backtrace+0x0/0x138) from [<c00443a8>] (do_IPI+0x1d4/0x208)
[<c00443a8>] (do_IPI+0x1d4/0x208) from [<c004a34c>] (__irq_svc+0x4c/0xe8)
Exception stack(0xd43bfe50 to 0xd43bfe98)
fe40: c1327320 d43be000 00000000 00000093
fe60: c08fa080 00000001 d421dc00 ffff9bae c097ab00 ffff9bae d43be000 00000002
fe80: 00000000 d43bfe98 c0691698 c03d97a0 600f0013 ffffffff
[<c004a34c>] (__irq_svc+0x4c/0xe8) from [<c03d97a0>] (i2c_imx_bus_busy+0x78/0x138)
[<c03d97a0>] (i2c_imx_bus_busy+0x78/0x138) from [<c03d9c38>] (i2c_imx_xfer+0x118/0x75c)
[<c03d9c38>] (i2c_imx_xfer+0x118/0x75c) from [<c03d75b0>] (i2c_transfer+0xc8/0x148)
[<c03d75b0>] (i2c_transfer+0xc8/0x148) from [<c03d06b0>] (_i2c_read_mult+0x54/0xe8)
[<c03d06b0>] (_i2c_read_mult+0x54/0xe8) from [<c03d0a9c>] (si114x_input_poll_als_ir_cb+0x30/0x84)
[<c03d0a9c>] (si114x_input_poll_als_ir_cb+0x30/0x84) from [<c03c1a14>] (input_polled_device_work+0x14/0x20)
[<c03c1a14>] (input_polled_device_work+0x14/0x20) from [<c00a53ac>] (process_one_work+0x12c/0x494)
[<c00a53ac>] (process_one_work+0x12c/0x494) from [<c00a5884>] (worker_thread+0x170/0x3cc)
[<c00a5884>] (worker_thread+0x170/0x3cc) from [<c00a9978>] (kthread+0x80/0x88)
[<c00a9978>] (kthread+0x80/0x88) from [<c004b408>] (kernel_thread_exit+0x0/0x8)
4th June 2020, 01:23 PM |#57  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by nickb1907

Can anyone help me get my wink relay out of boot loop? I have tried the youtube method and can't get android to boot. I have downloaded the edison file but I don't know how to flash it. I am new to this so if there is a guide to follow to flash it through putty or adb please send it along. I have tried to connect to it through adb without success. I don't know if I am using the right commands.

This is what i see through putty terminal. Then it reboots and goes through all this again.

I think your boot loop is caused by a failed internal memory.

MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
*** Warning - bad CRC or MMC, using default environment
Card did not respond to voltage select!
mmc2(part 0) is current device
MMC read: dev # 2, block # 2048, count 9728 ... Card did not respond to voltage select!
MMC: block number 0x2e00 exceeds max(0x0)
0 blocks read: ERROR
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Card did not respond to voltage select!
mmc2 init failed

I was struggling with the issue where my relay's memory is stuck in read only mode. This happens when the memory card is starting to going bad. In your case, it looks like it's totally dead.
"community.smartthings.com/t/beta-wink-relay-custom-smartthings-integration/111732/526?u=vvicked"
4th June 2020, 01:30 PM |#58  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by vvicked

I think your boot loop is caused by a failed internal memory.

MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
*** Warning - bad CRC or MMC, using default environment
Card did not respond to voltage select!
mmc2(part 0) is current device
MMC read: dev # 2, block # 2048, count 9728 ... Card did not respond to voltage select!
MMC: block number 0x2e00 exceeds max(0x0)
0 blocks read: ERROR
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Card did not respond to voltage select!
mmc2 init failed

I was struggling with the issue where my relay's memory is stuck in read only mode. This happens when the memory card is starting to going bad. In your case, it looks like it's totally dead.
"community.smartthings.com/t/beta-wink-relay-custom-smartthings-integration/111732/526?u=vvicked"

I actually got it working with the 3 cache clears and then 3 resets mentioned a few posts back. Then I kept pasting that command in putty and it booted into android. I don’t know if I actually needed putty or if it would have worked by just doing the clearing and resets from the relay. Either way it’s working now.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes