Related
I have read numerous posts listing the ways to get busybox installed on the phone. My problem is commands work under adb shell in recovery but do not work while the phone is booted w/out using a path or putting busybox in front. Ok so to the request. Will someone that has a stock rom still. Write instructions on how to get busybox installed. I need to be able to open terminal and run simple commands like uname as root. Thank you!
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
I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.
shmerl said:
I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.
Click to expand...
Click to collapse
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.
Cirkustanz said:
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.
Click to expand...
Click to collapse
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).
shmerl said:
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).
Click to expand...
Click to collapse
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.
jbats said:
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.
Click to expand...
Click to collapse
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.
shmerl said:
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.
Click to expand...
Click to collapse
I was pointing you in that direction for if and when you got near a computer using windows. Unfortunately you'll have to root that way. Once rooted you can stay away from win afterwards and just download and flash zips in recovery. I dual boot win 7 and Ubuntu 12.10.
Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.
Got a friend with a rooted phone? Got a otg cable? Use root transmission XDA link
There are a lot of rooting apps as well, but I wouldnt trust anything not found on XDA or the play store.
E107946 said:
Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.
Click to expand...
Click to collapse
Thanks. I have a fastboot and adb tools, from Android Platform Tools (it's a smaller package than a whole SDK: dl.google.com/android/repository/platform-tools_r16-linux.zip ). But will writing the rooted image unlock the bootloader? I'm a bit confused here. I thought the locked bootlader that was a main barrier for writing new images like CM with recover tools, and Odin/Heimdall actually unlock bootloader as a prerequisite for the rest. So will adb achieve the same? And if it does, what rooted image I should use for Blaze. One of these?
hotfile.com/dl/163659712/8fd8b1d/SGH-T769_UVLB7_Rooted_Deodexed_ROM.zip.html
hotfile.com/dl/163658008/35fc621/SGH-T769_UVLF4_Rooted_Deodexed_ROM.zip.html
OK, I managed to write a rooted kernel using Odin in the end. But that doesn't seem to help to write Cyanogen Mod to the device. I installed CWM (from Google's store) and rebooted into recovery. Now whey trying to apply an update using a CM image from download.cyanogenmod.org/?device=t769&type=
I'm getting the same signature verification error:
E: failed to verify whole-file signature
E: signature verification failed.
Does it mean that I still need to get another bootloader to flash it as well somehow?
UPDATE: OK, I figured it out. I flashed CWM from the CWM application itself, and then rebooted into recovery, which brought up CWM recovery. From there writing Cyanogen Mod worked without any issues.
Well, since you flashed boot image from Odin, you could just flash CWM with Odin as well. It would save you some time. But you figured everything out in the end anyway..
As a suggestion, I would recommend trying AOKP Beta. It is more stable than CM10 and works flawlessly with USB storage. It is my daily driver for over 2 weeks now.
!!!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