Related
Ok so I have rooted my 2.2, but how do I unistall these crappy preinstall sprint apps?
codyh325 said:
Ok so I have rooted my 2.2, but how do I unistall these crappy preinstall sprint apps?
Click to expand...
Click to collapse
When you install a different rom, they've taken most of the cr*p out. Also, you can download Root Explore from the market. It's around $3 and totally worth it. It lets you browse through your phone and delete apps. They'll be in the root under System -> Apps. There is another thread with a list of apps that are safe to remove. You'll have to find that in search. Type "Safe to Remove" and you'll find it.
There are quite a few threads on how to accomplish this.
I personally never felt the need to spend $3 to remove unwanted crapware!
The route I use is utilizing ADB. I find this is the easiest. Simple coding.
You will need to download the android SDK if you have not already done so.
Android SDK
ADB Beginners Guide
Basic ADB Shell Commands
EDIT:
Android ADB Page
Download Titanium Backup, go to setting and enable "Chuck Norris" mode, and you are good to go. Definitely check out the safe to delete thread and don't uninstall anything that has to do with Google Talk. It will screw up your market downloads.
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu. (ubuntu.com ...download the iso, boot as a live cd, install gparted....google for more details)
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools installed and working (adb is included with the SDK, so install the sdk and you will have adb. GOOGLE "adb sdk install" for more details):
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
What I've Used Root For So Far
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop. EDIT: The software MAGICALLY reappears after reboot. I can't wait to crack this phone!
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
good stuff bro ima try this.
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
yes but
Dalamak said:
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
Click to expand...
Click to collapse
Yes we did BUT that temp root method didn't allow access to the real files of the device. It accessed copies (simply put I know). This temp root gives ROOT access to the entire device which puts us a GIANT step closer to a permanent solution.
Also, the other temp method couldn't handle installing Apps in one mode and using them in another. Some Apps disappeared at reboot. With this method, Apps that are installed in either mode are always accessible.
Basically I did this for my own device and just wanted to share with others
But of course I thank you for your efforts, you are a god, I meant no disrespect
texasaggie1 said:
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu.
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools (adb) installed and working:
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
Click to expand...
Click to collapse
Dalamak said:
But of course I thank you for your efforts, you are a god, I meant no disrespect
Click to expand...
Click to collapse
LOL hahahah thats funny. I'm def not a god at this
Good job man! This will definitely make it seemer on the folks who aren't Linux friendly or lazy folks like me. Oh and btw... you're the futherest thing from a newb! Hahahha! You've been here longer than me. Its rare that I see the real old school guys here anymore. Weren't you in the wizard or tornado sub forum many years ago. You seem familiar...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Nevermind. I've decided to retract my comment and just try the process to see what happens.
Method worked amazingly well!
Thank you for this!!
Awesome job!
Sent from my T-Mobile G2 using XDA App
Will this work with the 4 click on-device root apk posted in this thread: http://forum.xda-developers.com/showpost.php?p=8535854&postcount=95 ?
Looks like a great guide as only 1 part is required - this allows me to part in my G1 AmonRa Recovery FTW!~111
(Also a great option if you are worried about booting up your G2 after formatting the SD as any progs looking for files there will be disappointed until you can copy them back ...)
Running a continuous Ping in Term now to see if that does the trick ...
EDIT:
Alright! this is awesome!
Q:
IF all we have to do to keep root is to keep the shell open - can't we run a prog or command to prioritize that prog ... like ... i remember that auto taskiller had settings against apps that were in the forgroud, background, background services etc ...
can we fool the OS into thinking this is allways a foreground process even though it's really running in BG ...or somehow give it highest priority?
EDIT 2:
Installed WirelesTeather.apk and ran and installed binaries - SU came up and granted all permission w/o issue - everything looked good.
Didn't open any other programs and decided to test it later, after noticing the AP didn't show I checked Terminal from the taskbar and it was back to $ (was closed by system)
I am running a fish aquarium for livewallpaper - so I'm sure this is why it closed as I'm running more processes at idle ... however, it looks like opening pretty much anything will cause the terminal to close and kill the "temp root'
Running a continuous Ping in Term now to see if that does the trick
FINAL EDIT:
OK! Ran continuous ping, opened Quake 3 - played for a bit - closed it.
Checked Term from the status bar - My Ping is still running !!1111 (IE the shell didn't close and we still have root)
So ... maybe this helps
You are the man. Downloaded. Tested. It works!
Sent from my T-Mobile G2 using XDA App
GREAT WORK!
Got it up and running, and just got 2.26 down, 1.23 up on my laptop off wireless tether.
so since this works directly with system files what happens if you try to metamorph something..will it revert on reboot or stay
Excellent job!
You are a genius! Your guide worked perfectly! I am typing this while tethered to the G2 - I agree with you, getting Root for tethering is worth the hassle of getting Root access! Keep up the great work!
I had been taking the SIM chip from my G2 to G1 (rooted, of course!) for Internet access - No more! Thanks again!
sino8r said:
...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Click to expand...
Click to collapse
ive tried, several different ways, even ones that had a good chance of bricking, i.e. messing with ruu, and swapping files in the middle of flashing, just to try and get this perm root
texasaggie1 said:
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop.
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
Click to expand...
Click to collapse
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Which Version?
aacrabtree said:
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Click to expand...
Click to collapse
Which tethering apk are you using? If you are using the one from the link I provided it should work. I am not having to turn off wifi first for it to work for me.
Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J
roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...
Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...
Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...
Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......
This is for n00bs like myself that had to search around before getting into this and doing it correctly. A lot was copied from the Inc S thread, but felt the instructions were needed here so no need for searching there and crowding their forum with our questions: http://forum.xda-developers.com/showthread.php?t=1039015
Psneuter exploit is working on DInc2, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Install the HTC Sync software or PDANet software to install drivers for your phone to Windows
2. Ensure that the device is in USB Debug mode, go to Settings > Applications > Development and "tick" USB debugging and plug in your phone to your PC
3. Unzip the attached .zip into a directory (like c:\adb)
4. Open a command prompt by going to start > run and running CMD, and cd to the directory where you extracted the .zip (like cd \adb)
5. Type "adb devices" > enter, and ensure that your device has been detected
6. Run the "pushroot.bat" file
7. Type "adb shell /data/local/tmp/getroot" > enter
8. Type "adb shell" > enter
9. You are now in # prompt. Type "/data/local/tmp/pushroot"
After the last step, a new # line appears. That's it! You're temporarily rooted
You have to redo steps 7, 8, 9 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
I run Bloat Freezer to rid the VZW apps
u can actually use the exact same process as the incS
I said that and linked to the Inc S thread for doing it
I just added in some steps for the issues I ran into, since it was my first time trying to do something like this and so others have a step by step to follow
And also so we have have something for this forum...thanks though
OK, question... if I do a temp root on the DInc2, then restore my wife's Titanium Backup to the new phone, can I also perminantly get rid of the VZW Bloatware, then reboot without Temp Rooting from that point on? (I know I will lose full Backups as well as SetCPU, etc. but will the Bloatware removal cause issues?)
I use Bloat Freeze and the VZW crap never comes back after a reboot when I have the "Alternate Freeze method" checked in the preferences, which is the Titanium Backup method
Maybe I am doing something wrong. I get to step #9 with
$ /data/local/tmp/pushroot and get
mount: operation not permitted
and a few more permission denied lines.
??? thanks in advance
Looks like the getroot did not work/run right, when you do step 8, the shell should start with the '#', not the '$'
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
xgunther said:
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
Use Titanium to freeze it. Don't delete it. Freezing works, but if you delete it it will just come back.
Sent from my ADR6350 using XDA App
I have done all the steps correctly up until step 5, well the problem is after typing in adb service, i get an extensively long list of different commands, and then the next step is to type in pushroot.bat, and when i do, heres what i get in return
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: dervice not found
C:\adb>
I dont know the problem...i do have Ongoing HTC Charge. USB Debugging connected. And PdaNet Connect (USB)
What could be the problem?
That should be adb devices, not serices
After that, you should see your device listed. When you typed services, the list you got was basically a help list for adb commands, since you did not type a valid one
Double check to make sure your device is detcted, if it is not, go to Windows' Device Manager and make sure the proper drivers were installed for your DInc
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
mykenyc said:
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
Click to expand...
Click to collapse
You must "freeze" them with bloat freezer or a similar app.
xgunther said:
You must "freeze" them with bloat freezer or a similar app.
Click to expand...
Click to collapse
With only a temp root wouldn't any bloat freezing reset on reboot?
x Eacott said:
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Click to expand...
Click to collapse
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
sixteen2nd said:
With only a temp root wouldn't any bloat freezing reset on reboot?
Click to expand...
Click to collapse
Negative, Freezing works on the temp root after a reset, just make sure if you use Bloat Freeze that you select the alternative freezing option (Titanium Backup method) when you do it
LowFire82 said:
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
Click to expand...
Click to collapse
There are a lot of things that could prevent adb from picking up your device... easiest would be to double-check that you have the USB Debugging option enabled on the device. The next easiest would be to make sure you have the correct drivers installed. I'd recommend using an app like USBDeview to see an extended list of all your installed USB drivers, and then deleting anything related to HTC/Android/adb. You can then reinstall the correct drivers which I believe LowFire mentioned in his OP.
/threadjack
Ahh! OK, I had to do a Master Reset of my wife's Inc2, previously it had TempRoot working.
I followed the instructions from the beginning after it was reset, but I cannot get TempRoot access. MyBackup Pro, Titanium, Root Explorer all say there is no root access. I get the phone listed at adb devices and get no errors running the commands. Anyone have issues gaining root?
xgunther said:
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
I have the same issue...just another # line after typing in the string from step 9 and hitting enter
What did you do?
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Just use root explorer to delete it from system/ app
Sent from my Galaxy Nexus using Tapatalk 2
I was under the impression that, that would not completely work? Isn't there another file somewhere that has to be removed as well? Thanks for the response!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
Take a look at this post, specifially method 2. See if you can figure out what those commands are actually doing.
I will help you out: you are essentially mounting the system partition as read-write, copying two files to the system, changing permission on the system, and then mounting the system as read-only.
So, in order to remove root, you need to mount the system as read-write, remove those two files (command is rm) and mount the system as read-only. [EDIT: depending on where the toolkit you used place su, it could be somewhere else than /system/bin, like /system/xbin or /system/sbin -- yet another reason not to use toolkits...]
Toolkits don't teach you that.
And for you follow-up question, the answer is no (if you are talking about updates). If you update using an OTA update, the update does not delete those two files, but it does change the permissions on them to disable root access.
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
shadrage said:
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
Click to expand...
Click to collapse
Give it a shot, and if you are having issues, post here and I'll guide you through it.
Appreciate it! I'll be fiddling around with it either tomorrow or the next day--pretty slammed this week.
Thanks again.
Let me know
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
nodnerb said:
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
Click to expand...
Click to collapse
It's very simple. If you still have root, just use root explorer and delete two files:
1) /system/app/Superuser.apk
2) the second file is su, and it could be in one of three places, depending on how you rooted:
/system/bin/su OR
/system/sbin/su OR
/system/xbin/su
That's it.
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Thanks
Thanks Efrant.
I'm trying to learn the ins and outs of adb, and it confuses me to no end. I'm slowing remembering playing with my dad's DOS computer when I was a kid, so command prompt and shell type work is coming back, but not easily.
efrant said:
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
. . .
Click to expand...
Click to collapse
Exactly!
And how to only remove Superuser data?
I mean, I want Superuser to ask me again if I grant or not superuser-permision.
I need this because I have in Superuser 5 times Titanium Backup.
All has the same id but only one has the Titanium Backup icon and the other doesn't.
And if I try deleting the app from the list... the app just go to "Denied" but still there.
So, I want to delete the whole data so I get a clean list of apps.
Thanks!
settings >> apps >> all apps >> super user
clear cache, clear data
3rdstring said:
settings >> apps >> all apps >> super user
clear cache, clear data
Click to expand...
Click to collapse
Thanks man! I cannot believe I did not try that before.
Thanks!
efrant said:
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Click to expand...
Click to collapse
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
USA Prime Credit Peggy said:
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
Click to expand...
Click to collapse
Follow the instructions in this thread. It will take you back to stock, and there are instructions on re-locking the bootloader as well.
Had to restock my Nexus as well. but my USB didnt work so I decided to take my losses and just return it, rooted with Superuser.
I had spend 2 days trying to restock it. and then this Tech Guy from my Carrier Tells me...
O you have rooted your Phone. Well that might be a problem with the insurance... unless you got a Nexus Device.
I was like what do you mean.
wel with all nexus devices you are allowed to root your phone.
So I think this is the best Solution there is . just take it back and save yourself some time.
this really works!!!!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
1. after you have or have not unrooted, search up superuser on playstore
2. click uninstall, if it says uninstalling........, ignore that and go to home page
3. go to folder and delete cwm-root thingy(the zip file you copied to your folder when you rooted) and delete that(seriously, thats important)
4. make sure you have the root remover file in your external sd card
5. turn off device, reboot by holding power and down/left
6. select install zip from sd card and install the root remover file
7. reboot and superuser should be gone lol
keep in mind that i did this on my galaxy tab 2 10.1 so it will definitely work on that
should work with any device
hope this helped
lol
wow, old thread...
I have use root explorer to delete the Superuser.apk and system/bin/su
but once i restart my device, those two thing happen again and again.
Help!!!