Any chance of a walkthru for us noobs to root the pulse? I've used three different adb's and can adb connect thru the lan to the ip address of the pulse but the next step of adb root gives a device not found error. Even thought the adb connect show connection on port 5555, the adb devices command s...

Any chance of a walkthru for us noobs to root the pulse? I've used three different adb's and can adb connect thru the lan to the ip address of the pulse but the next step of adb root gives a device not found error. Even thought the adb connect show connection on port 5555, the adb devices command s...

Dumb question, and you probably did already - but you try wiping it? Might clear whatever lockout there is on the box (assuming it's not server side / ip / mac based).

Hi, This is a list of everything showing up under "All Apps", of course some things are normal things (clock, watch tv, etc), but others are apps / links to web pages that don't exist on other boxes. The list is (mind any typos): Clock Crackle Downloads Flixter Google Chrome GTVebook Live ...

Can you comment on the Pulse's software reliability? A lot of Vizio Co-Star users report the Co-Star freezes often due to heat buildup caused by its small form factor. Since the Pulse is almost identical in size to the Co-Star, does it also suffer from software freezes due to heat? I haven't really...

The usb ports are for external devices only, and no - there is no root released for it yet (so no SSH etc).

I have another idea for permanent root and I'll try it soon: We could place a binary somewhere like on /data-partition. Then set the owner to root and give him the +s flag so it will be always executed as root. If we do that with a binary like busybox we should be able todo everything as root witho...

Do you have another TV you can try (ideally, one that isn't the same make or model?). Just trying to rule out a resolution mismatch between the box and your tv, as the video mode is usually 480p/720p until after the logos, then it kicks up to 1080i/p.

Yep, it's not possible - issue is that script is stored inside of the update, that is RSA verified (like, just about every android update) now, so we can't modify it at all.

Well the issue isn't that the update is too old, it's the fact that the update is a US update trying to be applied to an EU box. If you look at the start of the updater script (in the update): assert(getprop("ro.product.device") == "NSZGS7" || getprop("ro.product.device"...