Dust off the old adb commands

[Snow02]

I am not against one-clicks in fact I first got into it thanks to a simplified form in sholesmod. With that said it would be better in the long run for people to atleast know what the script is doing and know about adb. This will help people understand what is happening and take their time before rushing into anything. Please keep it civil the thread is meant to share knowledge.

Definitely agreed. And we're all having fun here I think.

[pc747]

100% agree with you. Knowing what is happening to your device even if you are running a script is a good thing to have knowledge of. I personally won't use one unless I write it myself for the simple fact that I don't like letting the computer "do its thing". That might sound snooty or elitist or whatnot, but it's just the fact that sometimes software loses its mind or another process interrupts a line of code or a call to something and things can go downhill quickly, and I would rather not take that chance with a phone.

The devs that code scripts do a good job. With that said, scripts do fail and I dont know how many times people have panicked because of it and they dont know what to do.

[coverton341]

Again, correlation is not tantamount to causation. Plus you make a couple of really hard to quantify assumptions. You just had stats? You should know better.

But let's look at it, from a pure numbers standpoint, if you will . Android sales were ~5.5 million units in Q1 2010. Last quarter? 60.5 million. I'd say there's probably a stronger correlation with the increase in overall users.

Round and round we go.

Very true, but you are also working with one glaringly incorrect assumption; One-Clicks did not come out last quarter. In fact they came relatively shortly after the adb method because they were just scripts. Anyway, we're both using a few logical fallacies, so I sit corrected. I still stand by the fact that One-Clicks opened up the ability to root to more people (which I think is a good thing) and therefore led to more looping devices that needed rescue services.

And yes, I am very much having fun. I enjoy engaging in intellectual conversation, something that is oh so woefully absent on these here internets for the most part (not really point at the community of these forums)

[Snow02]

Very true, but you are also working with one glaringly incorrect assumption; One-Clicks did not come out last quarter. In fact they came relatively shortly after the adb method because they were just scripts. Anyway, we're both using a few logical fallacies, so I sit corrected. I still stand by the fact that One-Clicks opened up the ability to root to more people (which I think is a good thing) and therefore led to more looping devices that needed rescue services.

And yes, I am very much having fun. I enjoy engaging in intellectual conversation, something that is oh so woefully absent on these here internets for the most part (not really point at the community of these forums)

Ok, then let's put it another way. Would you agree that an 800+% uptick in "my phone won't boot" threads over the past year or so sounds accurate?

[toddrhodes]

First off I just want to say thank you for posting these instructions. I have a GN reserved at the local VZW store and thanks to this thread I'll have an unlocked bootloader tomorrow evening without much trouble.

I rooted my D2 the "old fashioned way" and I think that helps in a sense to realize the gravity of what you're doing with the phone. After you go through that process it is no longer just a little old phone, it's yours, if that makes any sense. I could have one-clicked it but I wanted to know the process in more depth because that fosters a deeper understanding of what you're doing. Since I also make a hobby of modifying cars, I would relate it to someone building their own racecar vs taking it to a shop, ordering from a menu and getting the end result without actually doing anything other than coming up with the money to pay for what you wind up with. For me, I took great satisfaction from the fact that I was able to root it myself and didn't need someone else to write a script to have what I ended up with. Yes, I followed a tutorial but just like tonight, it's not just following a recipe like you're making a chocolate cake, you still have to figure things out on your own and put it all together to make it work in the end.

I'm rambling but I guess my point is that I like to see that I accomplished something without having someone else do every bit of the work for me. Yea, I didn't write the instructions and I wouldn't have been able to do what I did without your help, but is that really as easy as ordering up an app from the market? Not really.

Anyway, thanks again for the post, it was immensely helpful and hopefully tomorrow I can check back on this thread from my VZW GN

[martytoo]

Since the following two quotes from the OP seem to disagree, I would like to know if the phone is rooted after these procedures. Can it run Titanium Backup and/or Wireless Tether?

-Can I still receive OTA updates after unlocking the bootloader?

-Answer: Yes. Your phone really does not change at all when you unlock the bootloader. You will still receive updates from Google. Now, if you start putting on custom recoveries and rooting, you may run into issues with receiving OTA updates. The good news is that Google usually releases the system image files for their Nexus phones which makes it a breeze to go back to stock for updates.


5. Once it is done, you have just reflashed the recovery image and it will now stick. You are all done! You have an unlocked bootloader, a custom recovery image, and root access!