Hi:
I did root my phone, and I installed ClockwordMOD following the steps in this website:
pof [dot] eslack [dot] org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
This I did from 1.0.0B02 version can be downloaded from ZTE page. Later, I installed another ROM I downloaded from ZTE page, in this case, a ROM TME Spain.
With this version I started to have problems, so I tried to return to the previous version using the Recovery and could not. I was wrong.
Nor could re-root the phone, so I could not install CWM.
Fastboot not working, because when I was trying to make something out this error:
fastboot flash recovery recovery-clockwork-6.0.3.3-
roamer2.img
sending 'recovery' (5712 KB) ...
OKAY [0.487s]
writing 'recovery' ...
FAILED (status read failed (No such device))
finished. Total time: 5.824s
Unable to use fastboot or ADB, I had only the option of using the update.zip offering this site:
firefox [dot] ztems [dot] com
After updating correctly, restarting the phone everything seemed normal, but not passed the animated fox, and restarted again.
With version 1.1 installed FirefoxOS, the phone started to have problems.
Sometimes when unblocked the screen to put the code, pressing the numbers and did not write anything. I had to repeatedly press the power button for it to work.
The same was true at times when trying to access the applications. The touch did not work well at all or sometimes it was deemed.
Now when I try to update using any ROM from Recovery (which incidentally now says Android Recovery), I get the error:
E: failed to Verify whole-file signature
:crying:
elav said:
Hi:
E: failed to Verify whole-file signature
:crying:
Click to expand...
Click to collapse
Apply this update from your stock(android) recovery. It'll work!
update_signed.zip
LinuxHolic said:
Apply this update from your stock(android) recovery. It'll work!
Click to expand...
Click to collapse
Thanks. I try!!
Personally I couldn't careless about stage freight but rather in the bug fixes and enhancements mentioned.
Alsi, will Motorola update the OS as 5.1 + stage freight vs 5.1 alone like they did with jellybean + camera update vs jellybean
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
A proper changelog?
Can someone create a flashable zip? I can grab the ota if needed from my XT1053.
I think I've made one myself but it's been so long I'm leary.
---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------
ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
Easiest way is to backup data via custom recovery, offload it to your pc. Flash stock using stock script, wiping it clean. Once fully up to date, custom recovery, copy backup and restore it.
USB mode in TWRP makes this relatively painless. Even if encrypted it works perfectly.
ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
are u getting ""/system/app/3c_main.apk" has unexpected contents."?
ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
Same thing here. It just fails with no error message.
zyldragoon said:
are u getting ""/system/app/3c_main.apk" has unexpected contents."?
Click to expand...
Click to collapse
Yes, I see this in the error log. After it first failed I unrooted and reflashed a stock factory L-5.1-LPA23.12-15 (Retail) LMR1, just to be absolutely sure I was stock.
I tried to get the OTA again and it failed again.
Here's the relevant bit from last_error_log:
Finding update package...
I:Update location: /cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4Verifying current system...
file "/system/app/3c_main/3c_main.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
file size of "/system/app/3c_main/3c_main.apk" is 9638
sha1 of "/system/app/3c_main/3c_main.apk" is 5c1d9df1c32e8cc2f0750aec478941e5d7abe817
expected sha1 is: f9aafd2ebf8aa92804c45206f81e2b3b0904d209
cb28a4acc187de6c016ca7ba4ff9b7a5518520a2
1022009344 bytes free on /cache (9638 needed)
dumping bad file /system/app/3c_main/3c_main.apk to /cache/recovery/last_badfile
script aborted: "/system/app/3c_main/3c_main.apk" has unexpected contents.
"/system/app/3c_main/3c_main.apk" has unexpected contents.
E:Error in /cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Also, TWRP shows the following error:
Package expects build fingerprint of motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15.5/4:user/release-keys; this device has motorola/ghost_retail/ghost:4.4/13.11.1Q2.X-69-3/51:user/release-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip'
E:Error installing zip file '/cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip'
Click to expand...
Click to collapse
It's surprising to me that my device would have 4.4 release keys. WTF?
I've attached a couple of log files (one from the installer, one from TWRP) if anyone wants to poke around.
The other thing I noticed was that TWRP leaves the OTA zipfile in /cache, which causes the device to reboot and re-attempt the update automatically ad infinitum. So I used TWRP's file manager to move the zipfile out of /cache (and into /sdcard/Downloads so I could snag it).
vtluu said:
Yes, I see this in the error log. After it first failed I unrooted and reflashed a stock factory L-5.1-LPA23.12-15 (Retail) LMR1, just to be absolutely sure I was stock.
I tried to get the OTA again and it failed again.
Here's the relevant bit from last_error_log:
Also, TWRP shows the following error:
It's surprising to me that my device would have 4.4 release keys. WTF?
I've attached a couple of log files (one from the installer, one from TWRP) if anyone wants to poke around.
Click to expand...
Click to collapse
It seems that the sha1 in the ota does not match the sha1 in stock factory L-5.1-LPA23.12-15 (Retail) LMR1, i saw the same problem in moto's forum.
some people think that is because of unlocked bootloader, but when u try to relock your boot loader, but, it seems the Lollipop images on the factory restore page are even signed correctly, so we cannot even relock the bl now.
so i think we have to wait moto to give us another version of OTA file
This is the OTA file: https://mega.nz/#!NcsDQISa!Q1KWQJpRE-iey897T8JdiVNlNscscS4WXOvsxAratIY
i tried use system update, update from sd card, update from ads
no one works
the sha1 in update-script does not match
vtluu said:
The other thing I noticed was that TWRP leaves the OTA zipfile in /cache, which causes the device to reboot and re-attempt the update automatically ad infinitum. So I used TWRP's file manager to move the zipfile out of /cache (and into /sdcard/Downloads so I could snag it).
Click to expand...
Click to collapse
Um, usually you need STOCK recovery to flash an OTA. TWRP doesn't work.
KidJoe said:
Um, usually you need STOCK recovery to flash an OTA. TWRP doesn't work.
Click to expand...
Click to collapse
I did try the stock recovery first (I reflashed every factory partition image including recovery), and that didn't work.
I only installed TWRP after the stock recovery failed so I could get more information about how the update was failing. (And also so I could reinstall SuperSU.)
TWRP has worked for me with previous OTAs I think. I mean from the looks of it, it's opening and executing the update script like the stock recovery would; why would it necessarily not work (other than possible compatibility issues)?
The ota file is bad, it needs to be fixed.
Glad I'm not the only one with this same issue
The solution to apply the OTA is to use a firmware from here as well as to either use RSD lite or the following commands to flash it:
Code:
./mfastboot erase cache
./mfastboot erase userdata
./mfastboot flash partition gpt.bin
./mfastboot flash motoboot motoboot.img
./mfastboot flash logo logo.bin
./mfastboot flash boot boot.img
./mfastboot flash recovery recovery.img
./mfastboot flash system system.img
./mfastboot flash modem NON-HLOS.bin
./mfastboot erase modemst1
./mfastboot erase modemst2
./mfastboot flash fsg fsg.mbn
./mfastboot erase customize
./mfastboot erase clogo
./mfastboot oem fb_mode_clear
It was working for me on a XT1053 DE.
---------- Post added at 08:03 AM ---------- Previous post was at 07:55 AM ----------
Benoe said:
The solution to apply the OTA is to use a firmware from here as well as to either use RSD lite or the following commands to flash it:
Code:
./mfastboot erase cache
./mfastboot erase userdata
./mfastboot flash partition gpt.bin
./mfastboot flash motoboot motoboot.img
./mfastboot flash logo logo.bin
./mfastboot flash boot boot.img
./mfastboot flash recovery recovery.img
./mfastboot flash system system.img
./mfastboot flash modem NON-HLOS.bin
./mfastboot erase modemst1
./mfastboot erase modemst2
./mfastboot flash fsg fsg.mbn
./mfastboot erase customize
./mfastboot erase clogo
./mfastboot oem fb_mode_clear
It was working for me on a XT1053 DE.
Click to expand...
Click to collapse
I've downloaded the official firmware from Motorola and the update it's not working. What's the difference between this files? I mean the Motorola official firmware and the one you have shared?
What I have seen from this thread, Motorola stock firmware already users those steps when flashing. http://forum.xda-developers.com/showpost.php?p=55516176&postcount=8
Will that make a difference if reflashing stock firmware and using your flash instructions than official stock flash instructions?
Luescoff said:
---------- Post added at 08:03 AM ---------- Previous post was at 07:55 AM ----------
I've downloaded the official firmware from Motorola and the update it's not working. What's the difference between this files? I mean the Motorola official firmware and the one you have shared?
What I have seen from this thread, Motorola stock firmware already users those steps when flashing. http://forum.xda-developers.com/showpost.php?p=55516176&postcount=8
Will that make a difference if reflashing stock firmware and using your flash instructions than official stock flash instructions?
Click to expand...
Click to collapse
The method is not working with stock firmware directly from motorola, I tried that. The phone gets stock, but the ota upgrade fails.
I suppose the other firmware is also original, that's why the OTA works with it. I don't know why there is any difference, why there are more 5.1 firmwares
Yeah, I brought my XT1053 back to stock 5.1 using the Motorola official firmware download (TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz) from their site, but the OTA update for Stagefright still fails. It's odd, because flashing to stock worked for all the prior OTAs; something seems to be different about this one that's causing it to fail even on a phone that's been rolled back to stock in some circumstances.
Is the 5.1 firmware from Motorola firmware center link from above actually different in some significant way such that it would allow the OTA update to succeed where it fails with the "official" download?
EDIT: I just downloaded the firmware from the link above, and all of the components have different file hashes than the official firmware does, so it isn't just a repackaged version of the main firmware. Given all the issues surrounding the gpt/motoboot files, I don't know if it's particularly safe to flash the files from that motofirmware.center link or not.
EDIT 2: Flashed the motofirmware.center firmware (GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip) and re-ran the OTA update; everything went smoothly. It looks like there's some sort of issue with the "official" firmware from Moto's site.
I took it. I am unrooted. Boot unlocked .
Strangest thing is that after the app optimization which took around 15 min, the phone is faster and cooler. And get this, I do NOT see cell stand by drain in the battery stats. Will give it a couple of cycles and confirm back.
Didn't get Ota...While flashing through recovery...
E3002: Package expects build thumbprint of 7.0/NPJ25.93-11/1: user/release-keys or 6.0.1/MPJ24.139-63/64: user/release-keys; this device has 6.0.1/MPJ24.139-64/65: user/release-keys.
E: unknown command [log]
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Sideloaded Nougat first soak...Unlckd bootloader...flashed stock Mm via Adb...tried to relock bootloader via bootloader command...failed...
Koustavsarkar85 said:
Didn't get Ota...While flashing through recovery...
E3002: Package expects build thumbprint of 7.0/NPJ25.93-11/1: user/release-keys or 6.0.1/MPJ24.139-63/64: user/release-keys; this device has 6.0.1/MPJ24.139-64/65: user/release-keys.
E: unknown command [log]
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Sideloaded Nougat first soak...Unlckd bootloader...flashed stock Mm via Adb...tried to relock bootloader via bootloader command...failed...
Click to expand...
Click to collapse
Please search first as it has already been answered.
You flashed MM but it was the wrong one. Flash the one ending in 63 and try again. It'll work then
Flash correct one for your device
It was a 63 one...
Device and stock image file name please. Also some screenshots of he device options if possible
Also maybe try downgrading to a lower firmware and taking an OTA maybe
Hi everybody,
I have a problem with my phone Leeco Le Pro 3 X720.
My bootloader is unlocked, fastboot works, I have TWRP 3.2.1-0 (and tried different ones as well). Previously I had already installed tons of different custom roms. Last one was an update of AICP 13, it failed somwhow and it was in stuck in a bootloop. So, I wiped everything and tried to reinstall the custom ROM, but it is not working anymore, result is:
Code:
Compiled: Thu May 3 06:18:31 CEST 2018
Compiled: Thu May 3 06:18:31 CEST 2018 Device: le_zl1
Patching system image unconditionally...
performing update
Patching system image unconditionally...blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524/
254103552 bytes free on /cache (0 needed)
erasing 649540 blocks
writing 1024 blocks of new data
[...]
[INDENT][U][B] writing 1024 blocks of new data
Decompression failed with TRANSFORM
missing 1022790 bytes of new data
failed to execute command [new 2,60160,61184]
script aborted: E1001: Failed to update system image.[/B][/U][/INDENT]
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 6 second(s).
Error installing zip file '/sdcard/Download/aicp_zl1_o-13.1-WEEKLY-20180503213.zip'
Updating partition details...
I:Data backup size is 0MB, free: 23722MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'auto'
...done
It seems like the update process fails due to some problems with the file system. Same happens with sideload. BUT I can install EUI 5.9 via fastboot and it works fine.
e2fsck sometimes says that Inode 419 has bad axtended attribute block 196606, and that there are problems with the suberblock on /system. After I fixed it, there are no problems but still fails to install. Format data in fastboot results in (in twrp it works):
Code:
>fastboot format /data
Formatting is not supported for file system with type ''.
There are also problems with transferring the zip fails via MTP, the devices supposedly is disconnected, sometime it works, othertimes it fails...
What is wrong with my phone? Please help me
Thank you!
You should search before posting hint firmware their are threads on this
Sent from my SM-A730F using xda premium
I am currently on EUI 5.9 with 26s (LE_ZL1_LEX720-CN-FN-WAXCNFN5902607031S-5.9.026S-FASTBOOT.zip with AIO Tool) with stock recovery. So should I flash TWRP and then 20s (firmware-20S-X720-le_zl1.zip, 46MB)? Failed
Or should I flash LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip and then TWRP + Custom Rom? Failed
Nothing worked :/
Decompression failed with BLOCK_LENGTH_2
missing 2832296 bytes of new data
failed to execute command [new 2,62208,63232]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
Fixed
HELP
leeco1235 said:
I am currently on EUI 5.9 with 26s (LE_ZL1_LEX720-CN-FN-WAXCNFN5902607031S-5.9.026S-FASTBOOT.zip with AIO Tool) with stock recovery. So should I flash TWRP and then 20s (firmware-20S-X720-le_zl1.zip, 46MB)? Failed
Or should I flash LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip and then TWRP + Custom Rom? Failed
Nothing worked :/
Fixed
Click to expand...
Click to collapse
I am having the exact same issue as you, I always get error code 7. I was able to install eui but now eui installs but wont boot past the boot animation. What should I do???
---------- Post added at 04:02 PM ---------- Previous post was at 04:01 PM ----------
Please Help I am having the same issue, how did you fix your issue?
millkyway4 said:
I am having the exact same issue as you, I always get error code 7. I was able to install eui but now eui installs but wont boot past the boot animation. What should I do???
---------- Post added at 04:02 PM ---------- Previous post was at 04:01 PM ----------
Please Help I am having the same issue, how did you fix your issue?
Click to expand...
Click to collapse
I fixed it by installing the TWRP image from this thread: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
Afterwards I was able to flash any custom rom.
Good Luck!
I am getting always the same error:
E1001: Failed to update system image.
Updater process ended with ERROR: 1
I wiped and formatted every partition, installed the most recent firmware.
I would appreciate any suggestion or advise. Thanks.
Then begin from new. First the right miui version with mi flashtool( don't look your bootloader) and then step by step