Hi all,
I've just received the update from Google and the Nexus 9 is just in an infinite look with the "No command".
I did never activate the developers option, so when I try adb is does not find the tablet. Only thing I've found is that I can boot to fastboot (power + vol up) and then Apply update from adb allows fastboot to access, although when I try to push a OTA it breaks after some minutes (maybe wrong usb cable ?)
Do I have any hope? I bought it in October to Google last year, it's probably out of warranty? I don't mind to play anyway, I have two weeks of holidays in front of me .
Thanks in advance.
If you didn't screw up recovery, there is a solution(for people in a similar situation).
uruen said:
Hi all,
I've just received the update from Google and the Nexus 9 is just in an infinite look with the "No command".
I did never activate the developers option, so when I try adb is does not find the tablet. Only thing I've found is that I can boot to fastboot (power + vol up) and then Apply update from adb allows fastboot to access, although when I try to push a OTA it breaks after some minutes (maybe wrong usb cable ?)
Click to expand...
Click to collapse
You need to sideload the OTA from recovery not fastboot! See the solution linked in the previous post
corkiejp said:
You need to sideload the OTA from recovery not fastboot! See the solution linked in the previous post
Click to expand...
Click to collapse
I'm getting an error
e:error /sideload/package.zip
From what I know, the device wasn't tampered with so I'm not sure what the problem is.
gwuhua1984 said:
I'm getting an error
e:error /sideload/package.zip
From what I know, the device wasn't tampered with so I'm not sure what the problem is.
Click to expand...
Click to collapse
2 things to consider: -
Are you using the correct OTA zip? (i.e. From your current version to next available version, not to the latest.)
Was the OTA zip corrupted while downloading.
Other than that maybe post your error in the linked thread.
corkiejp said:
2 things to consider: -
Are you using the correct OTA zip? (i.e. From your current version to next available version, not to the latest.)
Was the OTA zip corrupted while downloading.
Other than that maybe post your error in the linked thread.
Click to expand...
Click to collapse
Recovery shows LRX22C and I'm trying to use either: LRX22L-LRX22C or LRX22C-LRX21R.
I get this when I'm trying LRX22L-LRX22C
system partiition has unexpected contents
E: Error in /side/load/package.zip
(Status 7)
LRX22C-LRX21R
/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates
E: Error in /side/load/package.zip
(Status 7)
gwuhua1984 said:
Recovery shows LRX22C and I'm trying to use either: LRX22L-LRX22C or LRX22C-LRX21R.
I get this when I'm trying LRX22L-LRX22C
system partiition has unexpected contents
E: Error in /side/load/package.zip
(Status 7)
LRX22C-LRX21R
/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates
E: Error in /side/load/package.zip
(Status 7)
Click to expand...
Click to collapse
Your system partition has probably been corrupted, maybe TRY to RMA it with google or where ever you bought it, if it is still in warranty?
Related
Hello,
I am a recent smartphone user and I did what good friends told me to do. So I rooted my phone and installed CWM recovery in order to change the bootloader and the logo. Not important changes but only to change the background of the logo and bootloader from white to black.
I haven't installed any ROM.
My phone is a ZOPO C3 - Android 4.2.1
SuperSU, MobileUncle and Root Explorer apps installed
Since a few days I have an "upgrade 1" available in the update system app. The upgrade is called "untrusted.zip.
When I try to install this upgrade, I get an error message at the bottom of the screen. Here the complete message:
"CWM-based recovery v.6.3.0.2"
"E: invalid command argument"
"Finding update package..."
"Opening update package..."
"Verifying update package..."
"E: signature verification failed"
Then I click to install "untrusted.zip" and the following is added to the message:
"Installing update..."
"Flashing logo..."
"Patched"
"Now you can reboot your phone".
After reboot the phone, the upgrade is still available. It seem not to have been applied.
Any idea what I missed please ?
as it says signature verification is failed hence the update was not installed
before selecting zip change the verification check in cwm-install zip from- here
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
stadeverois said:
Hello,
I am a recent smartphone user and I did what good friends told me to do. So I rooted my phone and installed CWM recovery in order to change the bootloader and the logo. Not important changes but only to change the background of the logo and bootloader from white to black.
I haven't installed any ROM.
My phone is a ZOPO C3 - Android 4.2.1
SuperSU, MobileUncle and Root Explorer apps installed
Since a few days I have an "upgrade 1" available in the update system app. The upgrade is called "untrusted.zip.
When I try to install this upgrade, I get an error message at the bottom of the screen. Here the complete message:
"CWM-based recovery v.6.3.0.2"
"E: invalid command argument"
"Finding update package..."
"Opening update package..."
"Verifying update package..."
"E: signature verification failed"
Then I click to install "untrusted.zip" and the following is added to the message:
"Installing update..."
"Flashing logo..."
"Patched"
"Now you can reboot your phone".
After reboot the phone, the upgrade is still available. It seem not to have been applied.
Any idea what I missed please ?
Click to expand...
Click to collapse
one more thing I forgot
if it is a phone upgrade then it wont work with root you have to try any temporary unroot for installing that
sangalaxy said:
as it says signature verification is failed hence the update was not installed
before selecting zip change the verification check in cwm-install zip from- here
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
one more thing I forgot
if it is a phone upgrade then it wont work with root you have to try any temporary unroot for installing that
Click to expand...
Click to collapse
Thank you for your reply sangalaxy !
As I told in my message, I am a recent user and Android is new for me (I just left my old GSM for a few weeks ).
Sorry if my question seem to be so stupid but how/where can I check in my CWM-install and how to temporary unroot ?
Thanks for your support
stadeverois said:
Thank you for your reply sangalaxy !
As I told in my message, I am a recent user and Android is new for me (I just left my old GSM for a few weeks ).
Sorry if my question seem to be so stupid but how/where can I check in my CWM-install and how to temporary unroot ?
Thanks for your support
Click to expand...
Click to collapse
for temporary unroot there are some apps even superuser has this option search google
for the check in cwm I don't remember correctly but in cwm home when you choose zip from sd there are 4 options
1 choose zip from sd
2 blah blah
in these 4 options there is one with verified option check that
sangalaxy said:
for temporary unroot there are some apps even superuser has this option search google
for the check in cwm I don't remember correctly but in cwm home when you choose zip from sd there are 4 options
1 choose zip from sd
2 blah blah
in these 4 options there is one with verified option check that
Click to expand...
Click to collapse
I found the way to unroot via SuperSu but I have a problem for the rest. I can only start in recovery mode via MobileUncle Tools (Vol (+) + Power doesn't work) and if I do that, I don't see anywhere an option to check in. Only install ZIP file is allowed. May be it not that way you mean but sorry again I'm a beginner :silly:
stadeverois said:
I found the way to unroot via SuperSu but I have a problem for the rest. I can only start in recovery mode via MobileUncle Tools (Vol (+) + Power doesn't work) and if I do that, I don't see anywhere an option to check in. Only install ZIP file is allowed. May be it not that way you mean but sorry again I'm a beginner :silly:
Click to expand...
Click to collapse
do you have a cwm zip for your phone if yes install that zip from recovery it will give you options
and if you are temporary unrooted check again with that update zip
Cershma suji
sangalaxy said:
do you have a cwm zip for your phone if yes install that zip from recovery it will give you options
and if you are temporary unrooted check again with that update zip
Click to expand...
Click to collapse
I don't have a cwm zip (my cwm recovery file was an IMG file) and if I'm temporary unrootet, after applying the Upgrade file, it is still the same situation: after reboot, the upgrade is still there.
stadeverois said:
I don't have a cwm zip (my cwm recovery file was an IMG file) and if I'm temporary unrootet, after applying the Upgrade file, it is still the same situation: after reboot, the upgrade is still there.
Click to expand...
Click to collapse
Idk what to do friend may be you have to unroot or leave the update
Sent from my GT-S6102 using xda app-developers app
I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
n2outlaw said:
I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62349128
n2outlaw said:
Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
DoLooper said:
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
Click to expand...
Click to collapse
I did try that and from USB and the same thing.
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=62349128
Click to expand...
Click to collapse
Thanks!! I used a link inside of the one you gave.
Return to Stock
Hi Everyone,
I know, I fell in a noob trap doing this and I already hate myself for it : I tried to OTA update my rooted Honor 7 and the device remained stuck in TWRP after reboot.
Log showed the following message in red : "E: error executing updater binary in zip"
I proceeded to a wipe and managed to start the system. This allowed me to unroot my phone, thinking I would then be able to update from a clean basis.
Unfortunately, the same error occurred and I am now stuck in TWRP again...
I would be grateful if anyone could provide me some leads to get out of my noob trap...
Thank you very much !
Edit : I finally understood how i managed to start system (I deleted the update.zip file and wiped again). Still, now how can I update to the latest version without getting stuck again in TWRP ? Thank you !
Prowls said:
Hi Everyone,
I know, I fell in a noob trap doing this and I already hate myself for it : I tried to OTA update my rooted Honor 7 and the device remained stuck in TWRP after reboot.
Log showed the following message in red : "E: error executing updater binary in zip"
I proceeded to a wipe and managed to start the system. This allowed me to unroot my phone, thinking I would then be able to update from a clean basis.
Unfortunately, the same error occurred and I am now stuck in TWRP again...
I would be grateful if anyone could provide me some leads to get out of my noob trap...
Thank you very much !
Edit : I finally understood how i managed to start system (I deleted the update.zip file and wiped again). Still, now how can I update to the latest version without getting stuck again in TWRP ? Thank you !
Click to expand...
Click to collapse
You have to flash stock recovery before update and unroot of course.
Sent from PLK-TL01H
Lucki_X said:
You have to flash stock recovery before update and unroot of course.
Sent from PLK-TL01H
Click to expand...
Click to collapse
Thank you for your answer ! I found the image of the stock recovery but I can only find instructions for windows and I run on mac... Do you happen to know how can I get to flash the recovery image using terminal ?
Thank you again !
Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
HI guys, I did this guide https://forum.xda-developers.com/moto-z/how-to/how-to-relock-bootloader-moto-z-xt-1650-t3821817 to relock bootloader and flash stock rom and it worked. I have now 8.0 oreo on my phone, but it doesnt OTA update, there is a security patch from 1st july, it downloads, then reboots to install mode, but while installing like 1/3rd of the bar, the android robot appears laying on the ground with red mark saying "Error". Any help is appreciated pls. thanks!
Pathera said:
HI guys, I did this guide https://forum.xda-developers.com/moto-z/how-to/how-to-relock-bootloader-moto-z-xt-1650-t3821817 to relock bootloader and flash stock rom and it worked. I have now 8.0 oreo on my phone, but it doesnt OTA update, there is a security patch from 1st july, it downloads, then reboots to install mode, but while installing like 1/3rd of the bar, the android robot appears laying on the ground with red mark saying "Error". Any help is appreciated pls. thanks!
Click to expand...
Click to collapse
try to sideload the ota through adb, you'll find out what's causing the error
Pulsa said:
try to sideload the ota through adb, you'll find out what's causing the error
Click to expand...
Click to collapse
error in recovery it shows me this:
Verifying current system... E3005: "/bt_firmware/image/btfw32.tlv" has unexpected contents. E:Error in /cache/Blur_Version.27.211.6.griffin.retail.en.US.zip (Status 7) Installation aborted.
You received error because you used the wrong OTA file (Blur_Version.27.211.6.griffin.retail.en.US.zip it's already installed on your phone if you re-locked it).
On the other topic I gave you the tutorial to sideload and the correct file to use, Blur_Version.27.231.8.griffin.retail.en.US.zip.
Pathera said:
error in recovery it shows me this:
Verifying current system... E3005: "/bt_firmware/image/btfw32.tlv" has unexpected contents. E:Error in /cache/Blur_Version.27.211.6.griffin.retail.en.US.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
just reflash the btfm file using fastboot
Pulsa said:
just reflash the btfm file using fastboot
Click to expand...
Click to collapse
Did that still same error and sideloading also wont work it gives me the same error