Problems with ADB push and --sync+ - General Questions and Answers

I'm attempting to use adb's push command on Windows 10 in order to transfer files from my PC to my Oneplus 9 Pro. I installed adb by following the instructions here. When I attempt to do the file transfer, I receive a large number of error message for some of the files, that all look like this:
Code:
E:\>adb push Music /sdcard/Music
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/????? ??....flac': No such file or directory
cannot lstat 'Music/????? ????????? - ??????? ?????? (2011)': No such file or directory
cannot lstat 'Music/????????? ??????? ??? - 1990 - ??? ?? ??????': No such file or directory
cannot lstat 'Music/???? ? ????????.mp3': No such file or directory
cannot lstat 'Music/??? ?????? ?????.flac': No such file or directory
cannot lstat 'Music/??????? ????.mp3': No such file or directory
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/?????? ????.flac': No such file or directory
cannot lstat 'Music/?? ?????? ???? ??? ? ? ????? ?? ??????.mp3': No such file or directory
cannot lstat 'Music/??, ???????.mp3': No such file or directory
I have used adb with these exact same files before, when I was still running Manjaro, with no issues or error messages such as these, so I'm fairly confident the issue is not with the files themselves. Even more bizarrely, when I attempt to use the --sync command, it doesn't even recognize it as a command:
Code:
E:\>adb push --sync Music /sdcard/Music
cannot stat '--sync': No such file or directory
I've attempted to uninstall and reinstall adb, but the issues persists in spite of that. What possible solutions are there to this?

Youn have to name the fullpathname of folder Music on PC.

xXx yYy said:
Youn have to name the fullpathname of folder Music on PC.
Click to expand...
Click to collapse
I do have the full path name, Music folder is located in E:\Music and I open Command Prompt to E:\ drive. I also know it's the correct path name because some of the files do transfer, but a large number have errors as discussed above.

Related

[Q] [HELP] CWM cant format /data (cant remove dropbox folder)

Hello,
I`ve got a little problem - I cant format /data in CWM because of this file/folder
Code:
/data/system/dropbox/[email protected]
So, I connect tf via adb,switched to /data/system a tried to delete dropbox folder with this command
Code:
rm dropbox -r
output:
Code:
rm: cant remove dropbox/even[email protected]: No such file or directory
Code:
rm:cant remove dropbox: Directory not empty
So I switch to dropbox folder (
Code:
cd dropbox/
) and recieved this:
Code:
ls: ./[email protected]: No such file or directory
Can anyone help me to format data/remove dropbox folder please?
Flash the superwipe script from ARHD
Thanks!

[Q] Unable to root Huawei MediaPad 7

hi all,
I am trying very hard to root my huawei mediapad but not getting success.
Following are my setup -
My device - Huawei MediaPad 7
OS - Android 4.0.3
I have enabled USB debugging mode
My PC is on Windows 7 Home Premium.
I following so many posts for rooting this device. I followed the following posts.
Link1
Link2
In link1, i downloaded the zip file and run the Install Root.cmd script. But it shows me following errors
Code:
failed on '/data/local/tmp' - Permission denied
link failed File exists
ÅÑαѺáúαπªáѼ (1/3)
/system/bin/sh: cannot create /data/local.prop: Permission denied
ÅÑαѺáúαπªáѼ (2/3)
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
sh: /system/xbin/install_bb: No such file or directory
rm failed for /system/xbin/install_bb, No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
ÅÑαѺáúαπªáѼ (3/3)
éßÑ ú«Γ«ó«!!!
Press any key to continue . . .
On Link2 - the download link does not work and shows error as follows
Code:
Oops! Google Chrome could not connect to depositfiles.com
Suggestions:
Access a cached copy of depositfiles.*com/*files/*9f8mfimjz
Try reloading: depositfiles.*com/*files/*9f8mfimjz
Search on Google:
Someone please help.

adb push "No such file or directory" error

HI Guys,
After searching the forums for a bit, and not having luck - I am opening a quick thread. All I am trying to do is push files back as I pulled them before my ROM upgrade.
Code:
adb root
adb remount
adb push blahfolder /storage/sdcard0/
Here is what I am getting as error.
Code:
E:\phone>adb push "themex" /storage/sdcard0/themex
push: themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png -> /storage/sdcard0/themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png
failed to copy 'themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png' to '/storage/sdcard0/themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockm
e.png': No such file or directory
E:\phone>adb push "themex" /storage/sdcard0
push: themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png -> /storage/sdcard0/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png
failed to copy 'themex/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png' to '/storage/sdcard0/com.gau.go.launcherex.theme.blackthemepro/icons/unblockme.png':
No such file or directory
FYI - I am not using absolute path as CMD prompt is running from the source directory already. E:\

[Q] cannot supercid and lost mmcblk0p4 file

i did super cid using supercid.sh file in mac to my HTC one XL/at&t
and i got this error
please help me..
mkdir: tmp: File exists
./supercid.sh: line 43: ./adb: cannot execute binary file
./supercid.sh: line 44: ./adb: cannot execute binary file
Copying your misc partition to your sdcard partition...
./supercid.sh: line 47: ./adb: cannot execute binary file
Making a backup copy of the file, just in case...
./supercid.sh: line 50: ./adb: cannot execute binary file
Copying the file to your computer so we can work with it...
./supercid.sh: line 53: ./adb: cannot execute binary file
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Converting the image file to text...
xxd: tmp/mmcblk0p4: No such file or directory
Checking to see what your CID is now...
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
We don't recognize your current CID.
You need to provide more information. What are your bootloader details? Are you perm rooted? What tutorial were you following? What commands came before the text you have posted here? What do you mean by you've lost the file?
PS. You've posted this in the General Section, I'll ask for it to be moved to the Q&A Section for you.
Sent from my Evita

Guide to replace kinguser with supersu

hey guys,
get this files then, you will find MRW folder inside the zip file , put that mrw in internal memory card
• Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
• Open Terminal emulator and type :
Su
• Allow root permission
• Type :
sh /sdcard/mrw/root.sh
(put space after sh , then /sdcard/mrw/root.sh)
• It might display some error ignore these errors, at the end it will launch supersu or open supersu manually.
• Update SU binary normal, then reboot
ALSO DELETE THE KINGUSER.APK ( superuser.apk) from /system/app manually, before reboot
and its done , i checked nicely , its working awesome
link for replacer files :- https://drive.google.com/file/d/0B7I...ew?usp=sharing
dont flash these files , (method working on lollipop 5.0, work on kitkat , jellybean also )
CREDIT : 1) Chainfire for awesome SUPERSU ( PLS DONATE HIM AND SUPPORT HIM> http://www.chainfire.eu/),
2) edwuard
3)ME
4) MY PARENTS and WIFE CLAIRE
File Missing
It's show to check the URL. Have you deleted the file ?
nope , the link is working , still i attach files here ,
vasansrine said:
It's show to check the URL. Have you deleted the file ?
Click to expand...
Click to collapse
check the attachment
is it safe
I am runing on android lollipop xolo prime please tell me is it safe
---------- Post added at 08:02 AM ---------- Previous post was at 07:20 AM ----------
So so so thanks I am trying to this this for year but now I have done with your amaging post I can't believe I so fear to doing this but successing I am so happy now thank thank you very much
Interesting. What do the am and pm commands do?
Seems to have worked on my Amazon Fire (KFFOWI/Ford), but I may have left Kingroot installed before rebooting
com.kingroot.kinguser:services
This method works. I tried it myself. The downside is that Kingroot will leave residual files and services even after you have enforced SUPERSU and updated it's binaries. Anyone know where I could locate KSysService and com.kingroot.kinguser:service?
Success on KFFOWI 5.1.2 via adb on Linux
I just tried this on KFFOWI with 5.1.2. It worked, but there were errors output by the script and I don't know if that's ok. It appears to be ok though. Here's what I did (on Linux):
Code:
$ unzip mrw.zip
$ cd mrw
$ adb shell
[email protected] $ cd /storage/emulated/legacy
[email protected] $ mkdir mrw
[email protected] $ exit
$ adb push busybox /storage/emulated/legacy/mrw/busybox
$ adb push root.sh /storage/emulated/legacy/mrw/root.sh
$ adb push su /storage/emulated/legacy/mrw/su
$ adb push Superuser.apk /storage/emulated/legacy/mrw/Superuser.apk
$ adb shell
[email protected] $ su
[email protected] # sh /storage/emulated/legacy/mrw/root.sh
The output looks like this (aparently errors are ok?)
Code:
---------------------------------------
---------- Made By : BEINGTEJAS -------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure [DELETE_FAILED_INTERNAL_ERROR]
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
rm: /system/app/Kinguser.apk: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/bin/install-recovery.sh-ku.bak: No such file or directory
rm: /system/bin/install-recovery.sh-ku.bak: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Success
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Then I followed through the install of SuperSU on the device, using the "normal" option and allowing it to remove the other SU that it detected. Finally, I rebooted the device and performed a quick test:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # exit
[email protected]:/ $ exit
The SuperSU icon is on available, the KingUser one is gone. Accessing root goes through SuperSU so it looks ok. If any of those errors pose a problem though, let me know!
when i type su and enter, I get a message "Daemon is stop" and i cant get root access, i have tried to reinstall emulator, re-allow kinguser root, but nothing works, busybox is installed
Edit: NVM, got it working with the SuperTool
The script managed to remove Kingroot, but SuperSU normal binary installation still fails. Plus, the Rootchecker now says that the root is not properly installed.
Should I install Kingroot again in order to gain root and try SuperSU again?

Categories

Resources