Database Users

download mode

I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?

May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler

What's up now ?
Sorted it out or still issues there ?

I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #

Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.

bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"

I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"

I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...

TWRP wont start ADB sideload

Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!

have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder

Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk

meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"

boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory

[Solved] [CWM] Can't adb shell in CWM

Hi all.
I have this S4, screen broken, no digitizer, USB debug not enabled and can't mount with MTP for unknown reasons. The owner asked me to retrieve some saved stuff.
Ok, I installed CWM recovery via Heimdall and plugged in the usb, but can't connect to it with adb:
Code:
$ adb devices
List of devices attached
(none)
I believe CWM is running just fine, 'cause if I push vol- and then power it goes in sideload mode, and then ADB can see it:
Code:
$ adb devices
List of devices attached
1c1a1234 sideload
...but obviously, with the device in sideload mode, i can't adb pull from it.
Any suggestions?

Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.

Lennyz1988 said:
Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.
Click to expand...
Click to collapse
.....aaaand this one made the trick!
Misson accomplished and reputation honored! Thanks!

How do I adb sideload to 6P in recovery mode from a mac?

I have done this from windows, but not having any luck on OS X (el capitain).
I can do adb commands when the device is booted (adb devices shows device). So I reboot into fastboot, and from there I get into recovery.
Once in recovery I select "apply update from adb" and the device waits.
However, on my mac adb devices doesn't show anything. Even after restarting adb daemon it still doesn't show device.
What am I missing? I assume I can do this on a mac?

did you install adb/fastboot into your path? do you have the latest adb/fastboot?
easiest Mac method for installing adb/fastboot: here.
Also for El Cap, see this.
Obviously pay attention to the part for El Cap users.

While the device is booted normally install the file using adb install <FileName> if you want to put an update.zip file on the phone. adb push update.zip /location on phone/

Thanks for the replies. I basically had to reconnect the device before entering apply update from adb .
All the paths and such were fine.
Sent from my SM-T810 using Tapatalk

S10+ on oneui 2 beta 2, adb doesn't recognise device in recovery anymore

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.