Database Info

[Q] ADB "can't find '/data/app' to install"

Hi everyone,
I can cd to directories and list files with no problem on my device. It's rooted, ADB works, I can install .apks, etc...
However, I tried to install an .apk in /system/app, and there was not enough room. So, I used the adb install command to install, and specified it to install to /data/app (where there is room, according to df) and I get this error:
"can't find '/data/app' to install"
Again, I can cd to /data/app, and I can list files there -- the directory DOES exist on my device. But when I specify any directory (not just /data/app) to install to explicitly, I get the "can't find... to install" error.
I have never seen this before. What gives?

I'm not sure what command you're using but you don't need to specify a directory in which to install to. Just use 'adb install myapp.apk' and it will put it in /data/app. From the sounds of it ADB is trying to find another package to install called "/data/app" and failing to find it.

Root help, error flashing recovery

I owned and rooted a NS4G last year without an issue.
I've got a Mac now, and just got a new NS4G and tried rooting it.
I was able to unlock the bootloader via adb commands in Terminal. But when I try to flash a recovery using
Code:
~/Desktop/adb-fastboot/fastboot flash recovery.img
I get
Code:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
I get the same error if the file is named twrp-crespo4g-2.0.0RC0.img or whatever. Either that "cannot determine..." or "unable to load".
So I can't get superuser because I don't have a recovery. In Rom Manager, it gives me an error cannot flash recovery or what not.
I'm presently stuck.

Nevermind. After some fiddling I realized I was typing in the wrong file name in the first place.
Amateurs.

New downgrade for J Butterfly 1.36.970.1 > 1.15.970.1

There is a new downgrade option released for firmware 1.36.970.1 to 1.15.970.1.
However my Japanese is not perfect and my understanding of hacking is very weak.
If there is someone more in the know could understand what the steps to take are that would be great.
Good luck all. I hope someone can make a guide as well to help other out.
I'll try my best as well.
Here is the link.
http://htcsoku.info/htcsokudev-news/au-deluxe-136to115-downgrade/

link to RUU 1.15.970.1 is dead

I have successfully downgraded my J Butterfly based on those instructions. I have simplified it because the original instructions seems to be overly complicated. It involved tricking a system app with root privileges to run an custom command, only to use run_root_shell later anyway.
I also did not use the run_root_shell supplied by the guide, instead I compiled a newer version direct from the source: https://github.com/android-rooting-tools/android_run_root_shell
You'll need
1. revone.dna-0.2.1
http://forum.xda-developers.com/showthread.php?t=2314582
2. A newer build of run_root_shell (attached)
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
https://mega.co.nz/#!jQtQ0BLS!279lf8k4sbKPTmWHTsPg6hbaGDatpq3xGGv4aE8N1h4
4. firmware.zip extracted from OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip:
http://kie.nu/1urK
5. adb and fastboot
6. An HEX editor such as XVI32
THIS WILL WIPE YOUR USER DATA, BACKUP ALL YOUR STUFF FIRST
Steps:
1. Run the following commands in command prompt to push files required by run_root_shell to device:
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
2. Run in command prompt:
adb shell
to access the shell on your device. Run the following commands to run run_root_shell, disregard messages about HTL21 not supported. You will be returned to the command line but with a hash (#) instead of a dollar sign, that means you have temprooted.
cd /data/local/tmp/
chmod 755 *
./run_root_shell
3. Run these commands on device shell:
chmod 666 /dev/msm_acdb
dd if=/dev/block/mmcblk0p21 of=/sdcard/p21
4. Run in another command prompt:
adb pull /sdcard/p21
to pull the file p21 from device, then open it with an HEX editor. Refer to the images on the original Japanese tutorial, change the version number near "ClearAutoImage" to 1.00.000.0 and save the file as p21mod.
5. Push the modified file back to the device by running in command prompt:
adb push p21mod /sdcard/p21mod
6. Back to the device shell, run these commands to write the modifications to the device and reboot into bootloader.
dd if=/sdcard/p21mod of=/dev/block/mmcblk0p21
reboot bootloader
7. Run in command prompt:
fastboot oem rebootRUU
to boot to RUU.
8. Run in command prompt:
fastboot flash zip firmware.zip
and it willl fail with this error: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
9. Run in command prompt:
fastboot flash zip rom.zip
to flash 1.15 ROM. It should take around 6 minutes. This wipes your user data.
10. In command prompt, push run_root_shell to device again. Also push revone.dna-0.2.1 to device.
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
adb push revone.dna-0.2.1 /data/local/tmp/revone.dna
11. Refer to step 2 to temproot again.
12. Run revone.dna on device shell:
./revone.dna -P
and you should see "revone successful - please reboot to continue".
13. Reboot and repeat step 12 again, this time you should see "revone successful - no need to reboot".
14. Run on device shell:
./revone.dna -s 0 -u
and you should see "revone successful".
15. ???
16. PROFIT!
You have now successfully S-OFFed and may proceed to unlocking and SuperCIDing your device as usual.

Corrupted
Phil_123 said:
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
.
Click to expand...
Click to collapse
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?

corrupted
darky4e said:
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
Click to expand...
Click to collapse
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.

darky4e said:
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
Click to expand...
Click to collapse
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK

Phil_123 said:
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Click to expand...
Click to collapse
Thank you very much! I have succesfully downgraded the phone! Thx for the instructions again!!

run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?

dfani511 said:
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
Click to expand...
Click to collapse
This method can only be used for the software version of the 1.36.970.1, I think your software version 1.39.970.1 is not SOFF

i have 1.39.970.3 ?????????????
OTA ??????????

Nice share, im succesfully unlock soff with this way
Sent from my MITO_A10 using XDA Free mobile app

"htl21 1399703 firmware" I want up because it cannot find the file.

ADB 1.0.32 for OTA update!!!

Hey folks!
I'm following this guide. From the command lines on Updating the platform-tools, I get an error "please consider trying to update again without a package filter"
Code:
android.bat update sdk -u -t platform-tools,tools
Downloaded the latest SDK and drivers. after writing down recovery.img, system.img and boot.img, I'm unable to update via sideloading.
Code:
adb sideload update.zip
The recovery screen turns out "You need adb 1.0.32 or newer to sideload to this device." I've checked out the SDK and confirmed the "Android SDK Tools (24.0.2)" and "Android SDK Platform-tools (21)" have been updated, which is possibly the ADB and fastboot etc.Now what more does it require to get ADB updated.
I've already updated the platform tools, sdk tools from the package manager. Regarding the PATH variable, Please shed some light though. I'm no experianced under LINUX or it's distro's nor have much knowledge in CMD terminal either. I've located the (cd) path to where the android.bat is installed for the 1st command line operation below.
Code:
android.bat update sdk -u -t platform-tools,tools
How come the 1st update platform-tools command went out wrong? All command line operations/downloading and writing down under the fastboot menu went out smoothly, except this sideloading.
Thanks.
:angel:

cloutz90 said:
to show the adb version use
Code:
adb version
it should be 1.0.32 or newer (see image attached)
Click to expand...
Click to collapse
I checked with the exact command line also, it's the same 1.0.31! Also the package manager shows out I'm at the latest platform and SDK tools.

Sigh of relief!
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:

CODENEX said:
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:
Click to expand...
Click to collapse
Having the same issue. How exactly did you "update the ADB version to the directory"

ADB issue
SantinoInc said:
Having the same issue. How exactly did you "update the ADB version to the directory"
Click to expand...
Click to collapse
about this ADB version issue, i have a different phone, but was facing almost same sort of problem.
I think he might have referred to this thread: http://forum.xda-developers.com/showthread.php?t=2317790;)

Essential Phone System Dump

Can someone who has an Essential Phone (PH-1) upload a zip of the system dump. Run the command below in ADB to pull the dump (no root required):
Code:
adb pull /system PH1_system_dump
The dump will be pulled to a folder called "PH1_system_dump". Zip and upload that folder so we can begin development on this device.

I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied

cabegol said:
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
Click to expand...
Click to collapse
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc

Shawn5162 said:
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Click to expand...
Click to collapse
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD

bmg1001 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
Click to expand...
Click to collapse
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help

Shawn5162 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure: I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Click to expand...
Click to collapse
Someone in this thread managed to get the boot.img. I downloaded it and tried rooting it with Magisk but it didn't work. He already has TWRP and Lineage but they're still unreleased as its being worked on. I can't try the boot image anymore since I'm on the newest update and the image posted was for the previous update.
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583/page3

You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb

Look on the post below the guy already pulled the zip file already. I pushed it to my device via adb.

invisiblek said:
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Click to expand...
Click to collapse
is the touchscreen daemon the last piece of the TWRP puzzle? Can it be manipulated with vol + - and power buttons?