Database Info

RC30 download link

Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.

OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.

neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come

What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails

I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.

but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.

Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.

Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**

Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*

DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?

JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?

Can not we flash back that old RC29 File again ????

The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img

spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang

RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.

JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?

JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.

syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.

I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30

well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?

OTA Supersonice 1.47.651.1-1.32.651.6_r

DO NOT FLASH THIS UPDATE UNTIL YOU HEAR FROM THE BIG GUNS OR RISK LOSING YOUR ROOT!
Please Be Patient!!!!
Sprint is pushing out a system update this morning with a size 21.43mb
Update Download Links:
http://www.mediafire.com/file/2myavzqygir/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip Thanks Calkulin!
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip Thanks Joeykrim!
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel Version
2.6.29-789bf291
[email protected] #1
PRI Version 1.40_003
PRL Version 60667
Thank you joeykrim for the following:
RADIO - the radio is updated through a radio.diff.
SYSTEM - no system/app files are changed
it appears this OTA is much more extensive than the previous OTA.
this one appears to apply small patches to every application in /system/app. a few are large in size, but most are very small.
it also appears to patch:
16 files in system/bin
etc/wimax/
etc/firmware/fw_bcm4329.bin and (ap)
31 files in framework
28 files in lib
2 files in lib/modules - bcm4329.ko and sequans_sdio.ko
SYSTEM updated files (might be more, researching now):
wifi module - BCM4329B1_002.002.023.0396.0402.hcd
android.hardware.camera.flash-autofocus.xml
android.hardware.telephony.cdma.xml
ton of framework files
libCamera_donut.so
libCamera_eclair.so
Fixes & Bugs:
From user npace: (I extracted and fastboot flashed the kernel zImage. Here's a rundown of the issues that I tested for fixes
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
3. 30 fps cap -- still there

same radio by your title?

Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.

is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root

danon.brown said:
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
Click to expand...
Click to collapse
Even if you rooted via toasts method, i would not update until a custom ROM is put out with the update included. You could lose root ability forever.

Anyone know the location of system updates are stored on the phone? I am trying to locate using the adb shell but have had no luck finding the download yet.

huoter said:
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
Click to expand...
Click to collapse
can you post this OTA .zip?

joeykrim said:
can you post this OTA .zip?
Click to expand...
Click to collapse
Its done downloading, just trying to find the darn file right now. Any ideas?

Awaiting an update zip

Here's the untouched update zip for those that want it. If you want to put it in the OP, feel free to
OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip

huoter said:
Its done downloading, just trying to find the darn file right now. Any ideas?
Click to expand...
Click to collapse
i didn't look into the last one and this is my first HTC phone so im not familiar with their OTA process.
perhaps try /cache? or any type of temp directory on /data or /sdcard?
we know it won't be on /system.

We install this from recovery, right?

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
I'd recommend not installing it at all until the devs here have had a chance to go through it and release it themselves. You risk loosing your root if you don't. Then follow their release instructions to apply it.

Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk

Shidell said:
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
Click to expand...
Click to collapse
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...

donatom3 said:
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
if you've applied this, can you take a screenshot of the about phone -> software versions or manually type all the info up on here?
im wondering about the PRI ...

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
No, looks like just about all the preloaded APK's are in there, including the Sprint crap. I assume if you apply it as stock you'll get them back, but I could be wrong.

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
The official froyo release from HTC / Sprint will definitely contain all the "Sprint Junk" and if you've given up root to one of these updates and go to apply that it will all come back. You may never get root again in order to re - clean it up once you apply froyo.
Be patient. It won't take the devs here long to cook up an update for us. Flipz had the rooted .6 update rom out in 24 hours or so...
.....
Just took a look inside the zip file. All the apk files are there, including the sprint junk...

Just installed....all is well with root...

Question about rooting 4.3

If I take the 4.3 update is the process to root it the same as it was on 4.2 or will we have to wait for a new way to root? I used this process previously and it worked for each update:
https://github.com/linux-shield/shield-root
Though now that there is a mapping utility I am not sure I will need to root it anymore... Depends on how good the mapping utility is.

This is not going to work unfortunately. I need to update the rooting procedure but am not really aware of how this is done on 4.3 (if anyone has pointers by the way) and the update arrived sooner than I thought. Will try to get that done quickly, please be patient in the meantime!

Great, thanks for the update. I will be sure to not even try then

Evo_Shift said:
Great, thanks for the update. I will be sure to not even try then
Click to expand...
Click to collapse
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.

agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
Can you explain more what you mean. I know how to flash CWM but what do you mean "root that way"?

First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389 (LINK DEAD: MIRROR: http://cl.ly/2o3n3f0C0G2S)
Copy it to your Minimal ADB & Fastboot folder.
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
adb reboot bootloader
fastboot boot recovery.img
Your device should reboot into CWM.
Then, grab the latest SU from here: http://download.chainfire.eu/351/
Copy the SU zip to an SD card. Choose "install ZIP from external SD" in CWM. Choose the SU zip. Let it finish, reboot and you're done!
Way too much damn work if you ask me, but made signficiantly easier thanks to the community. This was cobbled together from the various posts on the subject in xda developers. Thanks guys!

thank you shinratdr, that works perfectly.

Not sure what I did wrong here (have not seen this before myself) I installed the update, and everything seemed to work find. When I finally needed to use root it would not work, so i downloaded the root zip flashed that nothing changed.
From a terminal emulator on my shield when I enter su. I get no errors, and root does not work.
From the supercd /system/binuser app I get that su is not installed and it can't be installed.
From adb shell after entering su the prompt changes to # but noting that needs root works.
su is installed in /system/xbin and has the following permissions -rwsr-sr-x.
I am not sure what to do next.
Update
For now I am just restoring my back up of update59.

shinratdr said:
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
!
Click to expand...
Click to collapse
Maybe stupid question but just download this here?
http://forum.xda-developers.com/showthread.php?p=42407269
Never really rooted something before and not really looking forward to it due to loss of warranty but I really want to use the PS3 controller

Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!

Gnurou said:
Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!
Click to expand...
Click to collapse
Worked great. Thanks

agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
I can confirm that while you need to flash the stock recovery image you provided to update, after updating, I had no problem reflashing your CWM image in fastboot and then flashing SuperSU 1.65

Just posting as a follow up to my earlier post here
I had to download the superuser.zip from this Superuser page on the play store.

shinratdr said:
First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389
Click to expand...
Click to collapse
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!

punraz said:
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!
Click to expand...
Click to collapse
I hope you were able to find it. If not, I located the copy I left on my computer. Enjoy, this strategy seems to work fine with the latest update for a "quick" re-root.
http://cl.ly/2o3n3f0C0G2S

Thank you mate, all done now! Works like a charme. Greetings.

[Q] Updating to 4.4.4. If I have root, why do I need WP off?

I asked this deep inside another thread and got no responses, so maybe I'll try asking outright.
I'm rooted on 16.5.3, BL is LOCKED. If I update to 4.4.4, I keep root, but lose WP off. The changes to 4.4.4 sound exactly like the changes I want in my phone, which are improved camera quality and improved battery life.
This is what I know (or think I know):
- Most root apps will continue to work fine. I've confirmed the ones I use will still work.
- Xposed (which writes to /system), will no longer work, but I haven't used Xposed since I changed to ART runtime.
- I won't be able to replace any files in /system, which means su binary can't ever be updated which could be a problem for newer versions of SuperSU.
Any other drawbacks that I've missed?
Right now, the only one that I feel is of any concern to me, is the inability to update the su binary. However, let's say I keep this phone 2 or even 3 more years. Is it really necessary to update the su binary? I know SuperSU won't work if it needs to update the binary and can't, but I could just keep the same old version of SuperSU. If it works fine now, won't it work fine a year from now? Two years from now?

GnatGoSplat said:
I asked this deep inside another thread and got no responses, so maybe I'll try asking outright.
I'm rooted on 16.5.3, BL is LOCKED. If I update to 4.4.4, I keep root, but lose WP off. The changes to 4.4.4 sound exactly like the changes I want in my phone, which are improved camera quality and improved battery life.
This is what I know (or think I know):
- Most root apps will continue to work fine. I've confirmed the ones I use will still work.
- Xposed (which writes to /system), will no longer work, but I haven't used Xposed since I changed to ART runtime.
- I won't be able to replace any files in /system, which means su binary can't ever be updated which could be a problem for newer versions of SuperSU.
Any other drawbacks that I've missed?
Right now, the only one that I feel is of any concern to me, is the inability to update the su binary. However, let's say I keep this phone 2 or even 3 more years. Is it really necessary to update the su binary? I know SuperSU won't work if it needs to update the binary and can't, but I could just keep the same old version of SuperSU. If it works fine now, won't it work fine a year from now? Two years from now?
Click to expand...
Click to collapse
The upcoming L update, if true, will prevent root access to applications in /data. The binary may need tweaking to function... Root will definitely be operational for the next months for sure, I hope.

I've been wondering the same thing. I didn't have root four ten months and got along just fine on my maxx.
The changes in 4.4.4 are very tempting. I wonder if you were to make a symlink that put the su binary onto the SDcard instead of on the system if you'd be able to update it in the future.
Since the 4.4.4 update doesn't wipe out su, it shouldn't wipe out a symlink.
Any thoughts on that idea?

distortedloop said:
I've been wondering the same thing. I didn't have root four ten months and got along just fine on my maxx.
The changes in 4.4.4 are very tempting. I wonder if you were to make a symlink that put the su binary onto the SDcard instead of on the system if you'd be able to update it in the future.
Since the 4.4.4 update doesn't wipe out su, it shouldn't wipe out a symlink.
Any thoughts on that idea?
Click to expand...
Click to collapse
Sounds like a pretty good idea to me, but I don't know that much about Android/Linux so not sure if it'd work or not. Could the whole /system/xbin folder be symlinked to a folder on /sdcard? I remember somebody mentioning busybox couldn't be updated either, and if the whole folder could be symlinked, busybox could be updated if necessary as well.

all this discussion is why i will not update past jellybean even though my BL is unlocked...
Too much additional security/hoops to jump through with little to no added feature/functionality benefit imo

If you're BL unlocked, you have no hoops to jump through. Just flash 3rd party recovery (if you haven't already) and flash the latest SuperSU.zip and problem solved. Works on any version.

I don't have an answer to the OP's question, but after three months, I decided that root was good to have because I use an app called Notification Toggles and if I need to toggle GPS or airplane mode with a single tap, then that tool requires rooted phone.
Now, after root, that tool works just the way I want it to. Earlier it was a pain to turn GPS on or off - I had to press a few buttons to do that every time.
So, no 4.4.4 for me. I prefer to keep my root.
I am not sure what advantage the write protection has, but I will rather keep it, instead of sacrificing it.

May Update Help?

Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?

Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly

Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...

Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!

I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.

Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?

Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one

pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it

Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!

pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.

exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).

Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome

Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding​ it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.