I booted my Echo Show into recovery mode, and went over to the adb thing. I plugged it into my computer, and ran "adb devices". It came up with "CODE Sideload", but I'm not sure what I can sideload. I also tried "adb shell", but it just gave me "error: closed". If anyone can tell me whats possible to sideload, it would be great.
That sideload mode is only for firmware update. It only accepts Amazon signed ROM files (*.zip)
Related
I had a problem and my wifi tablet is now bootlooping. So I looked into using adb sideload to re-install a rom.
When I enter sideload (twrp) and do adb devices it lists my device with sideload beside it.
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF sideload
when I try to sideload the rom adb c:\rom.zip I get error closed.
I tried adb usb to reset the usb but getting error closed.
C:\Windows\system32>adb usb
error: closed
By the way I am running windows 8
Really stuck any ideas!
I have been able to download the stock image and use fastboot to flash so I think I have the issue sorted!
I had the same problem three days ago. Try this method. It works for me write this on command " adb sideload filename.zip" hit enter don't put quote. If this not for you, go head try
adb push filename/data/media/
If you are on 4.2.2
adb push filename/data/media/0/
Good luck
Sent from my SPH-D710 using xda premium
Sideload mode is just a subfunction of your recovery. Create a blank .zip file and push it to the device using adb push C:\pathtozip\whatever.zip to abort. You'll be kicked back to your recovery and will be able to reboot.
hi there
I installed twrp using adb, that means i am able to use adb when i'm in the OS
but when i boot into TWRP, i cant get my pc to recognize my phone, when i type "adb devices", nothing shows up ...
and when im in TWRP and go to advanced, adb sideload, i swipe to start it and it says "starting adb sideload feature.." and it stays forever -_-
what could be the problem and how can i fix it ?
j_h3000 said:
hi there
I installed twrp using adb, that means i am able to use adb when i'm in the OS
but when i boot into TWRP, i cant get my pc to recognize my phone, when i type "adb devices", nothing shows up ...
and when im in TWRP and go to advanced, adb sideload, i swipe to start it and it says "starting adb sideload feature.." and it stays forever -_-
what could be the problem and how can i fix it ?
Click to expand...
Click to collapse
Which twrp, first version didn't have adb support as I recall...
Happened to me too. Go to device manager and uninstall any drivers, then install generic adb device
When i tried to Boot from recovery mode i got Error message with no command.. none of those option in recovery mode working. My phone is UN rooted running on official 4.3 Jellybean. Is this only i m getting? or because my phone is unrooted its locked?
Some Assist would be nice thank You
try using ADB commands:-
connect your phone using usb cable (with usb debugging enabled in developer options)
open command prompt (windows)
if you have ADB as environmental path then just type "adb reboot recovery"
else you need to navigate to the adb.exe and then type the upper command.
it worked for me
can u link where can i download ADB tool
i've attached the latest ADB version 1.0.31 (don't use older versions as they wont work on our device)
Hi, this is my first post here.
I have a rooted Samsung S4 with a broken screen, that I can put in recovery mode and send commands with adb.
I would like to activate USB Debugging and I found on the forum the adb commands to do it.
I have a problem: when I restart the phone to exit the recovery mode and try "adb devices" I always find it "unauthorized".
I noticed that when I run in recovery mode "adb push adbkey.pub /data/misc/adb/adb_keys", the command seems to work. In fact, if I try immediately with "cat /data/misc/adb/ adb_keys" I see the content correctly.
But if I restart the phone still in recovery mode and I try again immediately "cat /data/misc/adb/adb_keys", the file is non-existent.
I guess this is not correct.
How can I try to solve?
Hi all,
I used "adb sideload" method to update my S10+ (AUT) to oneui beta 2. Now I'd like to update to beta 3 but when in recovery "adb devices" doesn't see my device anymore so I cannot sideload. When I reboot to system, "adb devices" shows my device without problem. I'm using stock usb cable.
Any help greatly appreciated.
EDIT: I was trying on OSX so I checked on Windows 10 and the result was the same.
EDIT2: Ok, so I went back to Pie 9 with ODIN. After that, ADB in recovery mode is back to normal. I used "adb sideload" to install beta 2, all fine, boots fine. But when going back to recovery, I get errors and device is not visible with "adb devices" once I choose the ADB update method.
This message on the phone when entering recovery mode:
#Reboot Recovery Cause is [BL:Recovery Mode Set by keys]#
E:[libfs_mgr]Unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing
E:[libfs_mgr]Failed trying to run /system/bin/e2fsck
Supported API:3
And then upon choosing ADB update mode:
# MANUAL MODE v1.0.0 #
Now send the package you want to apply
o the device with "adb sideload filename..."
EDIT3 : I cleared cache partition and factory reset. Now the errors are gone when entering recovery but phone still not visible with "adb devices" after entering adb update mode.
EDIT4: Ended up reinstalling only recovery from latest pie through ODIN as adb sideload as that one worked to sideload pie -> beta 2 but alas "adb devices" doesn't recognize my device. Conclusion, once updated to beta 2, I cannot use adb sideload to install beta 3. Any help appreciated
I have the same issue as you do on the S10+, except my recovery was corrupted from the beginning, on stock pie ADB sideload couldn't load due to missing usb node and configfs file.
I flashed multiple times with ODIN and it didn't bring ADB back. Luckily I had an old SD card laying around, so I have been able to flash each beta .zip from that. I've been checking ADB at each beta version, and as far as I can tell, my ADB keeps throwing the same error as yours...I'm not sure if this is a Samsung beta issue, or if our phones are just special.
Hopefully, you can continue to install the betas using an SD card.
I had the same error whem trying to flash the beta 3 update, but i solved it aplying the update.zip from a SD Card and all worked. Like the above post.