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
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.
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
What operating system you're using?
Look here: http://forum.xda-developers.com/showthread.php?t=2010312
only this drivers worked for me
http://forum.xda-developers.com/showthread.php?t=1992345
Threadz said:
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
Click to expand...
Click to collapse
Hi the command is 'adb devices' if it's showing you the commands adb is set up correct. You don't actually need adb for this though, get your phone in fastboot mode and type 'fastboot devices' with your phone connected. If it outputs anything you're ready to flash a factory rom and fix your phone.
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...
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
After flashing recovery via flashify i get TWRP 2.6.3.3
but when i try to get firmware update mode (download mode) it stucks says: download mode.. and cannot recognize by PC whatsoever, so cannot use lg flash tool or support tool or dp-tool.
and in this mode phone gets really hot!
when i enter recovery i couldnt manage to install any rom because my sdcard is empty and otg-usb is not recognizable.
and in recovery mode, pc cannot detect the device only unknown device as "LG D802"
so i found android adb driver and manuelly install to windows.. but still i cannot pust any file over usb via adb.
adb push command gives me "read only system" error.
i also tried adb sideload to install custom rom from pc..
adb sideload command still gives me "read only file system"
i am assuming this is due to secured Kernel.. but i don't know what to do..
i also try the terminal command in twrp for adb commands.. but still no luck.
what can i do to push any custom rom.zip or any way around to install kdz?
i manually installed usb adv driver.. do i need to install as lg adb device..
can you give me a link to adb "inf" driver file?
Y uninstall current lg driver and download newest driver then reinstall( y can use google to find). Good luck
thanks i solved the problem via ubuntu.
i used "adb push" to /sdcard still got "read only" error.
but when i used "adb push" to /tmp i can managed to send/copy some zip files into my device.