Database Users

Cannot get fastboot working in command line (win 7)

Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed

scotty7910 said:
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
Click to expand...
Click to collapse
are you in the same folder that the FASTBOOT.EXE is in when you run the command???

Make sure your running CMD as administrator. You can tell by the path that shows when cmd is launched. If its a regular user account it will path to something like: c:\users\"your username"\
If your running as admin it will path to something like: c:\windows\system32
Sent from my MB860 using XDA Premium App

Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.

beatphreek said:
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
Click to expand...
Click to collapse
Another handy thing is to open the folder then hold the shift key and then right click. You'll have an "Open command window here" option.

Yep I use that all the time...

used both the suggestions in here and still having trouble,can do the root of c folder,use the dir command see it is all there but the cd C:\fastbootpackage brings the same response again.Can anyone see where I am going wrong?Once the command line changes to fastboot what do I need to command?Phone is still attached (as per the guide I am following?)showing 100% phone needs manually rebooted.
I have all latest drivers on win 7 64bit and I am definetely running cmd as an administrator
Also as the third suggestion suggests if I open the cmd box from the folder what is the exact command to use from there?Is there an alternative to doing this as I am beginning to struggle?

Unlock your Bootloader
1. You need to download and install RDS lite on your PC:http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and extract IHOP_Bell.rarhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1136261&v=1&libid=1311795928774&out=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997&title=%5BPUDDING%5D%20International%20House%20of%20Pudding!%20(Unlock%2Froot%20thread)%20Updated%20July%2023%202011%20-%20xda-developers&txt=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar
3. Download and extract Fastboot tools http://gititbit.ch/FAST
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM*card*for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone*reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a.On Windows, press Start and type “cmd” then press the enter button
17.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example:* cd C:\Users\Kenneth\Desktop\fastboot-package)
a.cd*your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a.Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a.fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a.fastboot oem unlock ####
b.fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
This is the guide I have been using, thanks again

scotty7910 said:
"this is not an internal or external command"
Click to expand...
Click to collapse
This msg will only show if you are in different folder than your fastboot. You don't need to run cmd as administrator. The best thing to do is:
copy those 3 files (AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe) to your main c:\ (do not put to the folder)
Run cmd and type "cd \" this will move you to c:\
Now type fastboot and press enter - you should see various commands that can be used. (your mobile doesn't need to be connect to your pc to see this)
Now you can continue with unlocking. If you applied ihop.sbf already then startt from step 18.
I'm 99% sure that you were in the wrong folder.

Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?

scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Don't use the Rom Manager app. It sucks and doesn't work properly. Do things properly.
With XDA forum members there's no reason to do things half assed. Use your hole ass, dammit.

scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Well if you came that far then try to install tenfar's recovery, download this file :recovery-en-goapk-0630-1029.zip Unzip and move recovery-en-goapk-0630-1029.img to your c:\....Now reboot your phone and enter to fastboot mode. In cmd go to c:\ and type "fastboot flash recovery recovery-en-goapk-0630-1029.img" and then "fastboot reboot" DONE
If you have any problems try to download moto-fastboot (http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440). It's kind of the same thing as fastboot and to be honest I don't know what's the different between both (I think moto-fastboot is designed for 2.3.4 firmware). Extract zip and move moto-fastboot to c:\ and type the same command but instead of fastboot type moto-fastboot. I hope this make sense.
Also it's recommended to delete "install_recovery.sh" which apparently is in /system/etc/ BUT I never managed to find this file and I just ignored this step.

thanks foka, but I have already tried and tried again unsuccessfully to use tenfars cwm.I can install the recovery and delete the sh file all as normal using fastboot and astro.However for some reason there seems to be no way I can get into cwm having flashed it.when I attempt it I dont see the same menu I could scroll through as before.Then I tried a cwm of tenfars that was supposed to flash through rom manager.Again the flash went fine but could not seem to enter recovery mode.I see you installed aura 1.1 didi you flash a radio afterwards?My signal is comnstantly 1 bar.Could you reccomend a uk radio?

Well Ive flashed at&t radio N_01.77.30p which solved battery draining and 1 bar issue. I'm not sure why you can't use cwm recovery...
Sent from Motorola Atrix

What do you mean you don't see the same menu as before? When you hold volume down, power up phone, fastboot, scroll through the list and none of them say Android Recovery?

[Q] boot logo brick (?) [SOLVED]

i'm VERY new to all of this, and i promise i tried my hardest to find an answer in existing threads and google, but haven't found anything to help with my prob:
I tried (?) to root kindle fire [android police thingy], not sure if I succeeded or not (had a lot of "device not found" at the beginning) and tried to install RTL languages support at the same time.
I haven't installed any "TWRP" or "firefirefire" or anything like it.
after the reboot at the end of the RTL, the kindle got stuck on "kindle fire". I tried 20 second power button for several times, on and off power.
kindle fire utlity ("run") says:
adb status: online
adb rooted: no
boot status: 4000
when trying to root through this (temp root), i get: adbd cannot run as root in production builds.
I get the same phrase trying to do anything on the utiility.
Can I do anything to save this from being a 200$ coaster?
THANKS!

you can try to install fff and twrp with kfu (option 5)
then copy one of the prerooted stock images to sdcard:
http://forum.xda-developers.com/showthread.php?t=1402440
would recommend the secure one
and install with twrp:
http://forum.xda-developers.com/showpost.php?p=20543289&postcount=47

imageshack. us/photo/my-images/515/brickc.jpg/
(delete spaces)
i get about the same thing for every option i choose.
any other option?
(and THANK YOU for answering so quickly)

open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back

b63 said:
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
Click to expand...
Click to collapse
$ sign.. (waiting does nothing, "enter" produces yet another $ sign :X )

that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing

b63 said:
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
Click to expand...
Click to collapse
the kf is on 6.2.1 and the kfu is 0.9.2.
img521.imageshack .us/slideshow/webplayer.php?id=brick2m.jpg
(again, delete space)
on the first attempt with no. 5, it started downloading something but my internet went bad and the dl stayed on 52%. I manually downloaded the file and named it "recovery" (in the correct folder). after that, i got the message in "brick 3"
and another thing - even though i keep getting "adb rooted: no", after each time i "root", the device reboots, but it doesn't reboot after the "installation" of the twrp.

that with the recovery was right - it has to be recovery\recovery.img
the file should be ~10mb - maybe we have to do it manually
the problem is that burritoroot is allready installed and kfu can't gain root
you did not install burritoroot with kfu ? (kfu has a special version)
therefor we get the message "... can not run on production builds"
now we can look where the file is located and install with kfu or
install fff and twrp manually
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
second twrp manuell:
•copy recovery.img which you downloaded and renamed to the folder where adb.exe & fastboot.exe is located
•install with "fastboot -i 0x1949 boot recovery.img"
now we reboot into recovery:
•"fastboot -i 0x1949 oem idme bootmode 5001"
•"fastboot -i 0x1949 reboot"
now we should have the recovery system installed ...

b63 said:
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
Click to expand...
Click to collapse
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)

RYuval said:
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
Click to expand...
Click to collapse
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above

b63 said:
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
Click to expand...
Click to collapse
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )

RYuval said:
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
Click to expand...
Click to collapse
that's quite normal
what say your device manager about adb or kindle ?

b63 said:
that's quite normal
what say your device manager about adb or kindle ?
Click to expand...
Click to collapse
until recently, "adb android device" or something like that..
now it says the driver does not suit 64bit... (currently: unknown USB device)

it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
for information in device manager:
normal boot (4000) -> android composite adb interface
fastboot (4002) -> android adb interface

b63 said:
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
Click to expand...
Click to collapse
for some reason, that still doesn't work..
and the driver was properly installed earlier..

RYuval said:
for some reason, that still doesn't work..
and the driver was properly installed earlier..
Click to expand...
Click to collapse
for normal boot - have you ever been/worked in/with fastboot mode ?
we have to get the right drivers for every mode working
i just switched my kf to fastboot and return to normal boot to verify
try to update the driver manually (select manually)
alternately you can delete every driver with kindle or adb and then unplug and replug the kf
that' only a loose description that you see how it is done:
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay

will be updated (drivers installed.) the name's without "composite"

if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver

b63 said:
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
Click to expand...
Click to collapse
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..

RYuval said:
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
Click to expand...
Click to collapse
device not found on what command ?
your on an elevated command prompt (as administrator) ?
fastboot -i 0x1949 getvar product
it should return "kindle"

Stuck in TWRP? ADB won't recognise device? Try this!

I was one of those sorry suckers that somehow got my Kindle Fire stuck in TWRP and I couldn't reset the bootmode to normal. ADB wouldn't recognize the Kindle while it was in TWRP no matter what I tried. Here's how I got it booting again.
1. Download Kindle Fire Utility here.
2. Unzip and open a command prompt in the "tools" folder inside of the unzipped kindle fire utility folder. Do this in Windows 7 by double clicking on the KFU folder and then doubleclick on the tools folder. Next find an empty space in the folder and hold down "shift" on your keyboard and then click your right mouse button. Select "Open command window here".
3. Type in this command and hit enter:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
When that properly executes it will say < waiting for device >
4. On the Kindle Fire inside of TWRP select Reboot -> System.
5. During the reboot process the fastboot command will execute and set you back to normal mode. Now type this in your command window on your computer and hit enter:
Code:
fastboot -i 0x1949 reboot
That ought to do it for ya.
*edit* Wish I could change the title somehow. I misspelled "recognize"

Thank you!!! it worked perfectly. I think this happened because once in the ICS rom I select to reboot into recovery using Room Manager and got stuck on it (bootmode 5001). Anyway this solved the problem in a blink!

You rock!!!! took me two days to find this post..... ugh

Kafluke said:
Wish I could change the title somehow. I misspelled "recognize"
Click to expand...
Click to collapse
LoL...just tell everyone you're British

[Q] HD2 don't see of the pc when in fastboot mode (menù of clk)

Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks

g.andy said:
Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks
Click to expand...
Click to collapse
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english

AladdinSy said:
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english
Click to expand...
Click to collapse
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery (the new version have twrp) and it is possible only with fastboot
I have unstalled fastboot driver(download with sdk), infact ADB work great, but fastboot don't see the telephone
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2

g.andy said:
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery
Click to expand...
Click to collapse
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!

kokotas said:
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!
Click to expand...
Click to collapse
I will try. Thanks.
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2
EDIT:
Thank you all for the advice.
Honestly with ADB from recovery I have not tried but I solved by using another pc with w7. The only thing I do not spego is that with nthe same procedure on my pc does not work while on another it works perfectly.
I'll probably have to change pc.

Installing twrp using powershell

Flashed the factoy image 6.0 fine using the batch file.
But now need to flash twrp, i knew how to do it with a cmd prompt but windows updated to 10 and it's now [email protected]#$% F*&^%#%$ power shell so fastboot doesn't work.
Went into settings and clicked off power shell to switch back to cmd prompt, doesn't work,
So any idea how i can flash my twrp again!
[email protected]#$ windows and their power shell B*^^%$#%.

trsix said:
Flashed the factoy image 6.0 fine using the batch file.
But now need to flash twrp, i knew how to do it with a cmd prompt but windows updated to 10 and it's now [email protected]#$% F*&^%#%$ power shell so fastboot doesn't work.
Went into settings and clicked off power shell to switch back to cmd prompt, doesn't work,
So any idea how i can flash my twrp again!
[email protected]#$ windows and their power shell B*^^%$#%.
Click to expand...
Click to collapse
Cmd should be here
C:WINDOWS\system32\cmd.exe
You don't have it?

you cant use powershell for this. try this fix to bring back cmd on context menu https://www.windowscentral.com/add-open-command-window-here-back-context-menu-windows-10?amp

Tool
Fixed.
Used hard91's tool
https://forum.xda-developers.com/moto-g4-plus/development/motorola-moto-one-tool-v1-0-t3397163

trsix said:
Flashed the factoy image 6.0 fine using the batch file.
But now need to flash twrp, i knew how to do it with a cmd prompt but windows updated to 10 and it's now [email protected]#$% F*&^%#%$ power shell so fastboot doesn't work.
Went into settings and clicked off power shell to switch back to cmd prompt, doesn't work,
So any idea how i can flash my twrp again!
[email protected]#$ windows and their power shell B*^^%$#%.
Click to expand...
Click to collapse
Right click on start button, click cmd as administrative, direct to file loaction and you are set to flash.

nope
That"s ok if you know what to type for directory etc but a lot of people don;t
was easy when you could shift/mouse click to open the cmd box in the adb folder

DgnrtnX said:
Right click on start button, click cmd as administrative, direct to file loaction and you are set to flash.
Click to expand...
Click to collapse
With the latest Win10 update, that brings up PowerShell. You have to type cmd in the search box to open a command window.

lmacmil said:
With the latest Win10 update, that brings up PowerShell. You have to type cmd in the search box to open a command window.
Click to expand...
Click to collapse
The program itself is here, every time, since decades https://forum.xda-developers.com/mo...g-twrp-using-powershell-t3727761/post75019737

Fastboot doesn't work with powershell? Heck I use powershell almost every week flashing kernels, recovery's, etc.

lmacmil said:
With the latest Win10 update, that brings up PowerShell. You have to type cmd in the search box to open a command window.
Click to expand...
Click to collapse
Yes, but thats when only if you turn the option on from task bar or setting itself which refers as 'replace cmd with powershell'. Just turn it off and as i said you are set to go.
---------- Post added at 11:24 AM ---------- Previous post was at 11:14 AM ----------
trsix said:
That"s ok if you know what to type for directory etc but a lot of people don;t
was easy when you could shift/mouse click to open the cmd box in the adb folder
Click to expand...
Click to collapse
Ok so first of all, start cmd then for instance you are set for c drive and your files are in d drive the type "d:", then go to file manager and locate the file Location. Copy the location from address bar and paste it in cmd and cut the drive name from pasted line hit enter.
Type the regular command for flashing twrp and thats it.
---------- Post added at 11:51 AM ---------- Previous post was at 11:24 AM ----------
So there is a lot of confusion with regards with how to use cmd commands
Herr is a guide from YouTube how to replace powershell with cmd in context menu
Link : https://youtu.be/Ro7vJI6qqEU

DgnrtnX said:
Yes, but that's when only if you turn the option on from task bar or setting itself which refers as 'replace cmd with powershell'. Just turn it off and as i said you are set to go.
Click to expand...
Click to collapse
Apparently Poweshell is turned on by default because I never changed it. I have now changed it back. Thanks.

blowingoff said:
you cant use powershell for this. try this fix to bring back cmd on context menu https://www.windowscentral.com/add-open-command-window-here-back-context-menu-windows-10?amp
Click to expand...
Click to collapse
I flashed stock September security patch rom with PowerShell without a single problem by the way