[Q] xnph22r OTA update fail - ONE Q&A, Help & Troubleshooting

Hi! I have a oneplus one 64Gb. When i go on parameters /update system, my phone found and update xnph22r
i tried to install it but it always fail with an error message : E: failed to verify whole-file signature
I have to press chinese caracters and it reboot to previous mode
I'am new to android and i don't know what to do. Is there something i can do to fix this ? thanks
Sorry for my bad english

Solved
I succed to install xnph22r ota uptade on my phone.I downloaded manually ota updtate from here
I put the zip file on my phone memory and restart in recovery mode.
i have cwm6.0.4.8 but it's chinese version.. so i search in chinese language a "zip" name and after done i resarch my ota zip file and installed it .
Now it's fine
Hard to explain in english sorry

Related

[Q] Unable to install OTA updates in unrooted Shield tablet with original recovery

So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?

[Q] Update issue please help.

My oneplus is currently working on android 5.0.2 with cyanogen version
"CM-12.0 YNG1TAS17L" and recently i got a notification form software update that and update to "CM-12.0 YNG1TATAS213"when i clicked at that notification, it dint update and instead it restarted into recovery mode and i found the update file and clicked on it but it gives an error "error executing updater binary " . Please help
Use search.
http://forum.xda-developers.com/showthread.php?t=3150122
kaushik boggarapu said:
My oneplus is currently working on android 5.0.2 with cyanogen version
"CM-12.0 YNG1TAS17L" and recently i got a notification form software update that and update to "CM-12.0 YNG1TATAS213"when i clicked at that notification, it dint update and instead it restarted into recovery mode and i found the update file and clicked on it but it gives an error "error executing updater binary " . Please help
Click to expand...
Click to collapse
Download the full version and flash it manually thru any custom recovery.

OTA failed with BootLoader locked/Stock Recovery !?

Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
.
Hey man,
Just wanted to let you know: I have the EXACT same problem. Huawei AM7, KingRoot, OTA xxxB145 fail. I cannot further help, as I have no solution myself.
Hope someone can help.
Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.
Milly7 said:
Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.
Click to expand...
Click to collapse
Did a factory reset, still software update fail. Then tried to install stock rom over the stock rom, but software update still fails...
Did you try local update from internal or external SD card?
Yes, tried that, but same 'software update fail' problem...
Are you sure that you are flashing the correct file for your specific variant? You cannot flash TL10 on L09, etc. It will give the error if you do that.
I found the problem:
1) When installing an OTA there is a check on the file system first and if it fails, the update is aborted
2) KingUser/KingRoot leaves the file system in a dirty state (there is a kinguser.apk left in /system/app) so the check fails
3) to install a clean OTA you need to have a clean recovery so you need to:
3.1) unlock the bootloader (to be able to install a stock recovery)
3.2) download the update (e.g. ...B145) you want to install
3.3) use the Huawei extractor to get the recovery.img file from the package
3.4) flash the stock recovery
3.5) upgrate with the OTA
I discovered it step by step. Basically you need to unlock the bootloader to fix things and therefore it is a waste of time to user KingRoot/KingUser in the first place: but faster/cleaner to unlock the bootloader and install SuperSU.
Anubis
Still doesn't work I had the same but also had twrp recovery, I have my unlock code but no matter what adb I use I get remote command not allowed for trying to get stock recovery back or parse file failed with unlock code.
Any ideas would be much appreciated.
Anubis1965 said:
Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
Click to expand...
Click to collapse
u need to be unrooted to proceed ota. ..
Okay,
I have been trying over and over but there is no way I can perform an OTA. Here's the situation:
- The bootloader is unlocked
- Current Firmware: MT7-L09 ... B137SP03. According to the updater it should go with MT7-L09 ... B145
- OTA fails: on WiFi, local update (SD), forced (three buttons)
- In the systems/app folder I have this "KingUser.apk" app, has been left hanging there by KingRoot when I removed it
I was told to reinstall the stock recovery and try a local update, here's what I did:
1) I downloaded again the current FW (B137SP03) from here: http://www.huaweiblog.de/huawei/firmwareupdate-b137-fuer-mate-7-ota/
2) extracted update.app, opened with the Huawei Extractor, got recovery.img from update.app
3) rebooted the Mate 7 (vol down + power) in fastboot mode
4) flashed the stock recovery: fastboot flash recovery recovery.img, got an ok
5) rebooted
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis
Anubis1965 said:
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis
Click to expand...
Click to collapse
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...
tuddu said:
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...
Click to expand...
Click to collapse
Did you read what I wrote?
The OTA is called update.zip and you can perform an update by putting it into the dload folder of the SD card and then using the updater or with a forced update (three buttons boot).
The recovery file is called recovery.img and it is inside the archive update.app which is inside update.zip
Anubis
Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
That's it.
Anyway, peace and love.
tuddu said:
Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
...
.
Click to expand...
Click to collapse
No. I put the update.zip file in the dload folder of the SD card.
About removing KingRoot/KingUser after the self-removal option failed, I have only heard about installing SuperSu. Are you referring to it? Because that would imply to install a custom recovery, install supersu, clean-up, unroot via supersu, reinstall the stock recovery and then perform finally the OTA.
Paolo
:good:
oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis
Anubis1965 said:
oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis
Click to expand...
Click to collapse
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.
grofock said:
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.
Click to expand...
Click to collapse
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis
Anubis1965 said:
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis
Click to expand...
Click to collapse
You should do a clean install ( 3 buttons ) of the full B137 firmware, it was happening also with my phone and I solved the issue in that way.
After the flash you'll be on a clean stock B137 so you can put the "update.zip" in the "dload" folder ( it's an OTA update, not a full update.app firmware ) and be able to get the latest B145 :good:

Cant upgrade with official update

Dear All,
Please help me on this, i have root and unlocked my phone since last month, now i can't upgrade with official update. I download multi- tools [HONOR_6_and_6Plus_Multi-Tool ] from xda forum but i have no idea how to recover, someone can guide me step by step. Thank you.
P/S: when i try to upgrade to the latest official update B396, after download complete, the phone restart and show error "software install failed". when i load to fastloader the phone is show unlocked.
derrickgoi said:
Dear All,
Please help me on this, i have root and unlocked my phone since last month, now i can't upgrade with official update. I download multi- tools [HONOR_6_and_6Plus_Multi-Tool ] from xda forum but i have no idea how to recover, someone can guide me step by step. Thank you.
P/S: when i try to upgrade to the latest official update B396, after download complete, the phone restart and show error "software install failed". when i load to fastloader the phone is show unlocked.
Click to expand...
Click to collapse
Have you tried this ?
http://forum.xda-developers.com/showpost.php?p=57271268&postcount=6
Install a stock recovery, and after you can update. And after install your recovery and root it again.
It's work for me.
Send from Huawei Honor 6Plus PE-TL10
right now on which rom your device is running...
if custom..then please download stock full rom b390 zip file & extract it...find UPDATE.APP & put it in dload folder of your sd card..then power off phone...and start with all 3 buttons(vol+ , vol- & power)..automatically installing stock rom..then try to upgrade b396 ..if it is ota update..then put update.zip file in dload folder of your sd card...then open updater/local update/update.zip..& proceed.

Can not update at all

Hi,
I have MT7-L09 from Europe, I'm on B331, unlocked bootloader, rooted, with stock recovery and a lot of free space on both internal storage and SD card.
Today I received OTA update for B571. Downloading the file is okay, but when I reboot to install, it say that update failed because it failed to check the update files and asking me to download the package again. I tried again and again but I still got the same error message.
So I searched here for a solution, and I found that I should first install B560. I downloaded the full package and installed from local storage but once again the update failed. Then I tried to install the update package, but it failed too...
Now I just don't know what to do to upgrade to MM because update does not work at all !
Can anyone help ?
I have the same problem,but I'm on marshmallow L09C900B500
Okay, here's the solution I found myself.
I had to download full OTA B331 (which was the version that was already installed on my device), and then install it. Once done, just installed the update normally and it worked.
Now my device has Android 6.0 and EMUI 4.0 but I'm now looking for a root solution.

Categories

Resources