adb push file to trpw not working (closed error) - ZenFone 2 Q&A, Help & Troubleshooting

Hi, i have a ze550ml or Z008 , is it normal that the command adb push works only when the phone is booted and not when it is in twrp on sideload mode?
I updated the adb driver and i have the latest twrp 3.1.1 . The sideload command works on twrp sideload mode , but if i want only push a file to /sdcard/ when on twrp it says closed and fails.
The adb push file to twrp on sideload mode works on other phones ? Thanks

Paddy's said:
Hi, i have a ze550ml or Z008 , is it normal that the command adb push works only when the phone is booted and not when it is in twrp on sideload mode?
I updated the adb driver and i have the latest twrp 3.1.1 . The sideload command works on twrp sideload mode , but if i want only push a file to /sdcard/ when on twrp it says closed and fails.
The adb push file to twrp on sideload mode works on other phones ? Thanks
Click to expand...
Click to collapse
while being on sideload you cannot push file you can sideload only

Related

(Q) d855 stuck on adb sideload with stock recovery

I've entered recovery through quick boot app, didn't have twrp just stock to sideload the twrp img using a mac.(just to copy the file to internal sd) Mac didn't recognize my adb and now the phone is stuck on adb sideload screen, how do I get out of it?

can't get twrp adb sideload to work

i don't have ay ROM on my hpine right now and by mistake i wiped the internal storage so i am just stuck at twrp. I tried adb push with adb sideload on twrp bt it's not working and giving "error closed". How to get adb sideload working?
Meuuks13 said:
i don't have ay ROM on my hpine right now and by mistake i wiped the internal storage so i am just stuck at twrp. I tried adb push with adb sideload on twrp bt it's not working and giving "error closed". How to get adb sideload working?
Click to expand...
Click to collapse
TWRP supports MTP, why don't you just use that and copy the files needed to the storage. I did that multiple times.

ADB bootloader access no longer works?

*deleted*... it works now? fml wtf
ugh issue is back after I got in for a minute.
Is there any way to get a .zip format of the latest TWRP? I can get the stock recovery into adb sideload mode, but I don't think the twrp .img can be installed with sideload?
It's very strange adb doesn't see device in bootloader mode, but can see it when you choose adb from stock recovery screen.

No OS installed and adb push / sideload doesn't work

Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Not sure if it will help, but make sure you are using the latest ADB downloaded from:
https://developer.android.com/studio/releases/platform-tools
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
jeffrey268 said:
Not sure if it will help, but make sure you are using the latest ADB downloaded from: ...
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
Click to expand...
Click to collapse
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Flix117 said:
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Click to expand...
Click to collapse
I use this drivers https://androidfilehost.com/?fid=24591020540821930
xGOGI said:
I use this drivers https://androidfilehost.com/?fid=24591020540821930
Click to expand...
Click to collapse
Try this:
Download the stock recovery for your device:
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Place it in c:\OP3\
Go into cmd and go to c:\OP3\
then type: fastboot flash recovery recovery_op3.img
If you get reboots after this, do the following:
Boot back into fastboot and type:
fastboot format userdata
after that type:
fastboot flash recovery recovery_op3.img
Flix117 said:
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Click to expand...
Click to collapse
To clear some things up for you. Fastboot is only used in bootloader mode since that is what it is.
And for the adb sideload, are you initializing the sideload on your phone as well? To use sideload the phone has to be ready on the receiving end, in recovery you have to start adb sideload then launch the process on pc for it to work properly. And if you dont want the whole android SDK to just use ADB and Fastboot i recommend you install the minimal tool https://forum.xda-developers.com/showthread.php?t=2588979 :good:

Error: device not found while fastbooting

Hi everyone, after getting bootloader ublocked and minimal adb and fastboot tools installed on my pc I’ve started to follow step by a step what this web says to get my phone rooted.
magisk.me/root-mi-a2-a2-lite-magisk-install-twrp-recovery/
But while trying to install TWRP recovery I can’t finish step 8 because when I introduce the command “ adb sideload twrp-installer-daisy-3.2.3-0.zip” it puts me that device is not found so I cannot finish to install TWRP recovery.
Any suggestions?
ivvan14 said:
Hi everyone, after getting bootloader ublocked and minimal adb and fastboot tools installed on my pc I’ve started to follow step by a step what this web says to get my phone rooted.
magisk.me/root-mi-a2-a2-lite-magisk-install-twrp-recovery/
But while trying to install TWRP recovery I can’t finish step 8 because when I introduce the command “ adb sideload twrp-installer-daisy-3.2.3-0.zip” it puts me that device is not found so I cannot finish to install TWRP recovery.
Any suggestions?
Click to expand...
Click to collapse
Try this instead
adb push twrp-installer.zip /sdcard
But what I need to do before that? Should I move the twrp installer zip file to SD card? More things to do? I’m confused
ivvan14 said:
But what I need to do before that? Should I move the twrp installer zip file to SD card? More things to do? I’m confused
Click to expand...
Click to collapse
Get to fastboot. eg.
adb reboot bootloader
Boot TWRP
fastboot boot twrp.img
Copy the installer
adb push installer.zip /sdcard
Install using TWRP
Note that installing twrp removes Magisk so if you want root, reinstall Magisk.

Categories

Resources