Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
Related
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!
**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"
i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.
You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
has it previously been paired with your computer via ADB ?
3mel said:
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
nogods said:
yes - it shows up as a device with adb
Click to expand...
Click to collapse
hope this works for ya
Factory reset Android using ADB
I am trying to factory data reset my Oppo Neo 7 (Android 5.1) using ADB shell. Any way I can try and link to ADB shell?
android.stackexchange.com
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
try flashing the stock rom from adb/fastboot
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
blackhawk said:
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
Click to expand...
Click to collapse
the pixel 4a doesn't have an sd card
the ADB devices shows the phone's id with "unauthorized" next to it. All ADB commands return this:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
maoriboi said:
try flashing the stock rom from adb/fastboot
Click to expand...
Click to collapse
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
\
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
nogods said:
the pixel 4a doesn't have an sd card
Click to expand...
Click to collapse
Yes I know. Keep that in mind next time around as it makes life much easier.
All joking aside, sorry to hear about your issues.
AlexKarimov said:
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
Click to expand...
Click to collapse
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
nogods said:
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
AlexKarimov said:
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
Click to expand...
Click to collapse
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
nogods said:
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
Click to expand...
Click to collapse
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
nogods said:
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
Click to expand...
Click to collapse
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
O
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
yup - looks like it worked:
Erasing 'userdata' OKAY [ 15.171s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.158s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 15.797s
What nows "not automatically formating" mean?
nogods said:
O
yup - looks like it worked:
Click to expand...
Click to collapse
Awesome, thanks for the updates. I'm glad you got it going
nogods said:
What nows "not automatically formating" mean?
Click to expand...
Click to collapse
I'm not sure about this, I've never encountered that as far as I know. Did it say "can't determine partition type" after that?
Hi,
I don't see my device both on 'adb' mode or in 'fastboot' mode.
What can I do to see it or put it in either of these modes?
Thanks!
-ChipX
For ADB you obviously need to enable ADB debugging from the developer settings or to be in a recovery with ADB enabled. For Fastboot you need to be in bootloader mode (fastboot).
If your device is not recognized in either of these, check your drivers/cable/USB port.
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
ChipX8 said:
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
Click to expand...
Click to collapse
Try updating your SDK platform-tools. They may be out of date.
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
OzBoy1 said:
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
Click to expand...
Click to collapse
That's why sometimes it's a better idea to run the adb/fastboot commands from CMD versus PowerShell (CMD shouldn't need "./") -- I'm assuming you're using windows as Linux & Mac OS require the ./ regardless...
I'm sure platform tools needs to be updated (for the OP), but 2 things to keep in mind is to be sure not to be using anything like "minimal adb and fastboot" and there has been reported issues on the updated platform tools (r34), so maybe there's that to consider...
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
HipKat said:
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
Click to expand...
Click to collapse
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
xunholyx said:
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
Click to expand...
Click to collapse
I can't seem to find where OP is specifically using fastbootd versus regular ol' fastboot mode...
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
simplepinoi177 said:
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
Click to expand...
Click to collapse
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Lughnasadh said:
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Click to expand...
Click to collapse
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
Yeah, I've never needed admin privileges when using command prompt for any flashing I've done so it works fine for me.
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
HipKat said:
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
Click to expand...
Click to collapse
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
simplepinoi177 said:
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
Click to expand...
Click to collapse
Exactly. Now if Windows stopped making me go in and retoggle Run as Administrator after every update... >: