Database Users

Installed cutom rom now stuck on google screen :(

Ive checked other nexus 7 threads... but this isn't the case.
My nexus 7 is stuck on the google Boot I cannot rub Fastboot or recovery from the toolkit .. nothing at all. It cant find the device .
When I plug in the usb it still makes the sound on windows and so on.
It happened when I was prepairing to install a Custom ROM using JROMFlasher..
I followed all the steps, and when it came to install the ROM to the SD card it just rebooted (transferred to quickly I thought)
And then Ever since it has Just been stuck on the google screen.
I am quite pissed :L
Any Ideas?

I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Download the zip located here : platform-tools.zip Extract the contents to a folder name the folder Nexus7 or whatever you want.
Once thats done go ahead and open a command prompt window in that folder you can do that by Shift+Right clicking inside the folder and selecting "Open Command Prompt Here" or if on XP then open CMD and
Code:
cd C:\Users\Name-of-User\Desktop\Nexus7
Once in the CMD issue the command
Code:
fastboot devices
To see if the computer recognizes the device in fastboot mode. It should spit out a gibberish looking code with ....... Device at the end.
Then you going to flash the recovery to do that you issue this command
Code:
fastboot flash recovery name-of-recovery.img
inside the zip the openrecovery-twrp-2.3.1.0.img that is what you will put in place of "name-of-recovery.img" it will show on the screen writing recovery when its done hit the volume up button until the "START" Turn to "Recovery Mode." Then hit the power button you will boot into recovery mode. Once in recovery mode place the ROM.zip you want to flash in the same folder as the stuff you extracted to.
Then issue this command
Code:
adb push Name-of-ROM.zip /data/media
Of course you will replace name-of-ROM.zip with the actual name of the ROM you are flashing. Make sure you also have a gapps packaged which can be found on goo.im/gapps/ latest package is gapps-jb-20121011-signed.zip you will want to adb push that as well.
IF all is done correctly you should be able to install that ROM please follow this procedure.
1. Go to Wipe
2. Factory Reset (this will delete all your apps and apps data not the sd card)
3.Wipe Cache Partition
4. Wipe Dalvik Cache
5. Format System
6. Go to install and find the two ROM.zip and Gapps package at the bottom of the root of the sd card (/sdcard0)
7. Select to flash the ROM and then the Gapps
8. Reboot
Click to expand...
Click to collapse
You should be good to go now.

ÜBER™ said:
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Click to expand...
Click to collapse
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.

QuantumCipher said:
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
Click to expand...
Click to collapse
Its all good wrote you up a quick guide follow that and it'll get you back on track .

ÜBER™ said:
Its all good wrote you up a quick guide follow that and it'll get you back on track .
Click to expand...
Click to collapse
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)

QuantumCipher said:
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
Click to expand...
Click to collapse
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.

ÜBER™ said:
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
Click to expand...
Click to collapse
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..

QuantumCipher said:
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
Click to expand...
Click to collapse
Acutally its a zip of multiple components not just png's. The bootaniamtion.zip as a whole is what makes up that boot up animation. If you want to change the bootanimation you would replace that entire zip with one that you want. And then set the permissions and reboot. Some will even have a flashable. In order to modify system files you need root and a root explorer. There are multiple on the play store i would recommend Root Explorer if you have the money otherwise ES File Manager or Solid Explorer.

Bricked after wiping with twc
When I look for fastboot devices, nothing happens...
where do I go from here?

http://forum.xda-developers.com/showthread.php?p=35777264
Sent from my Nexus 7 using xda premium

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.

Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit

Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?

Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.

efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?

Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium

not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command

In twrp, it keeps saying starting adb sideload feature

i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!

Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"

Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2

Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium

efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

Messed up mako(Resolved)

I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.

----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
gee2012 said:
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
Click to expand...
Click to collapse
any other suggestions

anoymonos said:
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
any other suggestions
Click to expand...
Click to collapse
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore

gee2012 said:
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
Click to expand...
Click to collapse
ya but no red andriod appeared it just stayed in fastboot mode

anoymonos said:
ya but no red andriod appeared it just stayed in fastboot mode
Click to expand...
Click to collapse
Close CF Auto root, disconnect and reconnect usb and open CF Auto root again and try again.
If that doesn`t work flash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img in fastboot and flash this superSU zip http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip in recovery

I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Do a data factory reset in recovery, wipe cache and reboot. And try rooting again after you enabled usb debugging.

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
PS: If you have no rom/etc due to erasure, you can 'adb push' the zip files to /sdcard while in recovery.

C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
kbeezie said:
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
Click to expand...
Click to collapse

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
Dude why you are flasing a bootloader!

kbeezie said:
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
Click to expand...
Click to collapse
i have folled this link and am syuck at flashing bootloader.http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
basically all i can access is fastboot

This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.

zephiK said:
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
Click to expand...
Click to collapse
thats the problem it wont let me flash anything through fastboot

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
Do a data factory reset/ wipe cache in recovery and reboot.

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051

gee2012 said:
Do a data factory reset/ wipe cache in recovery and reboot.
Click to expand...
Click to collapse
i dont have a recovery everything got wiped

zephiK said:
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
Click to expand...
Click to collapse
yes proper drivers installed. Just unrooted and relocked old nexus 4 for return and then tried to root and unlock new one and it **** on me

It probably will if you use the proper syntax since you have to tell it which partition.
If you go and grab the TWRP 2.5.0.0 recovery image from their website for mako, you can use the following
fastboot flash recovery nameofrecovery.img
Making sure there are 4 parts as the word recovery is part of the command.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
Thus why you download one and flash. It's nearly impossible to hard brick a Nexus. Just helps not to receive panic. Take a couple breaths and figure out the proper commands.
Sent from my Nexus 7 using XDA Premium HD app

Nexus 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

Nexus 4.4.4 stuck in bootloop logo

Hi guys, my phone is on version 4.4.4 and I tried to root it yesterday on a mac, was able to unlock bootloader, wipe data, but reboot system step is stuck in the 4 colored circle loop. For some reason, a pop up window for android tranfer app on my mac says my device can't connect. I am able to access recovery mode but don't know how to go from there. I tried wiping cache and dalvik and then reboot, but no luck. Please help.
Thanks

If you unlocked your bootloader your personal data got deleted, so there's no important data on the device left, right?
You could try performing a factory reset in the recovery then, maybe this solves the problem

mihahn said:
If you unlocked your bootloader your personal data got deleted, so there's no important data on the device left, right?
You could try performing a factory reset in the recovery then, maybe this solves the problem
Click to expand...
Click to collapse
Yes, I did wipe data/ factory reset, then reboot device. However, its still stuck in bootloop with the 4 colored circles. Any other solutions?

kirastrike said:
Yes, I did wipe data/ factory reset, then reboot device. However, its still stuck in bootloop with the 4 colored circles. Any other solutions?
Click to expand...
Click to collapse
Try flashing the factory image which you can download from the Google servers. Just connect the phone in fastboot mode and run the flash-all.sh
Maybe you have to fix the connection problem first, but I have no idea how to do this on a mac. If you'd have access to a windows/Linux computer it might be easier, or you have to wait for another guy here who knows how to fix that on a Mac

mihahn said:
Try flashing the factory image which you can download from the Google servers. Just connect the phone in fastboot mode and run the flash-all.sh
Maybe you have to fix the connection problem first, but I have no idea how to do this on a mac. If you'd have access to a windows/Linux computer it might be easier, or you have to wait for another guy here who knows how to fix that on a Mac
Click to expand...
Click to collapse
Okay, so I'm on a windows xp computer. I downloaded the factory image from Google, put the the necessary img files in the same directory in C drive. How do i run flash-all from windows. Also, when I open a command prompt and type fastboot devices, it says fastboot is not recognized?

kirastrike said:
Okay, so I'm on a windows xp computer. I downloaded the factory image from Google, put the the necessary img files in the same directory in C drive. How do i run flash-all from windows. Also, when I open a command prompt and type fastboot devices, it says fastboot is not recognized?
Click to expand...
Click to collapse
Do you have fastboot installed? Google 15 second adb install xda.
To flash the flash-all.bat just double click on it. It will wipe your device so backup of you need to
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Do you have fastboot installed? Google 15 second adb install xda.
To flash the flash-all.bat just double click on it. It will wipe your device so backup of you need to
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
thanks jd. finally figured it out and flashed factory image. Phone is finally booted and up running again. Now time to try to root again ahaha

kirastrike said:
thanks jd. finally figured it out and flashed factory image. Phone is finally booted and up running again. Now time to try to root again ahaha
Click to expand...
Click to collapse
no problem man. Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
no problem man. Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hey jd, I'm trying to root but I can't seem to fastboot CWM img. I did put the CWM file into the same directory as the fastboot.exe file. When I opened up a command prompt to fastboot the img, it says "it cannot load the file, no such file or directory." Any ideas as to what this might be?
Thanks

Are you using
fastboot flash recovery cwm.img. Where cwm.img is the cwm image
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you using
fastboot flash recovery cwm.img. Where cwm.img is the cwm image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I renamed it to custom recovery.img and typed in the command prompt what you have above, but it can't find it

kirastrike said:
Yes, I renamed it to custom recovery.img and typed in the command prompt what you have above, but it can't find it
Click to expand...
Click to collapse
Did you open a command prompt on that folder? Go to the folder and then in an empty area shift, right mouse click, open a command prompt here
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you open a command prompt on that folder? Go to the folder and then in an empty area shift, right mouse click, open a command prompt here
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I did open a prompt on the folder that the cwm img was in.

kirastrike said:
Yes, I did open a prompt on the folder that the cwm img was in.
Click to expand...
Click to collapse
Try this
fastboot flash recovery recovery.img.img
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:48 PM ---------- Previous post was at 07:41 PM ----------
jd1639 said:
Try this
fastboot flash recovery recovery.img.img
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Wait, you renamed custom recovery.img? You can have the space in the file name
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try this
fastboot flash recovery recovery.img.img
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:48 PM ---------- Previous post was at 07:41 PM ----------
Wait, you renamed custom recovery.img? You can have the space in the file name
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, I named it back to custom recovery no .img and got it to flash. Thanks

kirastrike said:
No, I named it back to custom recovery no .img and got it to flash. Thanks
Click to expand...
Click to collapse
Good job!
Sent from my Nexus 5 using XDA Free mobile app