As far as step 22, what that does is rename (via a move "mv" command) the script file that will check and make sure you have stock recovery on every boot, thus disabling it. Enabling it would be to rename it back to the original, not changing the new extension to enable.
Now as far as unrooting with a few commands, well that could get tricky. As you know, the file that gives us root is the 'su' binary with the corresponding setting of it's permissions to 6755 (or 4755 in this guide). We now have unfettered root access. When we put the Superuser.apk file in /system/app it's function is to check each time an app calls for 'su' and then prompts us if we want to allow it or not. Without Superuser.apk any app could request 'su' and we'd never know. The busybox binary adds more shortcuts/commands to our system which many if not most root apps rely upon being in place to function.
So with all that in mind, in _theory_ you _might_ be able to unroot via these commands (DO NOT TRY THIS!!):
Code:
su
mount -o remount,rw /dev/nul /system
rm /system/bin/busybox
rm /system/app/Superuser.apk
rm /system/bin/su
reboot
However I am sure the second to last command would fail since you are using the 'su' binary and I doubt it would be allowed to be deleted while in use. AND THIS WOULD LEAVE YOUR PHONE OPEN TO ANY APP TO CALL SU WITHOUT YOUR KNOWLEDGE.
So - I think I've seen a couple of posts here that you have been able to use this method even after you have gotten the 83G OTA update. Have I read that right?
Cause I think I'm ready to take the plunge if it will work.
thank you. I just wanted a confirmation that it, in fact should work again.
I'm about to root the new update so
VVVVV
Ill post back here when im done. But yes, a couple of people have said they rooted frg83g
Quote:
Originally Posted by CegAbq
So - I think I've seen a couple of posts here that you have been able to use this method even after you have gotten the 83G OTA update. Have I read that right?
Cause I think I'm ready to take the plunge if it will work.
Device(s): Droid Bionic Rooted; Droid 1, 800 mHz UD 3.3.1
Thanks: 16
Thanked 24 Times in 15 Posts
back to stock from ealier in this thread by OMJ- Link broken!
Quote:
Originally Posted by crankerchick
Thanks I just used this to root my frg22. So I'm ready to start doing some ROMs which I'll read up on but I just have 1 question to make sure I understand. Since I did not backup anything before rooting, a backup that I make now (I'll be sure to make before doing any ROMs) will be a backup of my rooted phone, correct? Doesn't seem to be a big deal, but just want to make sure I understand.
Also, if I did ever want to get back to frg22 not rooted, would that be possible?
OMJ's response
[QUOTE]absolutely....you can either use an sbf file or flashingthis http://android.clie a5e329b00288.signed-voles-ota-50454.zip like you would a rom there is no way to make a backup of your system before its rooted...[QUOTE]
I still use the file that I downloaded from this link to return to stock. Once reactivate my phone I am prompted to do the OTA updates until my phone is current.
OMJ, do you still have this file or a new file (update.zip)) to revert you to stock? It would seem that this is a lot simpler than how people are trying to go back to stock. I don't know how to post the update.zip file myself.
Update: Okay, Teddy I see your link on your page with the frg83g ota update.zip. guess I'll use that the next time I need to un-root. And I appologize Teddy, I saw all the talk about using commands to un-root and didn't follow your link with detailed directions on how to flash an update.zip
Device(s): Droid Bionic Rooted; Droid 1, 800 mHz UD 3.3.1
Thanks: 16
Thanked 24 Times in 15 Posts
Quote:
Originally Posted by drummerjay08
I was just pushed the FRG83G update and have confirmed that this method works for rooting it also on my Droid 1. Awesome!
Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.
I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!
Device(s): Moto Droid, retired...
Samsung Charge on GummyCharged2.0
Thanks: 12
Thanked 8 Times in 8 Posts
Quote:
Originally Posted by djembeman
Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.
I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!
If you really like the 'stock' layout but want to have a faster phone, then Pete's is clearly the way to go. His Gingerbread runs like a champ on the Droid, and it's kept me from buying a Thunderbolt- I can wait for the Bionic and it's tegra2 processor now. I might just have to abandon the Droid in favor of some dual-core love when it finally drops, though.
Same here. It works great!! I am one of those people who un-rooted in order to get FRG83G. I got sick of problems with custom ROMs so I guess I have to go through this every time there is an update.
I am going to try the latest release from Pete Alfonso for Gingerbread though. It's intriguing!
I unrooted using the over the air update, installed Pete Alfonsos gpa 14,
and installed his custom kernels. i started with the 1G kernel and have been trying all the others. it all works flawlessly. Pete Alfonso is a perfectionist genius. WORKS PERFECTLY ON FRG83G
I'm on step 13. Instructions say "you should now see a # instead of a $", but I am still seeing the $. Should I continue anyway? Any suggestions would be appreciated.
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?
Last edited by josh99ta; April 15th, 2011 at 12:55 PM.
Device(s): The Droid Bionic......
OG Droid - rooted,
Kindle Fire
Thanks: 18
Thanked 78 Times in 74 Posts
Quote:
Originally Posted by rickbb
antivirus reports the mediafire link to rage is infected, is there a different link to download or is this a false message?
Welcome to the forums,
rageagainstthecage will set off some virus scanners as it uses an exploit to get root. The difference is the exploit is intentional as is your use of it. As long as you trust the source you download from you should be fine.
My desktop computer's virus scanner also considers it a virus when I run a scan.
__________________
Why bother doing anything if nothing is required?
i just have to say that this was the easiest root walk through i found for droids on 2.2. one of the best things about it is that i dont have to install a rooted ROM for it to work. i did have some issues with the command to disable the recovery, but im not worried in the least not wanting to install custom ROMs or kernels anyway. i just wanted a simple stock OS root. Thank you thank you thank you for being great.
P.S. i registered just so i could post to this thread.
you sir will have my gratitude for a very long time.
Device(s): The Droid Bionic......
OG Droid - rooted,
Kindle Fire
Thanks: 18
Thanked 78 Times in 74 Posts
Quote:
Originally Posted by teabling
i just have to say that this was the easiest root walk through i found for droids on 2.2. one of the best things about it is that i dont have to install a rooted ROM for it to work. i did have some issues with the command to disable the recovery, but im not worried in the least not wanting to install custom ROMs or kernels anyway. i just wanted a simple stock OS root. Thank you thank you thank you for being great.
P.S. i registered just so i could post to this thread.
you sir will have my gratitude for a very long time.
Teabling
Welcome to the forums and glad everything worked well for ya.
Hey, will this work on the original droid? I got up to about step 12 or so, and now my device doesn't come up when I enter "adb devices". I've double checked, and I do have the android folder, then the tools folder selected. I'm not sure what happened.
Device(s): Droid Bionic Rooted; Droid 1, 800 mHz UD 3.3.1
Thanks: 16
Thanked 24 Times in 15 Posts
Droid!
Quote:
Originally Posted by ptrsdwski
Hey, will this work on the original droid? I got up to about step 12 or so, and now my device doesn't come up when I enter "adb devices". I've double checked, and I do have the android folder, then the tools folder selected. I'm not sure what happened.
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?
Any help on this? I'm hitting the same road block.
UPDATE: I'm on step 11 now and it doesn't seem to be doing anything. As soon as I hit enter it returns me to a "$" prompt. When I type in adb devices it tells me permission denied. Where do I go from here?
Same here. I took the liberty of running ls -l and got this:
Code:
ls -l
-rwxr-xr-x shell shell 5392 2011-08-16 23:30 rageagainstth
in
-rw-rw-rw- shell shell 115962 1970-01-16 17:36 PdaNet.apk
Which seems to be right, I think? I think that corresponds to 0755. But anyway, I exited and ran adb shell again, and I still get $ instead of #
EDIT: Actually I think I figured it out. If you are having this problem, make EXTRA SURE you ran step 11, that is the part that runs the script that actually gives you root access! Don't know how I missed it, but check again.
EDIT: Actually I think I figured it out. If you are having this problem, make EXTRA SURE you ran step 11, that is the part that runs the script that actually gives you root access! Don't know how I missed it, but check again.
Brilliant deduction Watson! Yes, if step 11 is not allowed to finish properly, everything else is moot; you must run it again.
For some reason I am still seeing a $ when it should be a #. I am working with a droid 1 and windows 7 on my mac under parallels, but I dont think that should matter bc I have already connected and done the beginning steps. I am currently restarting my phone a couple times as many people have said that helps somehow?
I am having the same issue, no #, Still $ - Working with a Droid1 but build number: FRK76, is this my issue?
Device(s): Acer Iconia A500, Asus Transformer TF101, Samsung Galaxy Nexus, OG Droid
Thanks: 1
Thanked 12 Times in 10 Posts
Hate to necro-bump but trying to use this on an OG Droid I picked up today and when I get to step 8 (running adb shell) after I hit enter it returns to the next line and nothing happens, however I can not type anything and have to close the command prompt and reopen and redo the steps, but the same things keeps happening. Any help?
Could you click on the links provided and verify they are what you are doing? b/c teddy's link points to his write up which does not have a step 8 anywhere.....
Hate to necro-bump but trying to use this on an OG Droid I picked up today and when I get to step 8 (running adb shell) after I hit enter it returns to the next line and nothing happens, however I can not type anything and have to close the command prompt and reopen and redo the steps, but the same things keeps happening. Any help?
Did you make sure you enabled usb debugging? menu -> settings -> applications -> developement -> usb debugging checked
Quote:
Originally Posted by johnlgalt
Could you click on the links provided and verify they are what you are doing? b/c teddy's link points to his write up which does not have a step 8 anywhere.....
?? Which writeup of mine are you looking at? The one of mine that mirrors this one has the same step 8
Code:
adb shell
though mine does continue to include installing busybox but that's further down the command list.
Device(s): HTC Sensation 4G,Samsung Galaxy Mini S5570
Thanks: 0
Thanked 0 Times in 0 Posts
Directions listed are not completely safe
The original directions given at the top of this thread are not completely safe as they use specific /dev locations that may change from Samsung Mini to Samsung Mini.
I've written up the directions with some clarifications as well as an easy and safe way to extract the unlock code (which will work on Linux/Windows/OSX) and put it up on my site.
Unfortunately as a new user I can't specify links in my post, but you can find it by googling "davesource.com solutions" -it's posted as the solution for 2012-01-10. Perhaps someone with the ability to post links can post it for me?
Well, since this write up has nothing to do with the Samsung mini and only the Motorola A855 your post here is out of place. Maybe try posting your write-up in the proper section of this site.
SO CONFUSED!!!!! I'm really new at this and would love to root my phone to get custom Roms and remove all the useless preinstalled apps but its just to much for me, I can't do it. I know nothing about computers and finally give up.Glad it works for you guys though.
Well, you started a thread two days ago asking for help and now have given up. I mean no offence, but since your phone is basically a computer, some knowledge of computers and file structures and commands are kind of required.
The method in this thread will work, I have some guides as well.
Curious, though, in the other thread you first said you don't have a computer, then you said you do but no internet access. This forum is on the internet, how are you accessing it?
Well Teddy I do have a computer it's a windows XP from the stone age that has no internet access. The only internet I have is on my Droid and am using that to be on this forum and anything else internet related.I have given up because like I said I don't understand the " simple " instructions on how to use this root or any other for that matter. Some ppl just shouldn't try to do something like this having no knowledge of computers, files, or programs, me being one of them. I would still really love to root my phone, I hate being restricted, I just thought I woulde understand after reading up on it , but no luck. I love this forum though, it really is amazing how far ppl will go to help one another. Thanks so much for your reply and trying to help but my brain just doesn't work that way I guess.
...you SHOULD be able to successfully root your phone. It was easiest for me using my linux machine, though, from the Terminal. RSD Lite is definately your friend!! Good luck, and don't give up, brotha! I've rooted my OG Droid, and it's running so well (on the latest stable CyanogenMod) that my wife's using it to this day!
Yup finally got my Droid rooted with soc 1.7 with really no problems, it got stuck in a loop that I was able to fix with a helpful post. Thanks for everyone's help.
Now I'm trying to help root my boyfriends Breakout,doesn't seem as easy lol. We've tried a few different methods that seem to get stuck at one point or another and wont finish. I've talked to ppl that tried to help but still no luck.....
OK. I successfully rooted my Huawei u9000 - 81 using the info listed. Unfortunately, I had a screen issue (not related to rooting) and took it back to my carrier. They replaced my phone with an identical phone, however this time they upgraded me to version 2.3.4 and now every time i get to step 11 it runs (or so I think it does) and kicks me back to my "C:\android-sdk\platform-tools>" folder. I complete the adb-killserver and adb devices command but get the following:
cd /data/local/tmp
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2793, 2793}[*] Searching for adb ...
[+] Found adb as PID 7937[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\android-sdk\platform-tools>adb kill-server
C:\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
After about 10 minutes or so, my phone resets the connection and then I can get the list to show my device connected again. Same phone which was rooted on version 2.2 something now isn't working on 2.3.4.
As you can see...it wont list my device after running the rage file. I am stuck and want my root back...any help would be awesome.
Hey all, new to the forums and so far I am finding everything I need to try and re-purpose an old phone (and maybe upgrading my newer one if this works out).
Anyway, I have installed everything that I needed and followed all the steps to the t, but I am finding myself having issues with step 10.) chmod 0755 rageagainstthecage-arm5.bin.
When I enter this in it says "Unable to chmod rageagainstthecage-arm5.bin: No such file or directory. I clearly have it in the folder, but for some reason I keep running into this issue. I tried restarting the whole process and I still get this issue.
Hey all, new to the forums and so far I am finding everything I need to try and re-purpose an old phone (and maybe upgrading my newer one if this works out).
Anyway, I have installed everything that I needed and followed all the steps to the t, but I am finding myself having issues with step 10.) chmod 0755 rageagainstthecage-arm5.bin.
When I enter this in it says "Unable to chmod rageagainstthecage-arm5.bin: No such file or directory. I clearly have it in the folder, but for some reason I keep running into this issue. I tried restarting the whole process and I still get this issue.
Please help!
Never mind, I figured it out finally. Rookie mistake. lol Thanks for the easy tutorial! (Basically, the issue was a type that I continued to do over and over again. lawl)
adb push c:\droidroot\su /system/bin
I get the error: Failed to copy c:\droidroot\su to /system/bin/su Read only file system.
I've seen this question asked 2 times in the forum, but haven't seen a reply. Is there a way to change the permissions of the /system/bin directory from r to r/w?
The Motorola Droid - the first ever Verizon Android Phone - exploded onto the mobile market with an incredibly successful ad campaign that brough Android to the masses. With a huge and vibrant touchscreen, solid metal body, full QWERTY keyboard, 5M... Read More