Database Develop

[Q] W7 wont recognise phone when in fasboot mode

I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj

tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?

ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj

tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.

mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.

Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app

alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj

tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader

alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj

tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above

clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj

tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it

Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>

tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.

d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj

tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk

One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj

tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053

Yeah , sorted.
Thanks again for all your help.
tj

Alternate root method for Nexus 6? CF-Auto-Root gives nothing but issues.

I could never get CF-Auto-Root to properly work with my Nexus 5. I could get the script to launch but I always get this error:
downloading 'boot.img'... ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
I'm now experiencing the same issue with my Nexus 6. I'm convinced it's an issue with my computer, at this point.
With the Nexus 5 on Lollipop the alternate method is simply to flash a modified boot image, flash TWRP, then install the SuperSU zip. I'm looking to see if there is a similar method for the Nexus 6.

Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.

The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.

Pilz said:
Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.
Click to expand...
Click to collapse
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
eep2378 said:
The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.
Click to expand...
Click to collapse
Very true. I'll just enjoy the phone for now and wait it out.

That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work

Pilz said:
That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work
Click to expand...
Click to collapse
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?

sn0warmy said:
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?
Click to expand...
Click to collapse
2.27 is the latest beta and is a significant change since it doesn't patch the kernel. However it is a BETA and not 100% stable...but I think Chainfire will release it fairly soon (next few days).

Try the toolkit. ??

nexus6R3plicant said:
Try the toolkit. ??
Click to expand...
Click to collapse
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.

sn0warmy said:
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.
Click to expand...
Click to collapse
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go

nexus6R3plicant said:
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go
Click to expand...
Click to collapse
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.

sn0warmy said:
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.
Click to expand...
Click to collapse
Why not just pull the image file and fastboot-mac binary from the zip and run this in the terminal.
Code:
fastboot-mac boot <image>.img
Where <image> is the name of the image file.
Should work as long as they are in the same directory.

Wugs nexus root toolkit is updated and works fine

I gave in and installed Parallels back on my Mac and used Wug's toolkit, which worked perfectly. I typically hate using toolkits because I think it's best to always know ADB and Fastboot commands. But in this case, it did the job for me.
Thanks guys!

sn0warmy said:
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
Very true. I'll just enjoy the phone for now and wait it out.
Click to expand...
Click to collapse
Did you get a fix for this issue?
I'm getting the same error.
I unlocked my bootloader by running a separate command. do i need to relock the bootloader and run the script again.
I hate to lose all of my info

I found the issue to the error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
Looking at the errors and in the script, the script is looking for the a specific folder structure.
After extracting the chainfire package as instructed, I created two folders that I needed (your folder may differ).
I'm using Ubuntu should work for any other linux.
May work for window, but i don't know.
Folder structure is such, my folders are on my desktop ubuntu.
~/Desktop/Nexus6/tools
here should be the fastboot-linux file that is part of the package
~/Desktop/Nexus6/image
here put the CF-Auto-Root-shamu-shamu-nexus6.img file for rooting
~/Desktop/Nexus6
here should be the script root-linux.sh
I ran the script and now have root no issues with any errors.

Need help with ADB

Greetings,
Apologies if this has been asked somewhere else before, but I haven't found it anywhere after hours of searching. I've been trying to get ADB to work on my Kindle Fire HD 7 with no success. I've downloaded many drivers and the Android SDK and Android Studio as well. After installing all different drivers, when I connect the tablet to the laptop and test fastboot connection, I get the following:
C:\android-sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
I believe this is expected when I run this command, which I guess means the fastboot cable is working and perhaps the driver too? (not sure). However, when I run the following ADB commands this is what happens:
C:\android-sdk\platform-tools>adb devices
List of devices attached
(this comes empty, no result)
C:\android-sdk\platform-tools>adb shell
error: device not found
error: device not found
I've tried this in two different laptops and I get the same result on both. Both laptops are running Windows 7 and my tablet is currently running version 7.5.1. Any help would be greatly appreciated. And thanks in advance.

jbomxda said:
Greetings,
Apologies if this has been asked somewhere else before, but I haven't found it anywhere after hours of searching. I've been trying to get ADB to work on my Kindle Fire HD 7 with no success. I've downloaded many drivers and the Android SDK and Android Studio as well. After installing all different drivers, when I connect the tablet to the laptop and test fastboot connection, I get the following:
C:\android-sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.002s
I believe this is expected when I run this command, which I guess means the fastboot cable is working and perhaps the driver too? (not sure). However, when I run the following ADB commands this is what happens:
C:\android-sdk\platform-tools>adb devices
List of devices attached
(this comes empty, no result)
C:\android-sdk\platform-tools>adb shell
error: device not found
error: device not found
I've tried this in two different laptops and I get the same result on both. Both laptops are running Windows 7 and my tablet is currently running version 7.5.1. Any help would be greatly appreciated. And thanks in advance.
Click to expand...
Click to collapse
ADB doesn't work in fastboot mode,only fast boot commands do
Sent from my GT-i9100 running CM11

SafinWasi said:
ADB doesn't work in fastboot mode,only fast boot commands do
Sent from my GT-i9100 running CM11
Click to expand...
Click to collapse
LOL, THANK YOU SO MUCH! I can only LOL. I thought the ADB commands had to be run in Fastboot mode. No wonder. IT WORKS!!! Thanks again!!!

unknkown oem command

Hey folks, long time xda user heavy search user results in minimal posts..
ok here we go.
I unlocked bootloader and rooted device with magisk now im attempting to re lock my boot loader.
i factory reset device and flashed google factory image with supplied zip file from google
command im using is
"fastboot oem lock"
results
C:\Users\RyeMc>fastboot oem lock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
this is first lines from google factory image...
Sending 'bootloader' (8761 KB) OKAY [ 0.253s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
next i opened cmd and entered
"fastboot flash boot" then went and moved boot file into cmd window and said successful also tried boot_a and boot_b
unsure why i have tried to re download sdk manager android studio and input the file locations in the path under advanced settings.
albeit iv been out of the root game for a couple years made the mistake of getting a note 8 so i was stuck in that eco system.
some help or advice would be nice thanks.
before i rooted i made sure i was able to lock and unlock bootloader .

Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk

Thaiban said:
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
device is currently unlocked looking to relock device..

the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.

uicnren said:
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
Click to expand...
Click to collapse
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.

RyeMcFly17 said:
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
Click to expand...
Click to collapse
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.

uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
What he said! :laugh:
Easier Windows choice : r29.0.6

download the latest platform tools and extract it, in the folder with the PT files in the top search bar type cmd and then try.

oem unlocking already unlocked
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.

RyeMcFly17 said:
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
Click to expand...
Click to collapse
:good::good:
glad you got it sorted.

Rooting guidance, adb not seeing phone.

Hello all! Im scyyie and ive been a long time lurker on XDA for maybe 5 years or so.
Its been a while since ive rooted an android but im having some trouble in the process once i use cmd to flash the patched .img file. Let me explain and hopefully someone can eli5 lol.
information on my situation:
Razer Phone 2
android ver 9
kernel ver 4.9.112
build P-MR2-RC001-RZR-190914.3123
security update is Sept 25th 2019 i believe.
debugging is enabled.
OEM is unlocked.
I followed the user guide on xda to where I successfully unlocked bootloader, used magisk to patch an .img file matching my exact build (listed above). seems all good right? just flash the patched file i think? Well, my issue is when i turn off my phone, then hold volume down + power, i come to the bootloader/fastboot menu (i think its called?). I start adb shell with CMD prompt, with my patched .img in the same directory, and type "fastboot flash boot_a patched.img" but it hangs there and gives me this: Sending 'boot_a' (20780 KB) FAILED (Write to device failed (Unknown error)) fastboot: error: Command failed
When my phone is on, i used adb shell to use the command "adb devices" and my phone is listed with its serial. The issue (i think?) is when i put my phone into fastboot, adb doesnt detect it. I have installed the appropriate drivers i believe?
Yes i have searched for other guides on this issue but it seems none of these solutions will help. I have also tried installing samsung drivers as well. Im not tech illiterate but hopefully the issue isnt too much of a mystery to the knowledgeable people here.
Thank you all for reading and I hope something can happen here.

solved.
after more research it seems AMD cpus dont agree with this process involving ADB along with usb 3.0 causing an issue as well. I used a usb 2.0 on an intel laptop and the process worked as normal.