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
Related
sorry but how do i get to adb shell from the command propt??
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
wadeheisen said:
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
Click to expand...
Click to collapse
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
xxxk15 said:
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
Click to expand...
Click to collapse
What are you trying yo do? What rom are you running? Are you rooted? Need more info please.
cd to the sdk\tools folder. That is where the commands you need are.
adb remount
adb shell
Click to expand...
Click to collapse
but once i am in the tools folder what program do i use because when i click on them they come up and go away real fast??
Click to expand...
Click to collapse
Go to a command promt. In other words go to start and search for this
Cmd
Then type commands mentioned above
The easiest way is to just hold down SHIFT and then right click on blank space, and then select Open Command Window Here. Also, I'd HIGHLY recommend adding ADB to your PATH.
well i am running 2.09.1 DC and i am rooted. when i download apps it tells me "Insufficient Storage Available" I have enough internal memory so i searched that and one person said they fixed it by
cd /data/data
rm -rf info.lamatricexiste.network
So i wanted to try it but i am really confussed on how about going to do this
xxxk15 said:
well i am running 2.09.1 DC and i am rooted. when i download apps it tells me "Insufficient Storage Available" I have enough internal memory so i searched that and one person said they fixed it by
cd /data/data
rm -rf info.lamatricexiste.network
So i wanted to try it but i am really confussed on how about going to do this
Click to expand...
Click to collapse
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click Start
1. Click RUN
2. type CMD in the box press enter
3. In the command prompt type
Code:
cd C:\AndroidSDK\Tools
this is just a guess and where most people have it. It MAY be different for you.
4. Type
Code:
adb remount
adb shell
5. You should see a "#"
6. Now type
Code:
cd /data/data
rm -rf info.lamatricexiste.network
Kcarpenter said:
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click Start
1. Click RUN
2. type CMD in the box press enter
3. In the command prompt type
Code:
cd C:\AndroidSDK\Tools
this is just a guess and where most people have it. It MAY be different for you.
4. Type
Code:
adb remount
adb shell
5. You should see a "#"
6. Now type
Code:
cd /data/data
rm -rf info.lamatricexiste.network
Click to expand...
Click to collapse
ok i understand but my command propt comes up with stuff in it
C:\Documents and Settings\Admin>
How do i get rid of this??
I assume you used a kitchen to root?
FWIW This is really basic knowledge that you will need as you use your phone.
So if you are a PC:
0. Click
Click to expand...
Click to collapse
ok i understand but my command propt comes up with stuff in it
C:\Documents and Settings\Admin>
How do i get rid of this??
Click to expand...
Click to collapse
Nothing just type the commands that were given and UT will take u to the right directory
Papa Smurf151 said:
Nothing just type the commands that were given and UT will take u to the right directory
Click to expand...
Click to collapse
o ok thanks it worked!!
I previously received my vibrant rooted and using this method on the thread http://forum.xda-developers.com/showthread.php?t=734475 and i used the unrooted file on page two. everything worked great but i still have root. I have the superuser permission show up on my app list, i also tested to see if i have root by installing a root only app, and it worked. so can anybody help get to stock?
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
ttabbal said:
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
Click to expand...
Click to collapse
yes i used the nandroid. can you point me to the odin flash? and is the odin more dangerous to use than nandroid? thanks for the help.
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
vdub804 said:
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
Click to expand...
Click to collapse
listen, im new to this and ive already searched the devolpment section and theres a couple similar threads. so, since i dont really know what im doing, i asked for help. all i asked was to point me to the thread that someone who is experienced in this thinks i should use. thanks for the help.
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
ttabbal said:
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
Click to expand...
Click to collapse
thank you for the help. i was just confused as to which one to use. hopefully, when im more experienced in this, i wont post stupid questions like this.
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
stepinmyworld said:
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
Click to expand...
Click to collapse
did u type "su" before typing every other else?
it should be like:
# whatever you type
not $ whatever you type.
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
From the sticky at the top of the page (that says to read before asking). If you want to use the links, go to the sticky.
HOW TO UN-ROOT *ie, sending your phone in for warranty work
The following code can be keyed in Terminal Emulator (could also be done in ADB or deleting the files using Root Explorer). If you do use Terminal, change the keyboard to the stock Android KB prior to opening Terminal. Apparently the backspace on swype does not work in Terminal. Each line should be entered separately. bahnburner gave the instructions in this thread, which you should review first.
Quote:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
* Alternate Method *
TGA_Gunnman in this thread created a one click root/unroot program. Thank him for his effort.
mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
mrxela said:
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
It is in the sticky.
JEEBUS (10....)
mrxela said:
It is in the sticky.
Click to expand...
Click to collapse
aww shux. smh
thanks
I used root explorer and deleted those files, so that means I'm on stock and I can get warranty service? Thanks a lot guys, you have saved a noob
stepinmyworld said:
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
Click to expand...
Click to collapse
Haha rooting won't keep you from getting OTA updates.
ONLY WORKS WITH ANDROID 2.2 (FROYO)
For those of you that don't know, Google released a new Voice Search that allows "actions". For more info go Here.
First off, I wanna thank Tsenru, klinster, devlogic, BinaryMan, and Synchromatic @ the CM forum for all the info.
This is instructions for ubuntu so make the proper adjustments for windows if needed.
From ADB
Code:
adb pull /system/app ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
Once this is done you can search market for "voice search" and "google search" then after they're installed, reboot.
Now for the next step.
If the search hard key doesn't bring up the quick search box (keyboard input), do this.
Code:
adb remount
adb shell ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
adb reboot
Now all should work!
I had a wierd name for quick search box (com.google.android.googlequicksearchbox-1) so keep that in mind if you have any issues.
Now enjoy you fancy new voice search!
tried everyone's suggestions so far, with your suggestions I get:
rm failed for -f, Read-only file system
Worked for me, thanks!
beyondinferno said:
ONLY WORKS WITH ANDROID 2.2 (FROYO)
Now for the next step.
If the search hard key doesn't bring up the quick search box (keyboard input), do this.
Code:
adb remount
adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
adb reboot
Now all should work!
I had a wierd name for quick search box (com.google.android.googlequicksearchbox-1) so keep that in mind if you have any issues.
Now enjoy you fancy new voice search!
Click to expand...
Click to collapse
Rather then using the command adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
I suggest the command ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
ln -s creates a symbolic link to the file rather then moving the file. It keeps the google search file where the installer put it. If you move the file are you causing an issue in the future when the next upgrade comes around?
mmace said:
tried everyone's suggestions so far, with your suggestions I get:
rm failed for -f, Read-only file system
Click to expand...
Click to collapse
adb remount first... and when using rm try busybox...
busybox rm <<file>>
painter_ said:
Rather then using the command adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
I suggest the command ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
ln -s creates a symbolic link to the file rather then moving the file. It keeps the google search file where the installer put it. If you move the file are you causing an issue in the future when the next upgrade comes around?
Click to expand...
Click to collapse
Thanks for the tip!
Changing how to now.
Can't wait to try this tonight.
Sent from my HERO200 using XDA App
Worked great! thank you!
This worked for me as well. Thanks.
Not having much luck reactivating the search button.
I can confirm that it got the job done cause when I tried again, it popped up an error that the file already exists, so it succeeded in creating the link... any suggestions?
Just tried it, works great. Thanks!
what does adb shell PM uninstall do as opposed to adb shell uninstall
If you have TB, uninstall voice search and google search from backup/restore, then reboot phone and go to market install both, worked for me
andygu3 said:
If you have TB, uninstall voice search and google search from backup/restore, then reboot phone and go to market install both, worked for me
Click to expand...
Click to collapse
thanks that worked and it was way easier than adb.
I'd love to have this feature, but I get "failure" when I enter the adb shell pm uninstall com.google.android.voicesearch command. I can't figure out what I'm doing wrong, except that I have no idea what the difference between Ubuntu and Windows commands are.
Thanks for all the hard work. Any help is greatly appreciated.`
EDITED: I got it working. Not sure how. Even though I got a "failure" during the adb uninstall, the old voice search appears to have uninstalled already. Went to the market and downloaded the new app and it works!
Perilousp69 said:
I'd love to have this feature, but I get "failure" when I enter the adb shell pm uninstall com.google.android.voicesearch command. I can't figure out what I'm doing wrong, except that I have no idea what the difference between Ubuntu and Windows commands are.
Thanks for all the hard work. Any help is greatly appreciated.`
Click to expand...
Click to collapse
I should add I'm running FROYO 2.1, vanilla based on Cynogen's Aug. 13 mod
Working!
10chars
DirtyShroomz said:
Working!
10chars
Click to expand...
Click to collapse
Can you tell me how you did it? I noticed you had problems earlier.
Perilousp69 said:
Can you tell me how you did it? I noticed you had problems earlier.
Click to expand...
Click to collapse
Used SUFBS (or any file explorer). Went to system/app and deleted voicesearch.apk, rebooted, went to market and downloaded voice search
Sorry for bumping the old topic, but does anyone know the difference
between:
com.google.android.voicesearch.x and
com.google.android.voicesearch ??
I have a Verizon tab that was rooted. I updated to gingerbread which removed root. Is there a way to root now that I have gingerbread?
Thanks!
you may try SuperOneClick 2.2 with ZergRush...
Thanks. I'll give it a shot.
Soundchasr said:
Thanks. I'll give it a shot.
Click to expand...
Click to collapse
Did it work?
Haven't had a chance yet.
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
receptr said:
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Telling me, I have gingerbread on mine and it does nothing but forceclose crap all over the place
Lakilaulea said:
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Click to expand...
Click to collapse
I was able to get mine rooted by using the kernel from Galaxy Cubed 3 ROM. Downloaded the whole ROM and flashed only the kernel in heimdall. Then I used adb to push the correct files to the system and fixed permissions and rebooted. Worked great.
UPDATE:
If people want to know the adb commands I used, here they are:
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
You can copy and paste these commands to a bat file and run it in a command prompt window. These were taken from a script used to root devices.
Here are links for the files you need. They are:
su
superuser.apk
busybox
They need to be placed in the same directory that you run the adb commands from.
SECOND UPDATE:
Rather than go through all this, go here:
http://forum.xda-developers.com/showthread.php?p=19678785
This is dsb9938's plain stock EI04 VZW ROM that is pre-rooted. Just flash in Heimdall and you are good to go. As long as you only wipe cache and dalvik, all your apps should stay intact.
Gingerbreak.apk should do the trick. Worked on my P1010
chris_toshiba said:
Gingerbreak.apk should do the trick. Worked on my P1010
Click to expand...
Click to collapse
It did not work on my VZW Tab. Someone said it is because it only works on 2.3.3 and older gingerbread and we have 2.3.5.
BTW, look at my earlier post (second update) to get a really easy way to have rooted stock 2.3.5 VZW Tab.
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?