My pixel C has the issue today.
the robot was down. the system is 7.1.2beta
I was meet this issues last time. I was downloaded the OTA image,and use the "sideload " to save my pixel .its useful.
but today, when I downloaded the 7.1.2 OTA image and use the sideload. its unused
error tips as below
E:footer is wrong
E:signature verification failed
E:error :21
I try to downloaded again and again. even use my other laptop to do. also failed.please help me
I think that you downloaded the firmware image, and not the ota version. ( the first one requires fastboot and oem unlock ), the second adb sideload and tablet in recovery mode
Related
Hello All,
I have GPE version of GPad running Kitkat 4.4 Stock ROM. Last month I have used following link to enable chromecast mirroring. Due to the issues i have uninstalled superuser app and did factory reset. After that all well! I mean no issues with tablet.
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Yesterday I tried to sideload the GPE lollipop update but prompted with following error.
"/system/etc/audio_policy.conf" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
This morning I saw system update notification for Lollipop upgrade and opted to install it, but without any further msg during the system update it prompted with "Error!" After that I did factory reset. When it reboots starts optimizing 48 apps, but it prompts with following sequence of messages:
"Unfortunately sun beam has stopped. "
None of the apps loaded , no access to setting, just empty screen and on screen buttons at the bottom.
I spent quite some time looking around in xda to restore back to factory, none seems to work.
1. Tried flashing original stock .tot file, getting "Download user image is only available in the online environment!!
2. adb sideload, "/system/etc/audio_policy.conf" has unexpected contents
3. To Flash TWRP i am not getting access to setting to enable USB debugging.
Now i cant even put the G Pad in adb as i dont have access to settings to put in USB debug mode. vol down+power puts into bootloader, but cant access to adb commands.
Now I can only access to recovery and do sideload. but i am stuck with "/system/etc/audio_policy.conf" has unexpected contents error. Can someone share kitkat original version of audio_policy.conf? also how i can replace the exiting file as i dont have access to adb?
Greatly appreciate your help to bring back the G Pad.
regards
Raj
You can boot twrp from fastboot and flash either 4.4.4 or 5.0 back onto your tablet. Look at the thread in Android development for more details on flashing the stock images using twrp
Thanks! I was able to get back to kitkat with following method. I was able to flash recovery its now back to complete stock kitkat now.
http://forum.xda-developers.com/lg-...510-gpe-4-4-4-ktu84p-l002-stock-twrp-t2797883
After this I got system update notification to lollipop. Again got "Error!" msg during the install process.
I tried adb side load, got following error!
failed to verify whole-file signature
signature verification failed
installation aborted.
Any thought whats going wrong there?
My micromax android one phone is stuck during boot with micromax boot logo. It has 5.1.1 android version with build number LMY47V.
To recover this, I am trying to flsah rhe ROM with this OTA - d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7.zip
But I am getting below error:
Can't install this package over newer build
E:Error in /sideload/package.zip
However, in file ..\d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7\META-INF\com\google\android\updater-script, I removed the line which checks for newer build. But with that I am getting now following error:
E:Failed to verify whole-file signature
E: signature verification failed
IS there any way to avoid this signature problem.
Please help find OTA which could be flashed on my phone or any other suggestion.
I tried putting twrp recovery which requires device to be in debugging mode. Since my device is not booting to that stage, I skipped that part and tried if via other fastboot commands, it will be done or not. But this also fails as the device remains in default recovery.
I tried flashing through SP Flash tool also, but there it is not able to detect the device.
Please let me know if something else can be tried. Appreciate any help on this.
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
JJT211 said:
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
Click to expand...
Click to collapse
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
saxmydix said:
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
Click to expand...
Click to collapse
Yup, im on 29.0.4
So I found the command to switch to slot A
fastboot set_active a
Still stuck in bootloader mode.
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
OK I did the regular flash-all as you said and got error. At this point, the CLI says press "any key to exit"
I then exited, selected recovery - apply ADB update - opened CLI - adb devices (saw my serial #) and then entered "adb sideload image-crosshatch-qp1a.191005.007.zip"
And now after im getting:
verifying update package....
E: footer is wrong
Update package verification took .2 s (result 1)
E: signature verifcation failure
E: error: 21
Install from ADB completed with status 2
Installation aborted
EDIT: Im an idiot, I tried to sideload the factory image. Im sideloading the OTA now. Looks like its working. Standby
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
JJT211 said:
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
Click to expand...
Click to collapse
Tried several ways to get into recovery (fastboot.d) to sideload the ota after the i/o error... After a hour i got the trick (3. try to begin with flash-all.sh...). Somehow i always got trouble with system space when monthly update is downloaded automatically and can't get applied because i am rooted... Somehow it seems saver to install the full ota with sideload than the flash-all.sh procedure... Glad it also worked on your side.
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
Which file do i sideload? I tried crosshatch-qp1a.191005.007-factory-2989a08d.zip. It failed with same error as guy above. I then tried to adb sideload image-crosshatch-qp1a.191005.007.zip and i got the same error? which file am I supposed to sideload?
EDIT:Never mind. I found the file. downloading and flashing hopefully it works!
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
z3dulik said:
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
Click to expand...
Click to collapse
Just nuke it with flash-all.bat May factory image. You can boot TWRP and flash the R OTA as well.
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
When I turn it on i have an alert "your device is corrupt."
z3dulik said:
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
Click to expand...
Click to collapse
I would extract the factory image, fastboot erase user data then update bootloader, radio and vendor on both slots(reboot bootloader after each flash) then flash-all or fastboot update with the Taimen file that contains the vendor image
It's a bit longer of a process but it works.
Tried too, same thing. Looks like it's something related to recovery. Can't write to
z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
Swap slots and flash to both
Sent from my Pixel 4 XL using Tapatalk
Managed to flash twrp on boot_a
z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
I've got out of this before
Boot TWRP
Format data
Pop in an otg with stock OTA hit mount go back and hit mount then it'll appear as auto-1 in TWRP and flash the OTA
It works if you need to go back to previous month or Android version. Just make sure both slots are the same after you boot
OTG not recognised
/vendor error
also the factory images are missing from here? https://developers.google.com/android/images
I can see only OTA
fixed with factory android 10 april. thanks all for help
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
dkmoore said:
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
Click to expand...
Click to collapse
You should not have done that.
Nokia does not allow sideloading on this device. Please check your PM.