Database Users

How to Flash Clockworkmod Recovery 3.0 easily from your phone

I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.

there's nothing noob about it. that is a bonafide hack. nice!

I tried something like that but I didnt rename it correctly. So nice to know though. Good work.
Sent from my T-Mobile G2 using XDA App

Can u put that in a zip for lazy people like me
Sent from my T-Mobile G2 using XDA App

charlieton said:
there's nothing noob about it. that is a bonafide hack. nice!
Click to expand...
Click to collapse
How is that a hack? LOL

not really a "hack" per se but it tricks ROM manager into flashing a newer clockwork while still thinking it is the same old one. i thought about doing this the other day but never got around to it so great job on this

wineguy13 said:
Can u put that in a zip for lazy people like me
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
You need this is a zip to simply move a file to your SD card? Wow, that IS lazy. lol

I followed the thread but the download take u to a bunch of jumbled code.. is that right?
Sent from my T-Mobile G2 using XDA App

Typo
shadymnms said:
4. Mine was "recovery-cockwork-2.5.1.3-vision.img". Rename it to "recovery-cockwork-2.5.1.3-visionXXX.img" or something obviously different.
Click to expand...
Click to collapse
Nicely done, flashed it via your method.
You may want to correct the typo you have in there as I first tried to copy and paste your file names. It's clockwork, not cockwork.

shadymnms said:
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.
Click to expand...
Click to collapse
How does it feel clunky? fastboot flash recovery recovery.img is a lot easier than this method.

rp1783 said:
How does it feel clunky? fastboot flash recovery recovery.img is a lot easier than this method.
Click to expand...
Click to collapse
For some reason flashing recovery from fastboot hangs everytime on my phone. This way is good but I did it in terminal. I actually had to flash a cyanogen rom to get the fastboot command, this method would have saved that step.
Sent from my HTC Vision using XDA App

overpower said:
Nicely done, flashed it via your method.
You may want to correct the typo you have in there as I first tried to copy and paste your file names. It's clockwork, not cockwork.
Click to expand...
Click to collapse
Fixed. Thanks lol. I was doing in between flashing villian and was going back and forth. Ahhh... "cockwork", really? Musta slept in too late too.
Sent from my HTC Vision using XDA App

And the downgrade?

fastboot is a lot easier than this IMHO !
You will have fastboot if you have got adb setup on your PC. See the adb guide in this forum for how to setup adb (and fastboot too). It's worth going to the effort, because fastboot will help you with various things in the future. Also you will need the eng hboot.

thank you so much! man now this i can do. i was trying to adb or find terminal in my fastboot.

I'm just starting to install custom ROM tho my DZ, but is this means that ROM Manager will never integrate the new Clockworkmod Recovery?

shadymnms said:
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.
Click to expand...
Click to collapse
Thank you kind sir.

Thanks for this simple guide! Before I move forward though, a couple of questions - I need this recovery to flash gingervillain or the CM7 that's being worked on, right? But if I want to revert back to my nandroid backup of cm6.1.1, will I have to flash the old recovery before doing so? Cheers
Sent from my HTC Vision using XDA App

steviewevie said:
fastboot is a lot easier than this IMHO !
You will have fastboot if you have got adb setup on your PC. See the adb guide in this forum for how to setup adb (and fastboot too). It's worth going to the effort, because fastboot will help you with various things in the future. Also you will need the eng hboot.
Click to expand...
Click to collapse
now cmon stevie, i agree its good to have adb and proper sdk w\ drivers installed. But for the super ober noob thats wants shiny pretty new cw3 for whatever reason be it cm7 or just because, even trying to teach the super ober how to cmd and cd to the sdk is a larger challenge than this. Im just saying your a well respected source of info on xda to a lot of super obers and to say this is easier on the big picture, well thats just crazy talk. This is pretty easy for just about anyone.

kalipedia said:
Thanks for this simple guide! Before I move forward though, a couple of questions - I need this recovery to flash gingervillain or the CM7 that's being worked on, right? But if I want to revert back to my nandroid backup of cm6.1.1, will I have to flash the old recovery before doing so? Cheers
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
from what i've read this seems to be the case. i think i'll wait for a stable cm7 release before updating to 3.0

[Q]Can we use ClockworkMod Recovery instead of TWRP?

Just was wondering. I'm more used to what clockworkmod has so I figured it would be easier to install that instead. But I wanted to make sure it was supported before I went ahead and installed it. Anyone know?

Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.

androidcues said:
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
Click to expand...
Click to collapse
awesome. so i'm ok with installing it straight from rom manager right?
i'm a little paranoid bc a lot of people seem to be posting about bricking their fires.

Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.

gadgetman13 said:
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
Click to expand...
Click to collapse
thanks man, gonna go ahead and do it in a bit. fingers crossed .

Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk

Bmcd37 said:
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?

Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html

HeliosAI said:
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Click to expand...
Click to collapse
I thought CWM required the use of hardware buttons?

HeliosAI said:
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
Click to expand...
Click to collapse
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium

smirkis said:
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.

ndoren said:
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
Click to expand...
Click to collapse
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.

androidcues said:
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
Click to expand...
Click to collapse
its not sketch, just no room for error.
put recovery.img on the root of ur SD card, than open mobile terminal, than type these commands.
su (enter)
dd if=/sdcard/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery (enter)
just don't mistype it, all it does is make a copy directly to the /dev folder.
this is how, rom manager actually puts cwm on ur device.
or use this http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium

In Recovery, wiped probably too much - no ROM

Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.

l33ch0r said:
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
Click to expand...
Click to collapse
If you have Android SDK installed, you can use adb push to push the zip file to your internal storage. Put the ROM zip file in your Android SDK - Platform Tools folder on your computer, reboot the N7 into Recovery (connected to computer of course!), open Command Prompt window and change directories to where ever you keep your Android SDK (for me, it's: cd sdk/platform-tools). Then type:
Code:
adb push <name of ROM zip file> /sdcard
Wait, and after about 20 - 60 seconds it'll complete, then you can flash the ROM. It'll be on the root of your internal sdcard (/sdcard).

Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Or could you explain the steps so that even the bloodiest rookie of them all could understand it properly :-/
aaaw **** -.-
by the way, device is still in recovery

l33ch0r said:
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Click to expand...
Click to collapse
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.

RMarkwald said:
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
Click to expand...
Click to collapse
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"

Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium

l33ch0r said:
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Click to expand...
Click to collapse
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.

RMarkwald said:
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
Click to expand...
Click to collapse
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...

l33ch0r said:
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
Click to expand...
Click to collapse
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.

andymihail said:
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/

RMarkwald said:
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
Click to expand...
Click to collapse
No, wiping of my /sdcard was all my fault. I guess I have to take all credit for that
Well downloading the Stock with the toolkit takes quite some time...
foolish me -.-
Thanks for your help so far.
I'll definetely report whether it worked or not

I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.

l33ch0r said:
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
Click to expand...
Click to collapse
I can't remember my choice, was a few months ago.
Don't think you can go wrong with either.
I would try device is on.
Sent from my Nexus 7 using xda premium

RMarkwald said:
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
Click to expand...
Click to collapse
I would've used your solution immediately but I'm just too unfamiliar with this method
Toolkits are probably the easiest way - and it was pretty easy - who could expect me to wipe the zip, I just moved to the storage before flashing it?...

Why does this file has to be hosted on goo.im?
Goo.im gives me roundabout 120kb/s...

It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium

andymihail said:
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.

l33ch0r said:
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
Click to expand...
Click to collapse
It will remain unlocked until/unless you run the fastboot command: fastboot oem lock
If you don't run this, it will remain unlocked.

Whoaaaa I could scream!
Now that I downloaded the right one and try to flash it through the toolkit, it tells me, that there's no adb to be found. He doesn't recognize the device in bootloader.
What should I do?
OH THANK GOD! Tried it via recovery, he found it and restarted into bootloader

First of all: thank you so much guys - I was really shocked, but it all worked out
One more question before I make the same mistake again. Where should I put the zip which I wanna flash? When I have it connected to the pc, it shows me a portable device where the folders of the internal storage are (like Alarms, Android, DCIM, Download etc pp) - that's where I put the ZIP before.
Shall I keep it there?
And another question: what should I wipe in order to get it done properly?
Edit: Figured it out - got me CWM, much more familiar with that one
but thanks again for all your help guys

[Q] BIG MISTAKE!! Wiped the OS, Please Help

I was trying to wipe everything from Nexus 4 because i sold it and was going to ship the phone. I did this in the recovery mode (Team Win) and i had cyanogenmod installed.
It turns out i also wiped off any backups and also the OS on the phone. Now the phone has no operating system on it and only boots into recovery mode. I can't even transfer any backups to the phone because for some reason the phone isn't recognised as a storage device on my PC anymore.
What should i do?? I need to install any type of OS before i ship the phone
Please help

Flash factory images with a tool kit
Sent from my Nexus 4 using Tapatalk

Zehlek said:
Flash factory images with a tool kit
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Could you please elaborate a little bit?? i'm new to this.
What do you mean by "tool kit"??

Done this 2 weeks ago dont freak out. If u are a twrp user u can sideload the from into the device using adb. Make sure u have all the adb drivers on ur pc. Put the rom file into the folder where the adb files are. Now go to ur recovery/twrp advanced then choose sideload. Plug the phone into ur pc. Now go back to the folder whre adb is. Hold shift , right click and choose start open command wndow here. Now the black cmd box will appear type "adb devices" dont include the quotemarks. It should show device with serial and would say sideload at the right. This means ur phone is connected properly, then type adb sideload (nameofrom).zip and it pushes the file into ur phone it will be named sideload.zip. now reboot phone to recovery and flash awayyy. Sorry for the messy instructions
Sent from my Nexus 5 using Tapatalk

jyuuken said:
Done this 2 weeks ago dont freak out. If u are a twrp user u can sideload the from into the device using adb. Make sure u have all the adb drivers on ur pc. Put the rom file into the folder where the adb files are. Now go to ur recovery/twrp advanced then choose sideload. Plug the phone into ur pc. Now go back to the folder whre adb is. Hold shift , right click and choose start open command wndow here. Now the black cmd box will appear type "adb devices" dont include the quotemarks. It should show device with serial and would say sideload at the right. This means ur phone is connected properly, then type adb sideload (nameofrom).zip and it pushes the file into ur phone it will be named sideload.zip. now reboot phone to recovery and flash awayyy. Sorry for the messy instructions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you,
Do i download the rom from here ?? developers.google.com/android/nexus/images#occamkot49h
And then not extract, just copy that file to the phone using ADB?

If u want flash any custom rom, for the n4 i recommend purity or cataclysm.
Sent from my Nexus 5 using Tapatalk

jyuuken said:
Done this 2 weeks ago dont freak out. If u are a twrp user u can sideload the from into the device using adb. Make sure u have all the adb drivers on ur pc. Put the rom file into the folder where the adb files are. Now go to ur recovery/twrp advanced then choose sideload. Plug the phone into ur pc. Now go back to the folder whre adb is. Hold shift , right click and choose start open command wndow here. Now the black cmd box will appear type "adb devices" dont include the quotemarks. It should show device with serial and would say sideload at the right. This means ur phone is connected properly, then type adb sideload (nameofrom).zip and it pushes the file into ur phone it will be named sideload.zip. now reboot phone to recovery and flash awayyy. Sorry for the messy instructions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why not just flash it all through fastboot? I find that a lot better/easier than using twrp's adb push.

True , but i am more used to sideloading. U can guide him thru fastboot if u want
Sent from my Nexus 5 using Tapatalk

jyuuken said:
True , but i am more used to sideloading. U can guide him thru fastboot if u want
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
OR I can make a big guide with pictures and all for folks like him if there isn't one already... Is there?

Fast boot requires installing android adb if I am not mistaken. It can get messy if OP doesn't already have it installed.

If you're gonna ship it and sell it. Use this software to restore stock software: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-0-t2015469

If you're still stuck , i can help you via teamviewer.

Just use this to return to stock http://forum.xda-developers.com/showthread.php?p=34552123

calvinpl said:
OR I can make a big guide with pictures and all for folks like him if there isn't one already... Is there?
Click to expand...
Click to collapse
Rather than sounding sarcastic. If ur trying to implicitly bash some1 for not searching well enough atleast have the decency to post a link.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:33 AM ---------- Previous post was at 06:32 AM ----------
boltthrower56 said:
If you're still stuck , i can help you via teamviewer.
Click to expand...
Click to collapse
Great suggestion! Only a few wud do this for a stranger. Thanks bro
Sent from my Nexus 5 using Tapatalk

jyuuken said:
Rather than sounding sarcastic. If ur trying to implicitly bash some1 for not searching well enough atleast have the decency to post a link.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, I wasn't sarcastic at all... Sorry for making myself seem like an asshole. (happens to me sometimes...)
I just didn't have time to write a long post, explaining it to him + didn't he already solve his problem through adb?

The same problem happened to me but after thinking it through I found a solution. Just used wugs toolkit and flashed back to stock and selected the option soft-bricked. got me back to stock in no time. Just putting this out there if anyone else is reading this thread and dont/cant use adb.

[q] help!!!! No os

Ok, so i was going to backup my phone (NEXUS 4) and it got an error so i was in Team win recovery and accidentally erased my whole os and on top of that all my back ups so i got nexus toolkit to try to flash stock and it gave me an error so i did force flash i checked the model and board and what not and it all matched but on the command prompt it had an error loading system .img so i was going back to team win recovery... and it is now gone i get a android guy with a "!" and i need to know how to fix this please

Install adb drivers.
Download stock image from google.
Sideload image.
No need to panic, easy fixable.
Sent from my Nexus 4 using xda app-developers app

more info
failly said:
Install adb drivers.
Download stock image from google.
Sideload image.
No need to panic, easy fixable.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
can you go into more detail please, idk what much of that even is

bpqly1 said:
can you go into more detail please, idk what much of that even is
Click to expand...
Click to collapse
Read this, it's very well explained.
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

OK!
Ok, I will try this when i get home so about 15min and ill keep you posted on what happens. but i still have a question, why cant nexus toolkit do it? i think it is extracting it to the wrong folder because on the command prompt it says it cant find like system.img nor boot.img or something like that lol it has been a while since i last looked at it

fastboot
bpqly1 said:
Ok, I will try this when i get home so about 15min and ill keep you posted on what happens. but i still have a question, why cant nexus toolkit do it? i think it is extracting it to the wrong folder because on the command prompt it says it cant find like system.img nor boot.img or something like that lol it has been a while since i last looked at it
Click to expand...
Click to collapse
when i get to the actual flashing part with CMD when i type fastboot it says it isnt recognized as a command.... any clue?

bpqly1 said:
when i get to the actual flashing part with CMD when i type fastboot it says it isnt recognized as a command.... any clue?
Click to expand...
Click to collapse
Open the command window in the same directory as you have fastboot.exe. shift, right click on that directory and a window will pop up letting you open the command window there.
Sent from my Nexus 5

No fastboot.exe
jd1639 said:
Open the command window in the same directory as you have fastboot.exe. shift, right click on that directory and a window will pop up letting you open the command window there.
Sent from my Nexus 5
Click to expand...
Click to collapse
i dont seem to have a "fastboot.exe" file

bpqly1 said:
i dont seem to have a "fastboot.exe" file
Click to expand...
Click to collapse
Follow the first section of this guide to setup android SDK.
http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5

OK
jd1639 said:
Follow the first section of this guide to setup android SDK.
http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5
Click to expand...
Click to collapse
ok man give me a second im really new with all this cmd stuff, sorry but i love ALL the help i have gotten, you guys are awesome and the super fast reply's are amazing when your in need of help

You guys
Yall are ****ing awesome, because of you guys i have my phone back... i think each of you with all that i have... i use my phone for my job and because of yall i still have a job... you guys some how got some one that doesnt do much with android told me how to put a whole OS on and i appreciate it

bpqly1 said:
Yall are ****ing awesome, because of you guys i have my phone back... i think each of you with all that i have... i use my phone for my job and because of yall i still have a job... you guys some how got some one that doesnt do much with android told me how to put a whole OS on and i appreciate it
Click to expand...
Click to collapse
Glad you got it working.
Sent from my Nexus 5

bpqly1 said:
Yall are ****ing awesome, because of you guys i have my phone back... i think each of you with all that i have... i use my phone for my job and because of yall i still have a job... you guys some how got some one that doesnt do much with android told me how to put a whole OS on and i appreciate it
Click to expand...
Click to collapse
I don't seem to have any recovery any more any clue? I went to root without a computer and it can't find it can you tell me what I did wrong or should I just try nexus toolkit to root my device because I don't even think it is rooted. Or should I use cmd to root and put super user and custom recovery? If so do you know of a link.. I'm sorry but I appreciate the help
Sent from my Nexus 4 using xda app-developers app

bpqly1 said:
I don't seem to have any recovery any more any clue? I went to root without a computer and it can't find it can you tell me what I did wrong or should I just try nexus toolkit to root my device because I don't even think it is rooted. Or should I use cmd to root and put super user and custom recovery? If so do you know of a link.. I'm sorry but I appreciate the help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am not sure of a way to solve this problem you are having but I would recommend not using the toolkits for a little while, it seems to me like you have a bit to learn about ADB and rooting etc. And you need that to fix any problems you get into. The toolkits should be a shortcut for things you already know how to do, not to replace learning
Sent from my Nexus 4 using Tapatalk

bpqly1 said:
ok man give me a second im really new with all this cmd stuff, sorry but i love ALL the help i have gotten, you guys are awesome and the super fast reply's are amazing when your in need of help
Click to expand...
Click to collapse
You will lose root and the custom recovery do that is expected. Use the link you were given on page 1 and go to section E
Sent from my Nexus 5