[Verizon] unlocked my phone but fastboot flash recovery failed

[opeets]

I unlocked my Gnex using these instructions. The fastboot flash recovery step failed so I gave up after hours of getting nowhere and restarted my phone. When it rebooted a few minutes later it was as if I had just got the phone (which is by the way, what I really wanted...a clean slate).

1) Did I do a bad thing by unlocking and not doing some important step after (when I threw in the towel)?

2) What specifically did unlocking the phone accomplish for me? I'm a noob. At the very least my Morningstar app works again!

3) Should I still try to root it? What specifically would that allow me to do? Again, I'm a noob.

 

[iowabowtech]

Those instructions aren't very specific on how to fasboot flash files. You might check the how to root sticky here in these forums for some better instructs. Without knowing your knowledge level when it comes to adb/fastboot, I'd first mention that you need to have the recovery img placed in the platform-tools folder of the sdk (same folder that houses the adb/fastboot utilities). Did you do that and it still didn't work? If so, review the file and make sure it checks out size wise and that you aren't trying to push a zip file but rather just the img file alone.

If all that checks out, please post your cmd session so we can see the input/output which may give us some clues.

Also, those instructs are for a vzw gnex. Just wanted to be sure that's the right phone so that:

a.) we get the right files flashed
b.) we get this thread moved to the correct gnex root subforum where you can get the most help.

 

[opeets]

Those instructions aren't very specific on how to fasboot flash files.

They seemed pretty specific (even though they weren't). I even tried using this wiki which still wasn't perfectly accurate. In order to get around the "Waiting for Device" issue I had to run adb reboot bootloader first, which then allowed the SAMSUNG phone driver to appear in Device Manager (Windows 7 64-bit). Once it appeared in Device Manager, I was able to update the driver. After I did that I ran the fastboot oem unlock command and my phone warned me about unlocking the phone. Once I accepted the warning the phone was unlocked. After that I tried the fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img command (from the pcworld tutorial) and got an error message (it was so late last night that I didn't bother writing it down). I even tried the fastboot flash recover recovery-clockwork-touch-5.8.0.2-toro.img command (from the rootwiki tutuorial) and that also didn't work. I believe it was the same error message. I even tried moving the .img files into the platform-tools directory of my Android SDK folder and that did not work.

You might check the how to root sticky here in these forums for some better instructs.

I'm an idiot...how do I access it?

Without knowing your knowledge level when it comes to adb/fastboot, I'd first mention that you need to have the recovery img placed in the platform-tools folder of the sdk (same folder that houses the adb/fastboot utilities). Did you do that and it still didn't work?

See above.

If so, review the file and make sure it checks out size wise and that you aren't trying to push a zip file but rather just the img file alone.

If the file name was .img, could it possibly be zipped?

If all that checks out, please post your cmd session so we can see the input/output which may give us some clues.

How do I go about creating a text file of my cmd session?

Also, those instructs are for a vzw gnex. Just wanted to be sure that's the right phone so that:

a.) we get the right files flashed
b.) we get this thread moved to the correct gnex root subforum where you can get the most help.

Yes, Gnex for VZW. Where should I have posted this thread and how do I move it there?

Thanks for all the help. Very much appreciated.

 

[opeets]

One other question...what if I do absolutely nothing at this point? Are there any consequences of just unlocking the phone (other than wiping all of my apps/data)? My Gnex is running very smoothly now. I reinstalled all of my apps and restore my Google contacts. I even got my Morningstar app to launch which was why I started my journey down this path.

 

[trophynuts]

Moving thread to VZW All Things Root section.
Reason: Thread is specific to VZW Root methods
Thanks for understanding

 

[trophynuts]

i have pm'ed the OP with the new link

 

[opeets]

i have pm'ed the OP with the new link

Thanks.

 

[VoidedSaint]

They seemed pretty specific (even though they weren't). I even tried using this wiki which still wasn't perfectly accurate. In order to get around the "Waiting for Device" issue I had to run adb reboot bootloader first, which then allowed the SAMSUNG phone driver to appear in Device Manager (Windows 7 64-bit). Once it appeared in Device Manager, I was able to update the driver. After I did that I ran the fastboot oem unlock command and my phone warned me about unlocking the phone. Once I accepted the warning the phone was unlocked. After that I tried the fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img command (from the pcworld tutorial) and got an error message (it was so late last night that I didn't bother writing it down). I even tried the fastboot flash recover recovery-clockwork-touch-5.8.0.2-toro.img command (from the rootwiki tutuorial) and that also didn't work. I believe it was the same error message. I even tried moving the .img files into the platform-tools directory of my Android SDK folder and that did not work.


I'm an idiot...how do I access it?
There are no idiots here
See above.
The android sdk is the program you use to get adb installed on your computer, with adb you can proceed to learn more about your device

If the file name was .img, could it possibly be zipped?
no, sometimes .img files are contained within the zip

How do I go about creating a text file of my cmd session?
Copy and paste your cmd session, in the command session it gives you the option to do this


Yes, Gnex for VZW. Where should I have posted this thread and how do I move it there?
Already taken care of
Thanks for all the help. Very much appreciated.

One other question...what if I do absolutely nothing at this point? Are there any consequences of just unlocking the phone (other than wiping all of my apps/data)? My Gnex is running very smoothly now. I reinstalled all of my apps and restore my Google contacts. I even got my Morningstar app to launch which was why I started my journey down this path.

If you want to remain unlocked that is your choice, no one else's but yours, what steps did you take? do you have CWR(ClockWork Recovery) installed on your device? if so you can never accept updates.
in the even that you need to return your device, you have to return it in a locked state, no question about it. its very easy to return that to the locked state.

here is the link to the all things root guide, there it has all types of useful information, read up on it, dont understand something? pm either myself, scary alien, or any other guide/mod, we are always glad to help.

http://androidforums.com/verizon-ga...gs-root-samsung-galaxy-nexus.html#post3736589

 

[opeets]

Can anyone explain to me what "technically" happened in the process of unlocking my phone? All of my apps/data were wiped out. This is exactly what I intended (I didn't really intend to root my phone) but I didn't actually expect that to happen by simply unlocking the phone.

What really happened behind the screen?

 

[iowabowtech]

Can anyone explain to me what "technically" happened in the process of unlocking my phone? All of my apps/data were wiped out. This is exactly what I intended (I didn't really intend to root my phone) but I didn't actually expect that to happen by simply unlocking the phone.

What really happened behind the screen?

It factory resets the phone when unlocking (including anything on the /sdcard you may have noticed). So anyway, it's up to you on whether or not to proceed but you could have obtained the same results by doing a factory reset from the phone's settings menu. That said, I wouldn't relock the bootloader unless you were SURE you were never going to root in the future because if you relock, then decide to unlock again in the future, you're going through the full reset including wiping sdcard contents again (althouth the sd contents can be copied/stored in advance to avoid loss).

So, let us know. We'll be happy to help you through the fastboot flashing issue. It's probably something minor holding you up. The first question I'd ask is what usb cable were you using at the time? The one that came with the phone or a random one?

 

[opeets]

It factory resets the phone when unlocking

So its programmed to reset the phone (as it appeared on day 1) when someone unlocks it? If so, how does it accomplish this? Is there an image stored somewhere that overwrites everything?

(including anything on the /sdcard you may have noticed).

What gets stored in the /sdcard directory? I never placed any files there anyway. Besides the Gnex doesn't have an sdcard does it? I thought it was all internal memory.

So anyway, it's up to you on whether or not to proceed but you could have obtained the same results by doing a factory reset from the phone's settings menu.

So the menu setting really would have accomplished the same thing? I thought that doing it through the phone's menu only removed the apps and data. I was looking for a clean slate...kind of like reformatting a hard drive in a PC and reinstalling the OS.

That said, I wouldn't relock the bootloader unless you were SURE you were never going to root in the future because if you relock, then decide to unlock again in the future, you're going through the full reset including wiping sdcard contents again (althouth the sd contents can be copied/stored in advance to avoid loss).

If there's no reason for me to re-lock, then I won't. But if I ever need a clean slate again, I should just use the phone's menu setting to reset, right?

So, let us know. We'll be happy to help you through the fastboot flashing issue. It's probably something minor holding you up.

Okay, what's my first step?

The first question I'd ask is what usb cable were you using at the time? The one that came with the phone or a random one?

Not sure since I have so many...could be a random cable, why do you ask?

Thanks again for your patience.

 

[VoidedSaint]

do you know how to delete files off of your computer completely?
by holding shift delete, its deletes it permanently.
unlocking the phone pretty much does the same thing. and no there is no factory image that is replaced. it is just removing every bit of information in the memory banks.

you cannot install a rom, then relock the phone and it go back to stock experience, it will soft brick the device, and you will need to flash the stock image back over top of it to fix it

 

[iowabowtech]

So its programmed to reset the phone (as it appeared on day 1) when someone unlocks it? If so, how does it accomplish this? Is there an image stored somewhere that overwrites everything?

Good question. Not gonna lie, I don't fully understand the mechanics of it.

What gets stored in the /sdcard directory? I never placed any files there anyway. Besides the Gnex doesn't have an sdcard does it? I thought it was all internal memory.

Pics and music come to mind. Downloads and other files you may have obtained since owning the phone. It has a "virtual" sdcard. The location is actually /data/media but that directory is viewed by the phone as "sdcard" for all intents and purposes.

So the menu setting really would have accomplished the same thing? I thought that doing it through the phone's menu only removed the apps and data. I was looking for a clean slate...kind of like reformatting a hard drive in a PC and reinstalling the OS.

Should do the same thing. There may be some remnants here and there however. Some people have noted their phone doesn't quite appear to be exactly like new in the box. I've always thought it might be the feature to backup settings to Google servers that could cause this but not sure.

If there's no reason for me to re-lock, then I won't. But if I ever need a clean slate again, I should just use the phone's menu setting to reset, right?

I would. Unless you decide to root, then don't use the factory reset option in the phone's settings menu. All wiping is done in a custom recovery for rooted users.

Okay, what's my first step?

Some people have had issues transferring data with certain cables. When unlocking this was not an issue but now you're trying to move a file to the phone (recovery) so there's data transfer involved. If multiple cables fail, I'd like to see the results of the cmd session as mentioned.

Not sure since I have so many...could be a random cable, why do you ask?

See above.

.

 

[scary alien]

opeets,

Looks like you're in excellent hands with the above guys.

Just thought I'd chime-in real quick here:

1. Unlocking the bootloader undoubtedly causes the /data (and probably the /cache) partition to be reformatted (i.e., resulting in your files and apps going bye-bye). I did notice when I did this and rebooted (after also having done a full return to stock) that Google and the Market automatically re-downloaded my apps, which made me think that these were not wiped-out from the unlocking operation.

2. The really good news is that since you've successfully done the unlock operation, that you do indeed have fastboot USB access to your phone. That really means that the rest of rooting should be cake, assuming you can get a fastboot devices to report that it sees your phone again (after you've put it back in to fastboot/bootloader mode).

3. If I were new to the rooting scene and I were you, I would not flash the custom recovery (ClockworkMod, etc.) but would softboot it instead so that you can simply get the root binaries (su and Superuser.apk) installed. The would leave you with a stock recovery which will ensure that you'll be able to receive and installed the upcoming JellyBean OTA update (although since we're VZW, that might be a while, eh?).

4. Once you are rooted, you'll be able to flash a custom recovery outside of using fastboot. This can be accomplished via ROM Manager or via my app, Android Root Toolkit (which will also allow you to easily re-flash the stock recovery if desired).

Read. Ask questions. We'll all be here.



Cheers!

 

[opeets]

Okay, so tonight do I try the fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img command or something else as my first step?

Wait, before I do that....what specifically is the .img file? i.e. what does it contain, and what is the consequence of executing this command?

Prior to executing the command I assume I should enter fastboot mode (both vol buttons and power on the phone) and connect to USB cable.

Or am I going about this all wrong?

Gosh, I wish there was one GOLDEN video tutorial showing how to do all of this. There are just so many tutorials out there I don't know which to use. Each claims to be the simplest method, yet the two that I've tried were not straightforward.

 

[iowabowtech]

Okay, so tonight do I try the fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img command or something else as my first step?

Wait, before I do that....what specifically is the .img file? i.e. what does it contain, and what is the consequence of executing this command?

Prior to executing the command I assume I should enter fastboot mode (both vol buttons and power on the phone) and connect to USB cable.

Or am I going about this all wrong?

Gosh, I wish there was one GOLDEN video tutorial showing how to do all of this. There are just so many tutorials out there I don't know which to use. Each claims to be the simplest method, yet the two that I've tried were not straightforward.

Go here:
http://androidforums.com/verizon-ga...49-how-root-vzw-lte-samsung-galaxy-nexus.html

Scroll down to the "Clockworkmod method", click the show button to reveal the full blown instructs. As you read through that, note the soft boot instructs...this is what Scary Alien was referring to. See how the fastboot command is changed from fastboot flash... to fastboot boot...

Using the fastboot boot command will allow you to flash the su/superuser using Clockwork but then when you reboot, the stock recovery will replace clockwork recovery, thereby allowing you to be rooted, with the stock recovery. Those conditions will allow you to receive the official over the air update when it comes as Scary mentioned.

This would allow you to get into rooting without going full fledged into custom roms. So it's kind of a nice middle ground for folks who want to ease into things one step at a time.

 

[opeets]

I knew something was going to go wrong. First I copied the original su.zip file into the sdk-tools directory and that didn't work (using both commands in the tutorial) and then I tried the other su.zip file because I believe I had 4.0.4 installed. Also did not work. Now my phone is in CWM screen "Apply update from .zip file on SD Card" and I am afraid to disconnect it in this mode. Please help ASAP. Below is the command session:


C:\Program Files\Android SDK\platform-tools>fastboot boot recovery-clockwork-5.5
.0.4-toro.img
downloading 'boot.img'...
OKAY [ 0.498s]
booting...
OKAY [ 0.323s]
finished. total time: 0.823s

C:\Program Files\Android SDK\platform-tools>adb push su.zip /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

C:\Program Files\Android SDK\platform-tools>adb push su.zip /data/media/su.zip
error: device not found

(THEN I COPIED THE OTHER SU.ZIP FILE INTO THE platform-tools DIRECTORY AND REPEATED THE COMMANDS BELOW)

C:\Program Files\Android SDK\platform-tools>adb push su.zip /sdcard/
error: device not found

C:\Program Files\Android SDK\platform-tools>adb push su.zip /data/media/su.zip
error: device not found

C:\Program Files\Android SDK\platform-tools>


When I went into Control Panel under Other Devices, there was one listed called "Full" with a yellow exclamation mark. I've never had that happen before. Is this expected?

 

[opeets]

FYI...I just tried to send a PM to "scary alien" and "VoidedSaint" to see if they could give me a quick response but it told me that those are not valid user names.

 

[scary alien]

FYI...I just tried to send a PM to "scary alien" and "VoidedSaint" to see if they could give me a quick response but it told me that those are not valid user names.

opeets,

I'm here, but didn't get a PM (and I think I'm a valid user ).

It looks like you don't have the USB adb drivers installed...

Don't worry, though, here's what you can do:

1. Go ahead and reboot your phone--you didn't install anything since you soft-booted ClockworkMod

2. After you boot back up, download this file su.zip [which should be the latest version] (you can use your phone or your PC, but make sure its in the top-level of the /sdcard directory)

3. After you have the su.zip file in your /sdcard folder, go ahead and reboot back to fastboot/bootlader mode and soft-boot ClockworkMod again just like you did before

4. Now, when you invoke "install zip from sdcard" on the CWM menu and then "choose zip from sdcard", you should see the su.zip file in the list of files presented to you

5. Select and flash the su.zip file

6. Reboot and you should then have root

 

[iowabowtech]

^^+1.

If you don't see the option to reboot in the CWM menu, scroll down to "go back", then choose the reboot system option and it'll reboot the phone. You're in great shape still. Just a minor roadblock easily overcome.

 

[opeets]

Um, was just about to copy su.zip to my phone when I realized THERE IS NO sdcard directory on the phone!

 

[opeets]

See screen capture of my file system....DO I JUST CREATE A NEW sdcard DIR?

 

[scary alien]

Um, was just about to copy su.zip to my phone when I realized THERE IS NO sdcard directory on the phone!

Are you looking for it from connecting to it via your PC?

If so, its just the Computer\Galaxy Nexus\Internal Storage area from Windows Explorer.

Should be able to drag and drop or copy/paste it right in there.

Does that make sense?

edit: didn't see that you had already re-posted...you are good--that's the area you want to paste the su.zip file in (not inside any of those folders, but at the same level).

 

[opeets]

opeets,

I'm here, but didn't get a PM (and I think I'm a valid user ).

It looks like you don't have the USB adb drivers installed...

Don't worry, though, here's what you can do:

1. Go ahead and reboot your phone--you didn't install anything since you soft-booted ClockworkMod

2. After you boot back up, download this file su.zip [which should be the latest version] (you can use your phone or your PC, but make sure its in the top-level of the /sdcard directory)

3. After you have the su.zip file in your /sdcard folder, go ahead and reboot back to fastboot/bootlader mode and soft-boot ClockworkMod again just like you did before

4. Now, when you invoke "install zip from sdcard" on the CWM menu and then "choose zip from sdcard", you should see the su.zip file in the list of files presented to you

5. Select and flash the su.zip file

6. Reboot and you should then have root

I went ahead and created the sdcard directory, copied the su.zip and was able to apply it successfully (or so it said).

How do I know if it is rooted? I think I might be getting somewhere...

 

[opeets]

that's the area you want to paste the su.zip file in (not inside any of those folders, but at the same level).

So I was already in the sdcard directory and didn't know it? In that case I just created an sdcard subdir within the sdcard dir and that is where I copied su.zip. But it seemed to work. Should I delete the su.zip now and the sdcard subdir I made or do I need them?