Develop Bugs

adb sideload problem

Hi everyone,
just to clarify that It's my first time I try to unlock and root my phone, so no much knowledge.
I basically followed the steps to unlock the bootloader.
Everything worked perfectly, I reached the recovery, went on 'apply update from ADB'.
But then, when I enter in cmd: 'adb sideload <whatever the filename>'
it prints out the Android Debug Bridge instructions rather than transferring the zip file to my phone, and the phone keeps on asking "now send the package you want to apply to the device with adb sideload filename "
N.B.: the phone is recognized by adb, even when I enter adb devices, it is recognized
Any help?

did you try issuing the adb sideload command BEFORE pressing the button in recovery?
I had this issue before when trying sideload, in fact I think it WOULDN'T work if I started it via recovery FIRST. it has been a long time since I did this though, but I swear I remember not even having to press the button in recovery, I think it just automatically started once I issued the command from computer.

Yea, just tried it and same results

which recovery version are you using?(CWM or TWRP? and which version also)
and which adb version do you have on your computer? are you certain it is the latest available? did you install it through the Android SDK?

[Q] Installing OS into Nexus 7

Dear all,
I have a Nexus 7 3g, two days ago I rooted it so as to enable the tethering option. The rooting procedure I followed went well.
However, there as been some problem while enabling the tethering because at the boot the tablet was blocked while loading the OS.
So I decided to reinstall it but I had some problem and now the situation is that when I try to access to the recovery mode, I get the red triangle. I push power and bottom up, and I wiped all the data as suggested, typed "adb sideload android_4.3_stock_tilapia.zip", and got the error E: footer is wrong. E: signature verification failed.
I saw in the forum that I cannot use adb sideload to install a new OS but only for updates....
My question is: How can I use fastboot If when I type "fastboot devices" I have no device listed?
I thank you very much in advance for your help.
Best regards,
Enrico

etubaldi said:
Dear all,
I have a Nexus 7 3g, two days ago I rooted it so as to enable the tethering option. The rooting procedure I followed went well.
However, there as been some problem while enabling the tethering because at the boot the tablet was blocked while loading the OS.
So I decided to reinstall it but I had some problem and now the situation is that when I try to access to the recovery mode, I get the red triangle. I push power and bottom up, and I wiped all the data as suggested, typed "adb sideload android_4.3_stock_tilapia.zip", and got the error E: footer is wrong. E: signature verification failed.
I saw in the forum that I cannot use adb sideload to install a new OS but only for updates....
My question is: How can I use fastboot If when I type "fastboot devices" I have no device listed?
I thank you very much in advance for your help.
Best regards,
Enrico
Click to expand...
Click to collapse
Are you in the bootloader screen? If not then it would be 'adb devices'. 4.3_stock_tilapia.zip? That's for a 2012 N7 so I assume that's what you have.

wantabe said:
Are you in the bootloader screen? If not then it would be 'adb devices'. 4.3_stock_tilapia.zip? That's for a 2012 N7 so I assume that's what you have.
Click to expand...
Click to collapse
Thank you very much for your reply.
I was able to solve the issue by using Nexus Root Toolkit from the bootloader screen, as you suggested.
Enrico

[SOLVED] Sideload from recovery: Watch does not appear in adb devices

Hi all,
I have seen mentions in several places (including here http://9to5google.com/2014/12/18/how-to-update-android-wear-manually-ota-downloads/ and there http://forum.xda-developers.com/showpost.php?p=61430452&postcount=6 ) that it is possible to sideload an OTA to the SmartWatch 3 without using fastboot or rooting, just rebooting in recovery and running adb sideload.
However, in my case, although the watch properly appears in "adb devices" when it's powered on, when I go into recovery, it does not appear anymore... And thus I can't run "adb sideload" as adb, obviously, says "no devices found"
Any idea? Am I missing some trick? I have tried this both on Windows 8 and on Ubuntu, both behave in the exact same way.
I have also tried going into recovery using two different means: "adb reboot recovery" and using the menu that has fastboot/recovery options, nothing solves the issue.
Thanks!
PS: The reason why I am trying to sideload the OTA is to go 4.4 -> 5.0.1 and not 4.4 -> 5.1.1 because of all the 5.1.1 issues + I hate 5.1.1 UI

Did you click the adb sideload button in recovery? This enables adb.
If that does not work, try using fastboot to temporarily boot twrp from fastboot, but you will need to install fastboot drivers on your p.c. and find a 4.4 version of twrp.
The command is
Code:
fastboot boot twrp.img
From there you should be able to use adb.

Hi!
Do you mean selecting the "sideload" option in recovery? Yes I have selected this (by swiping down and then right to validate the choice) and my device still does not show up in adb. Have you been able to do this on the SmartWatch3? I feel like most people have experience with the LG G Watch...
In order to flash TWRP. I need to unlock the bootloader, don't I? If I can avoid voiding my warranty, that'd be great...
Thanks!

My first thought was the sideload option. I did not do it, but am on an SW3. I went right to option 2.
This does not unlock your boot loader, or void your warranty. What it does is hotboot another Rom (in this case recovery) without writing it to disk. I did do this, and it worked well.
This is the thread I followed. Skip the fast foot unlock step. That. An void your warranty.
http://forum.xda-developers.com/showthread.php?t=3107501

Oh! This is pretty awesome. Trying it, thanks a lot!

YESS! lekofraggle, I owe you a good one
So, for future readers, here is the procedure I went through. I have tried many different ways, this is the only which yielded results, so I'll only explain this one:
1) First, make sure that when your watch is connected to your phone, it displays the notification prompting you to upgrade your andoird wear version (I am not sure it will work if you don't have this notificaiton) (note that this notification only appears when the watch is connected to the phone in bluetooth, for me)
2) Follow http://forum.xda-developers.com/showthread.php?t=3107501 instructions to hot boot TWRP 5.0.2 (yes, even though you're in 4.4, does not matter (too much)). (command: fastboot boot twrp.img)
3) Root your watch by downloading the rooting zip from http://forum.xda-developers.com/attachment.php?attachmentid=3342605&d=1433157678 and "adb push yourzip /sdcard/root.zip"
4) In TWRP, your watch, go to "Install" and select "root.zip". You watch is now rooted.
5) Reboot your watch in normal android boot. Now push the OTA zip to it: "adb push yourota.zip /sdcard/update.zip"
6) Now is the trick: Replace the official OTA by yours: do "adb shell" and then "rm /cache/update.zip" and "cp /sdcard/update.zip /cache/update.zip".
7) Now check you still have the notification prompting for upgrade (your watch needs a bluetooth connection to phone, else it does not display it). Check the zip in /cache is still your by looking at the size, for instance: "ls -l /cache/update.zip" and compare with the size of your file.
8) If you're confident it is still your file, use the notifcation prompt on the watch and say you are ready to apply the upgrade.
9) Watch restarts and upgrade.... using your OTA file !
I tried using the custom "recovery command" that tutorials like http://www.carbontesla.com/2014/12/tutorial-update-smartwatch-3-lwx48p-android-5-0-1/ tell you to use but it would not work for me, only the notification would really trigger the upgrade...
Hope it helps!
PS: The reason for not using "adb sideload" directly from TWRP is that my OTA package (4.4 -> 5.0.1) would not be applied, it would complain that I am trying to apply it from a 5.0.2 system while it should be applied from a 4.4 system (oh, really?).

Great, I am glad it worked for you.
Two points for others travelling this path.
1)I am not sure you need to be rooted to do this, because twrp has its own permissions.
2) Did you try to use the install update.zip feature of twrp? That should have worked too.
Either way, I am glad you got there.
~Leko

My Nexus 7 2013 Bricked After 6.0.1 Update

I downloaded OTA Update on 6.0.1. After I installed the update, my nexus tablet became problematic. The google logo appeared and an android logo with a “No Command.” is displayed. It keeps on restarting.
I tried the Flash Stock + Unroot but everytime I do it, it says ADB Device Not found. I'm pretty sure I installed the driver. I notice the Device Manager keeps on reinstalling my device. I knew it because everytime I tried to Flash Stock my nexus tablet it says the the ADB Device was found but “unsupported”. And then when my tablet restarts, the toolkit says that "no ADB Device Found".
My problem here is how can I enable the USB Debugging? I can’t even land on the settings in my tablet. I can’t even do the fastboot mode (using the power on button, volume up and down).

Not shure, but think you can fastboot flash factory image without usb debugging enabled. But device must be unlocked. Just follow the flash factory image instructions on download site of your factory images from Google
Concerning bootloader hardware driver for fastboot, needed to flash. Only way I got that working (AND STABLE!) on Windows 8.X & 10 was by adding hardware id of my N7-13 to the inf file of the Google driver.
-With notepad add in inf-file in sections of BOTH x86 and x64 under other lines of Google Nexus 7 and save:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01 %SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0&REV_0100.
-Remove all old drivers of Nexus 7 related in Windows via device manager or better with USBDeview.
-Reboot with Windows 8/10 without checking hardware signature: hold shift while clicking reboot, choose advanced options, startup settings, option 7 with no hw signature check.
-In Win start device manager. Of unknown/usb/Android device choose update driver. Choose self from list, all devices, disk, browse to Google driver folder and choose that adjusted inf, click Ok.
Now there hopefully is no issue at all installing the driver. Google forgot to include hw id of our device. And it will be stable contrary to Naked driver, etc.that also miss correct hw id. Unless your hardware id is different from my Razor/Flo.
Check if device driver working correctly and Nexus is online in terminal via command 'fastboot devices'.
To be shure hardware id's of my Nexus 7-13 are via Windows device manager:
-adb tab normally booted:
USB\VID_18D1&PID_4EE2&REV_0228&MI_01
USB\VID_18D1&PID_4EE2&MI_01
-fastboot tab bootloader booted:
USB\VID_18D1&PID_4EE0&REV_0100
USB\VID_18D1&PID_4EE0

Thanks for the reply. However there are some pointers I could not understand. I am new on this process.
Does this one ends with a "dot"? Also, I'm having access denied on editing the .inf file.
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01 %SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0&REV_0100.
Click to expand...
Click to collapse
I am using Windows 7. Where is the Google driver folder? Is it correct I will create a inf-file on which folder?
Also on this one: I cannot understand how to do it or how to start on this process
Check if device driver working correctly and Nexus is online in terminal via command 'fastboot devices'.
To be shure hardware id's of my Nexus 7-13 are via Windows device manager:
-adb tab normally booted:
USB\VID_18D1&PID_4EE2&REV_0228&MI_01
USB\VID_18D1&PID_4EE2&MI_01
-fastboot tab bootloader booted:
USB\VID_18D1&PID_4EE0&REV_0100
USB\VID_18D1&PID_4EE0
Click to expand...
Click to collapse

frozenfire03 said:
Thanks for the reply. However there are some pointers I could not understand. I am new on this process.
Does this one ends with a "dot"? Also, I'm having access denied on editing the .inf file.
I am using Windows 7. Where is the Google driver folder? Is it correct I will create a inf-file on which folder?
Also on this one: I cannot understand how to do it or how to start on this process
Click to expand...
Click to collapse
Download Google USB driver from their website,
http://developer.android.com/sdk/win-usb.html
Unzip.
In there open with notepad the file android_winusb.inf.
Their add those mentioned lines direct under other lines of ;Google Nexus 7 in both [Google.NTx86] and [Google.NTamd64] sections.
Windows 7 don't need booting with hardware driver signature check disabled. Just confirm to install a unsigned driver when installing.
For the rest like said. Uninstall old Nexus 7 drivers. Manually update driver selecting adjusted android_winusb.inf file in downloaded unzipped Google Usb Driver-folder. Etc.

Hi Guys,
I have the same problem. I have the 2013 LTE with unlocked bootloader and stock recovery but no root Custom Rom, no root or other things installed. But I have device encryption and I need to get it booting again without loosing my data.
Error is as described above, I started the update, then it aborted with Error and after the automatic restart it stated "No Command".
When I tried entering Recovery it said "No command" again but i got in by pressing Power+Vol Up. In the logs it says "minzip: Error writing 32768 bytes from zip file from 0xbefef15c: No Space left on device..."followed by some more minzip-Errors.
In Android Update it called the OTA "6.0.1" but in Recovery it still says 6.0/MRA58V. Maybe I can just try and apply the OTA via ADB again (MMB29K?) or apply a newer OTA (MMB29O?), but I'll need confirmation that my data will be safe and a quick tutorial, please ^^
I'm guessing flashing those files manually should do the trick or removing something and applying the ota again. But how do I do that?
And if I try to "Apply update from SD card" it says "Couldn't mount /sdcard."
I did not try anything else like wiping anything, since I dont't want to lose my data.
Kind regards and thanks in advance
Hermelinmaster

Hermelinmaster said:
Hi Guys,
I have the same problem. I have the 2013 LTE with unlocked bootloader and stock recovery but no root Custom Rom, no root or other things installed. But I have device encryption and I need to get it booting again without loosing my data.
Error is as described above, I started the update, then it aborted with Error and after the automatic restart it stated "No Command".
When I tried entering Recovery it said "No command" again but i got in by pressing Power+Vol Up. In the logs it says "minzip: Error writing 32768 bytes from zip file from 0xbefef15c: No Space left on device..."followed by some more minzip-Errors.
In Android Update it called the OTA "6.0.1" but in Recovery it still says 6.0/MRA58V. Maybe I can just try and apply the OTA via ADB again (MMB29K?) or apply a newer OTA (MMB29O?), but I'll need confirmation that my data will be safe and a quick tutorial, please ^^
I'm guessing flashing those files manually should do the trick or removing something and applying the ota again. But how do I do that?
And if I try to "Apply update from SD card" it says "Couldn't mount /sdcard."
I did not try anything else like wiping anything, since I dont't want to lose my data.
Kind regards and thanks in advance
Hermelinmaster
Click to expand...
Click to collapse
Edit: Push, I could really use some help, please.

frozenfire03 said:
I downloaded OTA Update on 6.0.1. After I installed the update, my nexus tablet became problematic. The google logo appeared and an android logo with a “No Command.” is displayed. It keeps on restarting.
I tried the Flash Stock + Unroot but everytime I do it, it says ADB Device Not found. I'm pretty sure I installed the driver. I notice the Device Manager keeps on reinstalling my device. I knew it because everytime I tried to Flash Stock my nexus tablet it says the the ADB Device was found but “unsupported”. And then when my tablet restarts, the toolkit says that "no ADB Device Found".
My problem here is how can I enable the USB Debugging? I can’t even land on the settings in my tablet. I can’t even do the fastboot mode (using the power on button, volume up and down).
Click to expand...
Click to collapse
It's because you're trying to do this using a root toolkit. You need to go back to basics, flash the stock factory image using ADB/SDK and start over.

I fixed it by myself.
If anyone has ever a Problem like that, here is my solution to my specific problem:
1. I flashed TWRP
2. Backup with TWRP (data)
3. Flash Facory Images (Factory Resets didn't help at all)
4. Flash TWRP again (gets lost with the Factory images)
5. Restore all your data with TWRP
6. Reboot and be happy that all data is back.
It worked for me but it might not work for you, so no guarantee.
If you have a problem with my solution or if you need further instruction don't hesitate to ask.

Trouble Installing March Update OTA via ADB Sideload

Hello,
I downloaded the March OTA .zip from the thread in the general forum with the intention of installing via ADB sideload for the first time. I've installed the Android .sdk and confirmed that adb does work. Typing "adb devices" in the command prompt gives me the serial number.
I've used that to reboot to bootloader, go next to recovery, and click the "install via adb" option, at which point it instructs me to go back to the computer and push the file. I shift+right click on the folder containing platform-tools to open a command prompt tied to this folder (which also contains the downloaded OTA update, renamed "update" for convenience).
When I enter the command "adb sideload update.zip" it tells me that the device cannot be found. I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Device is stock, unrooted, bootloader locked. I wanted to try this before messing with fastboot and the binary images to get my feet wet, but it's been a headache inducing afternoon so far. I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Thanks in advance!

Try putting the OTA zip file in the same folder as the adb.exe file (in the platform-tools directory)

Moonboots said:
I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Click to expand...
Click to collapse
Are you using a Windows machine? I am far from an expert on these matters, but my sense is that failing to "see" the phone in recovery is usually a driver issue. See if this thread helps.
Moonboots said:
I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Click to expand...
Click to collapse
My experience has been that the only hard part of sideloading OTAs is the initial step of getting ADB running on a windows computer. Once you sort that out, it is very easy and also very liberating to not have to wait for updates over-the-air. Good luck!

Thanks for the help, all! The trick was letting Windows find its own driver (not the automatic setting, had to select this option) when the phone was in adb sideload mode. It's a different driver than fastboot and with the phone on.
Sideloaded the update last night and we're going strong! ?