Database Info

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.

pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?

All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.

rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1

pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.

zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")

You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus

rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back

rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."

pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?

rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1

pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed

pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

My borother screwed up his Moto G bad, won't boot

When my brother first got his Moto G, I helped him root it and set up Xposed Framework with a security module, per his request. When he got the notification to update to Android 5.0, he accepted it and thereby screwed everything up.
Now when he tries to boot the phone, it shows the Google logo with the unlocked bootloader icon underneath for a while before showing the boot error symbol (android guy lying on his back with a red triangle). I've noticed that during this boot animation, the screen flickers, which is something I've never seen before. When the error symbol shows up, I can hold volume up + power to get the recovery menu. I can also boot into the bootloader by holding volume down + power while the phone is off.
I've tried wiping the phone via recovery, flashing a factory image, anything I could think of, with no success. What should I do? Thanks in advance!

You probably have to flash full factory image including the bootloader in fastboot mode. Are you familiar with that?
tetakpatalked from Nexus 7 flo

tetakpatak said:
You probably have to flash full factory image including the bootloader in fastboot mode. Are you familiar with that?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Yeah, I'm sure I won't have any trouble with that. I couldn't find a link to a factory image though, do you have any idea where to look?

Muniosi said:
Yeah, I'm sure I won't have any trouble with that. I couldn't find a link to a factory image though, do you have any idea where to look?
Click to expand...
Click to collapse
On Motorola's website, same one where you can get bootloader unlock code. You just have to create login.
Did you see this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
tetakpatalked from N7100

tetakpatak said:
On Motorola's website, same one where you can get bootloader unlock code. You just have to create login.
Did you see this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
tetakpatalked from N7100
Click to expand...
Click to collapse
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.

Muniosi said:
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.
Click to expand...
Click to collapse
Ouch? I will check when I have my PC again, now I'm on road only with my phone.
tetakpatalked from N7100

Moto G Firmware
http://motofirmware.com/files/category/26-falcon/

ATTACK said:
Moto G Firmware
http://motofirmware.com/files/category/26-falcon/
Click to expand...
Click to collapse
That looks very useful, thank you so much! I'm not sure which file to download though. The device is a US-bought Google Play Edition phone, so would it be GPE_XT1032_KOT49H.M004_CFC.xml.zip?

Muniosi said:
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.
Click to expand...
Click to collapse
Hello mate, here are the firmwares:
http://www.firmware-team.com/forumdisplay.php?f=14
:fingers-crossed:

tetakpatak said:
Hello mate, here are the firmwares:
http://www.firmware-team.com/forumdisplay.php?f=14
:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot! I really appreciate it. I'll let you know if I have any troubles (but I should be fine). Thanks again!

I followed your advice and as far as I can see it should have worked, but I ran into an issue. Everything was going fine until I got this string of messages on the phone:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.

Muniosi said:
I followed your advice and as far as I can see it should have worked, but I ran into an issue. Everything was going fine until I got this string of messages on the phone:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I didn't check how the firmware gets installed. Is it a flashable zip?
If you are sure to have downloaded right firmware (for your device) and if you should flash zip in a custom recovery, just disable signature veriication in your recovery in such case.
But if the firmware consists img files that have to be flashed in bootloader mode with fastboot, maybe the firmware really doesn't match you device! Be sure to use proper factory image or recovery.
tetakpatalked from Nexus 7 flo

tetakpatak said:
I didn't check how the firmware gets installed. Is it a flashable zip?
If you are sure to have downloaded right firmware (for your device) and if you should flash zip in a custom recovery, just disable signature veriication in your recovery in such case.
But if the firmware consists img files that have to be flashed in bootloader mode with fastboot, maybe the firmware really doesn't match you device! Be sure to use proper factory image or recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I just downloaded the GPE_XT1032_KTU84P.M003_CFC.xml.zip file, booted into recovery, selected the sideload option, and used adb to push the .zip file to the phone. Did I do something wrong?

Muniosi said:
I just downloaded the GPE_XT1032_KTU84P.M003_CFC.xml.zip file, booted into recovery, selected the sideload option, and used adb to push the .zip file to the phone. Did I do something wrong?
Click to expand...
Click to collapse
IDK, as I wrote you before, you have to check the zip contents, and also to read in another threads how people are flashing factory image to Moto G.
Maybe the zip contains img files or also bootloader that need to be extracted and flashed in bootloader mode with fastboot (like on all Nexus devices)
I wasn't yet dealing woth flashing factory image on Moto G, on this phone I was so far only erasing it to install custom ROMs.
tetakpatalked from Nexus 7 flo

tetakpatak said:
IDK, as I wrote you before, you have to check the zip contents, and also to read in another threads how people are flashing factory image to Moto G.
Maybe the zip contains img files or also bootloader that need to be extracted and flashed in bootloader mode with fastboot (like on all Nexus devices)
I wasn't yet dealing woth flashing factory image on Moto G, on this phone I was so far only erasing it to install custom ROMs.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I'm not sure, but I unzipped the file and this is what it contained:
Code:
boot.img
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
motoboot.img
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2

Red triangle during the installation of Android 5.1 (OTA)

Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance

thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?

thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.

bitdomo said:
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?
Click to expand...
Click to collapse
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system

Visa Declined said:
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.
Click to expand...
Click to collapse
My nexus is completely stock, I never installed TWRP, ClockworkMod.

thejackal94 said:
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system
Click to expand...
Click to collapse
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.

bitdomo said:
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.
Click to expand...
Click to collapse
I tried to do the Wipe cache, but always same error (status 7)

thejackal94 said:
I tried to do the Wipe cache, but always same error (status 7)
Click to expand...
Click to collapse
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again​

bitdomo said:
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again​
Click to expand...
Click to collapse
I followed step by step the guide but again appears Status 7! I don't know what to do

thejackal94 said:
I followed step by step the guide but again appears Status 7! I don't know what to do
Click to expand...
Click to collapse
The next step would be doing a factory reset. If that not works then unlocking bootloader and flashing the latest stock rom in fastboot.

[Q] Trying to install CM

Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.

KalininTest said:
Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.
Click to expand...
Click to collapse
If your phone is on 4.3 or 4.4.2 you cannot install a custom recovery or CM because your bootloader is locked.

Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.

KalininTest said:
Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.
Click to expand...
Click to collapse
As far as I know, there is no way to unlock or replace the bootloader

Cannot sideload OTA

I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?

km8j said:
I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
Click to expand...
Click to collapse
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.

Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices

I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)

TonikJDK said:
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Click to expand...
Click to collapse
Hmm... Okay I will try this if next method fails. Thanks.
mrZoSo said:
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
donslade said:
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
Click to expand...
Click to collapse
So did you still adb sideload the Zip? Did that wipe the device?

km8j said:
Hmm... Okay I will try this if next method fails. Thanks.
So did you still adb sideload the Zip? Did that wipe the device?
Click to expand...
Click to collapse
Yes and it did not wipe the device.

Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update

mrZoSo said:
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
Click to expand...
Click to collapse
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.

This worked. Thanks all!

TonikJDK said:
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
Click to expand...
Click to collapse
True, but the guide was written just for sideloading the OTA, and works at this point.
Moving forward, you can always get the platform tools w/ADB, Fastboot from Google, without having to get the whole SDK or Android Studio.
Latest Platform Tools from Google for Windows