Database Info

Android SDK 1.5 trouble in Linux

I am a new to using Linux, I just downloaded the SDK 1.5 and I am having some trouble getting the tools to work properly. For example. If I try to open the emulator it will just sit there and do nothing. I cannot get adb to work either. I set it up / the instructions. Any ideas on what I am missing? Thanks

easiest way to fix the adb problem is to move your adb command that is included in the SDK into your /usr/bin or /bin directory. if you have a problem with either of those then type cd ~/<sdk>/tools followed by ./adb the "./" tells the phone to run the command in the current directory, otherwise you could just type the directory to adb to run it i.e. ~/SDK/tools/adb that's all you need. as far as the emulator i have no idea because i have never gotten it up and running properly

How do I add the ADB command to usr/bin?

You can do as followed:
- Run the Terminal
- cd to your sdk/tools directory
- Run these command:
Code:
#./adb kill-server
#./adb devices
If you see your HTC has been remounted, it's done!

sudo mv ~/sdk/tools/adb /usr/bin/adb

tubaking182 said:
sudo mv ~/sdk/tools/adb /usr/bin/adb
Click to expand...
Click to collapse
Got it thanks for your help! I still can't get the emulator to work. Oh well Thanks again

What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
You created the AVD, right?
What do you get when you type:
Code:
android list avd

stovenator said:
What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
Ubuntu version 9.04 & 64 Bit
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
You created the AVD, right?
What do you get when you type:
Code:
android list avd
Click to expand...
Click to collapse
bash: android: command not found

They made a change in 1.5 SDK that you must specifiy the virtual device you want the emulator to run. if you just double click on "emulator", it will print the error to console and exit.
So first cd to the tools directory of the sdk and type android[return]
you will be given the commands that android (the program) will accept. you can also do this for emulator.

Great!! Everything is working well now. Thanks for everyones help!!

How Do I get fastboot working in Ubuntu?

jordanjf86 said:
How Do I get fastboot working in Ubuntu?
Click to expand...
Click to collapse
http://andblogs.net/fastboot/

fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.

billc.cn said:
fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.
Click to expand...
Click to collapse
Actually it doesn't seem to be in the Linux 1.5 SDK; I had to build it. It's in the Windows SDK, though. Kinda weird.

Android SDK 1.5 emulator trouble in windows
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).

karan09 said:
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).
Click to expand...
Click to collapse
First, this is the wrong thread for such a question. This thread is about SDK issues in Linux, and you're asking about using debugging tools in Windows.
Second, if you say yourself that you are "not tech savvy", then I'm not quite sure why you are wanting to play with the SDK tools. I don't mean this in a derogatory way; I'm just not sure what it is that you're trying to accomplish.
That said, Android dev docs can be found here, and information specifically about the emulator is here.
- Chris

[HOWTO] Guide to running ADB under Fedora 11 (and equivalent distros)

Ok, I have fedora 11 installed on most of my computers, since i love this distro to death. My big thing was trying to get adb to work. This is my guide to get it to work, for now.
First things first. Navigate to /etc/udev/rules.d as root. Create a rules file called 50-android.rules (touch 50-android.rules). NOTE: You are better off looking at the contents and picking a rules number set other than what is listed. Sometimes udev is picky. For the newbies, so if any rules start with '50', then change the number by one or two, like 51 or 52. Paste this into the file:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
Make sure you use ATTRS, not ATTR or SYSFS, since this is a newer updated udev system.
After that, run udevadm control --reload-rules to reload your rules files. Now just run ./adb devices as root to make sure it recognized your HTC dream. I am working on this fix right now so you don't need to be root, keep patient. Now you can adb shell into your device either as root OR normal user, just as long as you start the server as root. This is a permissions problem, and hopefully I can fix this and/or find a fix soon.
I wrote this because i searched high and low through google, and only found a few good parts as far as a fix. Hopefully this helps a few people out there.

Just wondering if this has helped anyone. If not, delete this thread or do whatever with it....

I have adb on my eeepc 900 with f11 I believe this method works too as well. although it says it has been tested with ubuntu, it works pretty well with f11.
http://www.talkandroid.com/android-sdk-install-guide/
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:<path to your $SDK_ROOT/tools>
Click to expand...
Click to collapse

It helped me, since the creation of the file my OpenSuSE 11.0 recognizes the phone perfectly
Thanks a lot for your hint.

thanks it helped me. ill be looking forward to getting it to work without root

just use sudo instead

Just a heads up for user's using Ubuntu 9.10, this isn't needed. I connected my G1 to it and ran ADB with no adjustments to udev or anything else.
Pretty much it works out of the box.

Here is my version
download the .tgz file from googlecode
http://developer.android.com/sdk/index.html
sudo tar -xzvf android-sdk_r3-linux.tgz
Click to expand...
Click to collapse
Code:
sudo gedit ~/.bash_profile
heres my bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH=$PATH:/android-sdk-linux/tools
Click to expand...
Click to collapse
logout
login
connect android g1 device via usb to pc
open a terminal
Code:
adb devices
if you cant get a device try it with superuser.

Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb

Another option is to edit the /etc/profile and add
PATH=$PATH:/<Path to android-sdk>/tools
This option will allow any user to use the adb tools when logged in or if you
su -
into another user

I wrote a short guide as well for Windows and Ubuntu. Might help others.
Unfortunately, as anyone with a passing acquaintence with ADB knows, the scrolling issue can be a killer. I swear the other day I pressed "up" twice and it composed "rm /sdcard/rootfs.img /sdcard/system.ext2" and executed it. We run Android on our SD's btw.. Was not cool. Instead, I use ADB via telnet and it works beautifully. Here's how:
Code:
adb shell telnetd &
adb forward tcp:9999 tcp:23
Now type this: "telnet localhost 9999"
Enter "root" and hit enter
Finally update PATH: "export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/sbin:/system/bin:/system/xbin:/system/xbin/bb:/data/local/bin"
Okay, so 4 lines to enter and you have a "regular, sane" shell connection to the phone and you can actually scroll through history and text without it jumbling the text and executing random code. Enjoy.

lbcoder said:
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Click to expand...
Click to collapse
that works too as well but i would rather open up a terminal and type
sudo adb devices

sensimila said:
that works too as well but i would rather open up a terminal and type
sudo adb devices
Click to expand...
Click to collapse
WHY would you want to make it *MORE COMPLICATED*??
There is NO NEED for root.
/path/to/adb ...
THATS ALL.

This is kind of funny... i wrote this because i had trouble with it, so i am just sharing my fix...

In case this is interesting to someone:
The fix mentioned in the first post has to be applied to open SuSE x86 and x64 edition to make the G1 work. The external device works without it, but not the adb device.
Thanks again!

Just wanted to come and post that this does work with OpenSUSE 11.2 x86. Did this hoping to get adb to work with my LG Ally and it does. Thanks!

(Still) works for me on 64bit SUSE 11.4.
Before adding this file, I could not access my device with adb, received permissions errors.
Added this file, and I can shell into my device.
Permissions on adb itself was not the problem, it was access to the device when udev found it.
[edit]Actually used the lines from http://developer.android.com/guide/developing/device.html[/edit]

[SOLVED] (Sort of)[APP ?] EasyTether on Ubuntu 10.04 x64

See post 2!
Has anyone gotten this working? I emailed the developers and they sent me the drivers with instructions but the drivers are 32-bit (i386). The instructions are: Unsip to desired folder (in this case my home folder), in folder where unzipped
Code:
./sudo easytether connect
, then
Code:
sudo dhclient easytether0
. When I type the first command, I get
Code:
sudo ./easytether: command not found
I would really like some help with this. Thanks.
Edit: Btw, I have the correct libs and tried to --force architecture and nothing seems to work.

Google is my best friend... well, after my wife of course!
I found this: http://www.humans-enabled.com/2009/12/how-to-tether-your-verizon-droid-as.html
I downloaded and ran the python script and it's working great! Using it right now!
Best part of this is no root required!
Mods, this installs an app to the phone called azilink which can be found here. Also, if this has been posted elsewhere please feel free to move/remove/merge, however I posted this as more of a method to tether with Ubuntu. Thank you!

[Linux/Mac] ADB & Fastboot (Un)Install Script [Team BlueRidge]

[Linux/Mac] ADB & Fastboot Install Script
I have created a script to be used to install ADB and Fastboot on a Mac or a Linux computer. Simply run the script in Terminal or a similar application and it will copy ADB and Fastboot to /usr/local/bin/
Also, as of Version 3.1 this also installs the JDK for Linux-based systems.
While advanced users probably won't need this, it would be good for new users who need help using the ADB and Fastboot commands.
You can see the source at GitHub.
Download
If you have any problems or errors, let me know.

Changelog:
20171202
Moved entirely to GitHub
On Debian-based Linux, installs the adb and fastboot packages
Other systems, the binaries are pulled from Google's website
Executables are given +x permissions
Version 5.0
Hosted on GitHub and Google Code
Uses latest adb and fastboot (as of April 3, 2014)
Install to /usr/local/bin/
Version 4.1
Uses cp rather than mv
Hosted on GitHub again
Team BlueRidge project
Version 4.0
Now installs adb and fastboot to /usr/bin/ which is a more appropriate directory for the files.
Includes Readme now!
Version 3.1
Added JDK Install for Linux
Version 3
Created separate scripts for Linux & Mac
Updated uninstall script
Version 2.1.1
Fixed errors in installer
Version 2.1
More code efficient.
Better comments in script.
Version 2
Combined installer scripts into one Universal
Updated Uninstall.sh to remove udev rules
Version 1.1
Added udev rules for Linux
Version 1
Initial release

Linux
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.

shootind5nukes said:
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.
Click to expand...
Click to collapse
Thanks! I'll fix that and post an update soon!

JDK is now installed on Linux systems!

Now hosted on Google Code rather than GitHub.

Now installs to /usr/bin/, which is a more appropriate directory as these files are not required for normal system booting or are required for the general functions of your operating system.

i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices

boneskid1 said:
i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices
Click to expand...
Click to collapse
Does it say that ADB is not found or your devices?
Try enabling ADB (USB Debugging) on your device if it says no devices were found.
Gingerbread: Settings>Applications>Development>USB Debugging
Ice Cream Sandwich: Settings>Developer options>Android debugging

Thanks!!!! This worked perfectly. Using Ubuntu 11.10.

romuloxiii said:
Thanks!!!! This worked perfectly. Using Ubuntu 11.10.
Click to expand...
Click to collapse
I'm happy I could help! Don't forget to click "Thanks" if you liked it!
If you have any issues in the future with it, please feel free to let me know!

Good news!!! This is now a Team BlueRidge project and is on Team BlueRidge's GitHub

since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious

prflash3 said:
since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious
Click to expand...
Click to collapse
Download whichever for whichever platform. It's the script inside that you use that matters.

Trying to run the script on OSX, but when I am prompted to enter my password I can't type anything. Please help.

Ditto ul49, being prompted for a password, please advise

Simply type your account password. It won't look like anything is being typed but it is. This is how the "sudo" command works. It is for security.

really glad i found this.
i run "sh "sh script name" and i get this error
ADB-Install-Linux.sh: 5: ADB-Install-Linux.sh: Syntax error: newline unexpected
not sure if it's installed or what
thanks for making this set of scripts and if u could advise me on that error id be grateful.
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
crazy
apt-get install android-tools-fastboot
and
apt-get install android-tools-adb
worked

Just released the first update in two years. Sorry to leave this project unmaintained. The files are now hosted by Team BlueRidge as Google Code no longer supports downloads.

First, thank you very much for putting this together for fellow users. While I'm not the most savy of guys I thought I might just share my experience while installing this ADB + Fastboot package on my MacBook Pro (mid 2012) running OS X Mavericks 10.9.3 in the hopes that somebody might benefit from it as well.
So here it goes:
I tried running the installation script found in "Androidv5.zip" which up until now is the latest version (I think). The script failed to install:
"This will install ADB and Fastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/User/Downloads/Androidv5
Moving ADB
cp: /usr/local/bin/adb: No such file or directory
ADB Moved to /usr/local/bin/adb
moving Fastboot
cp: /usr/local/bin/fastboot: No such file or directory
Fastboot moved to /usr/local/bin/fastboot
You may now run Android Debug Bridge and Fastboot commands
Have a nice day."
So I figured I'd open the script file and run each command manually but they would still not work. I then decided to open the target directory
from terminal and it couldn't find it either, so I openned the /usr/ directory to find where the /bin/ directory was... and I found it at | /usr/bin | instead of | /usr/local/bin |.
I ran the commands in the script again manually one by one with the target directory set to | /usr/bin | and then closed terminal and reopened. After that I tried running "adb devices" and the output was "permission denied".
I then applied a "chmod 775 /usr/bin/adb" "chmod 775 /usr/bin/fastboot", closed & reopened terminal and voilà it worked!
Again I'm not a savy guy... there might probably be a better way to do this or perhaps I didn't run the install script as it was supposed to but anyway I decided to let you guys know how it went just in case it proves useful to somebody else....
Then again thanks a lot for sharing this! I finally have ADB + Fastboot on my Mac without having to nag about downloading the Android SDK. :laugh: :good:

Root vtab1008 honeycomb (masterkey)

!!!UPDATE!!!!
Sorry I lost my root files. I still have the base code i used to make them. I am trying to work with @saurik to get vtab1008 working with the cydia impactor so that this process will be eaiser. sorry about not keeping up here.
The linux root is still working.
!!!!!!!!!!!!!!!!!!!!!!!!!!!
I was able to get the VTAB1008 HONEYCOMB ROOTED. This device is no longer doomed to a rootless existence.
ROOT AT YOUR OWN RISK! I AM IN NO WAY RESPONSIBLE IF THIS BREAKS SOMETHING.
----WINDOWS ROOT (This worked for me)----
!!Some people have had problems with 64 bit systems.!!
https://dl.dropboxusercontent.com/u/...nys Root.zip (restored by grnsl2)
Download the latest java sdk http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
(if it installs anywhere but C:\Program Files\Java\jdk1.7.0_45\bin\jdb change the path in the runme.bat)
Setup ADB
Follow instructions at http://www.google.com/url?sa=t&rct=...5IAx2Xg-VjGm5pQ&bvm=bv.57155469,d.cGU&cad=rja
for the inf file use the one in the skinnys root,zip
!!!THIS STEP IS VERY IMPORTANT ^ IF YOU ARE HAVING ISSUES YOU MAY HAVE NOT COMPLETED THIS STEP!!!
Run Exploit
open command prompt (windows 7 type cmd in start menu and press enter)
CD to location you extracted the zip
example: cd "C:\Users\skinny\Downloads\Skinnys Root"
type "runme.bat"
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
----LINUX ROOT----
Get Linux on a live usb stick to run exploit (skip if you have a linux system)
Download 32bit kubuntu from http://www.kubuntu.org/getkubuntu/download
Get a thumbdrive at least 2 gig
Launch unetbootin
Select bubble next to diskimage
Choose ISO
Click on ...
Browse to the kubntu iso downloaded at A.
Set drive to your usb drive letter.
The next step will erase your thumb drive!!!!!
Click OK
Process will complete and ask you to reboot (reboot)
Select the thumbdrive at startup (i don't know what type of computer you are using but most systems you can press f8, f11, f12 or f2 tp get the boot prompt)
(For more information read this guide http://sourceforge.net/apps/trac/unetbootin/wiki/guide)
Select Default at the kubuntu boot prompt
Select Try Ubuntu
Get kubuntu linux setup for the exploit (skip if you already have android tools on linux)
Press alt+f2
Type "konsole" and press enter
Paste the following commands in.
Code:
sudo chown kubuntu:kubuntu /opt
mkdir /opt/exploit/
cd /opt/
wget http://dl.google.com/android/adt/adt-bundle-linux-x86-20131030.zip -O adt.zip
unzip adt.zip
mv adt-bundle-linux-x86-20131030/ adt/
echo 'export PATH=$PATH:/opt/adt/sdk/build-tools/android-4.4:/opt/adt/sdk/platform-tools' >> ~/.bashrc
source ~/.bashrc
sudo su -c "echo 'deb http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main
deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main' > /etc/apt/sources.list.d/oracle-java.list"
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EEA14886
sudo apt-get update
sudo apt-get -y install git
cd /opt/exploit/
sudo apt-get -y install oracle-java7-installer
Accept Java license agreement to install java 7
Run Exploit
Plug in your tablet
Enable debugging mode (Settings -> Applications -> Development -> USB debugging)
Paste the following commands in your linux console (if following steps use the konsole that you have been running commands in).
If you are not using /opt/adb/sdk for your android devlopemnt use your dir on the 3rd step
Code:
git clone [url]https://github.com/raymondhardy/mkbreak.git[/url]
wget 'http://goo.gl/Ox8qDx' -O Superuser-3.1.3-arm-signed.zip #thanks to @Munk0
unzip Superuser-3.1.3-arm-signed.zip
cp system/bin/su mkbreak/
cp system/app/Superuser.apk mkbreak/
cd mkbreak
./doit.sh /opt/adt/sdk
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
If you get stuck at any part of this process please post a reply with information about the problem you are having.
PROOF OF ROOT
Thanks and credit goes out to.
robertmillan
Jay Freeman (saurik)
PoC by Pau Oliva
Vinogans for leading me to masterkey exploit

NICE!!! Any instruction changes for windows?

gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Not yet i suspect someone will make a better root later on as of now this is linux only. This exploit uses of linux commands for injecting code into a system application to gain root.

I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)

skinnyquiver said:
I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)
Click to expand...
Click to collapse
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk

I updated the steps and re-rooted my tablet with them several times to verify that they worked. Let me know if they work for you
dandrumheller said:
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse

gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Got this working on windows (does not look very pretty but it works.

Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3

FadeFx said:
Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this

vinogans said:
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this
Click to expand...
Click to collapse
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3

FadeFx said:
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
u will have to update to .57 then u will get honeycomb update ..

vinogans said:
u will have to update to .57 then u will get honeycomb update ..
Click to expand...
Click to collapse
Thats bad, but i will give that a try. However, i cant promise that i will succeede and it will take me some days as i am quite busy with my real life as well
_________________________
tapatalked from GalaxyS3

So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk

grnsl2 said:
So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
You should be able to use this root with the 5.7 before going to honeycomb. This way you can have gingerbead rooted if your device came with the 5.7 update. I would like to get this running cm9 or cm10. The first problem with this is it will require a new kernal. I am going to be moving this weekend so it will be a while until I can get a build env to work on this. I plan on using this tablet to learn all about android rom making. Hope I don't brick it.

As Vizio has not released the kernel source I think we may want to look at using the xo-3 kernel.

Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?

unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
What os do u use? Check if adb is working
_________________________
tapatalked from GalaxyS3

unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..

vinogans said:
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..
Click to expand...
Click to collapse
Thanks for all the suggestions! I was surprised so many people responded on such a forgotten tablet.
I did enter the two commands in the shell (copied and pasted the exact commands) at the appropriate times, and they appeared to work.
I wasn't able to do the ADB setup exactly per the link on the OP, because my computer already recognizes the VTAB1008 under debugging mode, and runs ADB. If I try to uninstall and manually install the generic driver from the Skinny Root zip, it re-discovers and says the current driver is 'more current'. However, since 'adb devices' recognizes the vtab, and all the commands appear to be working, I should be good to go with ADB, right? Or is the generic driver from the Skinny Root zip file a critical component?
I also uninstalled Java SDK for x86 and re-installed for 64 just in case, but that didn't fix it.
Also tried disabling antivirus, no luck...
Is there a basic way to check whether java is working correctly? Or to read the java output as it is running the commands? Maybe something would show up there.
Thanks again

Do u see superuser app installed? If so, what does it output when you open it?
_________________________
tapatalked from GalaxyS3