Database Info

[Q]ADB Sideload?

My tablet has been hideously slow for the past 6 months or so. I've flash 15 or 20 different ROMs of various kinds, I always wipe factory reset and what not, but it remains slow. No matter what I do, after about 6 hours with the tablet on, it will slow down to a crawl then eventually crash.
Anyway I tried to wipe everything off my tablet. I completely wiped data and deleted every file off the internal sd. I figured just maybe it would help.
I was going to use ADB sideload to get stuff back on....but it just isn't working!
Is there some reason why ADB sideload doesn't work with TF300T and TWRP 2.4.4.0?
I am in TWRP in sideload mode with usb connected to computer, on my computer in the ADB command line when I type "ADB devices" I get:
012345689ABCDEF sideload
but when I try to actually use sideload "adb sideload rom.zip" I get "cannot read 'sideload'"
ADB push isnt' working either.
Neither is fastboot flash blob
Any ideas to get some rom back on my tablet?

having this problem too

zaner123 said:
My tablet has been hideously slow for the past 6 months or so. I've flash 15 or 20 different ROMs of various kinds, I always wipe factory reset and what not, but it remains slow. No matter what I do, after about 6 hours with the tablet on, it will slow down to a crawl then eventually crash.
Anyway I tried to wipe everything off my tablet. I completely wiped data and deleted every file off the internal sd. I figured just maybe it would help.
I was going to use ADB sideload to get stuff back on....but it just isn't working!
Is there some reason why ADB sideload doesn't work with TF300T and TWRP 2.4.4.0?
I am in TWRP in sideload mode with usb connected to computer, on my computer in the ADB command line when I type "ADB devices" I get:
012345689ABCDEF sideload
but when I try to actually use sideload "adb sideload rom.zip" I get "cannot read 'sideload'"
ADB push isnt' working either.
Neither is fastboot flash blob
Any ideas to get some rom back on my tablet?
Click to expand...
Click to collapse
You have probably already read and tried this but if not may give you an answer to using sideload.
How to Use Sideload
[FONT=ArialMT, sans-serif]1. Have a recovery installed on your device that supports ADB sideload like[/FONT][FONT=ArialMT, sans-serif] TWRP 2.3 or higher[/FONT]
[FONT=ArialMT, sans-serif]2. Have newer ADB binaries installed on your computer. If it's been a while since[/FONT][FONT=ArialMT, sans-serif] you installed ADB on your computer, you may need to get the latest ADB binaries in platform tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.[/FONT]
[FONT=ArialMT, sans-serif]3. Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then[/FONT][FONT=ArialMT, sans-serif] ADB Sideload.[/FONT]
[FONT=ArialMT, sans-serif]4. From the command line, type adb sideload /path/to/rom.zip (rom.zip location on pc)[/FONT][FONT=ArialMT, sans-serif]. The file will be copied to the path you have mounted. (internal or external sdcard).[/FONT]
I made the two things blue that previously kept me from using sideload.

Why stock recovery "apply update from ABD" does not work?

Why every time I get this error?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Restarting adbd...
No package received.
Installation aborted.
It is not driver problem, once I get this error even cable is connected or not!!
Please, any help!!!!
Thanks in advance...

saaj said:
Why every time I get this error?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Restarting adbd...
No package received.
Installation aborted.
It is not driver problem, once I get this error even cable is connected or not!!
Please, any help!!!!
Thanks in advance...
Click to expand...
Click to collapse
How are you sideloading the files?

I have similar problem.
when select (with power button) "apply update from ADB" in recovery mode
I have got this:
Now send package you want to apply
to the device with "adb sideload <filename>"...
status 255
No package received.
Installation aborted.
without "Restarting adbd..."
Device do not wait for any commands
When device is in recovery mode ADB returns error: device not found
Step by step what I'm doing:
- cevice connected, USB mode enabled
-In ADB dir in my computer cmd:
> adb kill-server
>adb reboot recovery
After device gets to the recovery mode and with volume buttons selected "apply update from ADB" and confirmed with power button a previously mentioned message was returned.
When I try to use "adb wait-for-device" in fast boot or recovery mode a device will never been found.
Device flashed with stock 15.0.A.2.17 and ROOTed

I have the same problem.. Any solution? :s

ADB sideload problem connection reset

I have a Pixel presently running NDE63P, not rooted, bootloader locked. I downloaded the NDE63X OTA image, verified the download with the SHA-256 hash, and attempted to put it on the phone. Adb is version 1.0.36 from latest Android Studio. Adb loads the image into memory and then immediately puts out the message "failed to read command: Connection reset by peer", and returns me to the command prompt:
Code:
D:\Users\Nick\Downloads\Google>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA69X0309603 device
D:\Users\Nick\Downloads\Google>adb reboot recovery
D:\Users\Nick\Downloads\Google>adb sideload sailfish-ota-nde63x-59a512a1.zip
serving: 'sailfish-ota-nde63x-59a512a1.zip' (~0%) * failed to read command: Connection reset by peer
On the phone screen, I see:
Code:
Finding update package...
Opening update package...
Verifying update package...
and nothing further.
After rebooting both phone and PC I also tried the sideload using an older version of adb from adb-setup-1.4.3.exe. That version doesn't give an error msg about "failed to read command", but it never gets beyond 0% serving of the update, and viewing the adb process in Windows task manager shows it consuming no CPU and performing no I/O (I let it run for about half an hour before killing the process and rebooting the phone). I'm using the USB C<->A cable that came with the phone, and tried it in a couple of different ports in the PC.
Any suggestions on why this problem happens?

Are you placing the update file in the same folder as your ADB location. You might want to consider using a new folder location for the ADB. If you use your downloads location you could possibly use the wrong file while updating since there are so many items typically in that folder. For example I use "Android" folder on my desktop and only keep my SDK, ADB etc. in there so it's always pretty clean and easy to find. You open that folder and shift-right click and open command prompt here or if you've got a Mac it is very similar, cd desktop, cd android.

I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Sent from my Pixel using Tapatalk

jay661972 said:
I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Click to expand...
Click to collapse
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.

NickJHP said:
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.
Click to expand...
Click to collapse
Did not work. Strongly suggests it was just coincidence that you got your OTA prompt after doing the steps.

Not to necro an old thread, but I had a similar issue and came across the solution. If anyone else encounters this problem, try different USB cords and USB ports. Very likely a USB port isn't supplying the proper data transfer.

Android 10 ADB

Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.

ADB appears to be working just fine for me.

When using adb make sure you have debugging enabled and grant the popup on screen

adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.

Also need to make sure that the proper USB drivers on the computer are installed/updated.

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.

D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...

Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do

a second adb server was running.
TNX

Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865

Cant get ADB in recovery mode, but works in live mode, and so does fastboot

On my Rooted Pixel 4a, I can use:
Fastboot - I flashed the latest update firmware as well as the rooted boot image
ADB Over WiFi - This is the most comnon way I connect for ADB
ADB While the Android OS is running
What I cannoit get woirking is ADB while in recovery mode,
If I go to recovery and connect via a high quality cable, I can see the device with
Code:
adb devices
C:\Java\x86\Android\android-sdk\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
091????????490 rescue
Click to expand...
Click to collapse
But none of the below works
Code:
>adb shell
error: closed
>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)
>adv shell 091XXXXXXXX490
error: closed
What am I doing wrong? how can I connect in recovery?

Stock recovery?

WillisD said:
Stock recovery?
Click to expand...
Click to collapse
Yes.

DiamondJohn said:
What I cannoit get woirking is ADB while in recovery mode
Click to expand...
Click to collapse
I always thought that adb from recovery was a TWRP thing?
I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.
Code:
$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I got the same thing booting to recovery by holding Vol down at boot.
Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.
Code:
$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed
Are you sure this is supposed to work with the stock recovery?

a1291762 said:
Are you sure this is supposed to work with the stock recovery?
Click to expand...
Click to collapse
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.
However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.

DiamondJohn said:
It wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
Click to expand...
Click to collapse
Yeah, it certainly seems to be speaking adb...
I didn't think to try...but maybe adb push and pull work?