My phone is without an OS hence sideloading. ADB set up fine. Device is recognised in ADB until I sideload. Then I get error device not found when installing. I'm using the latest SDK and have tried downloading the latest LG driver but I get an error in spanish (Ithink). Am downloading driver from here http://androidxda.com/download-lg-usb-drivers
Anyone help please?
PS - I am not sure if USB debugging was enabled before the brick...
So I've moved on from that. Manually installed the android composite drivers and all ok. But NOW I have a new error which I get regardless of the Rom. "error executing updater binary in zip '/sideload/package.zip"
Looks a more advanced error to me...
Is there any serious guru that can help me as I am now stuck. Tried Android ADB interface as driver and also latest LG as driver. I get to about 65% of install then "error updating binary....". It has to be a driver issue right???
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
bender_007 said:
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
Click to expand...
Click to collapse
Thanks for responding. It's internal memory so can only sideload anyway right? How would I 'push' and what mode would TWRP need to be in?
bender_007 said:
why don't you
"adb push filename.zip /sdcard/filename.zip"
instead of sideload ?
Click to expand...
Click to collapse
Ok worked this out. Have not put TWRP in to sideload mode and have entered the text in CMD. The cursor just flashes and has done for about 5 minutes now...But at least it doesnt say error
So it's pushed the rom to the SD card and I still get the error updating binary when I try to install. Tried 3 different roms and all get this error. Think there's nothing left to try.
There is. What twrp are you on? And what ROM are you trying to install?
bender_007 said:
There is. What twrp are you on? And what ROM are you trying to install?
Click to expand...
Click to collapse
Hi - I actually (naughtily) opened another thread on this as the problem is not with sideloading anymore. I cannot install anything (recovery, any rom) either by sideload or push. It's like TWRP is corrupt. I'm on 2.8.6.1. Installed simple tool v3.2 as well and I cannot overwrite TWRP as I get the fail again.
Extract the recovery.omg, push it to internal. Then use dd command to flash it manually
bender_007 said:
Extract the recovery.omg, push it to internal. Then use dd command to flash it manually
Click to expand...
Click to collapse
Thanks. Beyond that now. Tried installing CWM using installer and now get secure boot error. At least I finally got rid of TWRP
jamesbond_28_007 said:
Thanks. Beyond that now. Tried installing CWM using installer and now get secure boot error. At least I finally got rid of TWRP
Click to expand...
Click to collapse
How do you get rid of twrp and install CWM instead?
I think my TWRP is corrupted too, bootlooping for 3 days now
Related
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Trickee360 said:
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Click to expand...
Click to collapse
Can you get into bootloader with power+vol down?
boot into the bootloader, then via fastboot..
fastboot boot recovery recoveryname.img(press enter)
remember to put the recovery img file in the same folder that fastboot is located, on your computer.
bootloader's good to go and I'm in recovery but I need a way to get the rom on my tablet. Mounting sdcard doesn't appear to do anything while connected to my pc
EDIT: tried the CWM flash from sideload option and my command line says it "cannot read 'sideload'" do I need to start/restart the server another way? I feel like a total noob, lol
adb push rom.zip /sdcard/
Pirateghost said:
adb push rom.zip /sdcard/
Click to expand...
Click to collapse
started the daemon then got error: closed
Trickee360 said:
started the daemon then got error: closed
Click to expand...
Click to collapse
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Pirateghost said:
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no Can I do that through the sdk manager or do I have to update the sdk itself?
sdk manager can handle it
Pirateghost said:
sdk manager can handle it
Click to expand...
Click to collapse
Ugh. SDK manager won't install anything. EIther it says whatever package I'm working on requires API17 (which I'm trying to get, lol) OR it just plain can't "find" the package because acces is denied? What am I doing wrong?
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
sprafael said:
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
More info.what Phone mark modelo etc ?
Sent from my XT910 using Tapatalk 4 Beta
mc704 said:
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
Click to expand...
Click to collapse
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
sprafael said:
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
Click to expand...
Click to collapse
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
mc704 said:
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
Click to expand...
Click to collapse
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
sprafael said:
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
Click to expand...
Click to collapse
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
mc704 said:
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
Click to expand...
Click to collapse
the fastboot do you explain this link??
http://forum.xda-developers.com/showthread.php?t=2376681
I'm downloading the android SDK at this time
let's see if I understand
put the phone in adb sideload
will open the CMD in the fastboot folder,
type in adb sideload image-occam-jwr66v.zip
Flashable zip not factory image, try cm10
Sent from my Nexus 4 using xda app-developers app
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
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...
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord