Database Info

GUIDE - How to flash radio.img OS X

I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
List of devices attached
HXXXXXXXXXX device
Click to expand...
Click to collapse
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
flash radio
Click to expand...
Click to collapse
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
/Users/Liam/SDK/tools/fastboot flash radio /Users/Liam/SDK/tools/radio.img
Click to expand...
Click to collapse
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
fastboot reboot
Click to expand...
Click to collapse
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.

been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate

steve36 said:
been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate
Click to expand...
Click to collapse
Wrong thread. But the thread you want, and the answer, is here: http://forum.xda-developers.com/showpost.php?p=10113370&postcount=91
Do some searching first..
Anyways, yeah, now I can use my MacBook.

This seems to be an odd way of doing it.
Just download the fastboot-mac binary from the htc developer page. Drop it in the platform-tools folder of the androd SDK.
Start a Terminal and run:
/path/to/platform-tools/fastboot-mac flash radio radio.img
make sure you have radio.img in the current directory where you invoke the script.

I found it easier to drag and drop the files. Saves lots of typing and does the same job.

liam08 said:
I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.
Click to expand...
Click to collapse
Hi i did not notice your guide so i created one last night >>>>here<<<<

I use this:
http://qtadb.wordpress.com/

I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?

P1xelVandal said:
I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?
Click to expand...
Click to collapse
Use my guide downloaded the zip file read all of first post sorted
E=Mc2

leith51 said:
Use my guide downloaded the zip file read all of first post sorted
E=Mc2
Click to expand...
Click to collapse
it's a shame all the files are .exe and .bat *sigh* thanks anyway.

P1xelVandal said:
it's a shame all the files are .exe and .bat *sigh* thanks anyway.
Click to expand...
Click to collapse
localhost:~ Mac$ /fastboot/fastboot-mac flash radio /fastboot/radio.img
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)
localhost:~ Mac$
what am i doing wrong? (no i will not switch to PC))
This guy used my thread his problem was he didn't have eng s-off
E=Mc2

Stuck on htc screen 'flashed wrong rom'

Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.

imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.

I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?

imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.

imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM

Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?

imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img

I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium

imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)

Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!

[Q] Serious problem

Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue

devcager said:
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
Click to expand...
Click to collapse
Access your commands through a terminal window, like start > run > cmd to get into the prompt.
and from there work your way to your directory where you have placed it, and execute the command from that directory directly.

..

Thanks!
In the end I used adb to push backup in recovery...
All this I did because I wanted wipe my device - today I woke up and got a call and found out that my earphone stopped working I am afraid that it is due to condensation and next oxidation... I did not do anything wrong but when you come from cold winter weather into a warm flat it can happen Now I need to send it and hope the warranty will pass..
Anyway, I was looking for complete unroot process and found several advices. I am not clever from them. Is it enough to flash stock ROM? Recovery will be removed as well??

..

Election Day said:
Flash a stock ROM (this will also flash the stock recovery) and relock the bootloader with fastboot oem lock afterwards.
Click to expand...
Click to collapse
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it

devcager said:
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
Click to expand...
Click to collapse
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...

mahanddeem said:
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
Click to expand...
Click to collapse
it works only in "tools" and then it just says "waiting for device" and stucks When I tried "fastboot devices" it says nothing... I tried to reinstall drivers but maybe I have some old version? When I am in Windows copying files etc. it works well.

1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.

albundy2010 said:
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
Click to expand...
Click to collapse
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Fastboot drivers are something else than drivers for adb to be working? Because I dont know whats wrong. Thanks...

devcager said:
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Because I dont know whats wrong. Thanks...
Click to expand...
Click to collapse
If you have i9023 you need to add a line into the sdk for driver. You can search the tutorial threads for it.
Sent from my Nexus S using Tapatalk

try this
just check if you have fastboot and adb on the same folder, when I've rooted mine's got this issue, if cmd report "the command is an external one" simply means there is no such program in the folder you are in
copy both adb and fastboot in tools and platform-tools too, so you can run the command in both folder
cd>desktop > cd android>cd android-sdk> cd tools (then run adb or fastboot)
cd>desktop > cd android>cd android_sdk> cd platform-tools (thr run adb or fastboot)

1. Find out exactly what phone model you have if you don't know already.
2. Do the same for your computers os . Including 32 or 64 bit.
3. Combine that info and search the forum or just Google search. How to install fastboot drivers for phone model in step 1 with the os in step 2.

..

Thank you all. I decided to unroot it and relock it using Odin software which was great and quick. So I am done.... Adb has a lot of problems with drivers, commands, paths. This way was much easier

adb has no issues. User error.

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Maybe you are right. Maybe it was driver problem which I solved and then immediately used odin. Anyway, it is user friendly and I am finally done with what I wanted

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Agreed, but not the user friendliest.
For the OP: Good luck having it repaired!

[Q] I need help with my Nexus 5 with no OS on it.

I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.

1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work

First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.

awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.

The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?

What does the terminal say as an error? And are you running Linux, Mac, or windows?

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.

So just gonna ask again, what message did you get in the terminal?

Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit

After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?

Try adb kill-server then (I'm a little rusty with windows) su adb start-server

experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device

Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)

experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.

sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish

sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..

Thread cleaned.
Let's keep it on topic guys,

Please Help - Stuck in boot loop

Hi All, I hope someone can help.
I got this phone in December, and unlocked it, flashed TWRP and rooted.
My phone automaticly updated and was on version 7.1.2. But Super SU wasnt working anymore.
I tried to boot into TWRP but it was saying somthing like "No command given" when I tried.
I used Skipsoft toolkit to flash the recovery again (What I originally used) and when the phone rebooted, it gets to the Google logo and instantly reboots.
I can get to bootloader, but if I select recovery, it reboots.
Is there anything I can do here?
I did a backup in TWRP before I flashed, its stored on the phone.
Thanks in advance

I would use the tool to go back to stock. Just pick the last Google is the app I believe its V. Either update to the lastest software or I just flashed a rom with the newest vender

Hi, Thanks for your reply.
How can I do this though, I cant get the phone to boot, or into recovery

Is there a way I can use adb to push a TMRP so I can restore my backup?
My PC makes the noise as if something is attached by USB, but when I do adb devices, nothing shows.

Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again

You can get TWRP and root on the May update.
https://forum.xda-developers.com/showthread.php?t=3600606

Anthony2oo5 said:
Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again
Click to expand...
Click to collapse
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.

In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.

graymoment said:
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
X04D said:
In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.
Click to expand...
Click to collapse
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.

Anthony2oo5 said:
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.
Click to expand...
Click to collapse
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.

graymoment said:
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.
Click to expand...
Click to collapse
That error means flash-all.bat is not in the same directory as the command prompt you opened. You unzipped it elsewhere, didn't unzip it or you opened the command prompt in the wrong place.

Flash this file after flash other files
VerifiedBootSigner