Root just a quick go to h#$% and a thank you

[may2700]

i am posting this just so everyone know, not all rooting is easy and no, sometimes it dose'nt go right.
well I took the plunge today and rooted my droid, used easy root and followed the directions found on this forum. root was tricky at best as nothing went smoothly. but alas i got it rooted. then tried to install a theme for my new liquid froyo i just installed and thats when all hell broke loose. the phone became unusable. the amount of errors showing up on screen were only matched by the self reboots. eventually the phone just traded off from the DROID screen to the red eye screen and back and forth. at this point i came back to the forums to see what i could do. and thats were my thank you comes from. i found the post about returning your droid to the unrooted 2.01 and thats what i did. after a quick lesson about .7z files (who knew they were the new .zip files?) i was back up and running. in all it took me 7 hours to root, destroy, reflash and reload all my apps so i could be right back were i started.

a full day it was!
alot was learned!
alot was said (loudly)
alot was deleted
and alot was reloaded

in the end i am thankful for the experience but only because my phone still works. this post would have been alot different if it did not

my name is jim.... an i am again unrooted.... and most likely going to stay that way

 

[MaxPacker]

I've found that a lot of people have trouble with Easy Root.

If you've flashed a .sbf file to your phone to get back to 2.0.1, you can root the "harder" but more effective way.

But if it's not for you, it's not for you. This can stand as a testament that the phone can't be bricked, but it can be screwed for a while.

 

[Jcarmicha]

So much knocking of EasyRoot and I more or less think it is User Error.

I clicked "Root me" it rooted - I installed Rom Manager flashed Clockwork and instantly installed Cyanogen with perfection. I don't know what step people are missing in that but those worked perfectly with me. After that I even installed the Watermark'd theme with no errors.

Everything was so smooth. I plan on doing the GF's shortly as well.

 

[YankeeDudeL]

I got my Droid the day it dropped and never heard of rooting until about a month later. So after another month or so I finally took the plunge and I can't tell you enough how happy I am, now. I do think there was an app we could DL that made rooting easy, but I went to RootYourDroid.info and followed their guide (before there were guides here) and learned the step-by-step process.

I didn't realize how much that would help me because you learn so much more about the actual process and it helps you down the road when you run into errors. You gain a better understanding of how to diagnose and address the issues you will eventually run into, something these easy root applications do not.

For those who still haven't done so but are looking to root, I suggest biting the bullet and doing it the hard way. It'll help ya so much more in the long run.

 

[Danielson2047]

For those who still haven't done so but are looking to root, I suggest biting the bullet and doing it the hard way. It'll help ya so much more in the long run.

Well put, and my thoughts as well. Everyone told me to do it the hard way the first time and wouldn't regret it, and they were right. Gives you an idea of exactly whats goin on.

 

[PhilosoRaptor]

You didn't forget to charge the flux capacitor before rooting, did you..??! (It needs 1.21 jigawatts)

 

[johnnybirdman]

my name is jim.... an i am again unrooted.... and most likely going to stay that way

Hi Jim. I'm also a recovering un-rooter. My name is J. and I've been unrooted from 21 days now.

It's hard for a while but once you get past the first week the withdraw starts to go away and you learn to live with your un-rootness.
I was rooted once before this last time and had a relapse. I know the pitfalls of rooting and how to try to avoid the temptation. Try to stay away from places where rooted geeks hang out; phandroid, android forums, any website/forum dedicated to Megan Fox and ham radio conventions. Hope these tips help and I wish you continued success with your un-rootedness.
Namaste.
J.

 

[johnlgalt]

i am posting this just so everyone know, not all rooting is easy and no, sometimes it dose'nt go right.
well I took the plunge today and rooted my droid, used easy root and followed the directions found on this forum. root was tricky at best as nothing went smoothly. but alas i got it rooted. then tried to install a theme for my new liquid froyo i just installed and thats when all hell broke loose. the phone became unusable. the amount of errors showing up on screen were only matched by the self reboots. eventually the phone just traded off from the DROID screen to the red eye screen and back and forth. at this point i came back to the forums to see what i could do. and thats were my thank you comes from. i found the post about returning your droid to the unrooted 2.01 and thats what i did. after a quick lesson about .7z files (who knew they were the new .zip files?) i was back up and running. in all it took me 7 hours to root, destroy, reflash and reload all my apps so i could be right back were i started.

a full day it was!
alot was learned!
alot was said (loudly)
alot was deleted
and alot was reloaded

in the end i am thankful for the experience but only because my phone still works. this post would have been alot different if it did not

my name is jim.... an i am again unrooted.... and most likely going to stay that way

Hi Jim. I'm also a recovering un-rooter. My name is J. and I've been unrooted from 21 days now.

It's hard for a while but once you get past the first week the withdraw starts to go away and you learn to live with your un-rootness.
I was rooted once before this last time and had a relapse. I know the pitfalls of rooting and how to try to avoid the temptation. Try to stay away from places where rooted geeks hang out; phandroid, android forums, any website/forum dedicated to Megan Fox and ham radio conventions. Hope these tips help and I wish you continued success with your un-rootedness.
Namaste.
J.

I made a post here in another thread - see http://androidforums.com/droid-all-...moke-theme-phone-doesnt-work.html#post1438193

The biggest problem is that a lot of n00bs, and even some veterans, will claim that rooting is easy, and it is sure fire, and whatnot - but the biggest problem is that most of the n00bs never tell you to do your research and to do it well before undertaking this step. Most veterans will - but most root virgins will listen to another n00b saying "It's easy, it took me 0 minutes!" faster than they will listen to someone like me who will make a long winded post about taking caution, reading things thoroughly, etc. etc.

The aftermath of using such a tool with almost no support in case something goes wrong is a major thorn in my side - I had the same issue when I had seen folks use the previous "easy rooting tool", whatever it was called, back a few months ago. Being rather computer savvy (with that being a severe understatement) I still read documentation over and over, made sure I was familiar with steps, read horror story after horror story about what had happened to others rooting their phone - and decided to take the plunge anyway. This was before there was an SBF procedure to fix the phone in case it went south. I think.

Anyhoo, I now cannot live with an unrooted phone - I over clock, I use apps like Dual Mount SD Share, TiBu, Root Explorer, Set CPU, Temp Monitor, and a whole slew of other apps. I like being able to remove stupid apps that I am never going to use out of my system. I like removing all of the stupid WPs and LWPs out of my system b/c I'll never be using them. Ever. I like being able to completely control my phone.

now, before you think I am trying to convince you to root, I'm not. Rooting is not for everyone - and if you have no use for all of these things that I do, then I recommend that you not root your phone. You'll save yourself a lot of (potential) headaches, as well as a lot of time (that I spend trying this ROM, that app, this kernel, or that system file modification).

However, find a way to back up your apps - if need be search for one of my old and archived posts about how to backup your apps using the Android SDK and your computer.

It makes life a *lot* easier, just in case you ever have an "oops!" moment.

Also, look into apps that don't require root access, like SMS Backup and Restore by Ritesh S. You'll thank me later.

 

[YankeeDudeL]

The biggest problem is that a lot of n00bs, and even some veterans, will claim that rooting is easy, and it is sure fire, and whatnot - but the biggest problem is that most of the n00bs never tell you to do your research and to do it well before undertaking this step.

I almost feel ashamed for not mentioning that, now. lol

Yes, I had to do a LOT of reading up on it. Luckily, there were a lot of links and well-meaning users on here that helped with that. I toyed around with it for about a month before deciding that I was capable of doing it, and then I spent just about an entire day breaking down the process and examining exactly what I needed to do.

While the process itself doesn't take too long, researching exactly what you need to do and understanding it should. And with all the guides that are now available, you're doing yourself a disservice by not. This by no means people won't kindly help you no matter how you gained root access, just the more you understand the problem, the better a chance we have to help you.

 

[sevenstars]

...

 

[Jcarmicha]

Everyone seems to have issues with LFY. I'm avoiding it for sure.

 

[johnlgalt]

Everybody is *not* having issues with LFY. I am not and a lot of others are not.

there seems to be a few issues going around, and I am not sure of the common denominator yet, but one of them is that Clockwork Mod and SPRecovery are being erased and overwritten by the stock recover,y another is that after installing a ROM or theme the system hangs, and the third is that system performance slows to a crawl.

In all cases thus far, the *only* common denominator seems to be those who have updated to 2.2 using the original 2.1-patch OTA - and I am beginning to suspect that that patching process is breaking a lot more than just AAC+ playback and a few apps now.

 

[digdug1]

i too am guilty of not pointing out the all things root sticky to noobs at times. i researched rooting for weeks befort taking the plunge and i rooted the "old fashioned" way.im not saying i know it all but i like to think that and it gave me a better understanding of the process after root.
ps:
i am having no problems with liquid frozen yogurt. thus far it is the best rom i have tried(and i have tried almost all of them).

 

[Jamieinnh]

Count me in the group of doing it the "old fashioned" way..

Don't get me wrong, I love easy peasy... but doing it the old fashion way will show you what you're doing... You will have a better understanding of what you're doing to your phone.

7 hours to root and unroot your phone and install a Rom isn't that bad in my opinion if you're talking about taking a backup and being sure of yourself as you move forward in the process..

I would definitely give rooting another try and go the old fashion way.. you'll be proud of yourself when you're done and rooted..

Jamie

 

[d-man]

Bump for cautionary tales.

There is a reason the only phones that ship with root level access are for developers.

Rooting can potentially turn your phone into a very expensive brick. It should only be attempted if you are sure you know what you are doing and are willing to take the risk. I think things like One-click Root are a Very Bad Idea.

I'm really glad that Jim was able to recovery his phone. Let this thread stand as a word of caution to anyone else who thinks that rooting is easy and nothing can go wrong.

(That said, I can't wait to try Bugless Beast 0.5 )

 

[gnath9]

Rooting is for Geeks plain & simple...

If you can follow directions and enjoy learning, do your home work and have a little common sense about computers in general anyone can learn to root and flash roms etc .... I am living proof of that

so far I have never heard of a Droid being bricked yet even tho some have been stuck on the "M" logo or a boot loop and went running to VZW for a new phone cuz they "think" they bricked it.

If you want to learn all this cool stuff .... do your homework first it really is not that hard once you understand it.

FWIW ... I am a 48 year old who dropped out of high school on his 16th birthday. I got my first PC in 2002. I am self taught at PC building and can do a damn fine job at it. I flash roms, kernels and themes at will on my Droid.

Everyone is capable of doing the same. (I aint special)

 

[Psychokitty]

Rooting is for Geeks plain & simple...

If you can follow directions and enjoy learning, do your home work and have a little common sense about computers in general anyone can learn to root and flash roms etc .... I am living proof of that

so far I have never heard of a Droid being bricked yet even tho some have been stuck on the "M" logo or a boot loop and went running to VZW for a new phone cuz they "think" they bricked it.

If you want to learn all this cool stuff .... do your homework first it really is not that hard once you understand it.

FWIW ... I am a 48 year old who dropped out of high school on his 16th birthday. I got my first PC in 2002. I am self taught at PC building and can do a damn fine job at it. I flash roms, kernels and themes at will on my Droid.

Everyone is capable of doing the same. (I aint special)

Yeah, I agree. If you can't be bothered to do the research before flashing a different ROM on to your $600 phone, you're a fool for doing it in the first place. It's not the responsibility of the author of any guide or anyone saying how easy or great rooting is to preclude his post with a disclaimer. This is an Android forum filled with geeks doing geeky things. Chances are every question you might have has already been asked and answered.
Rooting and ROM flashing is now easier than ever, but you should still read the directions.
And OP, if you weren't aware that some themes don't play well with some ROMs, it's because you didn't do your homework. And if you didn't back up your ROM while it worked b efore adding the destructive theme so that you could do back to it, well then that's your fault to. (-Just a quick "go to h#$%" right back atcha )

 

[gnath9]

Yeah, I agree. If you can't be bothered to do the research before flashing a different ROM on to your $600 phone, you're a fool for doing it in the first place. It's not the responsibility of the author of any guide or anyone saying how easy or great rooting is to preclude his post with a disclaimer. This is an Android forum filled with geeks doing geeky things. Chances are every question you might have has already been asked and answered.
Rooting and ROM flashing is now easier than ever, but you should still read the directions.
And OP, if you weren't aware that some themes don't play well with some ROMs, it's because you didn't do your homework. And if you didn't back up your ROM while it worked b efore adding the destructive theme so that you could do back to it, well then that's your fault to. (-Just a quick "go to h#$%" right back atcha )

well said

I read many forums for months before I rooted and flashed roms. When I first signed up it was because I wanted to try to say thanks to all the many folks that didnt even know they had helped me. (I was a lurker) And now ... I like to try to help who ever I can. I just wish some peeps were more respectful of other members that are really just trying to help. (mini rant)

 

[Scottmc]

Yeah, I agree. If you can't be bothered to do the research before flashing a different ROM on to your $600 phone, you're a fool for doing it in the first place. It's not the responsibility of the author of any guide or anyone saying how easy or great rooting is to preclude his post with a disclaimer. This is an Android forum filled with geeks doing geeky things. Chances are every question you might have has already been asked and answered.
Rooting and ROM flashing is now easier than ever, but you should still read the directions.
And OP, if you weren't aware that some themes don't play well with some ROMs, it's because you didn't do your homework. And if you didn't back up your ROM while it worked b efore adding the destructive theme so that you could do back to it, well then that's your fault to. (-Just a quick "go to h#$%" right back atcha )

As someone who went down the rabbit hole, got scared and came back out I can second this sentiment. The reason I failed was because I failed to RTFP and follow the directions completely. I ended up in a reboot cycle but was able to recover easily using the RDSLite tool and reflashing a stock image. The mistakes I made were not being prepared, not researching each step, and , the worst of all, not taking my time with each step. Now that I know what I did wrong I will jump down the rabbit hole again, when I have more time to spend (maybe this weekend when my second phone get's here ).

All in all, it was a hairy process, I learned a lot, and, most importantly, I gained confidence and knowledge at the cost of some of my personal time (and a little stress and I tried to think of a creative story to tell the Verizon representative)

 

[Danielson2047]

Yeah, I agree. If you can't be bothered to do the research before flashing a different ROM on to your $600 phone, you're a fool for doing it in the first place. It's not the responsibility of the author of any guide or anyone saying how easy or great rooting is to preclude his post with a disclaimer. This is an Android forum filled with geeks doing geeky things. Chances are every question you might have has already been asked and answered.
Rooting and ROM flashing is now easier than ever, but you should still read the directions.
And OP, if you weren't aware that some themes don't play well with some ROMs, it's because you didn't do your homework. And if you didn't back up your ROM while it worked b efore adding the destructive theme so that you could do back to it, well then that's your fault to. (-Just a quick "go to h#$%" right back atcha )

Nice, constructive post. Not!!! I found this a little pompous. How do you know the poor guy/gal didn't follow instructions and it just didn't work. I just don't think calling 'em a fool is going to solve anything or make them feel very welcome. MY rant.

 

[Scottmc]

Nice, constructive post. Not!!! I found this a little pompous. How do you know the poor guy/gal didn't follow instructions and it just didn't work. I just don't think calling 'em a fool is going to solve anything or make them feel very welcome. MY rant.

Psychokitty did come off sounding a little elitist but this is a hacking community so some of that is to be expected. It was pretty light tbh compared to some of the rants I see on IRC and other boards. He is making a good point though. It's very important you read, UNDERSTAND, and follow each instruction to the letter. Any and all deviation will bring to a place you don't want to be. Don't get creative, follow the directions. I am living proof that if you don't bad things can happen. Not irreversible things, since I didn't do things like delete my recovery or remove system files (as some other n00bs do), so I was able to recover.

The point is that, yes, it's difficult to brick the phone, especially since RDSLite (and sbf_flash for us linux users) exists, but you can ruin your evening. Or even think that you did brick your phone. Don't enter into this lightly. Take it very seriously because if you don't you will make mistakes and be in one of the states mentioned above.

One more point, do you honestly think attacking another person also contributes to the overall positive energy of the discussion? You calling out Psychokitty like you did was not constructive in the least. Where I work we have a rule (we follow Kanban and Kaizen so this is rooted in that). The rule is that if you offer any kind of criticism you must follow it up with constructive suggestions. So, to set precedence I will follow my slightly negative comments with some constructive suggestions. In the future I think if you enter into a place that is strange and new you should probably ask many questions and defer to those who know more, even if they happen to have an elitist attitude. You do not know how much the leaders of these boards are bothered with the same questions and problems day in and day out. Your problem may be unique to you, but they have probably seen and heard it a thousand times already. Be cognizant of that when asking for help.

That is all.

 

[johnlgalt]

hell, it was pretty light compared to PKs usual (and highly amusing, and dare I say, justified) rants....

 

[gnath9]

I just don't think calling 'em a fool is going to solve anything or make them feel very welcome. MY rant.

LOL .... did you notice the title to the thread ?

 

[VIO]

hell, it was pretty light compared to PKs usual (and highly amusing, and dare I say, justified) rants....

this.

Also, yes. Yes, to all the thoughts and comments about reading, and understanding. I like to think of rooting not so much as a simple process of gaining su permission on your phone but a journey into a different way of thinking. It represents a shift that you decide to take in your position to your technology.

If you aren't willing to understand that shift you can end up in some pretty bad places without any of the knowledge one would have gained via the "hard way" that may just save your ass.

Like most things in life, creative and intelligent thought about a subject comes from an understanding of that subject (and how to play by the rules of that domain). I always suggest that people who want to root not only follow the directions to the T, but also understand what those directions mean.

For example the simple "Flash a custom Recovery" is easy enough to do; download CM and it "flash" but what happens if the recovery disappears (such as the recent 2.2 rooting woes). If you took the time to learn what a "Custom Recovery" is, what it does, how it connects to the rest of your phone, you are in a much better position to 1. not freak out and make a poor choice. 2. Troubleshoot the problem and 3. ask the correct questions on the boards.

I'm not saying that a technical mastery of the interplay between software, firmware, and hardware is necessary, but a general understanding of what those are certainly is helpful.

O' and always and without fail, make a backup. there is just never an excuse for not having a valid Nandroid on your phone!

 

[Psychokitty]

hell, it was pretty light compared to PKs usual (and highly amusing, and dare I say, justified) rants....

Reported for unnecessary commentary.