Hi,
I'm trying to root but getting the message 'adb not recongised as an internal or external command, operable program or batch file'. What does this mean? I've installed fastboot/flashmode and z3 drivers via flahstool. Am on UK Generic .98 firmware.
Thanks
Ok did some googling and found it was to do with the paths in windows. Updated environmental variables as per the below:
http://www.google.co.uk/url?sa=t&rc...0_IbQh9eEAUHHz45h5DM6_g&bvm=bv.87611401,d.cGU
So in mine, I've got SDK tools saved down in C:\Program Files\Tools and have set up my variable as ANDROID_TOOLS pointing to there, then ANDROID_PLATFORM_TOOLS pointing to their location in C:\Program Files\Platform-Tools and then set Path as %Path%%ANDROID_PLATFORM_TOOLS%;%ANDROID_TOOLS%
But when I run the rooting tool I now get 'The system cannot find the path specified' then *daemon not running. starting it now on port 537* then *daemon started succesfully* it begins sending files and then get several 'cannot stat' and 'unable to open' messages before the final:
'Error: Seems your kernel / device is not supported /system/bin/sh: data/local\tmp\getroot: not found
I am now on Global Generic firmware .23.0.a.2.93. Model is D6603, not locked to any carrier, and bootloader is unlockable.
Can someone please help? I need to get rooted ASAP as I'm home visting family before the weekend and said to my dad I'd root his phone before I head back to London.
Thanks.
Never mind - solved and now rooted! Absolutely no idea how - something within the extracted version of giefroot tool was extracted further to somewhere else, ran the tool again and it worked!
Related
Hi all,
I'm trying to run kaiser-HardSPLv1 on my system but getting an error. Here's my system info:
Windows XP SP2
AT&T Tilt
ActiveSync 4.5
- AT&T Tilt is connected to USB cable and sync icon is green.
- Extracted kaiser-HardSPLv1 to a folder. Two files are in the archive: kaiser-HardSPL.exe and README.txt.
- I followed instructions as per thread and Readme.txt.
However, when I run the utility I get an error stating that prun.exe is not a recognized program (see attached image). I placed prun.exe and also pput.exe in the same directory as extracted files. When I re-run kaiser-HardSPL.exe prun.exe and pput.exe are deleted.
I also ran tried running from the CMD prompt and double-clicking on the program with same results.
Has anyone else ran into this issue? I tried this on two systems and get the same problem.
Appreciate any feedback. Want to get this working to try the HTC ROM.
Thank you in advance.
-Mike
I was able to figure out the issue for this error. Just incase anyone has a similar issue...
In the registry (HKLM\Software\Microsoft\Command Processor) there's a key called "AutoRun". I have a few commands running from there each time a command prompt is executed. The command that caused the issue was "cd \". If the directory is changed the kaiser-HardSPL is not able to extract whatever files necessary to continue the flash process.
It's an extreme situation but I hope this may help someone.
-Mike
prun error
thanks a lot
Sorry for the extreme 'newbiness' of this question but I needs some help here. I just got a Google ION (32B) which I am currently trying to simply Root.
I have gone through all types of instructions and everyone leads to the same steps of applying the Recovery image through Fastboot, but when I do the steps listed after I put the phone in Fastboot, plugged it in, and run:
fastboot boot recovery-new.img
Nothing happens. I get no such file or directory. I check ADB and the phone reads just fine. I have tried on both a Windows machine - which I was able to install the proper drivers for, and in OSX, but neither will read: $fastboot devices.
What could I be missing or doing wrong. I have referred to the Wiki, Essential reading and Newbie resource
Any insight would be greatly appreciated.
Thanks
http://forum.xda-developers.com/showthread.php?t=529062
http://android-dls.com/wiki/index.php?title=Magic_Rooting
fastboot
You will have to download it seperatly.. try here:
http://android-roms.googlecode.com/files/fastboot-win32.zip
Try enable USB debugging and fastboot devices should work.
If not, your drivers may be loaded incorrectly. Installing HTC Sync usually fixes the drivers I've found.
Download recovery-new.img
Put it in the TOOLS directory of the ANDROID SDK and retry your commando.
Yeah I have actually tried all of those things. I am following the root process to a T but still no luck. Perhaps I am doing some wrong in the command line?
have you set the $PATH variable? you get this:
"I get no such file or directory."
Click to expand...
Click to collapse
error-message. my best guess is that you have forgotten to added the path to where your fastboot tool is located.
try changing the directory to where your fastboot tool is located.
*Fixed*
I really appreciate the help guys, I redownloaded the fastboot.exe, and it read the phone right away. Now to start loading ROMs
Hi all!
I have installed android sdk completely following the guide in stickies,in order to be able to capture screens and to try fixing the superuser fc issue..Installation of sdk/adb went fine,the only difference from the original guide is that there wasn't "Android SDK Platform-tools, revision 5" but newer file called "Android SDK Platform-tools, revision 8".
When I run "adb devices" command,it shows my device and that works fine,but I have encountered 2 problems so far.
1)The first one is that when i try to take screenshoot using ddms I get an error saying "01:53:11 E/adb: Failed to get the adb version: Cannot run program "C:\AndroidSDK\platform-tools\adb": CreateProcess error=2, The system cannot find the file specified" in command prompt,and when DalvikDebugMonitor opens,it pops an error saying "Failed to get the adb version: Cannot run program "C:\AndroidSDK\platform-tools\adb : CreateProcess error=2, the system cannot find the file specified".
2)The second problem I've encountered is that when I tried to fix superuser problem I got this : "C:\AndroidSDK\tools>adb push su /system/bin/adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/bin//su': Read-only file system"
Something doesn't work..My phone is connected in charge mode,usb debugging is checked..Im running ARHD 3.6.2,s-offed & rooted.
Thanks!
jafazec said:
Hi all!
I have installed android sdk completely following the guide in stickies,in order to be able to capture screens and to try fixing the superuser fc issue..Installation of sdk/adb went fine,the only difference from the original guide is that there wasn't "Android SDK Platform-tools, revision 5" but newer file called "Android SDK Platform-tools, revision 8".
When I run "adb devices" command,it shows my device and that works fine,but I have encountered 2 problems so far.
1)The first one is that when i try to take screenshoot using ddms I get an error saying "01:53:11 E/adb: Failed to get the adb version: Cannot run program "C:\AndroidSDK\platform-tools\adb": CreateProcess error=2, The system cannot find the file specified" in command prompt,and when DalvikDebugMonitor opens,it pops an error saying "Failed to get the adb version: Cannot run program "C:\AndroidSDK\platform-tools\adb : CreateProcess error=2, the system cannot find the file specified".
2)The second problem I've encountered is that when I tried to fix superuser problem I got this : "C:\AndroidSDK\tools>adb push su /system/bin/adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/bin//su': Read-only file system"
Something doesn't work..My phone is connected in charge mode,usb debugging is checked..Im running ARHD 3.6.2,s-offed & rooted.
Thanks!
Click to expand...
Click to collapse
Hi,
Did you install Android SDK on the root of your C: drive?
Because,that is where the program will look for it.
malybru said:
Hi,
Did you install Android SDK on the root of your C: drive?
Because,that is where the program will look for it.
Click to expand...
Click to collapse
Hi! Yes, I completely followed the guide several times..ALso read every possible similar thread online that could help me but nothing helped..At last, I reinstalled my Win7x64,and everything worked out,but using a different guide,because this one didn't work again.. Instead of installing javax86&x64, I installed JavaSDK..Now,everything is working properly.
However, thanks for trying to help!
Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files
UntamedDeviance said:
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Do you know if "C:\Windows\System32" is in your Environmental Variables Path? My friend had this problem recently, and for some reason it wasn't in there. We added it to the path, and everything works fine now.
EDIT: Here is a link to a tutorial on how to fix this error: http://helpdeskgeek.com/how-to/fix-not-recognized-as-an-internal-or-external-command/
Might try executing the command from a CMD window set to the directory where the files are as a quick test. I agree with checking the Env. paths too.
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).