Multiple phones - Root them, unroot them

[doomer4life]

well i finally got it rooted... now my phone reboots all the time so i have to unroot for now

 

[furbearingmammal]

Are you sure it's root that's doing that and not something else?

 

[dvsgod]

mine started rebooting randomly, mostly at the slide lock unlocking. I thought it had to do with my root, and tried multiple root attempts, and a factory reset. ever since I unfroze all the apps that were frozen with titanium it stopped re booting. still don't know wich app was trying to run, but I figure it out

 

[teddyearp]

It is .01% possible that rooting by itself will cause problems. The problems are 99.99% caused by what the rooter does afterwards.

 

[Karem]

Unbelievable! I was so scared to root because I've never done anything like it before. The closest thing was when I hacked my PSP.

I read through this whole thread to make sure I knew of problems that people were prone to and then proceeded with following the steps on the first page. 5 minutes later with no hiccups at all and smooth as can be, I'm rooted!

Thanks to everyone involved with this.

A quick question: what does rooting do when it comes to OTA updates? I may have read somewhere that you need to unroot to be able to get the OTA or something? Can someone clarify or expand on this?

 

[jstafford1]

Unbelievable! I was so scared to root because I've never done anything like it before. The closest thing was when I hacked my PSP.

I read through this whole thread to make sure I knew of problems that people were prone to and then proceeded with following the steps on the first page. 5 minutes later with no hiccups at all and smooth as can be, I'm rooted!

Thanks to everyone involved with this.

A quick question: what does rooting do when it comes to OTA updates? I may have read somewhere that you need to unroot to be able to get the OTA or something? Can someone clarify or expand on this?

Congrats on rooting....it can be scary the first time.

As for OTAs, rooting does nothing with them. If you accept an OTA while rooted, it will unroot you. I'm not sure what phone you have but on the D1 the recovery blocks OTAs so its no big deal. I'm not sure with the newer phones with locked bootloaders though.

Sent from somewhere...

 

[teddyearp]

I'm not sure what phone you have but on the D1 the recovery blocks OTAs so its no big deal.

Actually it's only a custom recovery that will block an OTA for the Droid 1.

@Karem, very good job! Same way I approach a new thing, read the thread for the issues and solutions.

good luck

 

[antmeyerx]

I wanna root my phone but im afraid i am going to mess up would someone be able to message me, and walk me through it a little more 1on1 and help me out

~Thank You

 

[furbearingmammal]

I wanna root my phone but im afraid i am going to mess up would someone be able to message me, and walk me through it a little more 1on1 and help me out

~Thank You

The only thing following this guide will do is root or fail to root your phone. It won't mess anything up -- we've verified it.

However, if you wish to PM a member of the Rescue Squad (we wear green tights and have lightbulbs screwed into our heads), I'm sure one of us would be willing to help you out.:icon_ banana:

 

[Alleyezonmike]

In step 2 A I type all the stuff into the terminal then force close it but when I re-open it, it just shows the $ sign again. What am I doing wrong???

 

[teddyearp]

Are you waiting for the rage file to finish it's thing first? Usually you should see a message about a bunch of children . . .

 

[The Albatross]

Well, I did the first four steps. Turned out it wouldn't work since I didn't have USB debugging on. So fixed that option. Went back to the Terminal and attempted to redo the commands, now get the result "Cannot fork".

Any ideas? Is there someway to completely start over?

 

[spaz33g]

Re starting the phone should give you a clean slate

tappin and a talkin

 

[The Albatross]

Re starting the phone should give you a clean slate

tappin and a talkin

So is the following poster correct?

I did Step 2 option A and got my ninja. I think you should consider one slight change to the instructions.
Step 4 reads:

1. ./rage*.bin
   This will take some time, just wait for the $ to show up so you know it is done.

I had the $ show up almost immediately, and I was suspicious about how fast that happened, but only waited a little while longer before quitting and restarting terminal. I had no #. I rebooted and repeated the first 4 steps, this time determined to wait a long time for some other sign (perhaps a second $) and after a while "[+] forked 3801 childs" appeared, but I kept on waiting almost an hour for another $ that never happened. When I reopened terminal again I had my #. I suspect that the rooting process is finished when the forked childs line appears, not when a $ shows up.

Cause I got the line saying "forked 3803 childs." does that mean I can now move on to the next steps?

 

[furbearingmammal]

Move on to the next steps. The childs line is, I'm told, what you're looking for.