Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx
Lewerosky said:
Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx
Click to expand...
Click to collapse
i never got the updat notification so i manuelly flash the bootloader and everything to be honest if you want i can upload the folder with litterally everything you need including my homemade batch file to do all the work for you haha
hello
can you provide the update file zip?
Lewerosky said:
Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx
Click to expand...
Click to collapse
Motorola XT1929-6 Your Phone Has loaded Diferent operating system. Help!
The phone was purchased at AT & T Mexico. When you start, your phone has been loaded with another system. please help. Software 9.0. ATTMX carrier
Model XT1929-6. Single sim, 64GB Storage 4GB Ram
Related
I have a prejudice google nexus original one I tried vodafone EPF30
since the OTA update did not come to the nexus is one of Frøya
by check in the code or through manual update, but there was
nothing to do the upgrade in both cases is not aborted
I understand why.
through check-in download the update occurs smoothly,
but when it goes to install the toolbar update stops in the middle '
appears and the android with the triangle and exclamation point and then nothing
more.
however, if you carry some manual dell'update the error
shows:
E: cant't open / cache / recovery / command
verifyng current system
Assert failed: apply_patch_check ......
E: Error in / SDCard / update.zip (status 7)
Installation aborted
PLEASE HELP ME I DO NOT KNOW HOW TO DO!
fluck74 said:
I have a prejudice google nexus original one I tried vodafone EPF30
since the OTA update did not come to the nexus is one of Frøya
by check in the code or through manual update, but there was
nothing to do the upgrade in both cases is not aborted
I understand why.
through check-in download the update occurs smoothly,
but when it goes to install the toolbar update stops in the middle '
appears and the android with the triangle and exclamation point and then nothing
more.
however, if you carry some manual dell'update the error
shows:
E: cant't open / cache / recovery / command
verifyng current system
Assert failed: apply_patch_check ......
E: Error in / SDCard / update.zip (status 7)
Installation aborted
PLEASE HELP ME I DO NOT KNOW HOW TO DO!
Click to expand...
Click to collapse
anyone can help me????
thanks
Fluck74
Hello,
I am having a hard time getting SuperSu 2.46 installed. When I first install it, a dialog says "The SU binary needs to be updated. Continue?" I press Continue and choose the "Normal" mode. It fails. If I retry and select the TWRP/CWM mode, it will eventually fail with the error:
E: failed to verify whole-file signature
E: signature verification failed
I've attached as much info as I could from this article:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
Model: RK3188 (China)
Android Version: 4.4.4
Kernel: 3.0.36+
Build: rk3188-eng 4.4.4 KTU84Q
After booting to TRWP mode, last_log is empty.
There was not a /tmp/recovery.log either.
I have the install log and also the list of various su commands but I do not see an area to upload files here.
Having same problem over here, its recomended that you download the supersu version you want into a zip file, then flash the zip into the system
Sent from my SCH-I545 using Tapatalk
Hi,
Here a brief of my phone
ZTE Blade Q Lux
Android 5.0.2
MSM8916
Installed exposed
Try to flash sdk21, all version but encounter error failed to update, file corrupted
Then I tried copy manually to root/system and root/meta-inf
Xposed detected SDK v80 installed but not activated
Checked the log but log error
What should I do? Please assist me
Thanks
Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted
Lex-ON said:
Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted
Click to expand...
Click to collapse
Use a recovery that allows disabling signature verification, for example TWRP.
TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks
Lex-ON said:
TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks
Click to expand...
Click to collapse
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"
orville87 said:
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"
Click to expand...
Click to collapse
Checked it. the stock ROM I downloaded from ZTE.com does not contain *.bin files. is it able to use adb flash? I was unable to do so
attached the file contents
As the title says, I am having trouble booting into 5.1.2 I try to adb sideload the bin file (update-kindle-20.5.4.2_user_542168620) and it gets stuck verifying update package. Then after I get the following error ( E: Could not verify whole-file signature ) and then it goes back to the recovery menu, Is there a fix around this?
dznSpencer said:
As the title says, I am having trouble booting into 5.1.2 I try to adb sideload the bin file (update-kindle-20.5.4.2_user_542168620) and it gets stuck verifying update package. Then after I get the following error ( E: Could not verify whole-file signature ) and then it goes back to the recovery menu, Is there a fix around this?
Click to expand...
Click to collapse
Sounds like the 5.1.2 package may be corrupt. Try downloading it again.
Hello,
I'm struggling with my s10, SM-G973F, i was rooted and twrp etc, then i decided that i want the q beta, went to ASII signup for the members ap to get the beta and tried 3 way's to run the update by SD card - could not mount the sd card and adb way and this failed, and offcourse i tryed trough the phone Software update but this had failed as well, can anyone give me a hint hot get this done.
When i'm on ASII if i try by card i get:
Reboot recover Cause is [BL: Recovery Mode is set by key)#
Support SINGLE-SKU
#Manual Mode v1.0.0#
E: Failed to mount /sdcard: no such file or directory
-- Couldn't mount sdcard.
Installation Aborted
When i do it trough adb is say it successful but i get every time on botloop , and i have downloaded the update from different sources.
Updated firmware to BTU: ASJD trough smart switch and then followed the the steps and downloaded the update ZSK3 (it showed directly beta 3) trough the software update from settings, after all done i end up in bootloop again.
Can anyone help with this, i spent my Saturday on this silly thing.
Many Thanks
Did you relocked the bootloader?