-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Recovery?
- Thread starter Steven58
- Start date
-
- Tags
- motorola droid 3
imnotmikal
Android Expert
Rooting is very simple. It's a 1 click system. I just got my phone about 8 hours ago and rooted it already. Anyways, go here and view the second post. It's 5 simple steps IIRC. Download the drivers and the rooting program. It walks you through it and once the phone's connected and program running, you hit any key and watch it do its thing. Took probably less than 5 minutes. I started it and just walked away.
imnotmikal
Android Expert
He was asking for recovery, not root.
I was saying that it's very easy and it doesn't seemed it's failed anyone yet. I understand why you'd want a recovery, but so far this root looks good and hard to butcher to the point where a recovery would be absolutely necessary.
cookie_monster
Android Enthusiast
Frisco
=Luceat Lux Vestra=
I'll second the ease of rooting with the method described in that thread.
It was great to get this thing free of so much of the junk in there, although I'll be even happier when a ROM or three come along which don't involve Blur.
Let me explain. After a year of rooting on the Droid X, which also has an encrypted bootloader, I've had to sbf (flash recovery) many, many times, as I was learning. Do I have to do it anymore? Not unless I'm going over to a second init rom, which I really don't do anymore as I'm happy with stock blur .602 rooted.
My son, however, is a classic tinkerer, a chip of the old block. I can see him playing around with things he doesn't know about and getting into trouble, bricking his phone. I'd rather wait till they get an sbf recovery. Then I won't have to worry when he says he's bricked his phone. (gone into a bootloop, got stuck at the boot animation or at the bootlogo).
Call me foolish, that's my threshold of comfort with this type of thing. When playing around with an encrypted bootloader, it's always best to wait until you have a recovery (sbf) to fall back on. Granted, there are no roms being flashed here, as yet, but still. I'm the father and those are my rules.
My son, however, is a classic tinkerer, a chip of the old block. I can see him playing around with things he doesn't know about and getting into trouble, bricking his phone. I'd rather wait till they get an sbf recovery. Then I won't have to worry when he says he's bricked his phone. (gone into a bootloop, got stuck at the boot animation or at the bootlogo).
Call me foolish, that's my threshold of comfort with this type of thing. When playing around with an encrypted bootloader, it's always best to wait until you have a recovery (sbf) to fall back on. Granted, there are no roms being flashed here, as yet, but still. I'm the father and those are my rules.
Let me explain. After a year of rooting on the Droid X, which also has an encrypted bootloader, I've had to sbf (flash recovery) many, many times, as I was learning. Do I have to do it anymore? Not unless I'm going over to a second init rom, which I really don't do anymore as I'm happy with stock blur .602 rooted.
My son, however, is a classic tinkerer, a chip of the old block. I can see him playing around with things he doesn't know about and getting into trouble, bricking his phone. I'd rather wait till they get an sbf recovery. Then I won't have to worry when he says he's bricked his phone. (gone into a bootloop, got stuck at the boot animation or at the bootlogo).
Call me foolish, that's my threshold of comfort with this type of thing. When playing around with an encrypted bootloader, it's always best to wait until you have a recovery (sbf) to fall back on. Granted, there are no roms being flashed here, as yet, but still. I'm the father and those are my rules.
I agree with you here. I got in over my head and ended up bricking my X before. I sound a lot like your kid (being 17 myself) and never being satisfied with stock or good enough. I was up til about 1AM on a Tuesday night trying to restore my phone and finally got it SBF'd. That was a pain and I understand your concern there.