Thanks to all of the devs who've been working on this phone, we now have various ways to get root access to our phone (ie. torpedo, AIO, etc.). The question I have is which method is the best or does it not matter? Are there any drawbacks to one method or another?
I've had success with using the AIO one-click method. However, I'm trying to narrow down the reason for my phone randomly rebooting. After my last wipe, my phone was stable for 2 days. Once I rooted it, my phone randomly rebooted the next day. I don't know if this was a simple coincidence or if somehow rooting caused the reboot. I know many of you have rooted and don't have random reboots. The only apps I had installed at this point where:
Deja Office
Enhanced Email
Titanium Backup
Any thoughts?
I'm rooted with the AIO one-click and I've never had a random reboot. Then again, before I rooted I never had a random reboot either. I think part of it is just luck of the draw and varies between individual phones. Some people have random reboots several times a day no matter what they do top their phones, some have none, and everything in between. Sorry I couldn't help solve your issue, but I hope I helped anyway.
Sent from my MB855 using XDA App
Thanks for your response and I'm glad the one-click method is working for you with no reboots. Of course, this sends me back to the drawing board.
I'm rebuilding my phone right now and will try the torpedo root method to see if my phone will be more stable. If not, I guess I'll get a 3rd Photon replacement. Like you said, maybe it is just the luck of the draw with the hardware. Some phones can handle the 1.4 oc kernels and some can't. Wish me luck...
According to this thread, rooting with the one-click method prohibits flashing the CM7 ROM but the torpedo method works. Therefore, there does seem to be a difference between the rooting methods.
I seem to remember hearing something about titanium backup being unstable on this phone, was that fixed?
Sent from one focused mopho!
Fortunately, Titanium works well on my MoPho.
sjamie said:
According to this thread, rooting with the one-click method prohibits flashing the CM7 ROM but the torpedo method works. Therefore, there does seem to be a difference between the rooting methods.
Click to expand...
Click to collapse
yea... thats not true... >.>
rooting doesnt mean unlocking. there is a difference. for instance between rooting and running odin on a samung phone, or rooting and running unrevoked on htc... rsdlite is much much lower programming then root is. since im on linux and i use sbf_flash i actually have a return to goodness script that roots me installs an unlocked bootloader and flashes cwm all in one for me for after locking it back up again.
And that thread does not state it prohibits flashing cm7 using AIO. He was just having some issues unlocking so it was recommended to start fresh using another method.
And like the man above^ says two different things /rooting vs unlocking.
just saying...
sjamie said:
According to this thread, rooting with the one-click method prohibits flashing the CM7 ROM but the torpedo method works. Therefore, there does seem to be a difference between the rooting methods.
Click to expand...
Click to collapse
Cool, if I misunderstood what was being stated in that thread... my bad.
Just trying to figure out what is making my phone unstable. I just rooted my phone using the torpedo method this time around which made me further appreciate the convenience of shabbypenguin's one-click method.
Let's see how long I can go without a random reboot!
no its cool, i get plenty of people that blame root for all sorts of things
Related
So I downloaded ryanza'sOCLF but I'm hesitant to run it.. wanted to find out a few things first which I couldn't seem to clarify using search in the forum.
Is it possible to just root using this program and not apply the lagfix? (seeing if this is easier since no PC involved)
Are there any problems reverting back to stock if rooting using this method?
Also does rooting wipe all data so should save it on a PC?
I ultimately want to root and apply the bionix fusion rom though I'm still unsure about the kernel to use etc. and I ultimately want to avoid lagfix since it seems that forgetting to disable it before flashing caused alot of bricks.
answers, tips, and recommendations are EXTREMELY appreciated.
Flaming will however also be understood though I did try the search tool for my questions.
omar26c said:
So I downloaded ryanza'sOCLF but I'm hesitant to run it.. wanted to find out a few things first which I couldn't seem to clarify using search in the forum.
Is it possible to just root using this program and not apply the lagfix? (seeing if this is easier since no PC involved)
Are there any problems reverting back to stock if rooting using this method?
Also does rooting wipe all data so should save it on a PC?
I ultimately want to root and apply the bionix fusion rom though I'm still unsure about the kernel to use etc. and I ultimately want to avoid lagfix since it seems that forgetting to disable it before flashing caused alot of bricks.
answers, tips, and recommendations are EXTREMELY appreciated.
Flaming will however also be understood though I did try the search tool for my questions.
Click to expand...
Click to collapse
-Yes, it's possible to just root.
-No, there's no problems reverting back.
-No, it doesn't wipe any data. Flashing another ROM how ever does.
Sent from my SGH-T959 using XDA App
omar26c said:
So I downloaded ryanza'sOCLF but I'm hesitant to run it.. wanted to find out a few things first which I couldn't seem to clarify using search in the forum.
Is it possible to just root using this program and not apply the lagfix? (seeing if this is easier since no PC involved)
Are there any problems reverting back to stock if rooting using this method?
Also does rooting wipe all data so should save it on a PC?
I ultimately want to root and apply the bionix fusion rom though I'm still unsure about the kernel to use etc. and I ultimately want to avoid lagfix since it seems that forgetting to disable it before flashing caused alot of bricks.
answers, tips, and recommendations are EXTREMELY appreciated.
Flaming will however also be understood though I did try the search tool for my questions.
Click to expand...
Click to collapse
Yes. You can use it for root only.
No problems using it to unroot either.
Stick with the stock fusion to start.
Sent using XDA App
Thank You guys very much for the answers! Had a G1 before this that I rooted and flashed a few times but the vibrant seems a little trickier than that so wanted make sure. Thanks again.
Hah. After flashing a few times, using Odin, and adding custom kernels, your really gona love the vibrant. Thing is tough as nails. I like to say good luck TRYING to brick this thing. I would suggest getting familir with odin though because rooting is "a gateway drug"
:-D
Sent from my SGH-T959 using XDA App
Guys and gals,
I just got a droid eris from a friend and want to root it and flash clockwork on it. I downloaded everything from unrevoked but when i try to install drivers for a windows computer it says that all drivers are up to date and it says htc bootloader. So i then run the package from unrevoked and nothing happens all it says on the screen is waiting for device. I have been all over you tube and forums can't find help to fix.
I am on 1.49 or something its also just stock 2.1. can anyone tell me what step I am doing wrong. please help.
DroidFamily said:
I just got a droid eris from a friend and want to root it and flash clockwork on it.
Click to expand...
Click to collapse
PROCEED DIRECTLY TO JAIL AND DO NOT PASS "GO".
Seriously, the combination of "newb" + "Clockwork" tends to be fatal to the Eris.
It is far more prudent for you to use the rooting methods described here in this forum - jcase's "Universal One Click .apk" comes to mind. Or, you can go over to AndroidForums and have a look at the Universal Root For Dummies. (The first rooting method that I mentioned is faster, but the second has an invaluable outline in the fourth post of that thread - with pictures - of how to use Amon_RA )
Only after you have completely mastered the use of the Amon_RA recovery should you consider using ROM Manager/Clockwork. (And you can use both, believe it or not).
Just yesterday someone hard-bricked their phone - possibly using the same recovery you are thinking of flashing.
If you insist on use Clockwork, for sure you ought to find out about what MD5 sums are, and how you can use apps such as scary alien's free market app "AFV" (Android File Verifier) to validate the signing of a ROM for which the developer has not provided a file size or MD5 signature.
bftb0
P.S. Neither of the two methods I mention above require a computer. That neatly solves your driver problem.
Much like the guy above, I'd avoid Clockwork and just go with something simple and almost guaranteed to work like the One-Click Root. With the Eris, Clockwork has a bad reputation. Some people buy into the taboo, some don't, but there's more evidence supporting bad things than good for it.
I'd avoid the possibility of turning your phone into a paperweight and steer clear of Clockwork.
bftb0 said:
It is far more prudent for you to use the rooting methods described here in this forum - jcase's "Universal One Click .apk" comes to mind. Or, you can go over to AndroidForums and have a look at the Universal Root For Dummies. (The first rooting method that I mentioned is faster, but the second has an invaluable outline in the fourth post of that thread - with pictures - of how to use Amon_RA )
Click to expand...
Click to collapse
Hindsight being 20/20 I would agree with the above post...
However I did use unrEVOked but was doing it thru linux so it was easier but did not like clockwork so I reflashed recovery with Amon_RA after I read up and realized how much better and easier it is.
This video I found will help if you still want to use the Unrevoked method
http://theunlockr.com/2010/09/22/how-to-root-the-htc-droid-eris-unrevoked-method/
Hope this helps you.
As a n00b - and I know this sounds like a commercial - really, the one click was the choice.
This is the thread that jcase started for that.
http://forum.xda-developers.com/showthread.php?t=742228
I am sure there is some really great reason to use a different method, but frankly, I just really needed to get on the newer roms. This was fast and easy. I didn't want to debug I just wanted it to work.
Just curious which rom are you going to be loading?
Ok coming from the evo to thunderbolt I'm not new to this I've rooted manual and auto root. But my question is the auto root that is available that is based on the manual root in the android development section will that root mr2 also? I know that mr2 can be rooted using the manual mr1 root as people have said it works. So wouldn't the auto root for mr1 prove to root mr2 the same?
Thanks for the help..
They auto-root methods perform the same commands as manual so yes.
If you're already familiar with doing it manually, why risk the problems associated with autoroot scripts though? It doesn't take that long. Plus you gain the benefit of a little better understanding of what's going on as well as knowing exactly what step you have problems with (which shouldn't happen really) as opposed to just having to say "autoroot didn't work" because you don't know what step it errored on. Manual is the way to go.
Just my 2cents.
Just an example of it not working out properly:
http://forum.xda-developers.com/showthread.php?t=1188806
It'll work, but the people using it are not the most informed on how to root, which is why they're using it and in order to use it, you have to be informed enough to know how do more or less what you would if you just pasted the commands using the manual method (sort of a catch-22).
tl;dr: you can use it, but the chances if it working right always and being a noob are not the greatest (nor is trying to get help if you screw it up).
Agreed, I've read a few cases where the autoroot script messed up in one spot or another. Manual root is def the way to go with the thunderbolt.
I like to think of the scripts as the easy way to do it for those who've done it or are doing it so often it's just a pain in the ass to do the manual method every time.
Scripts are just trouble if you can't verify the SDK is installed correctly and ADB works. And if you can do that, doing the rest is easy. The stuff you'll learn will prove useful as long as you're using android devices.
Although I've flashed non-phone devices in the past (routers, PAP2, Ipod classic, etc.) This is the first time I'm going to be flashing a SmartPhone that I've ordered which I should be getting very soon.
I ordered a Samsung Galaxy S II and have been crawling the forum trying to learn all I can before I try rooting and unlocking my phone when I get it. But I'm having trouble deciding on a few things.
Hopefully my question can become a guide for other new people who are just starting off like me.
Rooting:
To begin, I'm trying to figure out what's best for rooting.
I've looked at a few different methods..
Chainfire's direct method: http://forum.xda-developers.com/showthread.php?t=1103399
lyriquidperfection's one-click method: http://forum.xda-developers.com/showthread.php?t=1125414
CLShortFuse's one-click method: http://forum.xda-developers.com/showthread.php?t=803682
LitePro's ROM and Root method all-in-one: http://forum.xda-developers.com/showthread.php?t=1095274
All of these have their own merits. But I'm trying to figure out the best approach for myself.
Although Lightn'ing (LitePro's) looks interesting and I may try that ROM later, for now I want to avoid changing the ROM till I know I like the phone. So I'm looking at the first three choices.
The one that I think I would be able to do easiest is either lyriquidperfection's or CLShortFuse's methods as they both are one-click solutions and I just need to grab the right kernels.
I don't know if there's any reason I would want to go with Chainfire's instead of the two previously mentioned. If there is please let me know.
I asked this question on the respective threads but as of posting haven't gotten an answer of if there's any reason to flash the original kernel back after rooting and if I keep root if I flash it back.
I also don't know much about the use of Jigs to avoid the flash counter going up. Is there any reason I need to worry about the flash counter going up? Is there a limit on number of flashes on a phone?
Unlocking:
For unlocking I looked at:
http://forum.xda-developers.com/showthread.php?t=1092451
However it seems for my specific phone (Virgin/Bell) we use this method as posted in the same thread:
http://forum.xda-developers.com/showthread.php?p=16482293#post16482293
This seems pretty much straight-forward. I just got to root the phone then get and run the app mentioned. Phone will crash/reboot and then no SIM lock.
If there's anything that seems wrong with this let me know please.
Other stuff:
At some stage here I want to be able to back up the stuff on the phone and get other typical tools.
I keep hearing about ClockWorkMod constantly and it seems to be a tool for backing up the phone data and making it easier to flash stuff in without use of ODIN.
I haven't found clear documentation on how I would do this on the SGII specifically.
I also here Titanium backup (sp?) is also a good idea to install at some point.
Is there other apps or otherwise I should be looking into before I start this journey into the wonderful world of hacked smartphones?
-This is a place marker for me making amendments so that later this may be more or less a guide for other beginners-
Dav_Edward said:
Although I've flashed non-phone devices in the past (routers, PAP2, Ipod classic, etc.) This is the first time I'm going to be flashing a SmartPhone that I've ordered which I should be getting very soon.
I ordered a Samsung Galaxy S II and have been crawling the forum trying to learn all I can before I try rooting and unlocking my phone when I get it. But I'm having trouble deciding on a few things.
Hopefully my question can become a guide for other new people who are just starting off like me.
Rooting:
To begin, I'm trying to figure out what's best for rooting.
I've looked at a few different methods..
Chainfire's direct method: http://forum.xda-developers.com/showthread.php?t=1103399
lyriquidperfection's one-click method: http://forum.xda-developers.com/showthread.php?t=1125414
CLShortFuse's one-click method: http://forum.xda-developers.com/showthread.php?t=803682
LitePro's ROM and Root method all-in-one: http://forum.xda-developers.com/showthread.php?t=1095274
All of these have their own merits. But I'm trying to figure out the best approach for myself.
Chainfires simplest method less problems for most .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
I also don't know much about the use of Jigs to avoid the flash counter going up. Is there any reason I need to worry about the flash counter going up? Is there a limit on number of flashes on a phone?
Zero as Samsung will invalidate warranty for custom roms or rooted phones .
Other stuff:
At some stage here I want to be able to back up the stuff on the phone and get other typical tools.
I keep hearing about ClockWorkMod constantly and it seems to be a tool for backing up the phone data and making it easier to flash stuff in without use of ODIN.
I haven't found clear documentation on how I would do this on the SGII specifically.
Their is no documentation its probably written up in the FAQ or Wip but is a relativity simple tool anyway .Backup restore phones rom install custom rom wipe data factory reset reset battery stats to zero .
FAQ
http://forum.xda-developers.com/showthread.php?t=1065995
Wip
http://forum.xda-developers.com/showthread.php?t=1125282
I also here Titanium backup (sp?) is also a good idea to install at some point.
On a rooted phone Titanium pro allows you to back up your apps and also to freeze apps .
jje
Click to expand...
Click to collapse
Thorough stuff, props to you sir - you know search so you'll get your first thanks...
I would advice you to go with Chainfire's method. It's the easiest and most versatile method IMO. Definitely the best for beginners because you keep your stock ROM yet still are rooted and get Clockwork Mod.
The installed CWM (Clockwork Mod) Manager app with Chainfire's work is an easy way to see what it does - basically you can backup and restore your whole system/device, plus flash custom ROM/kernels/themes etc. Look into the flashing part later - baby steps are good here!
Titanium Backup is an excellent backup app for backing up/restoring apps and data, as opposed to the whole system. Buy the Pro version, definitely worth it.
I also like My Backup (also on Market), excellent for backing up contacts/SMS/MMS. The free version is a 30 day trial.
Can't help with unlocking, never needed to - sure others can help.
Good luck
Edit - JJ beat me too it, hadn't seen his post. Must type faster...
@JJEgan & @B3311, thanks for the useful information.
I was going to try those one-click methods because I thought those were the more newbie friendly methods. Thanks for the information to try using Chainfire's instead.
I will try using Chainfire's method instead with your advice when I get the phone. Having the tools like his CWM hopefully will make things easier.
I am a bit concerned though about his mention that Rom Loader won't work with his version of the build. I'd still like the ability to use custom roms down the road once I learn how to properly back up the phone so I can experiment with various roms till I find the one I like most.
Any advice about using rom loader or other possible difficulties using Chainfire's kernel?
Dav_Edward said:
@JJEgan & @B3311, thanks for the useful information.
I was going to try those one-click methods because I thought those were the more newbie friendly methods. Thanks for the information to try using Chainfire's instead.
I will try using Chainfire's method instead with your advice when I get the phone. Having the tools like his CWM hopefully will make things easier.
I am a bit concerned though about his mention that Rom Loader won't work with his version of the build. I'd still like the ability to use custom roms down the road once I learn how to properly back up the phone so I can experiment with various roms till I find the one I like most.
Any advice about using rom loader or other possible difficulties using Chainfire's kernel?
Click to expand...
Click to collapse
Most just put custom rom on sd card and flash via CWM .
Sorry no nothing about Rom Loader .
jje
I would also advice using CF-Root. I was scared of rooting my phone, but after using CF-Root, I don’t know why I was so scared. The process took a little over 30 seconds (I need practice). To me at lease I think it’s the easiest method, you just need to make sure to download the right kernel.
EDIT:
Get a UBS jig, After rooting, I had the "yellow triangle" I turned off phone, removed battery, inserted jig, put back battery, entered download mode, restarted phone and no more "yellow triangle"
Hello, all!
I ran through lots of threads, but I cannot find a remedy for my problematic rooting.
Firstly, maybe I have to warn you that I'm noob in rooting devices, I promise I'll catch up!
I very much would like to root my Dell Streak, I chose SuperOneClick 2.3.1 to do so.
I got SuperOneClick, turned my phone in USB debugging mode, allowed unknown apps, unmounted SD card.
Connected all cables...press Root and SuperOneClick gets non-responding after:
(see attached picture)
In this situation if I run adb devices I see mine listed.
Have you had similar situation? Have you got any ideas how to finish rooting my phone?
Ok. Forget SuperOneclick Go to this link and read, absorb, read again, read once or twice more then, absorb. Finally read over many more times and once you think you've taken it all in, read it again. Honestly. Rooting is great if you get it right but it's what nightmares are made off if you brick your phone.
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide#Rooting_your_phone
Basically, you need to install Streakmod (a custom recovery) using "Fastboot". This will enable you to install "Superuser. zip". This will "Root" your phone. Best of luck.
You're nicer to him than I would have been. All I will add to what you said is that the search engine is his best friend and he might want to learn how to use it.
Yeah, but if the OP comes back with the same question i'll send em back to the same link. As you know, there is probably an answer to every "Android" related question within this forum. People just need to look. I'm just being nice cos back in February i was a noob asking the same question. What i quickly learned was, if you bother to look, you find and you learn loads of other valuable stuff along the way.
I had simialar issue and solved it
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
One-click root solutions aren't recommended for the Streak because as you found out, they don't always work. However, the method on the wiki has a success rate of 100%. So what I don't understand is, why in the heck would anyone use a method that has a high rate of failure over a method that doesn't.
hey...s.o.c is no more recommended...
just flash the su.zip using streakmod and voila.. nothing else
Sent from my Dell Streak using xda premium
alpharetta said:
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
Click to expand...
Click to collapse
The reason, why we are using the SupperOneClick is already mentioned: You are proposing us to do the fastboot method to get the custom recovery running. But to do so on the streak we first need to avoid the automatic restore of the stock-recovery tool. And to do so, we need a rooted device...
You see our point? It's like a cat biting in it's own tail, or a man sucking his own... You got me though?
It's not a proposal. If you bothered to look at the bottom of the flashing guide page on the wiki, you would have seen the following note:
Not recommended: Gingerbreak, SuperOneClick, Universal Androot, Z4Root
Click to expand...
Click to collapse
That note is on the flashing guide for a reason: these methods quite frequently do not work on the Streak. Besides, this really isn't as difficult as you're making it sound. The one thing that needs emphasis is that you'll install StreakMod Recovery twice. The first time is to root. The second time comes after using a file manager to delete install-recovery.sh, the file that causes the recovery to get overwritten.
If that series of steps in the flashing guide is too much for you to handle, I would not recommend rooting. The Streak is arguably the easiest device to root, requiring no special tools like goldcards to do the job. If you want a real challenge, try rooting an HTC Inspire. Without special tools an Inspire cannot be rooted.
Hi there quick question as I just got my hands on a Dell streak I see you post the guide for rooting and say its 100% safe is this 100% correct cause I don't fancy bricking it also will it work on build froyo 2.2.2?
By the way I'm not not a noob as I rooted my dhd the hard way round when it first came out the same way the inspire was rooted also built 2 custom roms and work on 3 others
Only asking cause the set up of the Dell is very different to an htc and a year on htcs are getting easier to root with a one click tool
And please don't say to read read and read again as that's what I will be doing anyway I ain't going to fly before I can walk lol
sent from my dhd
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Strephon Alkhalikoi said:
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Click to expand...
Click to collapse
Thank you very much for the info seems pretty much straight forward will crack on with it in a few days once I'm familiar with as much as I can need to learn the streak more before I start playing lol
As for the inspire its pretty much the same as a dhd and tbh flashing a radio is as simple as flashing a Rom from recovery I also tested flashing the radio from a different htc phone and regardless that it flashed but got stuck on splash screen I could still not brick the phone, now its really difficult to brick inspire or dhd, but it is known that eng s-off can cause issues on the inspire but not on the dhd
Just some info back for yourself mate as a thank you for yours also will hit the thanks button next time I'm pc
sent from my dhd
Thanks for the info. I rooted my roommate's Inspire using the AAHK on the day she got it. It ended up being a little more time consuming than using REVOlutionary to S-OFF my Aria the second time I rooted it*. I proceeded to put Android Revolution on the Inspire and she's a happy camper.
*The first time I rooted the Aria, which was the day I got it a year ago, I used UnrEVOked to root it. At the time there was no S-OFF possible.
Perspective for users of devices with locked bootloaders:
All dell devices are the equivilent of S-OFF/unprotected bootloader devices.
S-OFF, root, and custom are all seperate (but closely intertwined) concepts.
There are equivilents of superuser.zip for the nexus devices, as they ship either S-OFF or have
'fastboot oem lock/unlock' available to allow the user to S-ON or S-OFF at will.
Superuser.zip is equally valid on an already s-off'ed device that has a custom rec installed.
If your device can be officially S-OFFed and you install a custom recovery and use superuser.zip (or the device's equivilent form) you never have to touch a one click tool.
If your device is S-ON and there is no official way to S-OFF you must S-OFF it first, usually that requires making changes on it while it's on, which usually requires root. The only way to root a live device is though exploits in android, this is what one click tools do.
After having S-OFF'ed you can install a custom rec, and then it doesnt matter if you're rooted or not as you can install custom recs.
As long as you remain S-OFF'ed you never have to worry about rooting as custom recs/flashing zips completely bypasses android's security model.
This is the only reason that Android 3.0+ can be rooted, the ONLY ways to root 3.0+ is by rooting outside android. There are no known exploits in 3.0+ (and hence ICS devices are completely unrootable for the time being if S-ON) Every single 3.0+ device is rooted by either by superuser.zip or superboots (which are normal kernels that automatically install superuser.zip without needing a custom recovery)
The problem with superboots are that they are device AND rom specific, during the 2xx era for the s5 there were superboots available. But they had to be remade for every single version as flashing the wrong one will brick your device.
Most of the exploits used by one click tools are patched by 360, and I believe ALL exploits are patched in 4xx. Normally there are known vulnerabilities in 2.3.3, but Dell has added their own fixes to these seeing as it's one of the few devices running 2.3.3 that hasnt been updated to 2.3.4 or higher
Superuser.zip is version independant, and to a degree device independant. As long as it can mount your /system partition it can root it.
The S-ON/S-OFF terminiology is specific to HTC devices, but the concept is common to all android devices;
Dell = always S-OFF
HTC = dependant on device/carrier
Moto = mostly S-ON, some atrix's can be unlocked, xooms always unlocked
Samsung = usually S-OFF
'fastboot oem unlock' = sets S-OFF if allowed
'fastboot oem lock' = sets S-ON if allowed