Database Users

Unroot the vibrant

I want to root but want to be reassured I can unroot for warranty purposes.

In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk

JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.

Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed

mmm easy
Ahh, easiest root/unroot makes me happy

Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.

bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?

Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..

skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?

ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice

mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?

where can I find the terminal On my pc?

temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.

bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?

Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks

temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.

hopefully this will help when people want to unroot if the update won't work without unroot

ADB required?

After looking at the rooting steps outlined here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
I was wondering if there was any reason you couldn't do the ADB steps in the terminal? Just place all the files on the sdcard and cp them to the proper directory from there. Taking ADB out of the steps would defnately make the process easier for people.
Is there something I am missing? Would this work?
Rooting the G2 and MT4G
Download:
gfree_temp-root.zip
gfree_04.zip
Unzip the contents of the above files, and place them them on the sdcard as follows:
/sdcard/ (root directory):
su
Superuser.apk
gfree
/sdcard/root/
rage
busybox
root
In Terminal make the following commands::
cd /sdcard/
cp -r /root/ /data/local/tmp/
chmod 0755 /data/local/tmp/*
/data/local/tmp/rage
After a minute or so, you will see the following message on the phone Forked #### childs. Press the Menu button & select Reset Term. The Terminal Emulator will exit out.
Launch Terminal Emulator. It will force close. Launch it a second time, and you'll have a root shell. You are now temp-rooted.
In Terminal make the following commands:
cp gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
/data/local/tmp/root
NOTE: You may see an error that states mkdir: /system/xbin already exists, if you do, simply ignore and continue on.
sync
Reboot. You are now perma-rooted, have radio S-OFF, and SIM-unlocked.

I perm rooted my first G2 without adb. There are specific guides for doing it without adb. Although if you do have the SDK and ADB, its very very easy lol.

Lol i didnt use adb. I use visionary and terminal
Sent from my HTC Vision using XDA App

I didn't use ADB either. Just a few simple commands in terminal.

http://forum.xda-developers.com/showthread.php?t=928160

Thanks, however.....
I have been reading that there have been issues with using Visionary to temp root. I just wanted to validate that it was OK to use terminal for the ADB steps.
Thanks!
~Jeff

[HOWTO]: Rooting the Huawei S7 Android 2.2.2 stock

Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might, like mine, just blink on and off for a while trying to flash what it thinks it finds is already flashed but what just gives an error!
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests done in that post on which rom work best for which model.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils im used to in the world of *nix was missing from the 2.2.2 image kindly provided by Huawei ( The Norwegian Telenor image i might add that the camera on a model 101 will not work with!) so i found an easier way! push push push!
Here's what i did, for convenience ill try making it a script, but be prepared to copy these commands manually instead! For windows simply remove the ./ and add .exe .
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adb binary that comes with SOC is a simpler route if your just in for a quick root fix. Simply rename the appropriate adb for your system and use this method.
The simplest thing to do i guess is to copy Exploits/psneuter or gingerbreak to the ADB folder (in SuperOneClick's folder) and go on from there, also copy su-v3 (rename it to su) and Superuser.apk from "Root/" to the folder (ADB), or if you choose to, rewrite this "script" with the appropriate paths. Im unsure if the following script will work in every case, so you might want to do it manually, but most should get the drift, if you are not comfortable with this procedure you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your USB mode to "Developer" mode
AND BE ROOT ON YOUR MACHINE!
Code:
#/bin/bash
echo "The BackAsswardsRootScript!\n\n"
echo "Lets start the adb server.\n\n"
./adb kill-server
./adb start-server
echo "Pushing the exploit psneuter onto the device.\n\n"
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter"
./adb push busybox /data/local/tmp/busybox
./adb shell "chmod 4755 /data/local/tmp/busybox"
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "We should be root now, making sure.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
./adb shell " /data/local/tmp/busybox mount -o rw,remount /system"
echo "Pushing the system files in place\n"
./adb shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/bin/busybox"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox"
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only, just for kicks!
echo "Remounting the filesystem as Read-Only\n\n"
./adb shell "busybox mount -o ro,remount -t /system"
echo "You should now be rooted my friend.\n Enjoy!\n"
Please help feed my Linux addiction! Go to http://threader.zapto.org and click Donate!

Rooting S7 using Gingerbreak
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.

Cool, theres a gingerbreak exploit in the superoneclick package also, i tried that after i though psneuter didnt work, just a matter of replacing psneuter with gingerbreak. Did you use this method though or did you find some other way?

I didn't change or replace anything. My terminal skills are not on a level to have the guts anyway.
I simply updated from S7V100R001C43B010 to S7v100R001C98B021.
Then ran the Gingerbreak 1.2 exploit.

Interesting, yeah the gingerbreak exploit will work, when i wrote the fist post i used the gingerbreak exploit instead of the psneuter one thinking psneuter didnt work, turns out it did though and i went back to that one as its designed for 2.2.2, didnt know of this wrapper though, thanks!

Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
threader said:
./adb shell "chmod 0755 /data/local/tmp/psneuter
Click to expand...
Click to collapse
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"

threader said:
Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might like mine just blink on and off for a while trying to flash what it finds is already flashed but what just gives an error. !
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests there on which roms work best for which models also.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils was missing from the 2.2.2 image kindly provided by Huawei (Norwegian Telenor image, that i might add, the camera on a model 101 will not work with!) soo i found an easier way! push push push!
Heres what i did, for convenience ill try making it a script, but im making it as i type this post so this is untested as a script(!) Be prepared to copy these commands instead!
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adblinux binary that comes with SOC will work just as well, simply rename it to adb and use this method. The simplest thing to do i guess is copy Exploits/psneuter to the ADB folder (in SuperOneClick's folder) and go from there, also copy su-v3 (and rename it to su) and Superuser.apk from Root to the folder (ADB), or rewrite this "script"/collection of commands i used" with the appropriate paths. Im unsure if the following script will work as is as i said, so you might want to do it manually, but most should get the drift, if not you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your usb mode to Developer mode
BE ROOT!
#/bin/bash
echo "The backasswardsrootscript!\n\n"
echo "Lets start the adb\n\n"
./adb kill-server
./adb start-server
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "Should say we are already root now.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
# This really should be /dev/block/mmcblk0p1, i have no idea why this works.
./adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p1 /system"
# Now instead of copying using cp or moving with mv, considering "cp" was missing
# and mv just didnt work for some reason...! I found just pushing the files straight to the
# system after remounting worked just fine
echo "Pushing the system files in place\n"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
./adb push busybox /system/bin/busybox
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only just for kicks!
echo "Remounting the filesystem as Read-Only\n"
./adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p1 /system"
echo "You should be rooted my friend\n Enjoy!\n BE SURE TO DONATE TO SUPERONECLICK!!!"
# One of the main strangenesses i found was the block device was logically enough placed on
# partioton 1, of block1 which really should have been block 0 part 1, but that doesnt work.
# So it boils down to that this shouldnt work but does for no apparent reason(!).
# even /etc/mtab says that mmcblk0p1 is mounted to a non existent /mnt/dcard
# as an EXT4 partition which isnt supposed to be supported until 2.3.x
Click to expand...
Click to collapse
Dear S7 users,I am using the ideos s7 by Teltra supllier and i did unlock sim by norwegian rom.I read a lot of document but i didnt find out an easy way to run clockwork that i can run cook rom,can u help me how to run it in easy way.Thanks and appreciate that.
http://www.androidtablets.net/forum...wegian-2-2-2-s7v100r001c57b111.html#post82863

PuZZleDucK said:
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
Click to expand...
Click to collapse
Great! Thanks! Ops, yeah missed that, fixed now, thank you for pointing that out. I haven't spent much more time on this. the pad has pretty much been untouched since i moved house. I would like to make this easier for less technical inclined here but its just a matter of replacing ./adb with adb.exe if your on windows. Besides, i don't want to be at fault for bricking someone. And maybe i could write some simple application for installing Gnu/Linux as well, ( http://forum.xda-developers.com/showthread.php?t=1109730 ) but that will have to wait until someone bribes me or hits me over the head i guess.

tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..
---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------
Maniacnl said:
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Click to expand...
Click to collapse
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..

[ROOT] Telstra from the Latest HC3.1 Update + Unsecured New Boot Image

Hi everyone, I am writing this post because there is currently no information on rooting the Telstra specified Motorola Xoom from the Stock 3.1 and still keeping 3G (the latest 3.1 update, not the problematic one). Since I don't have enough post to be able to write in Development section, I just write it over here and I take no credit for this.
With this root, you don't have to flash any custom recovery at all.
1/. Ensure that you have the Motorola Xoom STOCK 3.1, N_01.83.35P, H.6.3-25-5 or you can move back to stock, flash everyback from
developer.motorola.com/products/software/MZ601_H.6.1-38-9_Telstra_Australia.zip/
and receive the official OTA update.
2/. Ensure that you have already UNLOCKED your Motorola Xoom bootloader. This will wipe your device out so be very careful.
3/. Download the attachment file to this thread, which contain the new unsecured boot, su and superuser.apk file
4/. Enable USB Debugging on your Xoom
5/. Open command prompt, write the following code:
Code:
adb reboot bootloader
6/. Now your AU Xoom will reboot, continue to type this:
Code:
fastboot flash boot newtelstraboot.img
fastboot reboot
7/. Wait for your AU Xoom to reboot to HC. Open your command prompt, type this:
Code:
adb remount
adb shell su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
Now you got root on your Australian Xoom from Telstra with working 3G.
Cheers
Screenshots:
img638.imageshack.us/img638/1516/screenshot1ew.png
img21.imageshack.us/img21/1907/screenshot2ck.png

Shouldn't be Step 7 more like ->
Step 6
Code:
fastboot flash boot newtelstraboot.img
fastboot reboot
Step 7
Code:
adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb reboot
BTW: it should be called Non-US Xoom instead of AU Xoom

Oh, thks,
There are something I want to say though:
First, I don't think you should really need a reboot at the end of step 7. It works for me without the need to reboot.
Secondly, I'm not quite sure if my procedure works with other non-AU xoom. I have just been able to test on 3 Australian Telstra Xooms. At least they all work!
However, I'm new so I am willing to learn from you all. Thanks.

[VIDEO] How to Root the Amazon Kindle Fire HD Tablet

Major thanks to Sparkym3 for coming up with this exploit, and to Justin Case & Hashcode for helping do this on my tablet today.
Here are the files that you need:
http://www.reverendkyle.com/download/Superuser-3.1.3-arm-signed.zip
http://www.reverendkyle.com/download/Kindle_Fire_HD_ADB_Drivers.zip
Be sure to install ADB on your computer first!
http://www.reverendkyle.com/index.php/articles/130-how-to-install-adb-for-android-in-windows
The commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
The original instructions can be found here:
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/

lol, a whole 3 days, what took everyone so long?
Sent from my One X

I want to say don't release it until the 9 inch version comes out and we can root that too. Don't give amazon the details to patch it.

I think an alternate launcher would satisy lots of people without having to root.

supernoman said:
I want to say don't release it until the 9 inch version comes out and we can root that too. Don't give amazon the details to patch it.
Click to expand...
Click to collapse
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.

reverendkjr said:
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.
Click to expand...
Click to collapse
just tried adb shell and it says error finding device. any suggestions? how do i go into "developers" mode with the kindle fire hd?

http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
Sent from my SPH-L710 using xda premium

How complicated and how long of a process is this?
I'm not tech savvy but if not too difficult, I'll give it to a friend to attempt after I buy the Fire HD tomorrow!

Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?

Just about to report that thee was a working root. Good guide
Sent from my Nexus 7 using Tapatalk 2

tenchichrono said:
just tried adb shell and it says error finding device. any suggestions? how do i go into "developers" mode with the kindle fire hd?
Click to expand...
Click to collapse
I have the same trouble... any ideas would be greatly appreciated!
---------- Post added at 08:35 PM ---------- Previous post was at 07:48 PM ----------
tenchichrono said:
Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?
Click to expand...
Click to collapse
I got the drivers installed to fix my previous problem but now I have this problem above

tenchichrono said:
Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?
Click to expand...
Click to collapse
The command should be "rm -r /data/local/tmp"
It removes the directory and its contents.

reverendkjr said:
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.
Click to expand...
Click to collapse
I'm pretty sure rooting is not the problem everyone is concerned about. Flashing a different ROM will be the tricky part without a working custom recovery.

soupmagnet said:
I'm pretty sure rooting is not the problem everyone is concerned about. Flashing a different ROM will be the tricky part without a working custom recovery.
Click to expand...
Click to collapse
It's being worked on.

reverendkjr said:
It's being worked on.
Click to expand...
Click to collapse
Hey reverend, a little off topic, but could you post a video of root? I'll subscribe
Sent from my Nexus 7 using Tapatalk 2

ncvikingx97 said:
Hey reverend, a little off topic, but could you post a video of root? I'll subscribe
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's funny that you should ask for that. I'm working on a video of it right now. :angel:

Cool. Sub
Sent from my Nexus 7 using Tapatalk 2

Success!! Thanks for posting these instructions
Also, for verification purposes, I was able to successfully install ROM TOOLBOX pro and after several reboots the 'rebooter' shortcut works...

Now this is exciting! This should really get the ball rolling on the whole development for this device

So how about the Play store? Any ideas how to get it on?