Am trying to root an android device and for that I need to run ADB & Fastboot command.
Issue is that, fastboot command is giving an error and it just doesn't make any sense to me. After googling, only suggestion which I found was to update the Android SDK, which I have already done but it didn't solve the issue.
XXX-MacBook-Pro:Documents driftking9987$ fastboot devices
ERROR: Unable to create a plug-in (e00002be)
THere's an open issue with macOs High Sierra. There hasn't been a release of a known working version, but you can download it from the issue tracker itself and I just tests that it works:
https://issuetracker.google.com/issues/64292422#comment8
Download the latest SDK platform-tools worked for me:
https://developer.android.com/studio/releases/platform-tools.html
Related
I'm using Mac mini , MacOs monterey and m1 chip. When trying to setup flutter, it is giving error.
command: flutter doctor
o/p: /Users/admin/Desktop/flutter/bin/internal/shared.sh: line 229: /Users/admin/Desktop/flutter/bin/cache/dart-sdk/bin/dart: Bad CPU type in executable
I have tried below command but it is also not working,
Terminal command: sudo softwareupdate --install-rosetta --agree-to-license
Terminal output:
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
Rosetta 2 update is not available
you have to install rosetta first. In your terminal type:
/usr/sbin/softwareupdate --install-rosetta --agree-to-license
I got this error on MacOs VMware
and finaly I realized that i was downloaded the flutter sdk for arm Architecture, but i need this for x64 (intel) Architecture.
run "softwareupdate --install-rosetta" in the terminal
On macOs accidentally I downloaded arm architecture than x64 version.
Download proper version as per the system requirements.
My mistake was that , I had installed flutter sdk before installing the Rosetta. So that's why it was giving the above error. So, to resolve this, I removed the flutter sdk and installed rosetta first then again installed flutter and it worked properly.
I was working fine with Android Emulator (on Manjaro Linux) a few weeks ago, but after updating software The GUI of Android Emulator is not rendering or anti-aliasing is not working anymore. My apps are displaying horrible texts.
I'm using Hardware-GLES 2.0 for my graphic emulator.
Additional info:
Is there another alternative Android emulator working with Visual Studio Code?
ANSWER: Android Studio's Android emulator is not an efficient emulator, a better emulator is Genymotion.
I had a same problem. Downgrading Android Emulator to lower version solved the issue.
Latest version (before 30.9.5) that I could find was 30.8.4 with build id 7600983.
In order to downgrade firstly you will need to download the emulator. Here are the links for the version 30.8.4:
Linux - https://dl.google.com/android/repository/emulator-linux_x64-7600983.zip
MacOS - https://dl.google.com/android/repository/emulator-darwin_x64-7600983.zip
Windows - https://dl.google.com/android/repository/emulator-windows_x64-7600983.zip
You can also download even older versions here are few alternatives
After downloading the needed version of emulator you will need to unzip it.
The next thing is to replace your current emulator with new one.
Go to your Android Sdk folder (mine was ~/Android/Sdk)
cd ~/Android/Sdk
Rename your
current emulator files folder. mv emulator emulator.bak
Copy new
emulator
cp -r ~/Downloads/emulator-linux_x64-7600983/emulator/ .
Replace package.xml file (otherwise Android Studio will not
recognize your new emulator)
cp emulator.bak/package.xml emulator/package.xml
Restart your Android Studio and Enjoy!
Seems like this issue was fixed with newest major 32 version of Android emulator.
Newest 32.1.6 and 32.1.7 Canary 1 versions behave like the things were before 30.9.5 which broke anti-aliasing completely for me on all Windows devices. I am using Hyper-V so HAXM is not available for me.
Emulators archive: https://developer.android.com/studio/emulator_archive
Yesterday I've created Pixel 3 XL device to test my app on emulator. It was working yesterday but today I'm getting these errors when I try to run my app.
14:58 Emulator: C:\Users\Mert\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
14:58 Emulator: deleteSnapshot: for default_boot
14:58 Emulator: Process finished with exit code 0
for me, I have installed a newer version of HAXM and it worked perfectly
Deleting device from AVD Manager and creating a new one(I created the same one) worked for me
Download the google play version marked in yellow rather google API.
Creating emulator again with image from google play will also make sure reinstallation of HAXM.
I solve this issue within Android Studio SDK Manager, update to a newer version of Android SDK Build-Tools and Intel x86 Emulator Accelerator (HAXM installer), in the HAXM installer wizzard I put 4GB RAM size.
image
In my case I deleted the old devices and downloaded the Google Play play version image and manually changed adb.exe file.
Actually the working HAXM version isn't always the newests, as other answers suggest. I had HAXM version 7.8.0 (latest version ATM) installed on my Windows, but even though I was getting the question error (error while loading state for instance 0x0 of device 'goldfish_pipe'). I had it installed via its own installer, outside Android Studio, because I was getting error trying to install HAXM via Android Studio.
Then I had the idea to uninstall that latest version (7.8.0 ATM) and again try to install the version shown in Android Studio (7.6.5 ATM) via Android Studio itself, and it worked! So I realized the steps I needed to take in order to successfully install HAXM via installer (step 1 shown here) also fixed the problem trying to install it via Android Studio! And finally, after hours and hours of harrassment, I could successfully launch a virtual device on the emulator.
Below is the step for successfully installing HAXM (taken from here):
At last but not least, make sure you have no other virtual machine running! It would throw you at this thread's error.
My case is:
disable Intel x86 Emulator Accelerator (HAXM installer) in Android Studio SDK Manager
uninstall HAXM as a result
enable again Intel x86 Emulator Accelerator (HAXM installer) in Android Studio SDK Manager
install HAXM as a result
recreate emulated AVD
finally works for Me
When I run my game through Unity Remote 5 it works well, but when I build the apk and try to install it on my device, it shows app is incompatible, I have tried changing many settings in player settings section but nothing worked for me. What can be done with this problem?
I am using unity 2017.3, the Android version on phone is 7.0 (Nougat) (I also tried on oreo but didn't work either), minsdk version in player settings is set on the marshmallow and target SDK version is on highest installed.
I have had this problem before. Maybe you can try removing the app you just have installed and trying to install the new version.
But you should complete your question with more information as someone comented.
Hope it works!
I am totally new to Cordova, but now I have installed Cordova with NPM and installed Android SDK and set up an AVD which seems to work perfectly, until I want to emulate my project. Where the actual app for some reason is not loaded into the emulator.
The following action is done:
marvin:HelloWorld$ cordova -d emulate android
cordova library for "android" already exists. No need to download. Continuing.
Wrote out Android application name to "HelloWorld"
Wrote out Android package name to "com.example.hello"
Calling plugman.prepare for platform "android"
Preparing android project...
Processing configuration changes for plugins.
Iterating over installed plugins: []
Writing out cordova_plugins.js...
Running on emulator for platform "android" via command ""/home/marvin/Development/projects/HelloWorld/platforms/android/cordova/run" --emulator" (output to follow)...
Then it start Android emulator up, but the app is not there. Does anybody have a suggestion to fix this issue, so I am capable of actually testing in my emulator?
Thank you in advance.
I just had the same problem, and I was missing PATH to platform-tools in android sdk folder, after I added it everything was in place.
I had the same problem as well; I could run the cordova emulate android command just fine, and the emulator would eventually start up and function, however, the test app was never installed on the device. I was not getting any errors from the Cordova CLI or the console or anything.
I found that there is a bug report about this issue here: https://issues.apache.org/jira/browse/CB-4285
Two solutions have been found for this issue:
1. Make sure you are using an Oracle JDK and not an IBM JDK, and
2. Make sure the AVD that emulate starts up has a min-target-sdk set to API 10 (Android 2.3.3) or higher. (This was my problem.)
Sometimes it works deleting the previously installed version of the app in the emulator. For this you could also launch it with the option "Wipe user data" checked.
Just for the record, none of the other solutions worked for me.
I had the same issue. Following solved it for me.
Make sure that API level of your AVD is greater than minSdkVersion specified in config.xml specified in your cordova app.
If anyone still having this issue:
I had a same problem with device being offline.
if ddms is running it looks after connected devices.
adb kill server
and than run ddms
Also make sure your app id doesn't begin with a number or any other character like "_". For example, if your app id is com.4company.MyApp or com._company.MyApp it just won't load on the emulator. The first one is because Java doesn't allow names beginning with a number, and the second one I guess it's a Cordova thing.
You should also use adb logcat to show the emulator errors on the command line.
For me, the app was not starting up because I had a second emulator running in the background. Uninstalling bluestacks (android emulator for windows) fixed the issue in my case. Running "adb logcat" should tell you if you have multiple emulators running.
I just had the same problem, and It was my emulator device that was with the API 15. Just updated to API 17 and the problem solved.