Related
I have a few noob questions hopefully someone can answer
I rooted using toasts method part 1 and part 2
I have flipz .6 rooted rom and radio 1.39.00.05.31
Do I always have to go into hboot then select recovery every time or is there a direct path to boot into recovery?
Every time I install custom roms will i have to redownload all my apps every time? If so is there a way to easily back up the apps and restore them?
The superuser permissions app is there after rooting what is it used for?
LxMxFxD - the act of "ROOTING" is the act of giving super user. Super users are accounts on a phone or linux/unix device that can do EVERYTHING on the machine. Like the admin on windows. The whole point of rooting a phone is so you can get super user permissoins.
When i select the superuser permissions app i just see a black screen, should it do more than that?
ccapasso - What you are seeing is normal. The SuperUser Permission app is by default blank. However, once you start using apps that require su permission, such as Wireless Tether, it CAN start to have entries in it. I say CAN because you will notice that when you choose the Wireless Tether app, you will get a prompt asking you to allow. If you choose allow, it will continue as always. However, if you choose Always Allow, you will no longer get that prompt. Also, once you choose Always Allow, your SuperUser Permission app will now show a listing in it. If you simply choose Allow instead, you would still have nothing listed in the SuperUser Permission app.
How do I remove the proprietary apps?
you need to be in the recovery
from the cmd window type
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
rm amazonmp3.apk
check this post for a list of apps to remove
can anyone help me out with question 1 or 2?
1) http://forum.xda-developers.com/showthread.php?t=702214 - here's one way to do it...
2) Try Titanium Backup in the App Store - I tend to like it quite a bit.
oubravs2b said:
1) http://forum.xda-developers.com/showthread.php?t=702214 - here's one way to do it...
2) Try Titanium Backup in the App Store - I tend to like it quite a bit.
Click to expand...
Click to collapse
thanks!
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.
Hi guys,
Is it possible to have a shortcut icon on homescreen that powers the phone off. I have a protective gel case on my Desire and its a pain in the a**e having to long press it through the case and then select power off and then ok to confirm.
I am using quick boot app which is excellent but no power off option with it. Just reboot, recovery and quickboot. Have already requested Dev to add the function but not hopefull.
When long pressing the power button a menu pops up right? Is it possible to invoke that power menu in another way? Perhaps with a shortcut?
Surely its not rocket science to be able to click an icon and the phone powers off???????
Edit: see last post for solution
??
C'mon guys, someone must know a way to achieve this. Otherwise, whats this forum for?
5 minute job to knock up a zip patch file or a simple app for someone who know's what their doing. I feel a lot of people (certainly those using protective cases) would find such an app or patch (for rooted users like me) very welcome.
I would happily do it for someone else.
you can power off with the command
reboot -p
Click to expand...
Click to collapse
you can use gscript (light version available on the market for free.) to add a shortcut to that command on the homescreen.
You will need root access, i think.
??
C'mon man, you must know how to show some sort of gratitude or give some sort of feedback. Otherwise, whats this forum for?
5 minute job to go on your computer (or phone) and post a reply for someone who know's what their doing. I feel a lot of people (certainly those who help others) would find a simple thank-you very welcome.
I would happily do it for someone else.
My point is if you can't be arsed to reply to your own thread in 24 hours why bump it after a day with no reply?
reboot controll widget
Mercianary,
Don't get your knickers in a twist
Only seen your reply this morning. Thanks for your suggestion - gscript. Gonna try it out later today. Will post back.
Cheers dude.
What....these feelings...I feel bad now...sorry.
That widget looks like it would do the job great. Just depends of your stingy like me and wouldn't pay 87p for an app when I can do the same for free.
Just installed gscript and run a reboot -p script but it doesn't work
I get a stderr: not permited error
I am rooted and have the superuser app
Any ideas??
Try
su
reboot -p
Edit: that wont work. Make sure you tick 'needs su' box in gscript when you make the script. Should make it work
Got su box checked.
Tried
su
reboot -p
Tried re-installing gscript.
Tried reboot
Is it not working because, although I am rooted with unrevoked 3.2, I still have s-on? I wonder. Or, is it because reboot is not allowed to be run as a script???
But I have superuser app. Puzzled. Any more suggestions as I really want to get this working. By the way scripts not requiring su run fine.
http://www.appbrain.com/app/quick-boot/com.siriusapplications.quickboot
Hello
Yes I am already using quick boot but it doesn't have the option to simply power off the phone. Only reboot, recovery and bootloader. I have asked the Dev to add this option as others have also asked but not hopeful anytime soon.
All I want is a homescreen shortcut that powers off the phone. Simples!
Why am I getting not permitted error messages when trying to run following from gscript.....
reboot -p
It is set to use superuser but gives the error. WHY!!!!
Try running the command from a terminal emulator. If that works we know gscript is the problem (in which case I can tell you a work around).
If it still doesn't work maybe your rom doesn't support it (I use cyanogenmod and it works fine for me.).
Edit: double check gscript is set to 'allow' in superuser.
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Ik Desire said:
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Click to expand...
Click to collapse
Not for me. It must be different on different roms.
Are you using a sense rom?
By terminal emulator, do you mean an adb shell from a command prompt on P.C........Or do you mean something that runs on the phone?
Edit: Ran Alpharev last night and am now s-off All went smoothly. Have installed root explorer and was wondering what file/directory permissions I need to change to be able to execute scripts?
btw, thanks for your suggestions Mercianary and IK Desire
Edit: installed Android Terminal Emulator and ran
su (it asked for superuser permision and i allowed)
#shutdown (phone powered immediately off but would not switch back on - had to pull battery)
#reboot -p (same as above)
Totally stumped and baffled.
mercianary said:
Not for me. It must be different on different roms.
Are you using a sense rom?
Click to expand...
Click to collapse
Leedroid 2.2e. Using terminal emulator on phone. I have the same problem (have to pull battery before rebooting). But previously this was not the case.
Sent from my Evil Lair using Doomsday Device
Update
Have found a solution (sort of!). Have installed busybox and have created a gscript script as follows....
busybox poweroff -d 10 -f
This works and powers the phone off after 10 seconds. The reason for the 10 second delay is to give the system enough time to unmount filesystems and stop services. An ordered shutdown if you like.
Thing is....Is this what actually happens? I mean the poweroff command in busybox doesn't go through the init system. So, is it a "clean, ordered" powerdown???? It switches back on ok afterwards and everything seems to work.
But the question is am I risking corrupting the filesystem by shutting down in the way?
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!!!
Note: this is a mirror post of my other post, because all executables should work on the One X or the One. I've tested this on the One X.
These are instructions (and a helper script) to root the phone without unlocking or installing a recovery partition. It's based on temproot, and is ideal for anyone who doesn't want to modify their system software, or someone without a RUU who wants to make a full dump of their phone for backup in case they want to unroot.
Prerequisites:
- USB debugging should be enabled
- Get temproot from the Firewater folks (based on code by hikezoe and fi01)
- Get the SuperSU or SuperUser APK (I got it from inside this zip): http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
- Get a `su` executable (also inside the same zip): http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
- full-system-temproot.zip from this post and unzip the two files
Instructions:
- The Firewater folks recommend disabling screen lock and rebooting.
- Put SuperSU.apk, su, busybox, and root.sh into /sdcard/Download
- Connect to USB and run:
Code:
adb shell sh /sdcard/Download/root.sh
Follow the instructions, which consist of waiting for the root shell to appear (wait 10 minutes, then see a command prompt starting with "#"), then typing
Code:
/data/local/tmp/root2.sh
and hitting enter.
Note: the difference between this and the "naked" temproot hack is that the naked hack leaves you with a root shell which can run root commands, but no way for installed programs to use root capabilities.
I will refrain from making a "instruction unclear" joke, but the instruction could really use some improvement.
Fears said:
I will refrain from making a "instruction unclear" joke, but the instruction could really use some improvement.
Click to expand...
Click to collapse
I understand the instructions. Those that don't understand shouldn't do it.
I mean if people can't follow simple instructions that are posted, what chance have they got at doing anything remotely useful with a system dump.
Andy said:
I understand the instructions. Those that don't understand shouldn't do it.
I mean if people can't follow simple instructions that are posted, what chance have they got at doing anything remotely useful with a system dump.
Click to expand...
Click to collapse
On the other hand, some people live in countries without strong warranty laws. temproot is nice for them, so they don't need to unlock or ever uninstall their phone's default update mechanism.
Fears said:
I will refrain from making a "instruction unclear" joke, but the instruction could really use some improvement.
Click to expand...
Click to collapse
Which parts? I'm not going to multiply the length of this instruction ten-fold, but I'd like to supplement with links so people understand how to run commands in the adb shell, and other simple but necessary skills.
It might not be obvious but the little changes you made make the instructions much clearer (for me at least).
As they say: the devil is in the detail.
Can you then unlock the bootloader without wiping the data?
vbaros said:
Can you then unlock the bootloader without wiping the data?
Click to expand...
Click to collapse
No that's not possible it will always wipe data
Gesendet von meinem HTC One X mit Tapatalk
vbaros said:
Can you then unlock the bootloader without wiping the data?
Click to expand...
Click to collapse
You most certainly can, but I don't know whether anyone knows how.
I'd guess you need S-Off to do this, because the bootloader lock-unlock state is probably stored on a locked partition. You'll most likely need to run a single command to rewrite a byte of data, but it definitely won't be on the /system or /data partitions.
One-X-master said:
No that's bot possible it will always wipe data
Click to expand...
Click to collapse
Where's your ambition?
Did anyone try Xposed with this temp root? Does it work?
I followed all the instructions but when the script acquires root I just get the root # prompt and can't type anything. So I can't execute the last command.
What could be the problem?
EDIT: It works with the workaround.
Just start adb shell and then execute:
sh /sdcard/Download/root.sh
Can you turn temp root into a perm root after this procedure?