Hi guys,
so I have a PX5 unit that came with Android 8.0 and though a long failed update process I ended up in on Android 6.
I am trying to get back to Android 8. I have the official Android 8 image from the manufacturer.
When I try to install the update from recovery, I get the Error "Status 7".
I remove the assert-lines in the update-script, but I get the " verify whole-file signature" error.
Any way to fix that or force install the update?
Thanks
Related
Hi everyone,
I wanted to try CyanogenMod 7 and I installed ClockworkMod. Honestly I didn't like it for several reasons, so I've brought back my phone to the original system. The thing is everything works just fine except I want to install the system upgrade, the download is done and my mobile phone reboots in the attempt to apply the new system changes and... it stops, there's this triangle with an exclamation mark in it and the android robot. I try to press some buttons and clockworkmod shows up. An error is shown and it's the following:
Code:
download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_P_release_160253fsslvctb45xcxfhv.zip]
E: Can't mount SDCARD:download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_P_release_160253fsslvctb45xcxfhv.zip
Installation aborted.
Click to expand...
Click to collapse
I'd like to restore my system and get the latest upgrade, do I need to uninstall ClockworkMod? I've looked a bit in this forum for a solution but I didn't quite understood how to proceed. Will please anyone explain it to me?
A few infos you might need to know:
Hboot ver. 0.80
ClockworkMod Recovery ver. 3.0.0.6
Thank you for your help.
Update: I've managed to get into ClockwordMod and manually choose to install from zip file so I reach the download folder and select it, an error occurs:
Code:
-- Installing /sdcard/download/OTA_Buzz_Froyo_HTC_WWE_2.22.405.1-1.37.405.1_P_release_160253fsslvctb45xcxfhv.zip
Finding update package...
Opening update package...
Verifying update package...
E: failed to veify whole-file signature
E: signature verification failed.
Installation aborted.
Click to expand...
Click to collapse
-H.
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.
So I have not been able to use my Zenfone 3 Deluxe for a couple of years and have decided to revisit it again to hopefully fix the problem.
My Zenfone 3 Deluxe has been stuck in a bootloop ever since I've tried to downgrade.
So currently I am not able to access the bootloader. The only thing I am able to access is recovery mode to update from ADB or through SD card.
I've been reading up on a lot of ADB guides and have downloaded the latest one r29.0.5
The steps I've taken are:
1. Boot into recovery mode.
2. Download both UL-Z016_1-WW-4.12.40.1698-user.zip & UL-Z016_1-WW-15.0210.1810.73-user.zip from the Asus website.
The reason I downloaded the 4.12.40 is because I thought I had to match the firmware if the 15.0210 were to not work and it hasn't.
3. I would go to update from adb on my Zenfone 3 Deluxe
4. CMD: adb sideload UL-Z016_1-WW-15.0210.1810.73-user
The problem I have been currently running into and is making me frustrated is that I get the following Error:
E:unknown volume for path[/sideload/package.zip]
Verifying update package . . .
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
----------------------------------------
If anyone can help me bypass this failed whole-file signature situation, that'd be great. Thanks!
I've also read somewhere that installing a CWM or TWRP can bypass the whole-file signature error. I believe that can only be done by installing through SD card which I have in case if needed.
Any help would be appreciated. At this point, I'm just trying to get the phone to work again and update normally through the phone.
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.