Hi
Few days ago i wanted to install ADB to flash new ROM to my phone, bu trying to install ADB software i get the following error:
"Error during execution "install.bat". The system cannot find the file specified."
Does anyone know how to fix it?
Would really appreciate it.
BR
Yipers
yipers said:
Hi
Few days ago i wanted to install ADB to flash new ROM to my phone, bu trying to install ADB software i get the following error:
"Error during execution "install.bat". The system cannot find the file specified."
Does anyone know how to fix it?
Would really appreciate it.
BR
Yipers
Click to expand...
Click to collapse
It would seem the file is missing install.bat or something inside install.bat is wrong? My best suggestion to you is get nexus root toolkit. It comes with and cmd adb launch thingy and it saves a lot of time fafing. Just us that. Hope I helped
Related
Im getting Parse Error when Im trying to install some .apk... I also tryed download the file again, but unsucessfull...
Where is the problem? a corrupted file? wrong app version in a wrong ROM version?
Sorry... my english is so poor...
Thanks!
Can you give more details. Did you download it from the market or somewhere else? What are you using to install it? What are you trying to install.
supremeteam256 said:
Can you give more details. Did you download it from the market or somewhere else? What are you using to install it? What are you trying to install.
Click to expand...
Click to collapse
No... All the apps installed from the market is OK. Im tryng to install the PDFViewer.apk following the instructions mentioned in some thread here in XDA forum... but I had some problems with anothers detached apps... (ex: com.acme.android.powermanagerpro.apk)
How are you trying to install it? Are you using ADB or an app installer?
eoeAppInstaller... some many apps installs without a problem. others nope!
Do you have "allow install of non-market applications" checked under application settings.
supremeteam256 said:
Do you have "allow install of non-market applications" checked under application settings.
Click to expand...
Click to collapse
Yes,.I have a lot of non-market apps installed from this appinstaller.
Thats why Im thinking in whats wrong...
Im trying to install mainly PDFViewer... as mentioned in
...showthread.php?t=515340
What happens when you type your commands in terminal emulator. Do you get an error in there.
What's the specific error? While installing the apk, monitor logcat's output for any specific messages.
Try AppManager or AppsInstaller and see if that solves your problem. You can install apps with these as well.
All commands in terminal was done with success following the PDFViewer thread... no errors are presented.
But... When I try to install the PDFViewer.apk with appinstaller, a message appears...
Parse Error
There is a problem parsing the package
(again: my english sux, plz dont piss in my mouth).
just install the pdf viewer the same way you installed the others.
supremeteam256 said:
just install the pdf viewer the same way you installed the others.
Click to expand...
Click to collapse
Thats it... im trying to install like any other apps and im getting this error with eoeAppInstaller.
Code:
[B]Parse Error[/B]
There is a problem parsing the package
...
In the AppManager I can't see .apk files on my SD card... sounds strange...
---
Did you check logcat while installing the package? (adb logcat from terminal/command line) Logcat is more likely to contain specific info about why the install failed rather then a generic error message.
A problem parsing the package sounds like it can't unpack the AndroidManifest file, have you checked md5 sums of your downloads?
zer0day said:
Did you check logcat while installing the package? (adb logcat from terminal/command line) Logcat is more likely to contain specific info about why the install failed rather then a generic error message.
A problem parsing the package sounds like it can't unpack the AndroidManifest file, have you checked md5 sums of your downloads?
Click to expand...
Click to collapse
That most likely the exact problem. I posted in the relevant thread where your first reported the problem;
"Like what has been said before in this thread, try downloading it on your PC and transfering it over your usb cable. It sounds like you apk file is corrupt."
Hey guys.
I've been searching this damn problems all day and cant find a straight forward solution i can use so i resort to asking you guys for help. Im sorry if the solution is easy but i just cant seem to get it.
I was trying to unlock the bootloader today. So i downloaded the SDK and got an unlock code. But then the problems begin. First i missed AdbWinApi.dll. I relocated the file so Fastboot.exe would work. But now it does something and closes up in an instant.
How the hell do i make the screen stay open to enter commands?
Thanks in advance guys.
fastboot has to be done via CMD sounds to me like your double clicking on it.
Cant give you more info than that really out of not wanting you to brick your device, if your struggling to use fastboot to unlock you should think twice about doing it.
also just to add there is NO advantage right now in unlocking the device.
Aightu said:
Hey guys.
I've been searching this damn problems all day and cant find a straight forward solution i can use so i resort to asking you guys for help. Im sorry if the solution is easy but i just cant seem to get it.
I was trying to unlock the bootloader today. So i downloaded the SDK and got an unlock code. But then the problems begin. First i missed AdbWinApi.dll. I relocated the file so Fastboot.exe would work. But now it does something and closes up in an instant.
How the hell do i make the screen stay open to enter commands?
Thanks in advance guys.
Click to expand...
Click to collapse
Yep i've noticed the same thing, there seems to be a .dll missing in the sdk, now worries though, download this fastboot package, i used it to unlock my bootloader
http://www.multiupload.com/BMJ24IL6XY
waz000000 said:
fastboot has to be done via CMD sounds to me like your double clicking on it.
Cant give you more info than that really out of not wanting you to brick your device, if your struggling to use fastboot to unlock you should think twice about doing it.
also just to add there is NO advantage right now in unlocking the device.
Click to expand...
Click to collapse
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Aightu said:
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Click to expand...
Click to collapse
No not at all!
Simple download gingerbreak and root it with that go to market download root uninstaller and off you go.
You change DIR like this:
hold shift and right click on the folder containing the tools select open command prompt here. but please dont do it! not until youve read a lot more.
There is no need right now to unlock the bootloader. Wait for custom roms possibly the weekend i may have a go at a kernel overclock but that's if i get the time wolves are playing sunderland.
Aightu said:
I am double clicking it because i cant figure out how to run it via CMD. I cant change directory in the CMD. I thought the only way to remove bloatware was to unlock bootloader?
Click to expand...
Click to collapse
to change directory in a command prompt, use the cd "directory location" command or cd .. to go back a folder
AndroHero said:
to change directory in a command prompt, use the cd "directory location" command or cd .. to go back a folder
Click to expand...
Click to collapse
Ok i finally got the CMD thing running. It just keeps saying: Waiting for device. Ive re-installed the drivers but it still cant really connect. Phone does go into fastboot mode. Anyone got any idea? Because else im just gonne try another laptop.
Fixed, used wrong driver.
Note that the android_winusb.inf file provided by SE is a quick hack (do a diff of both versions to appreciate the workmanship..)
In particular, it will not work as it is on Vista or Windows 7 with AMD x64 CPUs.
To fix it, you'll have to open the .inf file in a text editor, and copy the "; SonyEricsson" line and the 3 lines that follow under the "[Google.NTamd64]" section.
Save it, replug your phone with the search key pressed, and windows should finally be able to accept the driver.
After rooting with SuperOneClick, I tried to install TWRP using the direction on their site (teamw.in/project/twrp2/79) but I keep running into the error of fastboot not found even though the fastboot.exe file is in the same folder adb.exe. Image attached.
Then, I tried to install TWRP though KF Utility by running the run.bat, but that also returned an error. Attachment 2.
Any help would be appreciated.
First screen is saying it can't find the fastboot.exe command
the second is saying that it can't find another command. both have been reported and responded to in the thread where the script is posted and discussed.
Thanks for the help. Have to dig through the thread page by page until I found it at page 15.
For anyone who has similar problem, follow this post http://forum.xda-developers.com/showpost.php?p=20514394&postcount=145
ch0mch0m said:
After rooting with SuperOneClick, I tried to install TWRP using the direction on their site (teamw.in/project/twrp2/79) but I keep running into the error of fastboot not found even though the fastboot.exe file is in the same folder adb.exe. Image attached.
Then, I tried to install TWRP though KF Utility by running the run.bat, but that also returned an error. Attachment 2.
Any help would be appreciated.
Click to expand...
Click to collapse
There seems to be a problem with your PATH variable. Which windows are you running?
my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.
Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Thanks.
I've installed TWRP 3.1.1-0, but when I use your software it says "error: no devices/emulators found", even if I put the correct cust path
persona78 said:
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Click to expand...
Click to collapse
Hi
After an update (official!) I re-encountered BALONG. After using your marvelous tool, it worked again, but there's no need to reset device (as written on CMD).
In addition, for the ones that get the error "no device attached" or something similar, you've only to reboot to TWRP, connect the phone to Windows and press Win+X, click on "device manager", look for "android device" or something similar. Right click on it and select "update driver", click the second option and than select that you already have the CD driver. You'll see a list: select "ADB composite device" and than finish: you've done!
Ah, I was about to forget: thank you!
Regards,
F
fixed
Hi.
Thanks for fast answer. I could fix the problem.
I downloaded the EMUI 3.1 as Magyar Telekom firmware from an arabic server cause ru huawei servers doesnt work lol. So I downloaded it I extracted boot, recovery, system, cust img files from UPDATE.APP with Huawei AppImage Extractor application. I flashed these with fastboot (Not TWRP, not huawei recovery). Fastboot from computer. Ok. But at the moment SIM does not work. I upgraded the system from Huawei update from settings (not recovery, system settings). After update the ROM and SIM is work perfectly.
Btw thanks your answer, topices too. This is a big help from you.
Have a nice day, Balázs.
How Can i use it for Meanaf Localization ????
How Can i use it for Meanaf Localization ????
@persona78
can you provide me Tool To fix Balong
Countryakistan
Mobile:ALE-L21
ROM:C185
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
-Mouhammad said:
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
Click to expand...
Click to collapse
Which Cust Path Do you Want?
hw/meafnaf?
MohmmadUzairKhan said:
Which Cust Path Do you Want?
hw/meafnaf?
Click to expand...
Click to collapse
The program detected this path : cust/hw/meanfaf
Is this what you mean?
-Mouhammad said:
The program detected this path : cust/hw/meanfaf
Is this what you mean?
Click to expand...
Click to collapse
What Do You Want?
hw/eu?
MohmmadUzairKhan said:
What Do You Want?
hw/eu?
Click to expand...
Click to collapse
Do you know what cuases this error?
Thank you its working excellent . And wipe is not needed. Tnx again ?
pls say me
how can i fix it with opened bootloader? must i flash cast?
Doesn't work. Did everything by the instructions. Twice.