• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] adb not working, but my connection is good?

B

bluroot

Newbie
I actually used ths guide once before to root my phone (and I don't know if a new user is allowed to post links, so I'm hoping the stars will un-link Jubakuba's Ultimate Guide over on the xda-developer site):

***http://forum.xda-developers.com/showthread.php?t=1529058***

Whatever it was I used to get myself rooted, THAT part was good. Then there was a bad rom flashing experience, the Google Framework was gone, and then the best advice I got was to follow Scary_Alien's tutroial to get my phone back to stock. Done, and I later noticed that no Gapps package is recommended for JB 4.1.1, which is where I am now with my stock phone on Verizon, maybe that was why? Anyway, I just want to get my root back so that I can at least run Titanium Backup. With a decent backup system, it won't be so bad if I have 1000+ apps on my phone after reading up and watching what happens to others with any given rom I may try!

So I am running commands in platform-tools, which has adb, fastboot, and any other files which I would use with the above. I have run fastboot to get this phone back to stock (to recover google framework), so that tested good. Just now I ran the command "fastboot devices", got a string of characters for output, guess that looks good (whatever they may mean). Now I need to run adb on a zip file which is sitting on my phone root, per Jubakuba's directions. This is what's failing, and it isn't the first copy of adb which I've tried - anyway, the error is "unable to load <filename> ". Why this, and can it be fixed?

I have to say (and I don't mean to complain, so please don't get me wrong) that I found so much worry about driver installation and adb woes to be a bit of a distraction, and I just wonder why rooting must be done through adb. I wonder this because I didn't need it when I rooted my Droid Incredible (HTC). There was a zip file to download and place on your phone root, but then you renamed it to something which told the fastboot system on your phone to load it when you start your phone in fastboot. I wonder why nobody seems to be doing that on their GN. Fastboot does look different on this phone, and I've no idea what Odin is about, but is it at all possible to make fastboot on your phone boot whatever trick file you give it?
 
Rooting doesn't need to be done through adb unless you're softbricked. All that needs to be done is unlock the bootloader, fastboot boot/flash a custom recovery, load that recovery, and then flash a compatible su.zip. This depends on your device already having the su.zip in the root of your sd before you do all this, but other than that it's pretty straight forward.
 
^^+1 to the above advice. My preferred way to root this phone is to fastboot flash a custom recovery and then use it to apply the su.zip for root. You CAN push the su.zip file via adb but with a perfectly booting phone, its easiest to just move it onto the phone via usb cable or Air droid (or similar), or email it to yourself etc. All kinds of ways to get it there.

On the topic of adb, you can run it 2 ways. One is on a fully booted phone and with USB debugging on. The other is from inside a custom recovery (handy for soft brick scenario as mentioned). If its not working under either of those instances, you either have a driver issue or you need to update your adb package.
 
Although some of the tools are the same, the process to root an Android phone varies from phone to phone and even from model to model.

The guide you linked should work fine to root your phone. The guide that is a sticky up in this section should work fine. And there are some 'toolkits' that can be used; but as you hinted at, the hardest part is getting the right drivers. Are you having a driver problem?

p.s. another way to restore your apps is through the Play Store itself. Open it, then touch the three dots and select "My Apps" and try that.
 
dete
jhawkkw said:
Rooting doesn't need to be done through adb unless you're softbricked. All that needs to be done is unlock the bootloader, fastboot boot/flash a custom recovery, load that recovery, and then flash a compatible su.zip. This depends on your device already having the su.zip in the root of your sd before you do all this, but other than that it's pretty straight forward.
Click to expand...
I'm afraid that I have been slightly confused over what is what. My phone is back to stock software with jelly bean 4.1.1, and it still displays the CWM interface when I select recovery when it's in fastboot mode. It also reads "unlocked" in fastboot mode. But Titanium says I don't have root access, so guess I don't have that. Will the above complicate the process of regaining root access?

When I followed posted directions to root my Droid Incredible, I put a file on my phone root, shut it down, and then I put it in fastboot. Other than a prompt for my authorization, fastboot automatically booted that file and did what it said, and I believe this behavior was caused by the file name, which I had changed per directions. I dont remember the exact file name, but if this can be repeated on the GN, what would be the file name?
 
bluroot said:
dete
I'm afraid that I have been slightly confused over what is what. My phone is back to stock software with jelly bean 4.1.1, and it still displays the CWM interface when I select recovery when it's in fastboot mode. It also reads "unlocked" in fastboot mode. But Titanium says I don't have root access, so guess I don't have that. Will the above complicate the process of regaining root access?

When I followed posted directions to root my Droid Incredible, I put a file on my phone root, shut it down, and then I put it in fastboot. Other than a prompt for my authorization, fastboot automatically booted that file and did what it said, and I believe this behavior was caused by the file name, which I had changed per directions. I dont remember the exact file name, but if this can be repeated on the GN, what would be the file name?
Click to expand...

You are talking about an altogether different animal there. When you loaded the file on your Inc, you were using the bootloader, not fastboot. HTC bootloaders (called hboot) can auto load files from the sdcard if they are named with a specific string of characters that is unique to that phone model. So for the Inc it was PB31IMG.zip. What you can do then, is auto flash certain files by powering down, then going into hboot. It's a proprietary feature to HTC phones and it's their way of being able to recover from certain sticky situations. And yes, it can be handy which is why many well versed rooters like HTC/hboot...because it's a bit more flexible on it's options than other bootloaders.

With all that said, nexus phones are even more flexible. All you need to do in order to root is fastboot flash a custom recovery and then flash the su.zip from the menu options of that recovery (clockwork, twrp, etc). So you get the su.zip file onto your sdcard, then go into recovery, then choose options to install zip from sdcard, choose zip from sdcard, and flash it. Boom, you have root upon reboot. It's easier imo. Hope that explains it all. If you'd like instructs, check here:

http://androidforums.com/3736596-post6.html

Note that is mentions using adb push to get the su.zip to the card. Once again, you don't NEED to do that if you don't want. Hook the phone up to a pc via usb cable and drag and drop the file onto the card if you prefer, then enter recovery and flash it. You'll see the necessary su.zip for 4.1.1 is linked there also.
 
I got the root power back, and was amazed how easy it was! For being "back to stock" I was surprised to find that I still had CWM, and it worked on my superuser file without any modifications needed. For now, I think Jelly Bean with the root is good enough. Thanks all who helped me through the mess that I started in!
 
Glad to see you have got it figured out. As iowabowtech pointed out (and I will paraphrase), what works for one phone does not work for another. Whatever you did for your Inc, just forget. You have a different phone now and different rules and methods apply.

good luck
 
You must log in or register to reply here.
Back
Top Bottom