Recent content by bdjohns1

Awesome that this will always be a fallback option. I can live with them not patching something that requires physical access to the device and some level of technical skill.

I haven't seen anything to that effect. I imagine you could just solder in a connector and see what happens. Wink does post their kernel source on GitHub for GPL compliance - it does appear to at least have basic USB support compiled in, so that's a start.

Try creating a file called /database/ENABLE_SSH - I think the scripts now look to see that that file exists before trying to launch dropbear (at least via the init.d scripts).

I'm fine with them taking away the ability to root the device via the webserver. I'm honestly surprised that such simple exploits even made it out in public and lasted as long as they did. I do think they should leave the ability for enterprising users to locally access their device using...

So, to manually update the updater, I assume the basic workflow on a already-rooted wink hub itself should just be: 1) ssh/TTY login as root while the hub is running regularly. 2) curl to grab the updater fs 3) flash the updater fs to the right partition 4) mount the newly flashed updater fs...

That's a good idea. I think you would only need to provide an equivalent file to http://wink-hub-images.s3.amazonaws.com/00.01/upgrade_00.01.txt That would be a good way to trick the system into thinking an upgrade was present to be able to get into the updater system. You'd just need to...

Good call, forgot about that. Thanks! I'm betting one of those new updater versions they have floating around doesn't have them either.

I'm probably missing something obvious in the process - I was trying to use nandsim to mount the updater images in an Ubuntu VM on my computer to poke around in them, review init scripts, etc. Anyone have a guide on how to do it? I'm having a hard time getting the ubiattach command to work...

Just as a note - I was on Kyocera version 2.000sp (the July Jelly Bean release) and was rooted. I got a notification today for the 2.002sp update, and was able to install it. So far, my root appears to have been preserved - Titanium Backup still reports it can get root.

Sero 7 Pro Sero 7 Pro

Great, glad to hear you were successful!

You've got some other issues there - adb shouldn't be throwing all of those errors every time you push, and the adb daemon shouldn't need to restart over and over. If you're getting an error saying that cp can't execute the first time you run pwn, that means that your busybox executable isn't...

Nothing too big - some tweaks to the notification pane to make the header more compact. Basically, just incremental tweaks as best I can tell.

Actually, I was able to get it to work. Here's the exact sequence I followed (stock Jellybean): 1) adb push busybox, pwn, and su over to /data/local/tmp 2) adb install Superuser.apk 3) adb shell. In the shell, a) cd /data/local/tmp b) ln busybox cp c) ln busybox mount d) ln busybox chmod e)...

So, I just rejoined the Android world after being away for a year or so when we all got DC phones at work. Obviously, mine's a Torque. My phone got the Jelly Bean update already. I tried Vic's method, and it didn't work. After digging around, I found that the su binary wasn't getting copied...