I have no idea why there's no tool for that yet, so I decided to make one myself, but I need your feedback to make it good for everyone. So, my current goals are:
1) As simple as possible, all required files should be packaged with the app or downloaded dynamically
2) Cross-platform compatibility (Windows, Linux, Mac)
3) Minimal user interaction, as automated as possible
I see two solutions:
* X11-less console Linux LiveCD image to be booted in VirtualBox or on real hardware.
Pros: completely controlled environment, no drivers required, bash scripting, all libs and binaries bundled.
Cons: large image size, sometimes difficult to use, no GUI so less user friendly
* GUI Qt app
Pros: flexible language (C++), nice GUI, simple to use, allows for small size and on-the-fly downloads
Cons: have to compile and test separately on 3 platforms, different libs/binaries, Linux dependency hell, probably no Mac support because I don't have one.
So, what do you guys say? I'm open for ideas now and won't start coding until Monday.
I only joined the android world a little while ago when the moto olympus/atrix came out but isn't getting root on this as easy as
a)make sure you have a microSd card inserted
b)make sure unknown sources is enabled
c)install the gingerbreak apk, openeng the app and clicking on "root device"?
I'm no developer and haven't a clue what it takes but this would be epic.
Windows GUI
Sent from my HTC Vision using XDA Premium App
Vigneshd said:
I only joined the android world a little while ago when the moto olympus/atrix came out but isn't getting root on this as easy as
a)make sure you have a microSd card inserted
b)make sure unknown sources is enabled
c)install the gingerbreak apk, openeng the app and clicking on "root device"?
Click to expand...
Click to collapse
Okay, I meant root+blob+CWM
Sent from my HTC Desire using XDA Premium App
smellmyfingers said:
I'm no developer and haven't a clue what it takes but this would be epic.
Windows GUI
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
K900 said:
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
I don't even know what these "blob" things are yet.But if you need testers, thats what the rest of us here are for. Count me in.
Hmm... I wonder how a plugin system could work... So, a core library that handles adb, device identification and plugin loading, plugins dynamically linked to the library (needs a stable API though) and a manifest that lists compatible devices and plugins to be used for them... Could be something like that (YAML inspired);
device:
info:
vendor: 'ASUS'
model: 'Eee Pad Transformer'
pciid:
uses:
- gingerbreak
- tf101
And libgingerbreak.so to push and run gingerbreak (a generic one) and then a device specific libtf101.so to take care of blob flashing action.
P.S. It's night here and I'm tired as hell. Sorry if I wrote some nonsense... If anyone is interested in making it big, PM me here or on github.
Sent from my HTC Desire using XDA Premium App
K900 said:
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
Yeah, that's just the thing. What's good about a livecd is that you are 100% sure it works everywhere, cause nothing changes. But if you make it native, you need drivers on Windows, udev rules or root privileges on Linux and a Mac to make it run on a Mac...
Sent from my HTC Desire using XDA Premium App
K900 said:
Yeah, that's just the thing. What's good about a livecd is that you are 100% sure it works everywhere, cause nothing changes. But if you make it native, you need drivers on Windows, udev rules or root privileges on Linux and a Mac to make it run on a Mac...
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
To make it simple isn`t going to be easy I`ll say it again best of luck.
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
Yup essentially like one-click rooting app for the Galaxy phones.
It is ***UHHH... get the software and d/l on the computer.....ummm.... click to open
Click the flashing neon sign that SAYS: "click here dummy !!" ...........you are rooted...........
Anything you coud put together would be an absolute god send. I managed to root my X10 okay, and my other half's Vega..... but the guides for the transforemer may as well be in mandarin for all I understand them. I really need a click here, install this, type that, press this, turn round three times and throw salt over your shoulder sort of guide..... or any of your lovely proposed one click solutions
The best I have is a pair of batch files that go through the pre and post root process that I've modded with directions. This assumes you have ADB setup from the Android SDK install and have the ADB drivers installed and working. You need to have USB Debugging enabled via Settings > Applications > Development. If you do not, get the Android SDK and read up on how to setup ADB. There's tons of posts on XDA about how to do just that.
Download tf101-root.zip here
md5: 57f22712625fe75f685499b60b189aa8
Firstly, run root-prep.bat from where ever you extracted tf1010-root.zip (preferably in your platform tools folder for your Android SDK install).
This is the batch file content of the root-prep.bat:
Code:
adb push gingerbreakBB /data/local/
adb shell chmod 777 /data/local/gingerbreakBB
adb push CWM_BLOB_V5 /data/local/
@echo off
echo Now do "adb shell" from another command window. In the shell, do "/data/local/gingerbreakBB" without quotes. DO NOT CLOSE THAT COMMAND WINDOW, EXIT THE SHELL, OR REBOOT AFTER GINGERBREAK IS DONE! THE ROOTING PROCESS MAY WIPE YOUR SD CARD SO BACK IT UP BEFOREHAND!
pause
Go to your Android SDK folder in explorer and (if you're on Vista/7) shift+right-click the platform tools folder and click "open command window here" for a new command window already set to that folder. XP users will have to do it manually or download the PowerToy from this page. Download the "Open Command Window Here" tool and it works exactly the same as on Vista/7. GINGERBREAK MAY OR MAY NOT WIPE YOUR SD CARD SO BACK IT UP BEFORE DOING IT JUST IN CASE!
Rooting process:
Code:
C:\aSDK\platform-tools>adb shell
$/data/local/gingerbreakBB
<you'll see all the gingerbreak stuff here>
#
DO NOT CLOSE THIS COMMAND WINDOW AND DO NOT EXIT THE SHELL WHEN IT'S DONE! If you don't get the # symbol in the shell after running gingerbreak, you'll have to run the root-fail-fix.bat then do the above again after the reboot.
This is the batch file content of the root-fail-fix.bat:
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb reboot
If you get the # symbol after gingerbreak is done, run post-root.bat from the same command window as you did root-prep.bat or a new command window. After the reboot you should be fully rooted!
This is the batch file content of the post-root.bat:
Code:
adb remount
adb shell dd if=/data/local/CWM_BLOB_V5 of=/dev/block/mmcblk0p4
adb push su /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/xbin/busybox
adb push Superuser.apk /system/app/
adb reboot
You can do the commands manually just to make sure everything works properly (encouraged) or just run the batch files from a command window if you're lazy.
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
That would be a godsend
I can appreciate how many would look at the rooting guide and say "WTF?" Think about it, unless you are command line savvy, the process can be daunting. Not including the linux users we have a generation (or two) who never had the "pleasure" of running DOS so they have not had the experience of a flashing cursor just waiting for the human to tell it EXACTLY what you want in PRECISE commands.
Ahhh...the good old days. (kidding....really...or so says my pet rock...with the mood ring)
Guess I'll hack together windows batch and linux shell scripts tomorrow and start working on the app later, cause I have no free time now.
Sent from my HTC Desire using XDA Premium App
have talked to the guy in Xoom section that created the various 1-Click Root proggies. Check them out here . Maybe he can give you a hand or some suggestions
Here are the threads
http://forum.xda-developers.com/showthread.php?t=1093126
http://forum.xda-developers.com/showthread.php?t=1011196
I am for whatever, even livecd is easier for you to make.
I think it is less work and with simple instruction it allways works.
Sent from my HTC Desire using XDA Premium App
I think with the key now out and the ability to modify any Asus TF ROM it might be wise to wait and make something that works with NVFlash? But I don't know a lot about this stuff so ignore me if you think I am an idiot
I vote for a GUI QT App. The point of One Click Root is to make rooting as painless as possible. A live CD doesn't seem to follow that...
Related
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]
Make sure your battery has a decent amount of charge in it, you don't want to run out of juice in the middle of this.
You will need to have the android sdk installed, as you will need to use the adb tool.
Windows users will need to install HTC Sync in order to get the usb driver for the phone installed.
Part 1: In which we find that the Evo spreads easier than a Thai whore during tourist season
Code:
adb shell "rm /data/local/rights/mid.txt"
adb shell "ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt"
adb reboot
Part 2: In which we find that engineers have no personality, but they make one hell of a bootloader
Put the files from Toast's Part 2, for nand unlock onto the sdcard (PC36IMG.zip, mtd-eng.img, recovery.img, flash_image)
then (after making sure the sdcard is remounted to the phone if you used disk mode to xfer the files):
Code:
adb shell "cat /sdcard/flash_image > /data/local/rights/flash_image"
adb shell "chmod 755 /data/local/rights/flash_image"
adb shell "/data/local/rights/flash_image misc /sdcard/mtd-eng.img"
adb reboot bootloader
When asked if you want to update, say yes. Relax for a while, the update takes some time.
When the phone eventually boots back up:
Part 3: In which I find the whore, and make her install a custom recovery
Code:
adb shell "cat /sdcard/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/recovery.img"
After this you should be fully rooted with nand unlock.
I highly recommend going through Whitslack's Starting Over method to bring your software and radios up to date.
You're done.
Pity this only came to light a few days before people are going to be upgrading to a new OTA.
No, this will not work for anyone who updated to 2.2.
epic!!! 789
niice!
Nice Find!
At least now people can be rooted prior to the new OTA!
damn it!
___
Sweet! Wish I had that method starting out. Lol.
Sent from my PC36100 using XDA App
does this method really work??
BAttitude7689 said:
does this method really work??
Click to expand...
Click to collapse
Yes it does.
ok, so i have no idea how that works... care to go into it alittle bit more?
khshapiro said:
ok, so i have no idea how that works... care to go into it alittle bit more?
Click to expand...
Click to collapse
The init scripts chmod 777 mid.txt on boot (this means that anyone can do anything to the file basically). By removing the file and linking it to mtd1, the chmod now makes mtd1 accessible by everyone after a reboot, which means that you can go directly to toast's part2 which starts with flashing mtd-eng.img.
Incidentally it appears the droid eris guys have been using this flaw to their advantage for a while as well ;D.
So no, really? What is "root?"
You do fine work, sir
posting in a legendary thread
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
netarchy said:
Part 1:
Code:
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
What would be more interesting is for someone on the new OTA non-root to see if this exists in the Froyo release. I'll look around for a posting of the OTA update non-rooted and try it on my smashed phone. At least I won't care if that thing looses root.
Could we get a "The easiest 1.47.651.1 root method with nand unlock" for dummies? I have no clue what to do with this code.
You need to use an ADB shell for this using the Android SDK....
I tried to use the Evo-Recovery shell and received permission denied errors.
I am not a DEV by any means, and do not claim any credit for any of this. However, for people who need help, this may offer some assistance -- this is definitely the easiest root method out there.
1. Download and Install Android SDK - Learn Here
http://forum.xda-developers.com/showthread.php?t=694250
2. Open up a Command Prompt by holding windows button & pressing R or by pressing Run and typing CMD.
3. Navigate your way in DOS to the Android SDK folder, then to the Tools Folder
4. Then enter in the code in part 1. After each line press enter...the line will repeat below it.
5. Follow Toasts Part 2 -- Link: http://forum.xda-developers.com/showthread.php?t=701835 -- Video found here: http://www.youtube.com/watch?v=tUXTB0eydwE.
5A. Because you didn't do Toast's Part 1 of Root first (you used an exploit provided by the OP), you will NOT have a NAND Backup. Put the Custom ROM you want to load on your SD card, and after unlocking NAND protection and doing the wipes, load it from the custom recovery in lieu of restoring your NAND backup.
6. You're now rooted w/ NAND Unlocked!
7. I would then suggest going here, and running this so you have a fully rooted, stock ROM with all your radio/wimax up to date: http://forum.xda-developers.com/showthread.php?t=715915.
Anyone know if this method will work on an unrevoked3'd Evo? I am trying to acquire full root and I was going to use SimpleRoot today but if this will work...
Thank you for this! Question about number part 7. YOu suggest running the fully rooted stock 1.47.651.1 afterwards. Would it be a bad idea to Just run the fully rooted stock froyo 3.23.651.3 or even any other custom rom for that matter? i.e OMJ's EVO 2.2 Custom rom? Thanks
regulator207 said:
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
Click to expand...
Click to collapse
No because you need the engineering hboot to flash it since it's not signed by HTC.
Should work on 1.32 or 1.47. Nice.
Someone should test if this still works in the new 2.2 update. Good chance it does.
damit!
justinisyoung said:
damn it!
___
Click to expand...
Click to collapse
Hey! That's what I was gonna say!
is there a way to use ubuntu to root the epic? I have ubuntu and I want to root my epic but I can't figure out how to use the one-click method because I can't really use the drivers. I was trying to use the terminal with adb but I don't really know what I am doing.
linux doesnt need drivers i made a one click script for linux ill see if i cant find it
http://www.mediafire.com/?hk59z8j5dve6tgf
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable
You can try following along the run.bat script included in the one click root. I did not need to install any drivers to root using Ubuntu, but I did download the Linux version of the android sdk (from Google) just in case (instead of using the adb included in the one-click-root download.
If you have your android-sdk-linux_x86 directory in ~/Downloads/, and you extracted the one.click.root file into ~/Downloads/ as well, here's what you could do:
cd ~/Downloads/one.click.root
(Now you're in the location of the one click root files.)
Next, type each line of the run.bat file manually. Any time you see "adb" replace it with:
sudo ../android-sdk-linux_x86/tools/adb (command)
You'll need to adapt a bit to your situation, but because most of the adb commands are native to adb and run on the phone, they should work verbatim on your Ubuntu system.
Didn't someone put out a Linux one click root, though?
EDIT: Yes, shabbypenguin did. Looks like he posted it above me before I finished typing my post. Whoops.
Complete Big edit....
I thought I bricked my phone but I didn't. I ended up getting the permanent root. I used this guide http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
Is there anything special I am missing? like busybox? or remount scripts? not sure what either of those are.
remount allows your system to have rw access with a simple command, busybox.. think of it as an extended shell
the zip i included in my post is based off noobnl's latest version and works fine with linux. i made it while using ubuntu
shabbypenguin said:
linux doesnt need drivers i made a one click script for linux ill see if i cant find it
[snip]
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable
Click to expand...
Click to collapse
Thank you so much for this! ... "You have no chance to survive make your time" means I'm rooted?
i made version 2, its in my sig, will root and install clockwork mod 2.5.1.0
My computer has very low ram, as a result anything related to flash or anything having high memory requirement crashes and usually freezes ie resulting in a restart
So I would like to keep the computer out of the equation
I am wondering if one can root a phone without a computer
This may seem like an odd request/question but I am in a terrible place, my stuff was stolen, I am even more broke than before.
Thanks for any help
You can try z4root.apk but it may or may not work....really need a computer with superoneclick
Sent from my SAMSUNG-SGH-I997 using xda premium
use virtualbox to run Windows and use superoneclick using the virtual Windows.
here's the website with info for getting it going and downloads
https://www.virtualbox.org/
good luck
hollywood528 said:
use virtualbox to run Windows and use superoneclick using the virtual Windows.
here's the website with info for getting it going and downloads
https://www.virtualbox.org/
good luck
Click to expand...
Click to collapse
his computer has low ram. running a vm will make that situation much much worse!
look in the dev section for a root/unlock tool from lost1 it includes adb, ragagainst the cage binary and a batch script for windows and shell scripts for linux and mac. just extract the package to a convienient place like c:\ in windows or your home or root directory in linux then using comand line cd into the extracted folder and run the approraite script.
I can do this within linux ?
GreenAce92 said:
I can do this within linux ?
Click to expand...
Click to collapse
yes, there are different scripts for different os's the root.sh is the one for Linux. under the assumption you are a Linux newb to execute a ascription you may need to change permissions to executable first. you can usually set this in gnome or whatever window manager you like. or with chmod
chmod 0755 root.sh
then to execute the script you just type
./root.sh
this is all assuming you are within the folder that contains the script.
it appears all it does it move a binary to /data/local wait a few seconds and then copy su to /system/bin. you could easily do that through adb if you are familiar with it.
So uhh
Could you dumb this down even further, I am a complete linux newb as you say and I have just installed Linux Mint 11 32bit on an old HD of mine so Linux is here to stay, I'm interested in learning it too
But anyways... what can you suggest so that I can catch up / understand what you have just told me to do?
Thanks for this
GreenAce92 said:
So uhh
Could you dumb this down even further, I am a complete linux newb as you say and I have just installed Linux Mint 11 32bit on an old HD of mine so Linux is here to stay, I'm interested in learning it too
But anyways... what can you suggest so that I can catch up / understand what you have just told me to do?
Thanks for this
Click to expand...
Click to collapse
first download the root/unlock package from this thread
forum.xda-developers.com/showthread.php?t=1081072
unzip the package and find the root.sh file.
ok, Linux sets file permissions that tell the system who can access the file and how. on Ubuntu new files are set as non executable by default. mint being based on Ubuntu is the same. the permissions are set with a 4 digit number, the first number is special permissions and you wont use that very often. the second digit is for the user that owns the file, the 3rd is for the group and the 4th is for the others.
if you use command line the chmod command will set these permissions. 7 designates read write and executable, 6 is read write, 5 is read and executable, 4 is read only.
but you can also set a file as executable in gnome. right click the icon and choose properties. there should be a box that says "is executable" or "alow execution of file as program" or something. check that box for the "script.sh" file.
once you do that right click in the widow of the folder that the root.sh script is in and choose "open in terminal" or "open window terminal here" this will open a command line window open to that directory.
make sure debugging is enabled in settings>applications on the phone and connect with the data cable. don't mount the SD card.
now type ./root.sh
that should start the script and root the phone. reboot when it's done.
Excellent
Many thanks to you good sir, I shall report back when I have tried this
Try looking here, works on Windows, Mac, and Linux: http://forum.xda-developers.com/showthread.php?t=1081072
GreenAce92 said:
Excellent
Many thanks to you good sir, I shall report back when I have tried this
Click to expand...
Click to collapse
oh forgot, you might need to set adb as executable as well. same thing. right click and go to properties>permissions>allow execution... or whatever it says in gnome. (I use kde and occasionally xfce for low performance hardware, but mostly kde)
Use heimdall to flash a custom kernel
!!!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