Database Users

[Q] N10 *seriously* bricked after CF-Auto-Root and OTA

Since I'm a newbie here I can't post this problem to "[N10] CF-Auto-Root". If some kind person with permissions could alert the people there to this problem I'd really appreciate it.
I installed CF-Auto-Root on my Nexus 10, and after an OTA upgrade to 4.3 the tablet is seriously bricked. The sequence was as follows:
* Started from stock 4.2.2
* Downloaded the latest CF-Root (July 29)
* Manually re-rooted (as instructed on first page)
* Everything is peachy. su in adb shell works, get root prompt, etc. Browsed directories but made no changes.
* Attempted an OTA upgrade to 4.3 (Forgot to re-lock the bootloader). Upgrade failed, giving some generic (as in uninformative) error message. I think it was something about file check failed,
Now the tablet boot-up doesn't get past the colored X. I can get into bootloader/fastboot mode (robot on back with panel open). The device information is as follows:
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: MANTALJ12
Carrier Info: NONE
Serial Number: <looks okay>
Lock State: UNLOCKED
Reboot Mode Flag: NONE
This is where I was when I first loaded CF-Root. However, now "adb devices" on the PC (Arch Linux) gives a blank list of devices. When I try to load the factory 4.3 image with "fastboot -w flashall" the PC prints the message:
< waiting for device >
and sits there. Not surprising since adb can't see the device.
I can get into recovery mode (robot on back with red triangle), and can access the menu. Performing wipe data / factory reset hasn't helped. From my PC "adb devices" still shows a blank list of devices.
When I start the "Apply update from ADB" utility from recovery mode, "adb devices" on the PC shows:
???????????? no permissions
If I then enter "adb sideload <file>" on the PC as the prompt on the tablet suggests (the file I used was an Android 4.3 upgrade zip file), the PC responds with:
error: insufficient permissions for device
Does anyone have any idea how I can get my tablet out of this mess? Right now all I want is to get my tablet working again. Any ideas are most welcome.

There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.

Solved
Got it solved (whew!). Had to run fastboot as root on the PC.

plastikowl said:
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Click to expand...
Click to collapse
Yeah, I knew I'd lose root, but I'd already installed CF-Autoroot. Figured it would be easy to root again after. Foolish me!
Afraid I forgot to write down the error so it's lost. I was trying to do a full flash but failing (see my "solved post"). The update attempt was desperation, trying to get to the tablet somehow.
Anyway, I managed to do a full flash to the 4.3 factory image, so my tablet is no longer an expensive paperweight.
Thanks very much for yout input.

[Q] Failed Kit Kat OTA update on rooted Nexus 7 Wifi - stuck on loading animation

I stupidly started the OTA update on my rooted device and it failed. Now I am stuck at the 4 circles animation after the Google logo.
I've tried following the guide to flashing a factory image with fastboot / return to stuck but at the step where I'm supposed to be able to list devices (step 3 of driver installation), no devices are listed.
In my Device Manager, the Nexus 7 is listed as MTP USB Device with a yellow warning triangle over the icon.
I've gone over the installation instructions many times and repeated the process 4 times.
What else can I do?

Now I see Android Device and under that Android Bootloader Interface in my Device Manager (using Windows 8) when I am in fastboot.
I tried updating the driver per instructions (although it only has instructions for up to Windows 7) and the message says that I have the most updated driver already.
However, my device is not listed once I try the command "adb devices"
I guess I am in "driver hell" but what how do I fix this? I've tried installing and uninstalling everything multiple times.
My N7 was rooted and has CWM. (Yes I know I know that I shouldn't have done OTA but I made a mistake.)

I had a similar problem, though on mine the installer ran after I said not to. Afterward my tablet would start up but stay on the four pulsing circles. I tried waiting and after an hour figured that wasn't going to work.
This is how I got my tablet working again. Mine is the wi-fi 2012 version. I first followed that same guide as you and it wouldn't work. So I tried a diffrent way.
after step 8 on that Flashing a Factory Image with fastboot / return to stock guide, installing the "Google USB Driver",
Download and install the Nexus Root Toolkit from Wugfresh (can't post links yet).
Set the tablet as the Nexus 7 (Wi-Fi Tablet) and Android build 4.3.0 JWR66Y
Then Flash Stock and Unroot under Back to Stock with Soft-Bricked/Bootloop chosen.
I chose the same factory image that I had set my tablet as, 4.3.0 JWR66Y.
Once it ran I was back on 4.3.0 and had a working tablet again.

annabwashere said:
However, my device is not listed once I try the command "adb devices"
I guess I am in "driver hell" but what how do I fix this? I've tried installing and uninstalling everything multiple times.
Click to expand...
Click to collapse
http://www.wugfresh.com/
Download and install Nexus Root Toolkit.
It comes with several ADB drivers and shows information about that.

Worked! Thanks!

Sideloading - device not found

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

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.

Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.

v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?

D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?

5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.

D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.

How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification

xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

Revert Android 11 to Android 10...

I have been on Android 11 DP since it was released and for the most part it has been stable. Unfortunately, my password app isn't working and could take months for it to be functional on 11.
Has anyone had success reverting back to 10 from 11? I've tried more times than I care to admit, but have not had any success.
Any suggestions would be welcomed.
G.

https://developers.google.com/android/images

Here you go

shannoncole05 said:
https://developers.google.com/android/images
Click to expand...
Click to collapse
I've tried several times, but have been unable to revert back!

Take note of which partition you are on, either A or B, check this on the main bootloader screen at the bottom of the screen. After you see if you're on A or B, flash the March factory image. As soon as the flash completes, you need to go right back to the bootloader screen and switch to the opposite partition that you are on. For example if you were on A before flashing the image, you need to switch to B and visa versa. To switch, from the bootloader screen type: fastboot --set-active=a or fastboot --set-active=b
After switching the active partition, reboot the phone and you'll be able to boot into Android 10 and will no longer be stuck on the 11 preview.

Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you

Downgrade
badwolf1972 said:
Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you
Click to expand...
Click to collapse
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools

Thank You!
caballon said:
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!

klm2349 said:
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!
Click to expand...
Click to collapse
Erased all right?

Question?
Not sure what the question is? It erased correctly and reinstalled Android 10.