I did not manage to install the v93 Bromite WebView indicated by you. Reason: invalid signature.
Did you follow Bromiteās instructions for installing the WebView component?
They seem to describe what to do to deal with signature mismatches, although I didnāt have any problem with that.
I just followed the steps in section Installation with root file manager or TWRP.
Hi, i am currently trying to install homeassistant on my shelly wall display. the teardown wetn very well and i seem to have the same version as you, but when it comes to dumping the whole flash i get this error: Preloader - [LIB]: Status: Handshake failed, retrying.... I start mtk plug in my usb c then plug in power, i tried it on ubuntu and win 11. Does anyone have the same error or knows how to fix it?
Hi! I created a GitHub repository with a detailed guide on how to hack the wall display. Additionally, I wrote a small app that integrates the display with Home Assistant, allowing you to use its relay and run the Home Assistant GUI while still viewing the temperature in Home Assistant.
You can check out the repository here. The guide includes step-by-step instructions and all the necessary files to get started. Enjoy!
Also luka177 it would be nice if you could contribute on the mtkclient part because it didnt work for me 
1 Like
Hello @RapierXbox, thank you for the guide! Where can I get the ShellyElevate.apk file? I couldnāt find a download linkā¦
2 Likes
You should find it in the release tab
1 Like
nice! glad it works
Hi, i have tried following the instructions, but I have a few questions:
-
is there a specific reason why the wiring example shows the 3.3V pin on the UART adapter being connected to the RX pin on the shelly board? I am using a different adapter and I did figure that one out, but I would kindly suggest a short pin connection description to avoid any confusion.
-
My controller appears to be stuck in a bootlop, does anyone know what might be going on? I have attached the last section of the serial output of the loop, after that it reboots (whole output is too long). Did I brick my device?
serial output
============================================================
[1980] [LK_BOOT] Android Partition Name : boot
[1980] [LK_BOOT] Android Boot IMG Hdr - Kernel Size : 0x007D4C75
[1980] [LK_BOOT] Android Boot IMG Hdr - Kernel Address : 0x80008000
[1980] [LK_BOOT] Android Boot IMG Hdr - Rootfs Size : 0x001C7894
[1980] [LK_BOOT] Android Boot IMG Hdr - Rootfs Address : 0x84000000
[1980] [LK_BOOT] Android Boot IMG Hdr - Tags Address : 0x8E000000
[1980] [LK_BOOT] Android Boot IMG Hdr - Page Size : 0x00000800
[1980] [LK_BOOT] Android Boot IMG Hdr - Command Line : bootopt=64S3,32S1,32S1
[1980] ============================================================
[1980] > page count of kernel image = 4010
[1980] > kernel mem offset = 0x80008000
[1980] > rootfs mem offset = 0x807dd000
[1980] > boot image size = 0x99d800
[1980] boot state: green
[1980] [PART_LK][get_part] boot
[1980]
read the data of boot (size = 0x99d800)
[2000] > from - 0x0000000001ec0800 (skip boot img hdr)
[2000] > to - 0x80008000 (starts with kernel img hdr)
[2760] [PROFILE] ------- load boot.img takes 401 ms --------
[2820] mt_disp_get_lcd_time, fps=5861
[LK_ENV]get_env apjtag
[2830] [APJTAG] current setting is 0.
[2840] model=MT6580
[2840] g_mt6311_hw_exist=0
[2840] mt6311 not exist
[2840] cluster-0: 4 core
[2840] cluster-1: 0 core
[2840] [ccci] modem standalone not support
[2840] mblock[0].start: 0x80000000, size: 0x3f800000
[2900] Not Support VCORE DVFS
[3000] mt_disp_get_lcd_time, fps=5879
[3000] videolfb - fb_base = 0xbf800000
[3000] videolfb - islcmfound = 1
[3140] mt_disp_get_lcd_time, fps=5861
[3140] videolfb - fps = 5861
[3140] videolfb - vram = 8388608
[3140] videolfb - lcmname = 0xce_st7703_ly_psd_dsi_vdo
[3150] [ccci] modem mem info not support
[3160] [ccci] modem mem arguments info using v1
[3160] PTP_INFO Only support in MT6795
start dump lk masp atag
dump sw sbc:22, sw sdl:22 , hw sbc: 0
dump lock_state, 1
dump rid, eff3c3f8, 47665af7, 861e0498, b8baef91
[3160] create masp atag OK
[3160] tee_reserved_mem not supported
[3160] non_secure_sram not supported
jj fixup hwinfo
[3180] jserial number W8T8ZDQSBY89LJAI
serial:W8T8ZDQSBY89LJAI 16
============ fdt_chosen_add_hwinfo 423 ==========inject jlcm data size: 66756 0 0
[3210] [PART_LK][get_part] proinfo
old crash record location
using DRAM
############ 43474244 === 0 0 0 0- 0 0 117
[3240] [PROFILE] ------- boot_time takes 1665 ms --------
[LK_ENV]get_env hibboot
[LK_ENV]get_env resume
[3240] resume = NULL
[3320] booting linux @ 0x80008000, ramdisk @ 0x84000000 (1865876)
[3320] [LEDS]LK: leds_deinit: LEDS off
[3320] [LEDS]LK: red level is 0
[3320] [LEDS]LK: green level is 0
[3320] [LEDS]LK: blue level is 0
[3320] DRAM Rank :1
[3320] DRAM Rank[0] Start = 0x80000000, Size = 0x40000000
[3320] cmdline: console=tty0 console=ttyMT0,921600n1 root=/dev/ram vmalloc=496M androidbo002000_0000000000|000000000_00000000000000000000 jseriall=-hwk00-0-0-117 printk.disable_u
[3320] lk boot time = 1665 ms
[3320] lk boot mode = 0
[3320] lk boot reason = power_key
[3320] lk finished ā jump to linux kernel 32Bit
EDIT: it is not bricked, it boots up just fine in its cradle. when connected like shown in the instructions, I get said ~10 second boot loop. are there any other pins that need to be connected?
Another quick update:
- it works for me now, thank you @RapierXbox for the guide!
- the board (at least my sample) is unstable at 5V. I had to crank my bench supply to around 6.5V to get out of that boot loop. It seems like it drowns out at ~5.5V and reboots, which happens when supplied over USB on my machine. Supplying exactly 5.0V made it reboot even quicker. Above 6V, the system booted with no problems. No idea what the optimal voltage would be, but I did not want to find out with my only display.
- For this described configuration, I hooked up the isolated bench supply to the supply pins designated 5V and GND in the guide. The UART-USB-board GND was also connected to this ground potential, RX to TX, TX to RX, and off it went.
- everything else in the guide worked very smoothly. A few APK names have changed, so 100% copy and paste does not work, but I think that is a hurdle everyone here can jump over.
- I installed a simple virtual button overlay to make navigation boatloads easier. I tried two, both worked. Just search vor āvirtual buttons open source apkā or similar, there are plenty of options. Install via ADB, activate the accessability feature for this app (usually a guided process) and you can navigate with back and home buttons.
Thanks again! Great work!
1 Like
have you taken a look at one of todayās app store websites? for sure you will find ShellyElevate.apk file there, Iām using null48.net and apkpure.com, the best app stores forever, take a look, and you will find it there. thx.
Not on either site.
@RapierXbox thanks for all your work here, Iām a HASS beginner and Iāve just ordered the display.
So with your modified display I assume you can have graphical touchscreen buttons?
Are there any notable limitations?
I havenāt been able to find the display resolution and refresh, any ideas on that?
For now yes like the search bar appearing on the top but I am gonna fix that soon!
Does somebody have a full device backup or a full image?
I would like to investigate the firmware, I wrote some apps to NSPanel pro maybe it is can be customized also.
1 Like