Database Users

help - Overclock Patch and update.zip

i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.

Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581

so phone will be stock again right? have to re dload apps and sync contacts and **** again right?

hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first

when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.

did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.

volume up + end button = Recovery

ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?

yes its suppose to be on the root of the sdcard too

still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...

can u link me to the tut u are using?

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

QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...

That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App

TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??

Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.

Updated root 1.49

READ IT BEFORE DOING IT
How to get into recovery
This is the way i figured how to get it into adb. I spent all day figuring this out.
It will take a couple tries but it will work
-Go to sdk folder then usb driver folder
-Make sure you have added to the inf file ; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
-Have a formated sd with allocation size of 4096.Don't format with phone do it with card reader or if you can't do it with usb...
-Boot your phone into HBoot with sdcard in.
-When the screen turns on wait a sec pop out sdcard make sure it doesn't scan sdcard.
-Start loop.bat or .sh
-Push volume up for recovery before wait 4 secs before your computer makes the sound pop it in.
-^^^Make sure you got around 3-5 secs before pushing it in
What to do when in adb recovery
-Do down volume and power and hit update it will fail.
-Adb push ota.zip /sdcard/update.zip
-Adb push root.zip /sdcard
-Have this command ready don't do it yet.
-Adb push update.zip /sdcard
-Press Hit run update.zip, as soon as you see a the green lil bar on your phone. PRESS ENTER ON CMD.
-Go to the partitions menu and mount system
-Go back and press update select install any zip from sdcard.
-Choose root.zip
-Reboot phone and install superuser.apk and allow it.
-Do adb shell then su if you see # you have root
-Download rom manager from market.
-Flash recovery ra or clockworkmod.
-^^^ if it doesn't let you, you messed up on rooting it.
Ill post a video of me doing it later. To lazy now
ADB RECOVERY VIDEO
http://www.youtube.com/watch?v=Uhc3SvOS6r4
PS ill figure it out later how i did with more practice
and don't flame or say video fake.. Or i just won't figure it out.
http://www.youtube.com/watch?v=eK_A0lH8uFM/color]
Hairston said:
I forgot that my digital camera can take video, duh. I can make one too if you want.
What would you need? Would a shot of the HBOOT screen showing 1.49 S-ON and then hitting <VOL UP> booting into Amon_RA recovery (to prove root) do it?
It really sucks that this procedure is such a living hell. Blame HTC for locking these things down so tightly in the first place. This is my first rooted phone and being able to play around with the custom roms and to do an image backup is pretty cool.
I see a lot of people in the Incredible root thread using the same basic method to root are having a tough time too. Misery loves company I guess.
Click to expand...
Click to collapse
^^^^^ proof right there
Another method
RKLamb2 said:
Alright sorry about that but it was like 4 in the mourning. I will use the other guys post for the slide and explain what I did.
The main thing I did different was as soon as pushed down to go to hboot I ejected my memory card at the exact same time. No scan or anything. Once I got to the part where I ran the loop I hit control C to stop it and and it was smooth sailing from there.
Memory card was a sandisk 8 gig that I formatted to 4096 in windows seven. I basically use both write up but I actually finished using the slide write
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Hit Volume Up + Power button to Bring up the Selectable Menu
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip /sdcard
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Click to expand...
Click to collapse

Dc_striker said:
i got it working now what files to i push to it sorry for noob post lol
Click to expand...
Click to collapse
Give exact details on what you did.

AcidRoot said:
Give exact details on what you did.
Click to expand...
Click to collapse
http://forum.androidspin.com/showthread.php?t=2757

Push the root rom AFTER you tell us how.

Dc_striker said:
http://forum.androidspin.com/showthread.php?t=2757
Click to expand...
Click to collapse
So you you just followed that and it worked?

AcidRoot said:
So you you just followed that and it worked?
Click to expand...
Click to collapse
yes lol couple of tries but it worked

Dc_striker said:
yes lol couple of tries but it worked
Click to expand...
Click to collapse
sd card in or out

and what sd card are you using?

AcidRoot said:
sd card in or out
Click to expand...
Click to collapse
push sd card in before recovery pops i think lol. btw a transcend sd card 8gb

Damn I have tried a million times a million ways and nothing. Any small little detail that you think we might be missing?

Dc_striker said:
push sd card in before recovery pops i think lol. btw a transcend sd card 8gb
Click to expand...
Click to collapse
well i tried and the script froze for a second then nothing and i haven't been able to do it again

ah hell

listyb01 said:
ah hell
Click to expand...
Click to collapse
like ever post say its all about time or luck so it will work on the eris

Yea I'm sure it will work eventually. Can you give me a few details?
Debug on or off?
pc connection settings (on eris)?
Anything else important that I may be over looking?
Congrats on the root! Froyo was just posted so looks like your first custom ROM can be a 2.2 build.

listyb01 said:
Yea I'm sure it will work eventually. Can you give me a few details?
Debug on or off?
pc connection settings (on eris)?
Anything else important that I may be over looking?
Congrats on the root! Froyo was just posted so looks like your first custom ROM can be a 2.2 build.
Click to expand...
Click to collapse
just look at the link i posted i just followed everything on there, but its either i popped in before recovery popped up or pop out and in in recovery

Guess my luck is not as good cause it isn't working.

listyb01 said:
Guess my luck is not as good cause it isn't working.
Click to expand...
Click to collapse
Damn keep trying but i posted this thread to everyone know this method should work

Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash

AcidRoot said:
Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash
Click to expand...
Click to collapse
just use this: "while true; do adb devices; done"
Still trying to get this working on OSX.

AcidRoot said:
Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash
Click to expand...
Click to collapse
for linux try while true; do adb devices; done

[Q] Unable to ADB Remount XOOM...!!

Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..

You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App

diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.

dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.

That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.

Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.

I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.

It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App

jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .

jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App

lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .

[How to] SBF to 2.3.340 [UBUNTU]/[LINUX]

I updated in a hurry to and wanted to SBF back, didn't find a very useful linux guide. I'm running Ubuntu 10.10
Files you will need:
1. sbf_flash
2. Full SBF 2.3.340
Guide:
1. Created a folder and place the files inside.
2. Make sure the sbf is unzipped into the folder.
3. Open a Terminal and change to the directory to your folder
4. Type chmod +x sbf_flash
5. Type sudo ./sbf_flash name of sbf file
6. Type in your password
7. Let it run until is shows "waiting for phone"
8. Restart the phone ( Make sure it's plugged into your PC )
9. Enjoy.
Hope it helps!

Thanks for the guide bro. This will be helpful down the road

this is one reason why i love ubuntu sbf'ing is so easy no drivers no programs

Thank you for this post. Messed up my x but was able to get it back up and runnning

Stuck. Mind adding Windows instructions?

mrkite38 said:
Stuck. Mind adding Windows instructions?
Click to expand...
Click to collapse
This is for folks on "Linux" to my understanding.
Such as a Windows based PC with a Linux partition with Ubuntu as a OS.
This maybe a good time to checkout Linux if you haven't already.

I'm aware of what Linux is. If the op has the ability to include windows instructions also, it would be convenient since the thread is already stickied.

AWESOME. Much easier...

Downloading files to do this now. One question..is this going back to stock or can I flash my back-up by doing this?
Sent from my DROIDX using XDA Premium App

Got most of this to work. When it tells me to reboot phone into bootloader..I can not access it. Can not get past the "triangle".
Sent from my DROIDX using XDA Premium App

sooo these instructions are reaaalllyy vague. for instance how do i get to the directory where my folder is? do i have the phone plugged in this whole time, or only when it shows "waiting for phone?" please make this noob useable. because i can't tell this right from wrong.
so i think i got to where i'm supposed to be..
[email protected]:~/Documents$ cd sbf/
[email protected]:~/Documents/sbf$ chmod +x sbf_flash
[email protected]:~/Documents/sbf$ sudo .sbf_flash VRZ_MB810_2.3.34_1FF_01
[sudo] password for derique:
i named the file i put the sbf_flash and the actual sbf file into "sbf"
so assuming that what i've done so far is correct, it won't let me type my password.. it actually won't let me type anything at all.
i got to [waiting for phone] but i didn't type in the "sudo" part of the command.
now i get to the part where it says waiting for phone.. so do i plug in when it's on, in the bootloader, or what?
when i plug in while it's in the bootloader i get this:
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
[email protected]:~/Documents/sbf$
but i don't think i'm rooted. i unrooted many times via z4root. so what else can i do guys? i need help

DeriquedeCoux said:
sooo these instructions are reaaalllyy vague. for instance how do i get to the directory where my folder is? do i have the phone plugged in this whole time, or only when it shows "waiting for phone?" please make this noob useable. because i can't tell this right from wrong.
so i think i got to where i'm supposed to be..
[email protected]:~/Documents$ cd sbf/
[email protected]:~/Documents/sbf$ chmod +x sbf_flash
[email protected]:~/Documents/sbf$ sudo .sbf_flash VRZ_MB810_2.3.34_1FF_01
[sudo] password for derique:
i named the file i put the sbf_flash and the actual sbf file into "sbf"
so assuming that what i've done so far is correct, it won't let me type my password.. it actually won't let me type anything at all.
i got to [waiting for phone] but i didn't type in the "sudo" part of the command.
now i get to the part where it says waiting for phone.. so do i plug in when it's on, in the bootloader, or what?
when i plug in while it's in the bootloader i get this:
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
[email protected]:~/Documents/sbf$
but i don't think i'm rooted. i unrooted many times via z4root. so what else can i do guys? i need help
Click to expand...
Click to collapse
It's asking if you ran the program as root, meaning you SHOULD use sudo. When it prompts for your password, just type it in and press enter. It doesn't show any placeholder characters.

Very vague instructions. I don't know what to do at all. Would like a bit more step by step in regards to what I enter in terminal.

double post.

SBF Ubuntu
Question, is it possible to SBF back to an older Bootloader? Thanks-AT

So, with this method i will be able to downgrade from OTA .596 to .340 ? Or can someone point out how can i get the .596 rooted and be able to install apex 2.0 RC. any help will be appreciated .

Yes, you can downgrade from the GB OTA to froyo with this.

Thank you.
Sent from my DROIDX using XDA App

Linux CD method
For those of you that are not very up on linux, the link below guides you into making a linux CD that you can insert into your windows laptop and contains all the programs you need to sbf your droid x back to froyo. You can then root it and upgrade to GB rooted using the 2 file method. It's almost idiot proof and the instructions are pretty good. If you can burn an ISO file onto a cd or usb drive and get your computer to boot from it then you should be able to sbf in about 10 minutes.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html

nukeruss said:
For those of you that are not very up on linux, the link below guides you into making a linux CD that you can insert into your windows laptop and contains all the programs you need to sbf your droid x back to froyo. You can then root it and upgrade to GB rooted using the 2 file method. It's almost idiot proof and the instructions are pretty good. If you can burn an ISO file onto a cd or usb drive and get your computer to boot from it then you should be able to sbf in about 10 minutes.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Click to expand...
Click to collapse
I can vouch for this CD method. I used it to sbf from GB OTA back to Froyo. It is pretty idiot proof. It will even coach you on how to get to the bootloader screen. Just one hint: eject the CD before shutting down. It will boot back to linux when you start up again.

Please help: How do u put files on the SD with CWM?.

Ok..
I cleared delvik cache.. battery and decided to try out a new kernel.. now it hangs..
Now I only have an 8 gig.. I guess i cleared out the backup to save space because as I went to look for it, it was gone. Now I cant get any roms on the phone to reflash.. and i deleted the ROMs on there...
How do I get a rom on the phone to reflash it. Any help would be greatly appreciated.
Thanks
Chris

Bump
Can anybody help with this? Basically is there a way to get files on the phone in recovery mode?
I'm sort of new... I see the side load but not sure how to use it. Says load the files on once activated but not sure how the relates to the computer. Or where I put the commands to do it. Thanks.
Chris
Sent from my SGH-I747 using xda app-developers app

You are running a custom recovery right?
You can use adb to push files when booted into a custom recovery.
The command used would be
Code:
adb push nameofzip /storage/emulated/0
To read more on adb check out efrants sicky http://forum.xda-developers.com/showthread.php?t=2010338 adb commands are about half way down on the OP.

When u say custom recovery do u mean CWM? I do have that... and my computer registers the phone when I plug it in. But nothing pops up. I don't think USB debugging is on...
I'll check out the link.
Sent from my SGH-I747 using xda app-developers app

Yep, that is a custom recovery. If you have questions post them here. I'll be around for a little while.

I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)

wizshaw said:
I think I am so close.
I got the adb and fastboot files, and upon checking devices in fastboot, it does say that my device is connected.
But I cant get the adb driver to put the files on my phone.
Im using "adb push -d C:\android1\cm-10.1-20121214-NIGHTLY-mako.zip
And it says device not found?
Sorry for the questions, but thank you for the help.
Chris
(and im in the directory where the adb file is located)
(Once I get this resolved... im always gonna have one backup on my phone)
Click to expand...
Click to collapse
Ok. The best way is to open the command prompt from the folder in which you have adb. The easy way to do that is hold down shift and right click. Then choose open window here.
Next, once you are booted into recovery type
Code:
adb devcies
If it returns a number then proceed to push the file. (Its easy to make a typo so change the file to something easy like cm10.zip)
So you would type
Code:
adb push cm10.zip /storage/emulated/0

I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4

slymobi said:
I erased everything the other day by mistake and total noobishness Lol. I just used wugs tool kit to flash the stock image back. Might be useful if struggling with adb etc.
Sent from my Nexus 4
Click to expand...
Click to collapse
What is anyone going to learn by using a toolkit?! I commend the OP for putting in the time to learn how to use adb. So in the future if they were to run into a problem they would know how to easily fix it.
Sent from my Nexus 4

I got it guys.
I realized that fastboot and adb only get activated in their respective UI's... And i refined my CMD commands a bit after a little more reading.
Problem solved. And i learned more about the android platform in the process. Time well spent.
I want to formally thank you guys. This is why this community is great.
Chris