MTP broken, ADB sideload and push don't work - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

I installed TWRP and am trying to transfer the xiaomi.eu MIUI10 rom to the device to flash it, but I keep getting errors.
Trying to drag and drop through explorer always results in the same error:
(Cannot copy rom.zip. The device has either stopped responding or has been disconnected.)
Trying to sideload gives the error:
(Total xfer: 0.00x)
Trying to push gives the error:
(adb: error: failed to copy 'rom.zip' to '/sdcard/rom.zip': remote couldn't create file: Required key not available
rom.zip: 0 files pushed. 49.2 MB/s (262112 bytes in 0.005s)
Edit:
I realize I wasn't in sideload when trying to push. Now it gives a different error:
(adb: error: connect failed: closed)

Related

[Q] CWM unable to mount int / ext sdcard

I am sure this has been asked before but I cannot find any solutions so I am asking again. I flashed CWM v5.0.2.8 using Odin on my GM2 successfully but I have the following problems:
1. runme.bat from rootme.zip does not work. I get the below:
--- pushing busybox
error: device not found
--- correcting permissions
error: device not found
--- remounting /system
error: device not found
--- copying busybox to /system/x
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- installing busybox
error: device not found
error: device not found
--- pushing SU binary
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- correcting symlinks
error: device not found
error: device not found
--- pushing Superuser app
error: device not found
ALL DONE!!!
Press any key to continue . . .
2. I am in a CWM bootloop now - I cannot boot to OS anymore
3. And the biggest - CWM cannot view mount my int / ext sdcard (tried TWRP, same problem). Fixing permissions doesnt help. Wiping doesnt help as it stops at /sdcard/android.secure
Any help will be appreciated. Thanks.

Read-Only file system error when trying to push via adb

I've tried running a script for TA partition restoration (I had it backed up) but ended up with "Permission denied" error while it tried pushing a file into my internal sdcard.
Code:
=======================================
PUSH BACKUP TO SDCARD
=======================================
failed to copy 'tmpbak\TA.img' to 'sdcard/restoreTA.img': Permission denied
*** Restore unsuccessful. ***
So I opened up adb myself to see if I am able to push manually but it fails despite what destination I choose with "error: Read-Only file system".
Code:
android-sdk-windows\platform-tools>adb
push C:\yo.txt root\sdcard
adb: error: failed to copy 'C:\yo.txt' to 'root\sdcard': Read-only file system
Any thoughts?

ADB Sideload not working

Tried to copy my LOS-Customrom.zip via Sideload:
-> Starting ADB sideload in recovery Failed
Message on PC:
D:\Fastboot>adb sideload lineage-16.0-20180916-UNOFFICIAL-titan.zip
adb server version (31) doesn't match this client (40); killing...
could not read ok from ADB Server
* failed to start daemon
adb: sideload connection failed: cannot connect to daemon
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: protocol fault (couldn't read status): Connection reset by peer
...It didn´t work.

RECOVERY TWRP CANT INSTALL XZDUALRECOVERY

I am trying to install XZDualrecovery without success, can someone help me?
I received this when I tried to run:
==============================================
= =
= XZDualRecovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit
Please choose install action.
[1,2,3,4,5,6]?2
cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: Nenhuma conexão pôde ser feita porque a máquina de destino as recusou ativamente. (10061)
* daemon not running; starting now at tcp:5037
* daemon started successfully
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting device and ROM info
=============================================
Device model is C6943
Firmware is 14.6.A.1.236
Android version is 5.1.1
=============================================
Step2 : Sending the recovery files.
=============================================
adb: error: cannot stat '..\tmp\dr.prop': No such file or directory
adb: error: cannot stat '..\system\bin\chargemon': No such file or directory
adb: error: cannot stat '..\system\bin\mr': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory
adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory
adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory
adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory
adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory
adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory
adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory
adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory
adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Unable to open /data/local/tmp/recovery/busybox: No such file or directory
sh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================

hammerhead write error

I tried to install ubports to my nexus 5 and I got the error
Error: fastboot:flash: Error: Flashing failed: {"error":{"code":1},"stderr":"ery'FAILED (remote: 'flash write failure')\rfastboot: error: Command failed"}
I tried to fix it with nexus root toolkit and tried normal adb help?

Categories

Resources