Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R180 Build2,846
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
SVN Revision: 169
CASUAL Build Number: 2,792
Problems known at release: none
Problems Identifed:
Kill Switch/update downloaded message contains no spaces.
SVN Revision 180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
just4sc said:
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
Click to expand...
Click to collapse
I'm pushing out the kill switch now. http://code.google.com/p/android-casual/source/list
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
This is revolutionizing android and fast. i love you.
Everything appears to be working great Adam.
Thanks.
I've just relesed the following build. All previous scripts should be killswitched. Please test this and verify that there are no errors.
SVN R180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
Sorry, I uploaded the wrong file. Correct file is up now. There should be no problems now.
Please let me know if this works and what OS you are using.
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
B-Mod said:
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
Click to expand...
Click to collapse
Could you please grab the log from about>show log>copy to clipboard.. Then paste it here in
Code:
tags?
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
Code:
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
Adam, did you figure out why the phone did not reboot?
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
Sorry, but I won't be able to test it till Thursday night, as I am working out of town and not near my PC.
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
All seems to run well here.
--Test Script--
Testing Testing Revision 1
Script is out of date. See http://xda-developers.com for more information. Updating.
OMFG TESTING meta information
Downloading Updates
Test Script.scr...4kb Test Script.zip...1880kb Test Script.txt...4kb ... Update Sucessful! MD5s verified!
rebooting with ADB
rebooting with Fastboot
Running Windows 7.
I will test this tonight when I get home.
I am trying to build an apk file for release. My application lib contains a jar (probably obfuscated) from a third party vendor of one of my company's hard-wares. When I build the apk in debug mode it is successful, but when I try to do it in release mode using "ant release" it throws the following error.
Code:
BUILD FAILED
C:\adt-bundle-windows-x86_64\sdk\tools\ant\build.xml:868: Can't read [D:\Workspace\MyProject\libs\ThirdPartyJarV3.1.jar] (Can't process class [g.class] (Unknown verification type [10] in stack map frame))
I have successfully built apks in release mode for other projects (which doesn't have this jar file.)
It seems to be an issue around proguard not being able to read this class in the jar. I have looked through ProGuard's trouble shooting manual and also on google and found no help with this particular error:
Code:
(Unknown verification type [10] in stack map frame)
I also updated proguard from V4.7 to 4.10, but it still encounters the same error.
To my little mind it seems to be a problem with the jar itself and if so how do I fix it? Any help would be appreciated. TIA!
[P.S: I'm new to android]
Hello friends!
I am using Termux in order to run ruby.
I installed ruby successfully with "apt" command, and it functions fine.
Current ruby version:
Code:
$ ruby -v
ruby 2.3.3p222 (2016-11-21 revision 56859) [arm-linux-androideabi]
The problem is, I can't really install gems. I tried to install bettercap for the experiment, but it failed. This is what I get:
Code:
$ gem install bettercap
Fetching: colorize-0.8.1.gem (100%)
Successfully installed colorize-0.8.1
Fetching: network_interface-0.0.1.gem (100%)
Building native extensions. This could take a while...
ERROR: Error installing bettercap:
ERROR: Failed to build gem native extension.
current directory: /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1/ext/network_interface_ext
/data/data/com.termux/files/usr/bin/ruby -r ./siteconf20161129-14856-1cclchu.rb extconf.rb
mkmf.rb can't find header files for ruby at /data/data/com.termux/files/usr/lib/ruby/include/ruby.h
extconf failed, exit code 1
Gem files will remain installed in /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1 for inspection.
Results logged to /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/gem_make.out
I found some instructions if I ran "gem help install" but I couldn't really understand what to do in order to fix that.
Can anyone help me to solve this? BTW I have a rooted device so I can use "su" and "sudo" and all that stuff...
Thanks for people who answer~
FurySh0ck said:
Code:
mkmf.rb can't find header files for ruby at /data/data/com.termux/files/usr/lib/ruby/include/ruby.h
Click to expand...
Click to collapse
You can install ruby.h with:
Code:
apt install ruby-dev
.
fornwall said:
You can install ruby.h with: .
Click to expand...
Click to collapse
I installed ruby-dev but it still won't work. It tells me it saved a log file which contains the explanation to the failure. I'll post the whole code, but please pay attention to the last part of it:
Code:
apt install bettercap
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package bettercap
$ gem install bettercap
Building native extensions. This could take a while...
ERROR: Error installing bettercap:
ERROR: Failed to build gem native extension.
current directory: /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1/ext/network_interface_ext
/data/data/com.termux/files/usr/bin/ruby -r ./siteconf20161206-31345-1xerjr9.rb extconf.rb
[*] Running checks for netifaces code...
[*] Warning : this platform as not been tested
checking for getifaddrs()... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/data/data/com.termux/files/usr/bin/$(RUBY_BASE_NAME)
/data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:456:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:541:in `try_link0'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:556:in `try_link'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:765:in `try_func'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:1051:in `block in have_func'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:942:in `block in checking_for'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:350:in `block (2 levels) in postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:350:in `block in postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:346:in `postpone'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:941:in `checking_for'
from /data/data/com.termux/files/usr/lib/ruby/2.3.0/mkmf.rb:1050:in `have_func'
from extconf.rb:43:in `<main>'
To see why this extension failed to compile, please check the mkmf.log which can be found here:
/data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/gems/network_interface-0.0.1 for inspection.
Results logged to /data/data/com.termux/files/usr/lib/ruby/gems/2.3.0/extensions/arm-linux/2.3.0/network_interface-0.0.1/gem_make.out
Any solutions in mind?
BTW Thanks for your time, I appreciate anyone who tries to help.
Device in question, although likely not relevant to the issue I am having: Pixel 2 XL (Taimen). Let me know if there's any info I may have missed sharing that could help solve this.
My overarching goals here are:
1. Build vanilla AOSP "user" variant without root or any other additions
2. Sign the build with my own release keys
3. Be able to git-checkout release tags at a later time, build again, and produce OTA updates for this vanilla AOSP build
So far, I have been able to successfully build the latest release and flash it to my device using:
Code:
fastboot flashall
The device boots and runs as you would expect.
However, that is all using the test-key. I have followed the official documentation for generating release keys:
hxxps://source.android[.]com/devices/tech/ota/sign_builds#release-keys
The same documentation page provides the following listing for generating the release image:
Code:
make dist
./build/make/tools/releasetools/sign_target_files_apks \
-o \ # explained in the next section
--default_key_mappings ~/.android-certs out/dist/*-target_files-*.zip \
signed-target_files.zip
Apparently SignApk.jar doesn't work with password-encrypted keys (it throws an exception then swallows it which causes the whole thing to fail at a later point), and signing the APKs in the target files ZIP fails. Fine, I'm willing to use an unencrypted key for testing this project.
So I successfully get a signed-target_files.zip.
Lastly, the documentation provides the following for producing the release image:
Code:
./build/make/tools/releasetools/img_from_target_files signed-target-files.zip signed-img.zip
This also works successfully (minus the typo with the filename, switching the '_' character for '-'), so I use this to install:
Code:
fastboot update -w signed-img.zip
Then I get symptoms of the problem:
1. Warning that the bootloader is unlocked (fine)
2. White screen with "Google" logo
3. Reboot to bootloader
I never see the "android" splash screen after 2. like when I
Code:
fastboot flashall
to install the test-key version which does work.
So something else that I decided to try was to create an "unsigned-img.zip." I basically used img_from_target_files on the original, unsigned target_files.zip. and did a
Code:
fastboot update -w unsigned-img.zip
. This also booted successfully.
=====================
To recap:
1. Building is successful
2. "fastboot flashall" is successful
3. "fastboot update unsigned-img.zip" is successful
4. "fastboot update signed-img.zip" is NOT successful and always reboots back to the bootloader
Is there something I'm missing with regards to the image signing? If I'm doing this and having this issue on an unmodified AOSP branch, shouldn't everyone else be having these signing issues, as well?
Any help is appreciated.
It worked for me without -w argument:
Code:
fastboot update signed-img.zip
BackgroundI had recently planned on integrating the Crash SDK to my app. However, my app was developed through Eclipse and the integration process was different from that in Android Studio.
By referring to the official materials, I downloaded the tool package and used it to generate an Eclipse project package.
However, when the build.bat file in the aar2eclipse/aar directory was executed according to the procedures in the document, an error was reported in the command line. The error information was as follows:
FAILURE: Build failed with an exception.
* What went wrong:
Task ' assembleRelease ' not found in root project ' aar '.
Problem Reoccurring1. I first thought that the problem might be caused by my company's intranet. But when I connected to the Internet, the problem remained unsolved.
2. Then I guessed that it might have something to do with the Android development environment.
I borrowed a colleague's PC to execute the build.bat file, and it that did the trick. Therefore, I was able to conclude that the problem was caused by incorrect configurations in the Android development environment. I compared the configurations on the two PCs and found that the environment variables were different. ANDROID_HOME was missing from the environment variables on my PC.
CauseHuawei's Eclipse tool package is unable to run properly and reports an error without the ANDROID_HOME variable.
Solution: Right-click This PC and choose Properties from the shortcut menu. In the displayed dialog box, click the Advanced System Settings tab and then click Environment Variables. In the System Variables dialog box, create a new ANDROID_HOME parameter.
Set the value to the installation path of the local Android SDK, and the problem will be resolved, as shown below.
Reference:
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-get-started#h2-1587519820720