So I just picked up the new Samsung Vibrant AKA the Galaxy S and I have been trying everything out there to succesfully root it. I have tried everything available on this site and ssveral others, and have ruled every issue out other than this: that the TMobile Vibrants do not allow you to access the recovery screen. This became apparent after I attempted to access it through the cmd prompt and was told that it was inaccessable.
My question is this: is there a way around this or will I have to go in through Linux. I've specifically put off upgrading to 2.2 from 2.1 because it is (presumably) much easier to root im 2.1.
At any rate any help at all would be appreciated.
Sent from my SGH-T959 using XDA App
I have a rooted Vibrant, so it's not an issue with the phone per se, but it does seem that there was a batch of them made that will not allow you to either go into recovery or download modes via physical hardware (holding volume keys, etc), and at least in one other instance I've read, the person couldn't root his Vibrant. I've also read that this wasn't supposed to be the case and a fix is potentially being worked on (all hearsay, of course, so don't take this as any kind of gospel).
Yeah that's definitely what's going on with mine (presumably). I guess I'll just keep my eyes peeled and wait for a fix to come out. Thanks!
Sent from my SGH-T959 using XDA App
My Vibrant is one them. I tried today(Multiple time) using the new method of downloading the update.zip onto my phone and holding down volume/power buttons together and it will not root.
Does 'adb reboot recovery' work for you guys? Your phone must be in Develop. mode in order to get adb commands to work.
Nope. Again, the problem is or phones won't aglow us to access the boot recovery menu. Presumably samsung or tmobile got wise and started locking that feature out.
Sent from my SGH-T959 using XDA App
Related
I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Authorities have been notified..... probably on their way to your house now......
alecjake said:
I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Click to expand...
Click to collapse
Pack your bags, get on the first flight out of town.
Sent from my SGH-T959 using XDA App
Hahaha nice jokes.
Don't worry they don't check every phone infact they putthe phones on racks and a computer auto turns them to stock erasing everything
No worries
Sent from my SGH-T959 using XDA App
I bricked mine and sent it back to them with a custom rom and a i9000 kernel on it....no problem once its in good physical condition they wont give you any trouble
alecjake said:
I swapped out my Vibrant for a new one and forgot to delete the file for root. Is this a problem or will T-Mobile not even notice the file and just wipe the internal mem? I unrooted it before I sent it in but I forgot to delete the file.
Click to expand...
Click to collapse
Vibrant + Nero + OCLF
I hope you don't get charge cuz if they find out you will. Trust me I got a couple of friends working for Tmo.
I did the same thing OP, no big deal... I didn't get charged..
When I got mine I asked the sales person about rooting the phone. Keep in mind this is a salesperson and not T-Mobile corporate, but she really knew her stuff. She was the one everyone else in the store went to for help when they were not sure of the answer to a customer's question.
She said, if you have to return it just get it back to looking stock. Have the stock ROM on the phone and remove any obvious root or root required apps if they are still installed after you put the stock ROM on there. She said if it made me more comfortable I could remove busybox and su, but that nobody was going to go digging into the file system to see if the phone was rooted.
Basically they know, even if they don't officially acknowledge, that rooting the phone does not break it. If the phone is running stock firmware and it is still having issues then it is highly likely that the issue is hardware. Also, the preliminary acceptance or denial of the claim is done in store. If it makes it back to the factory it is pretty much accepted unless something really fishy pops up, like it is obvious you have been dissembling the device. They might kick it back if they find a FFC or soldering at the GPS antenna, but they are not looking for the su executive at that point.
They don't check the phones out that they get back they just restore them or whatever
lrobles787 said:
I hope you don't get charge cuz if they find out you will. Trust me I got a couple of friends working for Tmo.
Click to expand...
Click to collapse
Vibrant + Nero + OCLF
Yeah. Everyone is right. No worries. I ducked up a captivate on a30 day test drive with ATT, I took it back with stock ROM and even left superuser icon on there just hid it with launcher pro. Shouldn't have any problems. I didnt and believe they didn't wanna take that phone back on day 29.
Sent from my ADR6300 using XDA App
I've sent mine to samsung after i bricked it messing with roms, it was sent in with absolutely nothing original software wise.
didnt even get a warning. they flashed and sent it back A-ok
T-Mobile support confirmed that there have been alot of complaints regarding sluggish phones after updating to OS 2.2.1. They said that they are offering to exchange myTouch 3G phones with the LG Optimus-T phone due to the problems caused by the update. I checked the specs on each phone and they are quite similar; the LG's processor is a bit faster. Has anyone tried the LG Optimus-T? I'm gonna go to the T-Mobile store to test it out, but I figured I'd check out all your opinions before I make a decision.
Thanks,
-Adam
optimus is way faster. it feels better in the hand too. and it can run lwp smoothly without lags
Think I'm going to have to look into this.
g1user101 said:
optimus is way faster. it feels better in the hand too. and it can run lwp smoothly without lags
Click to expand...
Click to collapse
I tried out the Optimus-T at the T-Mobile store; the extra 80Mhz of processor really makes a drastic difference! I'm definitely gonna swap the myTouch for an Optimus-T. The one thing that I wasn't able to test out at the store was the built-in microphone. I'm a musician and I use the mic alot to record guitar riffs if I think I'm going to forget them. I tried out a couple different smart phones before I went with the myTouch and the mics on some of the other phones were terrible. Anyone have any comments on the quality of the Optimus-T's mic? When it comes down to it, I really don't have any option but to swap phones; 2.2 drools on the myTouch.
-Adam
adam79 said:
2.2 drools on the myTouch.
Click to expand...
Click to collapse
That's fixable, but I would definitely be OK with a new phone.
DonJuan692006 said:
That's fixable, but I would definitely be OK with a new phone.
Click to expand...
Click to collapse
How is it fixable? I've tried multiple hard resets. Running it with no applications or widgets running, no GPS, no anything and it still is sloooooow. What do you suggest because I'd rather keep the myTouch. Please advise.
Thanks,
-Adam
Easy day. Download this file and rename it sappimg.zip (not sappimg.zip.zip)(To make sure go to Start->Control Panel->Folder Options->View Tab-> Uncheck "Hide known file extensions"). Then download this file and rename it to update.zip. Next, put them both on the root of your SD card. Boot into hboot (volume down+power) and the phone will pickup the SAPPIMG on it's own and do a file check. When prompted, hit the trackball to continue, it'll run the updates, then hit the trackball again to reboot. When you get to the activation screen, turn the phone off. Power on holding (home+power) which will get you to a screen showing a triangle with an exclamation point and a phone. Hit (home+power) again to bring up the recovery menu. Select the "wipe data/factory reset" option, then select "apply update.zip from SD card". Let it do it's thing and sit until your back at the activation screen. I'm sure you can figure it out from there.
DonJuan692006 said:
Easy day. Download this file and rename it sappimg.zip (not sappimg.zip.zip)(To make sure go to Start->Control Panel->Folder Options->View Tab-> Uncheck "Hide known file extensions"). Then download this file and rename it to update.zip. Next...
Click to expand...
Click to collapse
What does this do to the phone? Will it void the warranty?
No, everything is stock. Your basically downgrading back to Android 1.6 and then reapplying the update, but doing it properly. The update should have included a script that would clean up the phones cache, but it apparently doesn't which is the root of the sluggish phone. I had the same issue until doing what I told you to do. Of course, I've been rooting/ROMing/theming my phone for 6 months, so I kind of figured that was the problem. Also to note, doing a factory reset after applying the update just doesn't seem to be cutting it. With my method, you'll come to the update as clean as possible.
DonJuan692006 said:
No, everything is stock. Your basically downgrading back to Android 1.6 and then reapplying the update, but doing it properly. The update should have included a script that would clean up the phones cache, but it apparently doesn't which is the root of the sluggish phone. I had the same issue until doing what I told you to do. Of course, I've been rooting/ROMing/theming my phone for 6 months, so I kind of figured that was the problem. Also to note, doing a factory reset after applying the update just doesn't seem to be cutting it. With my method, you'll come to the update as clean as possible.
Click to expand...
Click to collapse
Oh yeah, one more thing.. Can I do this on a Mac, or do you need a Windows computer?
Thanks,
-Adam
A Mac will be fine.
Sent from my T-Mobile myTouch 3G using Tapatalk
if I re-root and use clockworkmod recovery, will the cache cleaner on there be suitable for this?
Sent from my T-Mobile myTouch 3G using XDA App
No, you need a fresh install, not just to clear out cache.
[Q] Mytouch 1.2 trade in?
So I've been hearing that tmobile is offering a phone trade in for devices bricked by the ota update. It seems that the replacement for the mytouch 1.2 is the optimus t. The fender edition receives a vibrant.Is this the same as the optimus GT540? And is it worth manually bricking my phone to get it? And since the fender is switched for a much better phone, would it be possible to get that instead of the optimus? Please let me know.
Edit: Yes I did read the other thread about this, but that one moved off topic.
Sent from my T-Mobile myTouch 3G using XDA App
The Optimus T is also the Optimus One P500. You won't be able to get the Vibrant, even if you offer to pay the difference, I tried. Maybe if your persistant enough and get a nice CS Rep you may be able to weasle one out. Either way, your getting a better phone.
Sent from my T-Mobile myTouch 3G using Tapatalk
So you're saying I could pretend it was a fender to get the vibrant? Because I know the ship you the phone first, before requiring you to send it back. And will they let me trade in for lagginess, or do I manually have to flash the wrong update?
Sent from my T-Mobile myTouch 3G using XDA App
Vibrant is out unless you find a CS that's just really nice or you annoy them to the point they'll do anything to shut you up. Their going to base the swap out off of what device your account has on it. So if your account says you have a regular 1.2 then your getting the Optimus. Unless, like I said, pigs start flying and cows start pooping fossil fuel. From what I've read they're doing it for lag as well but only after you go through the facade of them having you do a factory reset from recovery and waiting a day or so.
Sent from my T-Mobile myTouch 3G using Tapatalk
Note that I can manipulate these people well. I bricked two mytouches trying to get root(before androot existed), and ive gotten mine replaced every time. I'll try and keep you posted.
Sent from my T-Mobile myTouch 3G using XDA App
The exact same thing happened to me but in my case, i bricked three phones and this is my forth one that i am using now. Pissed off one of the reps, he said i cleaned out their stock. Hhaha
Sent from my GBRider_v4.0FR using XDA App
Does this apply to the original my touch 3g? If so I would like something different than this phone. I am happy with it if not but if I can get a new phone because of the OTA update I am all for it.
A couple days ago my epic stopped being recognized by any computers. Tried multiple cables and all that. I used the rerfs stock ec05 to get back to stock before bringing it in to Sprint. They won't do anything to it cause of my extended battery, which sucks cause my stock battery sits by my window and got rained on causing the spot to turn red. They won't touch it now. I used z4roo to root, flashed the cheese gingerbread from asc somehow. Now I'm stuck. I can't flash cwm through rom manager cause it only sees device as I9000. I can't flash gps fix or anything cause it fails signature. How do I change how rom manager sees my device so I can flash cwm so I can fix everything?
Sent from my SPH-D700 using XDA App
Everything I have read says that rom manager does not work on the Epic so don't use it
Did you try a different pc? Im sorry if these are obvious answers but issues like this tend to be overlooked. Try a differerent pc. Redownload the drivers. Odin back to stock. These phones are actually hard to screw up software wise so if all else fails its a hardware problem. Some people like to use the standalone drivers, for some reason I like to install kies. Its workes guaranteed for me everytime.. and I use the stock usb cable. Im actually one of the very few people who like it lol
Sent from my SPH-D700 using XDA App
RushAOZ said:
Did you try a different pc? Im sorry if these are obvious answers but issues like this tend to be overlooked. Try a differerent pc. Redownload the drivers. Odin back to stock. These phones are actually hard to screw up software wise so if all else fails its a hardware problem. Some people like to use the standalone drivers, for some reason I like to install kies. Its workes guaranteed for me everytime.. and I use the stock usb cable. Im actually one of the very few people who like it lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Any suggestion is welcome. I tried 4 different cables on two computers. Phone isn't being read through usb on my car stereo anymore either.
Sent from my SPH-D700 using XDA App
power down and put it in download mode pressing 1 on keyboard and power button
connect to computer
if still not recognized and/or drivers do not load properly
uninstall old drivers and install them again or try different drivers
pdanet android has also worked for me successfully installing 'some' drivers
i would recommend the drivers straight from samsung website...they worked for me both on x86 and x64 windows 7 computers
if you can get into download mode (yellow triangle) and connect properly to pc
go ahead and odin eb13 or ec05 stock tar (ec05 if possible and doesn't hang on formatfs.rfs)
then update as usual to your desired rom using the relevant one-click cwm
if you had to go back to eb13...use one-click cwm2.5 first...then step up from there
Honestly, sounds like a bum port on the phone. I'd try calling Sprint rather than the store as I've had a LOT better luck dealing with them on the phone.
eigerzoom said:
power down and put it in download mode pressing 1 on keyboard and power button
connect to computer
if still not recognized and/or drivers do not load properly
uninstall old drivers and install them again or try different drivers
pdanet android has also worked for me successfully installing 'some' drivers
i would recommend the drivers straight from samsung website...they worked for me both on x86 and x64 windows 7 computers
if you can get into download mode (yellow triangle) and connect properly to pc
go ahead and odin eb13 or ec05 stock tar (ec05 if possible and doesn't hang on formatfs.rfs)
then update as usual to your desired rom using the relevant one-click cwm
if you had to go back to eb13...use one-click cwm2.5 first...then step up from there
Click to expand...
Click to collapse
Tried all that. I ended up taking my whole phone apart and seeing if there were bad connections. Everything looks good. I might just say I dropped my phone in lake pay my deductable and get a new one and use this for spare parts.
Sent from my SPH-D700 using XDA App
bjhill2112 said:
Honestly, sounds like a bum port on the phone.
Click to expand...
Click to collapse
Yea, that's what I'm starting to think :-(
If anyone has any other suggestions I'd Love to hear them. Thanks to everyone for their help so far.
Sent from my SPH-D700 using XDA App
BWFBezerk said:
A couple days ago my epic stopped being recognized by any computers. Tried multiple cables and all that. I used the rerfs stock ec05 to get back to stock before bringing it in to Sprint. They won't do anything to it cause of my extended battery, which sucks cause my stock battery sits by my window and got rained on causing the spot to turn red. They won't touch it now. I used z4roo to root, flashed the cheese gingerbread from asc somehow. Now I'm stuck. I can't flash cwm through rom manager cause it only sees device as I9000. I can't flash gps fix or anything cause it fails signature. How do I change how rom manager sees my device so I can flash cwm so I can fix everything?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Why not buy another stock battery or borrow one from a friend and take your phone to another sprint store?
BWFBezerk said:
A couple days ago my epic stopped being recognized by any computers. Tried multiple cables and all that. I used the rerfs stock ec05 to get back to stock before bringing it in to Sprint. They won't do anything to it cause of my extended battery, which sucks cause my stock battery sits by my window and got rained on causing the spot to turn red. They won't touch it now. I used z4roo to root, flashed the cheese gingerbread from asc somehow. Now I'm stuck. I can't flash cwm through rom manager cause it only sees device as I9000. I can't flash gps fix or anything cause it fails signature. How do I change how rom manager sees my device so I can flash cwm so I can fix everything?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
From sprint:
Code:
04/11/2011 02:20:10PM System: "Thank you for contacting Sprint. My name is Quinn J.."
04/11/2011 02:20:10PM ME: "Warranty question for Samsung Epic + Battery??"
04/11/2011 02:20:20PM ME: "hi quinn"
04/11/2011 02:20:23PM ME: "i had a question about warranty"
04/11/2011 02:20:27PM Agent (Quinn J.): "Hello."
04/11/2011 02:20:43PM ME: "bestbuy sells sprint phones"
04/11/2011 02:20:44PM ME: "they also sell this:"
04/11/2011 02:20:45PM ME: "<link removed silly xda>"
04/11/2011 02:20:51PM ME: "an extended battery for the phone"
04/11/2011 02:21:46PM ME: "does using a non-samsung battery void my warranty?"
04/11/2011 02:23:20PM Agent (Quinn J.): "No your warranty will not be void if you use non Samsung battery."
That should answer that, no?
They already marked on my ticket that I had water damage
Sent from my SPH-D700 using XDA App
BWFBezerk said:
They already marked on my ticket that I had water damage
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Water damage on a battery that wasn't in the phone? LOL. That sounds so shady haha. Effing sprint
CapoCriminali said:
Water damage on a battery that wasn't in the phone? LOL. That sounds so shady haha. Effing sprint
Click to expand...
Click to collapse
I put my stock one in when I went back to the store, I didn't even notice the sicker until they opened it. They wouldn't believe my story that I don't use it.
Sent from my SPH-D700 using XDA App
For some strange reason, my computer won't recognize my Epic if I plug the USB cable into my front ports. Just doesn't see them. But if I plug them into the ports on the back of my computer, totally sees it. I dunno why, but maybe that will help you as well.
Install the samsung usb driver offered on samsung.com reboot your pc (wndows 7 usually doesn't ned a reboot) also it is possible that the phone may only utilise usb 2.0, had the same trouble the other day and fixed it by installing the usb driver.
Sent from my SPH-D700 using XDA App
Anyone else notice you can access download mode with power volume up or down . I forget. I got there a couple times. I never had a lg phone since the ally years ago and only kept that a week since it sucked. But otherwise I have only used download mode for Samsung to use Odin. Does lg have an Odin like application for there mobile devices. Thanks in advance.
Sent from my Nexus 4 using xda premium
I noticed that too but really don't see the point since we have factory images and a virtually unbrickable bootloader unless I'm wrong here.
Yeah but if it is like Samsung it would be cool to have an app like mobile Odin to flash with. Just never saw that option on any other phone than a samsung
Sent from my Nexus 4 using xda premium
Bit of a bump but I got into this mode, but for the life of me I can't work out how to get out of it.
Okay, wasn't holding the button down for long enough.
Hope this helps
Hold volume - (volume down) while pressing and holding power. Holding both of these gets you to the boot loader (or fast boot as some call it). This is the Nexus version of ODIN. From this menu you can use volume up or down to toggle different options (check the mode at the top of screen). The power button works like an ENTER button. If you have permanently flashed a custom recovery, this is how you access recovery during a boot loop or other catastrophe.
In this mode you can use ADB (Google it if you don't know what this is) to send files, flash files, boot a .img file or recovery, or even reset it to stock. This is by far way better than any other 3rd party method that I have encountered. It's what makes a nexus a nexus. However it is a little bit of a pain to get the Android SDK set up and running for some people.
I recommend every body that has this device to familiarize your self with what I am talking about.
If any of you need my help feel free to drop me a PM. Stay frosty!
parker09 said:
Bit of a bump but I got into this mode, but for the life of me I can't work out how to get out of it.
Okay, wasn't holding the button down for long enough.
Click to expand...
Click to collapse
How did you get into it? Or did you just get into the bootloader?
jasonpantuliano said:
Yeah but if it is like Samsung it would be cool to have an app like mobile Odin to flash with. Just never saw that option on any other phone than a samsung
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
odin was hellish. thank goodness its gone. fastboot is so, so much better and safer. fully documented aswell. in the s2 forum, that was my first cellphone, odin smashed countless of devices, and i mean smashed em dead. rooting my s2 after having paid such a sum of money made my heart beat like crazy. unlocking nexus via fastboot/adb, pfff, dont even care, i just know it'll work.
molesarecoming said:
odin was hellish. thank goodness its gone. fastboot is so, so much better and safer. fully documented aswell. in the s2 forum, that was my first cellphone, odin smashed countless of devices, and i mean smashed em dead. rooting my s2 after having paid such a sum of money made my heart beat like crazy. unlocking nexus via fastboot/adb, pfff, dont even care, i just know it'll work.
Click to expand...
Click to collapse
Seriously, and the number of bricks I saw from people hitting the wrong stuff in Odin was nothing short of amazing.
Sent from my Nexus 4 using Tapatalk 2
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
PiCASSiMO said:
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
Click to expand...
Click to collapse
Nope
Not stock
Need custom ROM AFAIK
Sent from my A510 using Tapatalk HD
PiCASSiMO said:
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
Click to expand...
Click to collapse
Doubt Google would add that in. Have to flash a custom ROM.
Custom ROM is the only way. If you want we can guide you through the process of flashing one if you like to. Don't use a toolkit is the first step. Take the time and learn it as it takes < 30 minutes to learn and it will be a basic "get me out of this hole!" method when your phone is somehow ever in a non bootable state and you won't mistaken yourself for bricking your phone when its not
http://forum.xda-developers.com/showthread.php?t=1972508 is a good guide to get started on for unlocking your bootloader which is the first step.
Don't know why everyone is so against toolkits. I have used them on my galaxy nexus. Sgs3 and now my nexus4 numerous times and haven't had a single issue. Ever.
The toolkits runs the same commands that you would if you were to do it in fast boot and cmd.
Sent from my A510 using Tapatalk HD
c_86 said:
Don't know why everyone is so against toolkits. I have used them on my galaxy nexus. Sgs3 and now my nexus4 numerous times and haven't had a single issue. Ever.
The toolkits runs the same commands that you would if you were to do it in fast boot and cmd.
Sent from my A510 using Tapatalk HD
Click to expand...
Click to collapse
I am personally against toolkits because people are using it without knowing what they're doing and not knowing how to do basic things such as fastboot and adb. Then they come to using recoveries not knowing what happened and end up messing their phones up.
Yes it runs the SAME commands, but you aren't doing it yourself.
It's like what I said in other threads,
Let's say you wanted to go from Home (point A) to school (point B). You can do it in two ways,
1) Do it manually and learn the steps on how to go from Point A to B.
2) Use a toolkit that will get you to Point A to B, not knowing HOW you got to Point B.
I'm not saying this to get people to become smart or learn some stupid commands that they will never use. Chances are, every user flashing things on XDA should know these basic commands (not even know because you can just look it up).
If you used Method 2, what happens if theres a road closure? What do you do there?! you used a toolkit, you are stuck and you resort to asking questions on how to get back to Point A to reroute yourself to Point B.
If you used Method 1, you are able to backtrack yourself to fix problems leading to a better community which will result in less questions on how to return back to stock for warranty purposes, RMA purposes, flashing something and their phone isn't booting up but THEY CAN boot into bootloader mode (if they used toolkit, they dont know how to flash back to stock or flash a new recovery). Things like that. After all, this is a DEVELOPER forum not a tech support forum, am I not right about this?
Both method 1 & 2 brings you to Point B. But method 1 is more important as eventually, people using toolkits will need to use fastboot and adb sometime. Maybe not today, but sometime in their lifetime they will have to use it and will have to learn. So why not spend the 15-20 minutes and learn it now? Not be spoon fed. I used the G1, I had to work my butt to obtain root via 30-35 minute of using ADB shell and terminal emulator.
Yes method 1 takes longer (not that much longer) but in the end it'll pay off and is worth spending that 15-20 minute reading it, it's a step-by-step process and doesn't take a rocket scientist to know how to do it. It looks difficult at the start (it really doesn't, just follow the steps in the guide as it goes) but after that it looks like a walk in a park and is just as easy as using a toolkit.