| Author |
Message |
|
hitokiri
|
 Posted: Mon Oct 10, 2011 12:39 pm |
|
 |
| Android 1.0 |
|
|
Joined: Mon Oct 10, 2011 11:40 am
Posts: 11
GTV Device Owned: Logitech Revue
|
cj_000 wrote: You should be able to- yes. However, of note, with user - you lose root, and any extra permissions it grants you.
Furthermore, since the original recovery still exists, just update to the this recovery before you are going to update to user - as it may revert the recovery on you. So you are saying to STAY in userdebug and only use this update when i want to go get the official update since this removes root, correct?
|
|
  |
|
 |
|
cj_000
|
Posted: Mon Oct 10, 2011 12:54 pm |
|
|
| 1.6 Donut |
|
|
Joined: Fri Jul 29, 2011 2:13 pm
Posts: 115
|
|
Well - that's what I'd do. However, it really depends how you want to use the box. I have a few, so it's not a big deal to keep one on userdebug (to preserve root).
|
|
| |
|
|
|
hitokiri
|
Posted: Mon Oct 10, 2011 1:07 pm |
|
|
| Android 1.0 |
|
|
Joined: Mon Oct 10, 2011 11:40 am
Posts: 11
GTV Device Owned: Logitech Revue
|
yeah, i've been holding off since day 1 since there was no way to get back to stock. now since there is a way out, i cant wait to upgrade. i have a couple of combinations i want to try out. like esfileexplorer + moboplayer  hope those work. It would make streaming media nigh perfect!
|
|
| |
|
|
|
wjddesigns
|
Posted: Mon Oct 10, 2011 5:47 pm |
|
|
| Android 1.0 |
|
|
Joined: Mon Aug 01, 2011 7:03 pm
Posts: 4
|
|
Having issues here - when I go to CMD and do ADB connect it gives me the "Unable to connect to 192.168.1.17:2"4 but that is what the GTV IP addy is - I can take off the port but it says it is unable to parse... I have the correct IP for my computer in the GTV dev screen - any ideas?
|
|
| |
|
|
|
gdeeble
|
Posted: Mon Oct 10, 2011 6:19 pm |
|
|
| 1.5 Cupcake |
|
|
Joined: Mon Aug 01, 2011 8:54 pm
Posts: 63
|
Are you putting adb connect 192.168.1.17 or 192.168.1.17:24? You need just need it to look like the first one.
|
|
| |
|
|
|
wjddesigns
|
Posted: Mon Oct 10, 2011 6:28 pm |
|
|
| Android 1.0 |
|
|
Joined: Mon Aug 01, 2011 7:03 pm
Posts: 4
|
gdeeble wrote: Are you putting adb connect 192.168.1.17 or 192.168.1.17:24? You need just need it to look like the first one. when I try to do "192.168.1.17" it says unable to parse as <host>:<port> in the cmd window
|
|
| |
|
|
|
tipster67
|
Posted: Mon Oct 10, 2011 7:04 pm |
|
|
| Android 1.0 |
|
|
Joined: Thu Oct 06, 2011 4:30 pm
Posts: 5
GTV Device Owned: Logitech Revue
|
|
| |
|
|
|
tipster67
|
Posted: Mon Oct 10, 2011 7:07 pm |
|
|
| Android 1.0 |
|
|
Joined: Thu Oct 06, 2011 4:30 pm
Posts: 5
GTV Device Owned: Logitech Revue
|
wjddesigns wrote: gdeeble wrote: Are you putting adb connect 192.168.1.17 or 192.168.1.17:24? You need just need it to look like the first one. when I try to do "192.168.1.17" it says unable to parse as <host>:<port> in the cmd window The proper port is 5555 I believe..... 192.168.1.17:24 would need to be 192.168.1.17:5555
|
|
| |
|
|
|
gdeeble
|
Posted: Mon Oct 10, 2011 7:22 pm |
|
|
| 1.5 Cupcake |
|
|
Joined: Mon Aug 01, 2011 8:54 pm
Posts: 63
|
|
| |
|
|
|
wjddesigns
|
Posted: Tue Oct 11, 2011 7:13 am |
|
|
| Android 1.0 |
|
|
Joined: Mon Aug 01, 2011 7:03 pm
Posts: 4
|
|
After reading that ADB connect tutorial (which should be attached to the OP's instructions on the first page) I got it to work with port 5555 instantly - Thanks everyone >_<
|
|
| |
|
|
|
