yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] silow:
This is the error message you receive when fastboot cannot find the file as you typed it. Do a dir on that directory and post it here.
[Samsung Galaxy Nexus] open1your1eyes0:
Ok so major failure to check something on my part on my part guys. Apparently you cannot use fastboot to boot a recovery image with a command. You must flash recovery first, then boot to recovery by selecting it from the options. I have updated the OP with these changes. I do apologize for the inconvenience.
[Samsung Galaxy Nexus] CannotResist:
Here is what I have on my screen. You can see that the file is in the same folder as fastboot. you can also see what I am typing, and what the result is. Any ideas?
[Samsung Galaxy Nexus] open1your1eyes0:
I have changed the instructions, see OP.
[Samsung Galaxy Nexus] CannotResist:
I saw that you changed it, but it still isn't working when I try step 5. I'm not rooted yet, so if I understand the OP correctly, I have to temporarily flash CWM and then go into recovery. It fails when I give that command, so if I try to go into recovery from the bootloader, it gives me the android with the red triangle.
[Samsung Galaxy Nexus] bangdrum:
That file is not there for me either. Not sure if you saw my last post.
[Samsung Galaxy Nexus] open1your1eyes0:
When you issue the command "fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img" what is the error it gives. Please post a screenshot.

Well to be honest, I really can't explain it being there unless it was taken out before or you have some kind of modified build. By idea, if the file is not then then if you reboot into recovery each time you will see Clockworkmod (after you flashed it of course) and not the stock recovery.
[Samsung Galaxy Nexus] CannotResist:
Last login: Thu Dec 22 14:14:44 on ttys000

Sean-Manleys-MacBook-Pro:~ sdosiris29$ ~/desktop/adb-fastboot/fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

error: cannot load 'recovery-clockwork-5.5.0.4-toro.img'
[Samsung Galaxy Nexus] open1your1eyes0:
Try these two commands:

First: cd ~/desktop/adb-fastboot

then hit enter

Second: fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

then hit enter again
[Samsung Galaxy Nexus] CannotResist:
Sean-Manleys-MacBook-Pro:~ sdosiris29$ cd ~/desktop/adb-fastboot

Sean-Manleys-MacBook-Pro:adb-fastboot sdosiris29$ fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

-bash: fastboot: command not found
[Samsung Galaxy Nexus] open1your1eyes0:
Ok it appears something is wrong with your paths there. Therefore it is not finding the recovery file.

Enter the command "ld" and screenshot what it outputs.
[Samsung Galaxy Nexus] CannotResist:
I actually got a link from a friend of mine for rooting the nexus s 4g, and followed it, and it looks like it wanted the path twice. This is what I entered in there and you see the result.

Sean-Manleys-MacBook-Pro:adb-fastboot sdosiris29$ ~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

sending 'recovery' (152 KB)... OKAY

writing 'recovery'... OKAY

sending 'recovery' (5140 KB)... OKAY

writing 'recovery'... OKAY

Going to move on to the next steps. Thanks for the ideas, I think we are in the home stretch.
[Samsung Galaxy Nexus] open1your1eyes0:
You are right...pardon my terminal skills are a little rusty...haven't worked with UNIX in a while.
[Samsung Galaxy Nexus] fdm1:
Fastboot on Mac works just fine. I did all of the instructions with no problem on a Mac (with the exception that one of the steps had the word "recovery" in it one too many times. I think you just need to type "./" or something like that in front of every command. If that's not it, just search the forums for it and you'll find out how.
[Samsung Galaxy Nexus] bryandamon:
No SD card

Sorry noob question here:

My Verizon Galaxy Nexus is stuck in an infinite boot loop so I can't use apps to load files to my the phones memory. I am trying to load the ICS factory images from:

(blocking my link but I'm getting my files from code.google)

Since the phone doesn't have a SD card, how do I get the .tgz file on my phone? I've read in the posts to use ADB push but hoping there is an easier way? I'm researching ODIN right now but hoping someone can help me out.

Cheers

---------- Post added at 08:59 PM ---------- Previous post was at 08:10 PM ----------

If anyone has a similar problem this link helped me

droidmodderx<dot>com/galaxynexus/unbrick-unroot-unlock-restore-your-galaxy-nexus-to-factory

(sorry, would't let me post a full url)
[Samsung Galaxy Nexus] bangdrum:
Yes that's the problem. I was on the complete stock rom rooted. Adb pushed recovery the first time and it got me into cwm. After I booted I rebooted in recovery to find the red! Searched here and rootz for an answer. Looked for the file but she wasn't there. I don't know what to do man. I know there's others with this problem as well
[Samsung Galaxy Nexus] open1your1eyes0:
I would fastboot flash the recovery and system partitions for your phone then try again. I know for a fact the fastboot images contain the recovery-from-boot.p file so you should be good after that. Not sure why quite a bit of people are experiencing this issue.
[Samsung Galaxy Nexus] Kryptonian_Knight:
I just used the app to install
[Samsung Galaxy Nexus] TCommander:
1. Stock ICL53F, Rooted, DeOdexed and Zipaligned. - File was Missing LONG before this ROM was installed

2. Battery % and Soft Buttons installed - File was missing LONG before these mods were installed.

3. App is File Expert which has just as much root access as File Explorer (Which produced the exact same contents. I can take a screen shot of a different app with the same results if that is helpful.
[Samsung Galaxy Nexus] bangdrum:
Alright, I'll give that a shot when I get some free time. Will having installed via rom manager affect the fastboot process at all?
[Samsung Galaxy Nexus] open1your1eyes0:
Not at all, you will lose root however so you have to follow all the steps afterwords.
[Samsung Galaxy Nexus] bangdrum:
Ok so check this out man. I don't know whats going on but I completely reverted to stock except for relocking my bootloader. Rooted. and booted into the stock recovery. booted up and the file isn't there.... I don't know what to do. I haven't installed cwm yet either.
[Samsung Galaxy Nexus] escoe:
Hello I am stuck on step 3

3. Flash CWM (fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img)

Do I flash this through windows command prompt? if so what command do I use.

Or if this is flashed through bootloader menu please detail steps for doing so thank you.
[Samsung Galaxy Nexus] phillybizzle:
+1
[Samsung Galaxy Nexus] zombieflanders:
You have to be in the directory where the fastboot executable is (for example, C:\android-windows-sdk\platform-tools). But this raises the question of why this would be a problem for you at the end of the process. After all, during the unlocking and rooting process you would have had to be issuing commands in that directory multiple times, including a command that you would have executed exactly the same way at least once before if you had rooted correctly.

Try /sdcard/clockworkmod/backup. And it's supposed to be a folder, not a file.
[Samsung Galaxy Nexus] scott62185:
I cannot rename/delete/move the recovery file either (says it's "read only") and I am on version 2.17.2. As far as I can tell it is the newest version. I have tried to push R/W as well. Any ideas? Thanks...
[Samsung Galaxy Nexus] MarkGbe:
Is there a fix for the whole having to flash recovery anytime i want to use it or is that still an issue?

Right now i can't just go into recovery or i get the red triangle screen. So i flash recovery, then do what i have to do in there. Rinse and repeat..

---------- Post added at 08:36 AM ---------- Previous post was at 08:28 AM ----------

nm did a bit more searching and found the fix.
[Samsung Galaxy Nexus] michaelkahl:
Anyone else have an issue with the controls being way to unpredictable in CWM? Sometimes I press volume up or down and get nothing, other times it jumps 3-4 or more options and sometimes it moves up or down one selection on the menu. It's very frustrating and difficult to use.

Yes I did a search, no I didn't find much on this.
[Samsung Galaxy Nexus] drPheta:
Dude, you need to follow the instructions to the "T". That means extracting things where they need to be extracted, directing to the proper directory, and making sure your commands match those same Paths to the "T".

You're typing a command in a directory where the executable file doesn't exist... and telling the program (which lives in a different directory) to push a file (that also lives in a different directory).
[Samsung Galaxy Nexus] TCommander:
I also could not find the /system/recovery-from-boot.p file on my phone. I had done the boot loader unlock, root and CWM flash through ADB and when I went to look for the file it just wasn't there.

I used the tool kit from the link below to resolve the issue and now my phone is consistently booting into CWM Recovery when prompted. I did several things so I'm not sure exactly what I did that fixed it. If you are having this issue you are obviously already rooted. I ran the deletion of the file command. I also ran the flash CWM command and the flash stock recovery command (not in that order.) In the end the last things I did were to run 3 (delete the file) and run 4 (Flash CWM Recovery). Hope this fix proves repeatable for others.

http://xdaforums.com/showthread.php?t=1400871

Big Thanks to mskip
[Samsung Galaxy Nexus] vihil:
Yeah that file isn't there for me, neither. But, I also can reboot into fastboot and launch CW recovery without reflashing it. So I don't think it's an issue this file isn't there but you just can omit that step and be done with it.

Anyway, if it is there for you and you want to remove it, you can also remount r/w manually (w/o paying $3.50 for Root Explorer):

(Note that I got the path and fstype through "adb shell cat /proc/mounts".)

$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
[Samsung Galaxy Nexus] SolipsistX:
I'm having a problem with the superuser app. I applied su.zip without problem and I can find su and Superuser.apk in the right places and su works (running 'su' in adb shell gives me root and I can remount and alter /system).

However, the Superuser app doesn't work. Any app that tries to get root fails, and Superuser itself can't get root to install a new su binary. I checked for su updates (I have 3.0.3 and 3.0.3.2 is out), but the superuser updater fails at the "Gaining root access" step.

The updater also fails to find busybox, but I assume that is ok since the updater continues and I checked su.zip and it doesn't install busybox (so I assume others would have had the same problems).

anyone else have problems like this? I doesn't block me from getting clockwork mod installed, but I can't use any apps that need root since Superuser is broken.
[Samsung Galaxy Nexus] SolipsistX:
I've solved my problem by manually installing su and Superuser.apk pulled from the androidsu.com site. By manually I mean using adb to push the files and then shell to copy them into the right places and set the permissions.
[Samsung Galaxy Nexus] RoBBYTroN:
Rename recovery-from-boot.p to revert to stock for 4.0.3?

I would like to root, install clockworkmod, and backup and all that. However i know that you are unable to receive OTA updates not on a stock ROM.

So the question is, when the 4.0.3 update is finally released and pushed OTA. Would i be able to go through root explorer to rename the modified "recovery-from-boot.p.bak" back to "recovery-from-boot.p"? Will doing this allow me to simply reboot my phone to have that file recover my stock recovery and allow the OTA to be installed? I know this would likely unroot me, however what i am most concerned about is receiving this 4.0.3 update. I will still be using the stock rom as i am rooting just for the tethering now. Would it be better to just wait for the update to root and do all this?

Thanks in advance for helping a newb.:)
[Samsung Galaxy Nexus] x.v_:
Pretty sure you can just "adb remount"? :p

I wouldn't be too concerned about getting the update. There will be zips made for all of us rooted/ROM'd users. That is the beauty of having a Nexus phone. :)
[Samsung Galaxy Nexus] marshallladd:
I have this same issue. Also, after flashing something, every once in a while I get a message on CWM saying "back button disabled" at which point the power button doesn't select anything and just turns the screen on and off. I have to either do a battery pull or adb reboot to get out recovery at that point.
[Samsung Galaxy Nexus] dawynkoop:
You'll get the back button disabled message if you scroll between the beginning and the end of the list too many times. use volume up and volume down to scroll back and forth between the beginning and end again and it will re-enable the power button and you can continue like normal.
[Samsung Galaxy Nexus] xformulax:
i have this problem too... not sure if its hardware or cwr.
[Samsung Galaxy Nexus] glhelinski:
su.zip push

hi,

where in the steps is the best place to "push the su.zip" occur? and isn't this the proper command? adb push su.zip /sdcard/

thanks
[Samsung Galaxy Nexus] BiggShooter:
I watched / followed the directions in a youtube video when I rooted my Samsung Galaxy Nexus (Verizon LTE / CDMA). Everything worked perfectly and i rooted without any problems / issues / errors!

Since I'm still considered a "new user" to the forums, I could not post the link. However, if you search the following in YouTube, you will be directed to the video I watched:

How to Root the Verizon Galaxy Nexus 4G LTE

Hope this helps! :)
[Samsung Galaxy Nexus] beatlesfan01:
Also having this issue. After multiple "jumps" the power button no longer selects. It just turns the screen off/on. I then have to do a battery pull.
[Samsung Galaxy Nexus] glhelinski:
thanks. those confirm the steps (and they also reference this thread too)...so looks good to me.
[Samsung Galaxy Nexus] marshallladd:
awesome. that fixed it. thanks.
[Samsung Galaxy Nexus] tu3218:
Can we just download RM and then flash CWM that way?
[Samsung Galaxy Nexus] Kryptonian_Knight:
I did and works great

Sent from GALAXY NEXUS

Thank if helped
[Samsung Galaxy Nexus] tu3218:
awesome thanks!
[Samsung Galaxy Nexus] dcdgoth:
By flashing factory image, it will remove the CWM recovery and back to original recovery right?
[Samsung Galaxy Nexus] dcdgoth:
well anyone?
[Samsung Galaxy Nexus] open1your1eyes0:
Only if you flash the recovery portion of the factory image as well. Which by default, it does so. You can use fastboot to manual flash partitions however, avoiding to flash recovery and keep CWM.
[Samsung Galaxy Nexus] Stadsport:
Edit: Nevermind I'm retarded.
[Samsung Galaxy Nexus] jyrlyn:
Does anybody have any advice on how to get started fixing this? I play around with my phone on several different devices and am not very confident with adb commands. I'd just prefer that it work naturally.
[Samsung Galaxy Nexus] htowngator:
That is probably an issue with not having a real SD card anymore.
[Samsung Galaxy Nexus] jyrlyn:
Probably. But there should still be a way to mount the storage while in recovery, without having to get fastboot on every machine you touch. The device shows up on my windows 7 machine, but in a different (and inaccessible) state than when it is in fastboot or fully on. So I would assume that the storage just needs to be put in an accessible state, which should be perfectly possible. I just don't have a developer's eye to glean what to look for.
[Samsung Galaxy Nexus] thunderstruck!:
It's annoying as hell not being able to mount storage. I was flashing a ROM the other night then realized I had forgotten to put gapps on there when I went to flash. Wound up rebooting just to copy a stupid file over, instead of pushing it while still in recovery.
[Samsung Galaxy Nexus] Natolx:
You can push without mounting USB storage using adb on the computer. I just adb push (file) /sdcard/ and it works fine.

On another note: Is a fix for the navigation problems with double/triple menu movement from one click being looked at?
[Samsung Galaxy Nexus] tu3218:
Can I just rename /system/recovery-from-boot.p and then flash CWM via RM to have CWM as the default? I flashed CWM but I forgot it wouldn't set it as default if this file is in there.
[Samsung Galaxy Nexus] jbartcaps:
Anyone else notice the messed up dates on your backups when trying to restore one on or after Jan 1st 2012? I did a backup today Jan 5th and when I went to restore it the date was 2000_01_00. Kinda scared me for a second haha.
[Samsung Galaxy Nexus] vaffanculo403:
I wish I could get it to even make a backup. This happens every time....
[Samsung Galaxy Nexus] wolfman87:
I just did this through Clockwork ROM Manager. I selected flash recovery, then it asked me to confirm my phone as CDMA or GSM, then it downloaded/flashed it.

Simple. :D
[Samsung Galaxy Nexus] Androidalchemist:
But with cwm using rm if you reboot using the stock img doesn't it get rid of cmw. So then you have to flash it again
[Samsung Galaxy Nexus] wolfman87:
Not sure I followed that.

I did find out (after a couple of attempts and some research) you have to rename/delete the recovery-whatever.p before you flash CWM Recovery. It won't stick otherwise.

Also, if you don't want to pay for Root Explorer, you can use ES File Explorer, in the settings you can tick off mount system and make writable. Then go to the favorites to navigate to the root folder.
[Samsung Galaxy Nexus] cancerouspete:
anybody else getting a volume button bounce in recovery? clockwork seems to have the 'volume bug'.

sometimes a single push up or down can cause double and triple hits. this is particularly annoying when triple up presses disables the power button
[Samsung Galaxy Nexus] jerrycycle:
Known issue. Try the touch custom mod version. That issue is fixed.
[Samsung Galaxy Nexus] cancerouspete:
thanks, sorry. searched but didnt find anything. apparently didn't search hard enough :)
[Samsung Galaxy Nexus] jerrycycle:
[RECOVERY] ClockworkMod Recovery *Touch-Enabled* (CDMA Edition) http://xdaforums.com/showthread.php?t=1428338

[RECOVERY] ClockworkMod Recovery *Touch-Enabled* (CDMA Edition)
[Samsung Galaxy Nexus] Gongadin:
That's basically what I did and it worked. Although instead of renaming the file, I created a new folder called "deleted stuff" or whatever, and using root explorer just moved it into that folder. Not a fan of renaming things just in case i screw something up and need it again. Once it was out of the system folder, I just reflashed recovery through rom manager and now it reboots into recovery from rom manager just fine. Still getting a quick flash of "superuser stopped working" and kind of a "pop" from the speaker when it reboots, but it works fine. Haven't really looked into that issue yet, next on my list...
[Samsung Galaxy Nexus] ohnoezmahfone:
Ditto for me, using 5.5.0.4
[Samsung Galaxy Nexus] automaddux:
I dont see an option in fast boot to install clockwork

so I followed the steps including deleting the file in /system. when I went into fastboot mode it shows me four options Start, restart bootloader, Recovery mode and power off. I choose recovery mode thinking that's where I flash the .img but instead I got Andy laying on his back with an exclamation symbol. I took the risk and pulled the battery after several attempts of backing out of this screen and thankfully was able to reboot. please tell me what I'm doin wrong. I don't see what menu to go into on your steps and I am obviously a noob.
[Samsung Galaxy Nexus] ogdobber:
the screen where it says start...look down at the bottom, in small red print "FASTBOOT MODE"..your there

that is the (page) where you run the terminal commands;)
[Samsung Galaxy Nexus] holmes6:
Yes. I'm amazed that any dev would put their name on this junk..

careless dev and didn't even mention it in the OP

seriously, have some standards, this software is crap
[Samsung Galaxy Nexus] vaffanculo403:
Actually dude its very useful and I'd bet it has saved just about everyone's ass in here at one time or another. If you have a problem with it and the volume rocker bug annoys you that much then don't use it. Its that simple. But good luck flashing ROM's and modding you phone without it.
[Samsung Galaxy Nexus] denpad2010:
maybe im stupid but i cant understand,well let me say i am not a native english speaker and really im still learning the language lol,anyway i did root the phone with odin i am on 4.0.2 and yes im sure is rooted,ok now i want cwm recovery so what can or have to do to get it,i am confortable using odin so is there a way to do using adin is better but if i have to use anoter way is ok i can try,but i need very easy step tp follow lol thanks a lot any help will be appreciated
[Samsung Galaxy Nexus] Shayes784:
if you want clockwork mod to be permanently installed, you need to use the info in the first post, and use fastboot to install the CWM after removing the stock boot img.

ive never used odin and i would recommend using the methods noted in these threads because thats what most of us are using. otherwise, you will probably find very little support for it.
[Samsung Galaxy Nexus] ogdobber:
I think you meant recovery-from-boot.p
[Samsung Galaxy Nexus] denpad2010:
yes i dont see much support and really i dont understand how use fastboo5t i downloaded the cwm file then say go fastboot and flash cwm how i will flash if file in my pc and not my phone u see what am saying i mean i know im not an enflish speaker but i need more easy to follow steps.... i want try a rom but i dont see any odin room probablly i will stay stock with root:confused:
[Samsung Galaxy Nexus] holmes6:
Obviously the software is useful, it's the basis for pretty much all hacking on all devices. One might say it's of critical importance, that's exactly my point, while the bugs may be minor, EVERYBODY is experiencing them. Those of us that are flashing frequently are dealing with this day in and day out.

Almost every dev here that has any popularity and respect is coding to relatively high standards.. there simple aren't annoyances like the bug in cwm anywhere else I have found. An obvious bug like the one we're talking about should be dealt with, or else the software can be considered broken and abandoned. I imagine at least part of the problem here is that CWM gets ported, probably not by koush to each device, with varying quality assurance.

Anyway, Touch based recovery seems to solve this problem, so kudos to the developers on that software.
[Samsung Galaxy Nexus] edgie168:
Well, if you can fix it yourself..
[Samsung Galaxy Nexus] vaffanculo403:
Exactly. If you think its been abandoned after not having an update for what like 3 weeks add you're smart enough to fix it then go for it. My guess is that you haven't even donated or bought the premium version of ROM Manager and you are *****ing about something you got for free.
[Samsung Galaxy Nexus] GaresTaylan:
Im running into an issue that is confusing me. Im unlocked and have root access. I have transferred the CWM file to the internal storage on the phone.

When I use fastbook and then boot into recovery... there are no options available to install anything.

Also, when i use root explorer and I go to delete that file, /system/recovery-from-boot.p isnt there to begin with?

What do I need to do so I can get CWM installed? In fact, anything I put on the internal storage... ROMs, kernals, etc... none of it shows.
[Samsung Galaxy Nexus] A2Eric:
I had some trouble getting CWM to work on mine too. Did you download ROM Manager and go into the app and flash CWM Recovery? Then maybe go into root explorer and look for that file.